From content
This skill should be used when the user asks to "tighten this up", "tighten the prose", "clean up the writing", "check for AI tells", "make this sound more human", "de-slop this", "run a writing pass", or when completing a writing task that should not read like AI output. Scans prose for statistically overrepresented AI writing patterns and rewrites flagged sections.
How this skill is triggered — by the user, by Claude, or both
Slash command
/content:tighten-proseThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A final editing pass that catches and removes AI-detectable writing patterns. Not a detector — an editor. The output reads like a human wrote it because, after this pass, a human shaped every sentence.
A final editing pass that catches and removes AI-detectable writing patterns. Not a detector — an editor. The output reads like a human wrote it because, after this pass, a human shaped every sentence.
Read references/ai-tells.md for the full catalog of patterns, organized by category with examples and fix strategies.
AI writing tells evolve as models change. Fetch the current vocabulary list from Wikipedia:
https://en.wikipedia.org/w/api.php?action=parse&page=Wikipedia:Signs_of_AI_writing&prop=wikitext&format=json
Extract the "Words to watch" lists and AI vocabulary entries. Newer models drop old tells and develop new ones — the live source catches drift the static reference cannot.
If the fetch fails, the static reference is sufficient. Proceed without it.
Read the full text and scan across all categories:
| Category | Signal |
|---|---|
| Vocabulary clusters | 3+ AI-overused words in a section |
| Inflated significance | Phrases that inflate importance without adding information |
| Superficial -ing clauses | Participial phrases tacked on as fake depth |
| Promotional language | Travel-brochure / sales-deck vocabulary |
| Vague authority | Phantom expert attributions ("Industry reports suggest...") |
| Formulaic transitions | Five-paragraph-essay connectors (moreover, furthermore) |
| Negative parallelism | Overuse of "not X, it's Y" construction |
| Rule of three | Every list having exactly three items |
| Copula avoidance | "Serves as" instead of "is" |
| Elegant variation | Thesaurus cycling to avoid repeating a concrete noun |
| Em dash density | Em dashes at 2-3x human rate |
| Formatting tells | Mechanical boldface, title case headings, emoji decoration |
The signal is density, not individual hits. One "crucial" is fine. A cluster of three AI vocabulary words in two paragraphs is a rewrite.
Present a concise summary:
Do not list every individual word match. Report clusters and structural patterns.
For each flagged section, rewrite to eliminate tells while preserving meaning.
Fix strategies:
Constraints:
If only a few sections changed, present before/after pairs for the changed passages. If the whole piece needed work, present the full rewrite.
Do not explain every change. The writing should speak for itself. Mention only changes where the reasoning is non-obvious.
Designed to work standalone or as a step in other writing workflows.
Standalone: Point at text and say "tighten this up."
Composed: Another skill (like blog-post-writer) calls for a tighten pass as its final quality gate. When composed, respect any voice calibration the parent skill has already established. Tighten removes autopilot patterns, not personality.
references/ai-tells.md — Full catalog of AI writing tells with examples, fix strategies, and density guidance. Adapted from Wikipedia's "Signs of AI writing."npx claudepluginhub tinetti/claude-plugins --plugin contentCreates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.