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/context-guide.md
View on GitHub# Context guide
Load this guide when genre conventions affect an edit. The core preservation rules always apply.
## Technical documentation
Prefer observable behavior, exact interfaces, prerequisites, failure modes, and runnable instructions. Keep code, commands, identifiers, paths, protocol terms, and established concepts unchanged. Terms such as API surface, primitive, vector, passive, and eventually consistent may be precise rather than jargon.
Do not turn every paragraph into short imperative sentences. Explanations still need relationships and context. Preserve normative terms such as MUST, SHOULD, and MAY when they follow a specification.
## Academic and scientific prose
Preserve citations, qualifications, terminology, and the distinction between observation, inference, and hypothesis. Passive voice may be appropriate when the method or result matters more than the actor. Do not replace cautious language with certainty or insert a stronger causal claim.
Avoid invented sources and do not generalize beyond the evidence provided.
## Legal and regulated text
Treat contractual clauses, disclosures, policy language, and regulatory terminology as protected unless the user explicitly authorizes substantive editing. Plain-language improvements must not alter obligations, permissions, exceptions, defined terms, scope, or legal effect.
If an edit might change interpretation, explain the concern instead of silently rewriting it.
## Marketing and product copy
Promotional language is not automatically wrong in marketing. Remove unsupported superlatives and generic excitement, but preserve the intended persuasive function. Prefer specific capabilities, evidence, and customer-relevant outcomes over empty claims.
Do not create testimonials, adoption figures, comparisons, or guarantees.
## Casual and personal writing
Preserve contractions, fragments, humor, slang, and idiosyncratic punctuation when they belong to the author. Do not polish the text into corporate prose. First person is appropriate only when present in the source or explicitly requested.
## Correspondence
Courtesy is not the same as chatbot filler. Keep greetings, thanks, and invitations that serve the relationship. Remove canned praise and repeated offers that do not fit the exchange.
## Exact and quoted material
Do not rewrite direct quotations, titles, citations, transcripts, code samples, commands, identifiers, URLs, structured data, or text marked verbatim. Edit the surrounding prose instead. If quoted material appears inaccurate, flag it separately rather than changing the quote.
## Unclear genre
Infer conservatively from the text. Preserve the current level of formality and personality. If a major voice change would be required, ask the user rather than guessing.
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 |