editing-for-clarity-and-tone
Skill1 starsChanged 3 months agoMITView on GitHub
Use when revising existing prose for clarity, concision, structure, readability, or an explicitly requested tone while preserving the original meaning and factual content.
In this repository65 other files it gives its agents.
- analyzing-change-blast-radiusSkill
- analyzing-developer-career-opportunitiesSkill
- art-directing-web-interfacesSkill
- assessing-developer-proficiencySkill
- auditing-dependency-riskSkill
- auditing-pixel-perfect-frontendSkill
- bootstrapping-modern-web-appsSkill
- brag-slimSkill
- building-brand-guidelinesSkill
- building-conversion-product-pagesSkill
- building-developer-career-roadmapsSkill
- building-hybrid-game-assetsSkill
- building-premium-nextjs-interfacesSkill
- building-project-showcasesSkill
- building-regression-testsSkill
- building-reliable-node-api-boundariesSkill
- choosing-application-architectureSkill
- craft-premium-motionSkill
- creating-character-sprite-pipelinesSkill
- defining-brand-strategySkill
- designing-action-combatSkill
- designing-developer-portfolio-evidenceSkill
- designing-relational-data-modelsSkill
- designing-software-boundariesSkill
- designing-test-strategiesSkill
- designing-ui-systemsSkill
- designing-visual-identitiesSkill
- documenting-architecture-decisionsSkill
- engineering-gsap-animationsSkill
- evaluating-developer-proficiencySkill
- evolving-postgres-schemas-safelySkill
- humanizing-generated-proseSkill
- implementing-reference-faithful-uiSkill
- investigating-codebase-semanticallySkill
- managing-implementation-slicesSkill
- mapping-existing-codebase-structureSkill
- naming-brands-and-productsSkill
- optimizing-frontend-motion-performanceSkill
- orchestrating-cinematic-web-motionSkill
- planning-codebase-changes-with-evidenceSkill
- planning-engineering-workSkill
- planning-launch-distributionSkill
- planning-safe-refactorsSkill
- planning-written-communicationSkill
- preparing-project-launchSkill
- profiling-postgres-query-performanceSkill
- reconstructing-images-as-threejsSkill
- reviewing-api-securitySkill
- reviewing-apple-platform-interfacesSkill
- reviewing-pull-requestsSkill
- reviewing-web-securitySkill
- selecting-working-methodsSkill
- shipping-github-vercel-changesSkill
- teaching-developer-conceptsSkill
- testing-integration-boundariesSkill
- testing-playable-gamesSkill
- testing-web-applications-end-to-endSkill
- threat-modeling-applicationsSkill
- tracing-code-execution-pathsSkill
- translating-figma-to-nextjsSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
If the user asks for fact-checking, research, or substantive expansion, treat that as a separate task.
- Distinctive: line 27
Structure: put the reader's needed context before dependent detail.
- Distinctive: line 28
Sentences: prefer direct subjects and verbs, remove filler, reduce nested qualifiers, and keep necessary nuance.
- Distinctive: line 36
Prefer the smallest change that achieves the requested improvement.
- Distinctive: line 38
Do not normalize every paragraph into the same cadence, add generic transitions, or make a personal draft sound like corporate copy unless …
- Very specific: line 42
Use humanizing-generated-prose when the explicit problem is generic or AI-shaped writing and the revision needs pattern-level …
- Distinctive: line 46
When the user asks for a rewrite, return the complete revised text.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Editing for Clarity and Tone
Overview
Improve an existing draft without silently changing what it says. The governing contract is fidelity first, then clarity, structure, density, and tone.
Establish the Editing Contract
Identify:
- the exact text in scope;
- audience and genre when known;
- requested tone, formality, length, or house style;
- facts and claims that must remain unchanged;
- protected spans: quotations, citations, URLs, code, identifiers, names, dates, numbers, legal wording, headings, or user-marked text.
If the user asks for fact-checking, research, or substantive expansion, treat that as a separate task. Do not disguise new claims as editing.
Edit in Passes
- Meaning: resolve only ambiguities that can be fixed without guessing. Flag uncertainty rather than inventing intent.
- Structure: put the reader's needed context before dependent detail; merge repetition and split overloaded paragraphs when useful.
- Sentences: prefer direct subjects and verbs, remove filler, reduce nested qualifiers, and keep necessary nuance.
- Terminology: make repeated concepts consistent without replacing precise domain language with generic synonyms.
- Tone: adjust distance, warmth, formality, confidence, and rhythm to the requested situation. Tone must not change the certainty of factual claims.
- Length: cut redundancy before cutting evidence, conditions, exceptions, or action-critical detail.
- Fidelity check: compare the revision against the source for changed numbers, names, claims, citations, scope, obligations, and conclusions.
Minimum-Effective-Edit Rule
Prefer the smallest change that achieves the requested improvement. Distinctive phrasing is not a defect simply because another sentence would sound smoother.
Do not normalize every paragraph into the same cadence, add generic transitions, or make a personal draft sound like corporate copy unless that is the explicit target.
Boundary With Humanization
Use humanizing-generated-prose when the explicit problem is generic or AI-shaped writing and the revision needs pattern-level naturalization while preserving protected content. Use this method for broader editorial work where clarity, tone, structure, or concision is the primary goal.
Deliverable
When the user asks for a rewrite, return the complete revised text. Add explanation only when requested or when a material ambiguity, protected conflict, or substantive change needs disclosure.
Reference Signals
GDS/ONS plain-language guidance supports user-focused structure, concise sentences, task-centered headings, and common language. Microsoft and Google style guidance reinforce direct, helpful, accessible prose and consistency for global audiences.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

