Skills de-slopify
📦

de-slopify

Content revision r1 Safe ⚙️ External commands

Polish AI-Written Documentation

AI-assisted documentation can sound formulaic and distract readers. This skill guides manual edits that remove common LLM writing tells while preserving meaning.

Supports: Claude Codex Code(CC)
🥉 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "de-slopify" from https://skillstore.io/skills/dicklesworthstone-de-slopify.md and its manifest at https://skillstore.io/api/skills/dicklesworthstone-de-slopify/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/dicklesworthstone-de-slopify.md Signed manifest GET /api/skills/dicklesworthstone-de-slopify/manifest Signed lockfile GET /api/skills/dicklesworthstone-de-slopify/lockfile

Test it

Using "de-slopify". This tool is not just a linter, it is a complete quality platform. Here is why it matters: teams move fast.

Expected outcome:

This tool is a quality platform that goes beyond linting. It helps teams move faster without losing review discipline.

Using "de-slopify". Let us dive in! This guide, which we built carefully, walks you through every step.

Expected outcome:

This guide walks through each setup step in order.

Using "de-slopify". It is worth noting that the API is powerful and easy to use.

Expected outcome:

The API is powerful and easy to use.

Security Audit

Safe
v8 • 7/6/2026 Open versioned report

All static findings are false positives caused by Markdown fences, inline code formatting, prose rewrite examples, and fixed workflow examples in SKILL.md. No evidence found for command execution intent, data exfiltration, network access, filesystem abuse, or prompt injection.

1
Files scanned
223
Lines analyzed
0
Review items
0
False positives ignored

Risk Factors

⚙️ External commands (31)
SKILL.md:35-41 SKILL.md:41-65 SKILL.md:65 SKILL.md:66 SKILL.md:67 SKILL.md:68 SKILL.md:107-109 SKILL.md:109-112 SKILL.md:112-114 SKILL.md:114-119 SKILL.md:119-121 SKILL.md:121-124 SKILL.md:124-126 SKILL.md:126-131 SKILL.md:131-133 SKILL.md:133-136 SKILL.md:136-138 SKILL.md:138-141 SKILL.md:141-143 SKILL.md:143-148 SKILL.md:148-152 SKILL.md:152-155 SKILL.md:155-159 SKILL.md:159-184 SKILL.md:184-187 SKILL.md:187-191 SKILL.md:191-193 SKILL.md:193-211 SKILL.md:211-217 SKILL.md:217-220 SKILL.md:220-222
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/dicklesworthstone-de-slopify/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/dicklesworthstone-de-slopify/security.svg)](https://skillstore.io/skills/dicklesworthstone-de-slopify?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/dicklesworthstone-de-slopify?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/dicklesworthstone-de-slopify/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/dicklesworthstone-de-slopify.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

Dicklesworthstone. (2026). de-slopify security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/dicklesworthstone-de-slopify/audits/8

BibTeX citation

@techreport{dicklesworthstone-dicklesworthstone-de-slopify-2026, author = {Dicklesworthstone}, title = {de-slopify security audit report (audit version 8)}, institution = {Skillstore}, year = {2026}, number = {8}, url = {https://skillstore.io/skills/dicklesworthstone-de-slopify/audits/8}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "de-slopify security audit report (audit version 8)" version: "unspecified" type: report authors: - name: "Dicklesworthstone" date-released: "2026-07-06" url: "https://skillstore.io/skills/dicklesworthstone-de-slopify/audits/8" identifiers: - type: other value: "skillstore:dicklesworthstone-de-slopify:audit:8" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
85
Content
71
Community
83
Spec Compliance

What You Can Build

Clean README Releases

Clean AI-assisted README text before publishing a project or release.

Review Documentation Tone

Revise API documentation, guides, and contribution pages for a more natural tone.

Refine AI Drafts

Turn generated draft text into concise product or engineering documentation.

Try These Prompts

Clean a README Section 
Review this README section. Remove AI-style patterns, reduce emdash use, and keep the original technical meaning.
Revise Release Documentation 
Edit this release note for a natural technical tone. Remove formulaic phrases and forced enthusiasm without changing facts.
Line-by-Line Style Pass 
Perform a line-by-line de-slopify review of this document. Explain major changes and preserve necessary technical structure.
Prepare Public Docs for Launch 
Review this full documentation draft before launch. Remove LLM writing tells, keep terminology consistent, and return a concise final version.

Best Practices

  • Review each sentence in context before changing punctuation.
  • Preserve technical accuracy before improving tone.
  • Compare before and after text for meaning, voice, and clarity.

Avoid

  • Do not replace every emdash mechanically.
  • Do not remove structure that helps readers scan technical docs.
  • Do not rewrite code examples, commands, or API names as prose cleanup.

Frequently Asked Questions

What does this skill do?
It helps remove common AI writing patterns from documentation and README text.
Does it run a formatter?
No. It provides manual review guidance, examples, and rewrite patterns.
Which files is it best for?
It is best for README files, API docs, contribution guides, blog posts, and public-facing text.
Can it review code?
It focuses on prose. Keep code, commands, and identifiers unchanged unless the user asks.
Will it remove every emdash?
No. It recommends keeping punctuation when it improves clarity or preserves the intended voice.
Is it safe to use with Claude Code and Codex?
Yes, but review changes before committing because style edits can alter tone or emphasis.

Developer Details

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Repository

https://github.com/Dicklesworthstone/agent_flywheel_clawdbot_skills_and_integrations/tree/main/skills/de-slopify

Ref

72d5025b022c77f7a51bdf5c1637c689c80e89d1

Maintenance freshness

7/18/2026

Usage

13 downloads · 280 views

File structure

📄 SKILL.md