drafael/coding-harness / skills/unslop
unslop
VerifiedEdit or review prose to remove formulaic AI-writing patterns while preserving facts, meaning, and the author's existing voice. Use for small style-only edits, articles, reports, messages, release notes, and other prose, or as the final pass after substantial technical writing. When technical-writing is available, use it first for substantial technical documentation and design artifacts. Do not use for code-only tasks or text that must remain verbatim.
| File | Kind | Size |
|---|---|---|
| LICENSE | other | 1.1 KB |
| README.md | markdown | 2.1 KB |
| SKILL.md | skill md | 5.8 KB |
| references/context-guide.md | markdown | 2.7 KB |
| references/examples.md | markdown | 3.8 KB |
| references/pattern-catalog.md | markdown | 7.2 KB |
references/pattern-catalog.md
View on GitHub# Pattern catalog
Use this catalog for full audits and ambiguous edits. A match is a prompt to inspect context, not an automatic violation.
## Content
### 1. Inflated importance
Watch for claims that an ordinary event is pivotal, enduring, symbolic, a testament, a turning point, or part of an evolving landscape. State what happened and why it matters in concrete terms. Keep significance language when the source supports it.
### 2. Context-free name-dropping
A list of publications, companies, or experts does not establish relevance. Keep the source that supports the claim and say what it reported. Preserve a list when the list itself matters.
### 3. Superficial `-ing` analysis
Clauses beginning with "highlighting," "ensuring," "reflecting," "showcasing," or "fostering" often append unsupported interpretation. Delete the clause or turn it into a sourced, testable statement.
### 4. Promotional language
Review words such as vibrant, breathtaking, groundbreaking, renowned, stunning, must-visit, nestled, rich, and commitment. Replace advertising copy with observable details unless promotion is the requested genre.
### 5. Vague attribution
"Experts believe," "industry reports suggest," and "some critics argue" conceal the source. Name a real source already provided, preserve justified uncertainty, ask for evidence, or remove the claim. Never invent attribution.
### 6. Formulaic challenges and outlook
"Despite these challenges, it continues to thrive" rarely tells the reader anything. Name the concrete problem, response, result, or plan.
## Language
### 7. Stock AI vocabulary
Review additionally, crucial, delve, enduring, enhance, foster, garner, highlight, interplay, intricate, landscape, pivotal, showcase, tapestry, testament, underscore, valuable, and vibrant. Keep any word that is the clearest accurate choice.
### 8. Fancy substitutes for `is` and `has`
"Serves as," "stands as," "boasts," "features," and "offers" often inflate a simple statement. Prefer `is` or `has` when no distinction is lost.
### 9. Forced negative parallelism
Replace "not just X, but Y" and "it is not merely X; it is Y" with the actual point. Keep the contrast when both sides are necessary and genuinely opposed.
### 10. Forced groups of three
Do not add or trim items merely to make a trio. Use the number the subject requires.
### 11. Synonym cycling
Repeatedly renaming the same thing can obscure identity. Choose the established term and repeat it when repetition is clearer.
### 12. False ranges
Use "from X to Y" only for endpoints on a meaningful progression or range. Otherwise list the topics directly.
## Style and formatting
### 13. Em-dash overuse
Repeated em dashes can create artificial punchiness. Use a period, comma, colon, parentheses, or revised sentence when that reads better. Keep an em dash when it expresses the intended interruption or emphasis.
### 14. Rhetorical colon overuse
Colons belong before explanations, examples, lists, and formally related clauses. Rewrite colons used as habitual dramatic connectors. Keep them where grammar or document structure calls for them.
### 15. Decorative boldface
Do not bold every acronym, product, or key phrase. Keep bold text used for navigation, warnings, accessibility, or an established document convention.
### 16. Inline-header lists
A list such as "**Performance:** Performance improved" repeats itself. Use prose or a useful label followed by new information. Keep scannable labeled lists when the labels carry structure.
### 17. Title-case headings
Use the document's established heading convention. Prefer sentence case only when no style guide says otherwise.
### 18. Decorative emojis
Remove emojis used as automatic heading or bullet ornaments. Preserve them when requested or meaningful to the author's voice, brand, or interface.
### 19. Quotation-mark normalization
Do not treat curly quotes as inherently artificial. Follow the document's locale and typography. Never alter quotation marks inside code or exact quoted material.
## Communication artifacts
### 20. Canned chatbot phrases
Remove "Of course," "Certainly," "I hope this helps," "let me know," and similar scaffolding when it adds no meaning. Keep courteous language appropriate to real correspondence.
### 21. Model disclaimers
Remove training-cutoff and "available information" disclaimers copied into finished prose. Replace them with a dated factual limitation only when the limitation matters and is supported.
### 22. Sycophancy
Cut automatic praise such as "Great question" or "You're absolutely right." Respond to the substance. Keep genuine acknowledgment when the conversational context calls for it.
## Filler
### 23. Wordy setup
Prefer "to" over "in order to," "because" over "due to the fact that," and "if" over "in the event that." Delete "it is important to note" when the sentence works without it.
### 24. Stacked hedging
Reduce "could potentially possibly" to the level of uncertainty the evidence supports. Do not remove legally, scientifically, or socially meaningful qualifications.
### 25. Generic conclusions
Replace "the future looks bright" and "exciting times lie ahead" with a concrete plan, result, unresolved question, or no conclusion.
## Jargon and plain speech
### 26. Empty technical metaphors
Review substrate, wedge, vector, locus, vantage, nexus, primitive, harness, surface, bedrock, scaffolding, modality, paradigm, gold-plating, ratchet, evacuate, endgame, north star, and flywheel when used metaphorically. Replace empty decoration with the mechanism's real name. Keep precise domain terms such as vector, language primitive, API surface, or interaction modality.
### 27. Feelings in place of mechanisms
"SQL you can read" and "the database stays close at hand" describe an impression. Prefer a behavior readers can verify, such as "`.toSQL()` returns the statement sent to the database." Preserve subjective language in reviews, essays, and other genres where experience is the subject.
### 28. Dense sentences
Split a sentence when readers must backtrack to understand its main clause. Do not enforce one idea per sentence when combining related ideas improves flow.
### 29. Unhelpful passive voice
Name the actor when responsibility or mechanism matters: "the compiler validates the query." Keep passive voice when the actor is unknown, irrelevant, deliberately backgrounded, or required by the genre.
### 30. Unsupported adverbs and intensifiers
Replace "significantly faster" with a measurement when one is available. Otherwise use the strongest accurate verb or retain the qualifier if it carries real meaning. Technical adverbs such as cryptographically or eventually may be essential.
### 31. Needlessly formal words
Prefer use over utilize, help over facilitate, and many over numerous when meaning stays intact. Keep formal or specialized language required by the audience or domain.
## Cross-cutting tests
For each proposed change, ask:
1. Is the passage actually unclear, unsupported, repetitive, or formulaic?
2. Would the edit preserve factual content and degree of certainty?
3. Does the replacement fit this author, genre, and audience?
4. Is the flagged wording precise or required in this context?
5. Does the edit remove a problem rather than exchange it for a different mannerism?
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |