
Rewrite
- 26 installs
- 87 repo stars
- Updated June 9, 2026
- owl-listener/inclusive-design-skills
Helps with ai & agent building tasks during AI-assisted development.
About
rewrite is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted coding.
- rewrite
- AI & Agent Building
- AI-coding skill
Rewrite by the numbers
- 26 all-time installs (skills.sh)
- +2 installs in the week ending Jul 18, 2026 (Skillselion tracking)
- Ranked #9,702 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 1, 2026 (Skillselion catalog sync)
npx skills add https://github.com/owl-listener/inclusive-design-skills --skill rewriteAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 26 |
|---|---|
| repo stars | ★ 87 |
| Last updated | June 9, 2026 |
| Repository | owl-listener/inclusive-design-skills ↗ |
What it does
Helps with ai & agent building tasks during AI-assisted development.
Files
Rewrite for Accessibility
Take existing content and rewrite it to be accessible to people with diverse cognitive abilities and literacy levels — without losing accuracy or meaning.
Process
Step 1: Assess Current Readability
Using readable-content, evaluate:
- Current reading level
- Sentence and paragraph length
- Jargon and specialist terms
- Content structure and scannability
Step 2: Identify the Core Message
For each section, answer: what is the one thing the reader must understand? Write that down in one plain sentence. This becomes the opening line of the rewritten section.
Step 3: Rewrite
- Replace jargon with plain alternatives
- Shorten sentences to 15–20 words
- One idea per sentence, one topic per paragraph
- Front-load each paragraph with the key point
- Use active voice throughout
- Address the reader as "you"
- Add examples to clarify abstract concepts
Step 4: Fix Links
Using link-text-design, rewrite any link text that doesn't make sense on its own. Replace "click here" and "read more" with descriptive link text.
Step 5: Present Before and After
Show the original alongside the rewrite with annotations explaining each change. Include the reading level of both versions.
Rules
- Never sacrifice accuracy for simplicity — if a term is essential,
keep it and define it
- Don't condescend — plain language is clear language, not childish
language
- Preserve the author's intent and tone where possible
- Flag any content where simplification might change the legal or
technical meaning — let the team decide those tradeoffs
Output
Deliver the rewritten content with:
- Reading level of original vs. rewrite
- Change log of significant edits with rationale
- Flagged passages where meaning may have shifted