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/examples.md
View on GitHub# Boundary-focused examples
These examples demonstrate editing constraints, not fixed wording. Never add facts that the source does not contain.
## Puffery without invention
**Before**
> The release marks a pivotal moment in our ongoing journey, underscoring our commitment to a seamless developer experience.
**After**
> The release adds automatic retry configuration and reports failed attempts in the build log.
Use this rewrite only when those features are present in the source context. Otherwise remove the puffery without supplying new features.
## Vague attribution
**Before**
> Industry experts believe the change will significantly improve adoption.
**After when no source is available**
> The team expects the change to improve adoption.
Use that version only if the source identifies the team as holding the expectation. Otherwise remove the sentence or ask for a source.
## Preserving uncertainty
**Before**
> The policy could potentially reduce processing delays.
**After**
> The policy may reduce processing delays.
Do not rewrite `may` as `will`.
## Protecting code and identifiers
**Before**
> Call `client.createSurface()` to create the API surface. The method returns `undefined` when the feature is disabled.
**After**
> Call `client.createSurface()` to create the API surface. The method returns `undefined` when the feature is disabled.
Here, `surface`, the identifier, and the return value are precise. No edit is needed.
## Contextual punctuation
**Before**
> The migration has one hard requirement: PostgreSQL 16 or later. Older versions are not supported.
**After**
> The migration has one hard requirement: PostgreSQL 16 or later. Older versions are not supported.
The colon introduces an explanation and should remain.
## Removing repetitive punctuation
**Before**
> The cache is fast—but only when warm—and it can hide stale reads—which makes debugging harder.
**After**
> The cache is fast when warm, but it can hide stale reads. That makes debugging harder.
The problem is repetition, not the existence of an em dash.
## Passive voice with and without a useful actor
**Before**
> Requests are validated before execution.
**After when the actor matters**
> The gateway validates requests before execution.
Keep the original when the actor is unknown or irrelevant.
## No invented first person
**Before**
> Some users find the unattended agent behavior concerning.
**Wrong**
> I find it unsettling to imagine agents working at 3 a.m.
**Better without a named source**
> Unattended agent execution concerns some users.
Do not create an opinion or experience for the author.
## Preserve exact quotations
**Before**
> The report describes the result as “a pivotal shift in the landscape.” The accompanying data shows a 4% change.
**After**
> The report describes the result as “a pivotal shift in the landscape.” The accompanying data shows a 4% change.
The stock language is inside a direct quotation. Critique it outside the quote if needed; do not rewrite it.
## Technical metaphor versus technical term
**Before, empty metaphor**
> The service provides a robust substrate that acts as a flywheel for innovation.
**After**
> The service stores shared configuration and distributes updates to workers.
Use the replacement only when the source establishes those mechanisms.
**Before, precise term**
> Reducing the public API surface limits the operations available to plugins.
**After**
> Reducing the public API surface limits the operations available to plugins.
`API surface` is precise here.
## Correspondence without chatbot scaffolding
**Before**
> Great question! Of course, here is the revised schedule. I hope this helps. Let me know if you need anything else.
**After**
> Here is the revised schedule.
Keep a greeting or closing when it serves the actual relationship rather than acting as automatic scaffolding.
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 |