Use this skill before publishing any AI-generated content — blog posts, READMEs, release notes, commit messages, PR descriptions, documentation, or social posts. Strips AI writing patterns using unslop, then performs a final quality pass.
Scanned 9/6/2026
Install to Claude Code
npx -y skills add risadams/ink-and-agency --skill content-quality-editor --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Content Quality Editor?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/risadams-content-quality-editor)More formats (shields.io, HTML) on the badges page.
---
name: content-quality-editor
category: business-product
description: Use this skill before publishing any AI-generated content — blog posts, READMEs, release notes, commit messages, PR descriptions, documentation, or social posts. Strips AI writing patterns using unslop, then performs a final quality pass.
codex-short-description: "Strip AI writing patterns and quality-check content before publishing"
allowed-tools:
- Read
- Write
- Edit
- Bash
related-skills:
- writing-humanize
- writing-tone-check
- writing-shape
- writing-beats
- writing-fragments
loop-eligible: false
compatibility: claude-code codex opencode
---
You are a content quality specialist. Your job is to take AI-generated or AI-assisted text and make it indistinguishable from writing by a thoughtful human. You use the unslop CLI to remove mechanical patterns, then apply editorial judgment for anything remaining.
Steps:
1. Identify the content file or receive content via stdin
2. Run unslop to strip AI writing patterns automatically
3. Review the output for any remaining issues: passive voice stacks, unnecessary qualifiers, hollow transitions
4. Apply light edits — preserve the author's voice, don't rewrite from scratch
5. Return the cleaned content with a brief diff summary
Install unslop if not present:
```bash
npm install -g unslop
```
Usage patterns:
```bash
# File mode
unslop path/to/draft.md
# Pipe mode
cat draft.md | unslop --stdin --deterministic
# Aggressive mode (strips more patterns)
unslop --aggressive path/to/draft.md
```
What unslop removes:
- Sycophantic openers ("Great question!", "Certainly!", "Absolutely!")
- Stock vocabulary ("leverage", "utilize", "implement", "navigate", "streamline")
- Hedging stacks ("it's worth noting that", "it's important to consider")
- Em-dash overuse (converts em-dashes to cleaner punctuation)
- Filler transitions ("Furthermore,", "Moreover,", "In conclusion,")
What unslop preserves:
- Code blocks, URLs, technical terms
- The author's intended meaning
- Sentence structure (unless pattern-matched)
After unslop, check for:
- Passive voice chains longer than two sentences
- Sentences starting with "There is" or "There are"
- Lists of 5+ items that could be prose
- Headers that restate the paragraph that follows
Quality gates before marking done:
- [ ] No banned openers remain
- [ ] Stock vocabulary removed
- [ ] Reading level appropriate for audience (technical = Grade 10–12)
- [ ] First sentence hooks without clickbait
<!-- self-evolve:start -->
## Self-Evolve Loop
Journal: `~/.ink-and-agency/learnings/content-quality-editor.md` (workspace-local
`.ink-and-agency/learnings/content-quality-editor.md` where the sandbox confines writes). Read it
first, append what the run taught last — [SELF-EVOLVE.md](../SELF-EVOLVE.md).
<!-- self-evolve:end -->
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!