edit-for-readability

Featured

Applies Han's shared Human-Readable Output Standard to a target you already have — a file on disk, text pasted into the prompt, or a draft already produced in the conversation — by dispatching the readability-editor to rewrite its prose so the main point comes first, headings are descriptive, each paragraph carries one idea, and sentences stay short and active, while preserving every fact. Use when you want to make a document or draft readable, edit or polish prose for readability, clean up writing, tighten wording, or re-apply the readability standard to something already written. Rewrites prose only, leaving code, diagrams, and citation identifiers unchanged. Does not write new feature or system documentation — use project-documentation. Does not restructure code or review it — use refactor to restructure code and code-review to audit it. Does not judge the underlying work or raise findings; it only rewrites the writing.

Code & Development 263 stars 23 forks Updated today MIT

Install

View on GitHub

Quality Score: 91/100

Stars 20%
81
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Edit for Readability Take a target the user already has and rewrite its prose against the shared readability standard, preserving every fact. The judgment-heavy rewrite belongs to the `han-core:readability-editor` agent; this skill's job is to resolve what the target is, dispatch the editor over it, and deliver the result. ## Operating principles - **This is the standalone readability pass.** The readability standard applies at generation time, so synthesis skills (research, project-documentation, investigate, code-review, and the rest) already bake it into their own output. This skill exists for the gap the standard names explicitly: a file or draft that was written or hand-edited *outside* one of those skills, and so was never checked against the standard. Reach for it on an existing target, not as a step inside another skill. - **Fidelity outranks readability on every conflict.** Every claim, quantity, named entity, and stated condition or qualifier in the target survives the rewrite with its precision intact. The editor enforces this and returns a fact-preservation ledger; the skill's job is to pass the whole target through and surface that ledger, never to let a fact be dropped for the sake of a smoother sentence. - **Prose only.** The editor rewrites prose regions and leaves code fences, diagram bodies, rendered markup, and citation identifiers (`A1`, `[F5]`, and the like) byte-for-byte unchanged. Do not ask it to touch anything else. - **The editor holds the stand...

Details

Author
testdouble
Repository
testdouble/han
Created
4 months ago
Last Updated
today
Language
Shell
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Featured

readability-guidance

Surfaces Han's shared Human-Readable Output Standard — the readability rule and the writing-voice profile — into the calling skill's own context, so the caller drafts in voice and runs its self-check against the current standard sourced from one canonical copy. Use when a prose-producing skill needs the shared readability standard available in context before it drafts. Governs the shape of a written deliverable, where explanation-guidance governs what a run says to a person in a turn. Runs in the caller's context and hands control straight back; it does not produce a deliverable of its own, rewrite anything, or judge the caller's work. Does not run the adversarial rewrite pass — dispatch the readability-editor agent for that, or use edit-for-readability to rewrite an existing target. Does not cover explaining technical work to a reader who will not implement it — use explanation-guidance for that.

263 Updated today
testdouble
Code & Development Listed

edit

Refine an existing draft to read as easily as its ideas allow — at the grade the content earns, never below the floor your audience expects, never inflated above it. Runs a diagnose→propose→refine→gate-check methodology: shells out to the deterministic readability_diag.py for the countable flags (does NOT recompute them), judges intrinsic-vs-extraneous load, proposes refine moves with a floor/ceiling check, and on --apply runs the gate it can't game (meaning-preservation held outside the rewriter). Read-only default; --apply refines + gates. Voice-neutral; composes with a defect/AI-pattern linter and a content-drafting skill. TRIGGER when: user says "edit this for readability", "make this read easier", "reduce reading effort", "tighten this prose", "readability pass", "refine for clarity". DO NOT TRIGGER when: user wants a defect / AI-pattern / brand check (use a linter); to draft net-new content (use a content-authoring approach); a named-recipient message; or a literal file edit (use the editor directly).

0 Updated 1 weeks ago
bamboo-DCM
AI & Automation Listed

readability

Check whether a draft is actually readable by locating where a reader falls off — weak paragraph junctions, back-references with no antecedent nearby, and terms used before they are explained — then dispatch a fresh-context second reader to catch contradictions and repetition that no script can see. Use this whenever the user asks whether something is readable, clear, hard to follow, confusing, well-structured or "does this flow"; whenever they ask for a readability check, a readability score, a Flesch or grade-level reading, or a second opinion on a draft; and as the last review pass before publishing a blog post, README, ADR, runbook or long technical explanation. Also trigger on "read this end to end", "does this make sense", "fresh eyes on this", "where does this lose people", "is this too dense", "second reader", "cohesion", "flow check". Reports locations and never a grade level — if the user explicitly wants a Flesch or Gunning Fog number, use this skill and explain why it is not computed. For AI textu

8 Updated 5 days ago
kevin-burns