UX Writing
content-designer/ux-writing-skill
Applies UX writing practice to interface copy such as buttons, errors, forms and onboarding, using four quality standards and accessibility guidance.
Write and structure content for diverse reading abilities and cognitive styles.
Install Readable Content
$ npx skills add Owl-Listener/inclusive-design-skills --skill readable-content -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills readable-content --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/accessible-content/skills/readable-content .claude/skills/readable-content && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "readable-content" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessible-content/skills/readable-content into .claude/skills/readable-content/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "readable-content", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessible-content/skills/readable-contentType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Owl-Listener/inclusive-design-skills --skill readable-content -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills readable-content --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/accessible-content/skills/readable-content .agents/skills/readable-content && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "readable-content" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessible-content/skills/readable-content into .agents/skills/readable-content/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "readable-content", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/inclusive-design-skills --skill readable-content -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills readable-content --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/accessible-content/skills/readable-content .cursor/skills/readable-content && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "readable-content" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessible-content/skills/readable-content into .cursor/skills/readable-content/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "readable-content", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Owl-Listener/inclusive-design-skills.git --path accessible-content/skills/readable-content--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Owl-Listener/inclusive-design-skills --skill readable-content -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills readable-content --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/accessible-content/skills/readable-content .gemini/skills/readable-content && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "readable-content" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessible-content/skills/readable-content into .gemini/skills/readable-content/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "readable-content", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Owl-Listener/inclusive-design-skills readable-contentInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Owl-Listener/inclusive-design-skills --skill readable-content -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/accessible-content/skills/readable-content .github/skills/readable-content && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "readable-content" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessible-content/skills/readable-content into .github/skills/readable-content/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "readable-content", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/inclusive-design-skills --skill readable-content -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills readable-content --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/accessible-content/skills/readable-content .opencode/skills/readable-content && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "readable-content" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessible-content/skills/readable-content into .opencode/skills/readable-content/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "readable-content", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
readable-content- GitHub stars
- 103
- Token cost
- ~883 tokens
- SKILL.md length
- 451 words
- Files
- 1
- Skills in repo
- 55
- Repo updated
- First seen
- Licence
- MIT
At a glance
Write and structure content for diverse reading abilities and cognitive styles.
- Works in 5 steps: Is the most important information first? → Can someone scanning only headings and… → Are sentences under 20 words on average? → …
- Writing long-form content
- SKILL.md covers Core Principle, Content Structure, Writing for Readability and Content Types With Specific…, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Readable Content is an agent skill from Owl-Listener/inclusive-design-skills. Write and structure content for diverse reading abilities and cognitive styles. Use when writing long-form content, help documentation, product descriptions, policies, terms, or any content that needs to be understood by a wide audience. Triggers on: readability, reading level, too long, too dense, wall of text, hard to read, simplify content, content accessibility, scannable, skimmable.
Its SKILL.md is about 880 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Writing & Content, covering Plain language and style rules, Accessibility and Copywriting. The repository describes itself as: Inclusive design skills for AI coding agents — from cognitive accessibility to adaptive interfaces, inclusive research, and accessibility decision-making. The licence is MIT.
When your agent uses it
- Writing long-form content
- Help documentation
- Product descriptions
- Any content that needs to be understood by a wide audience
Example prompts
- “/readable-content”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Is the most important information first?
- Can someone scanning only headings and bold text get the key message?
- Are sentences under 20 words on average?
- Is every paragraph under 4 sentences?
- Would someone with a grade 8 reading level understand this?
What it can do on your machine
Read from SKILL.md and the folder at commit 6e0740f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Readable Content loads about 883 tokens when it runs. Until then it costs about 102 tokens; SKILL.md has 451 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Owl-Listener/inclusive-design-skills at commit 6e0740f, republished under its MIT licence (© Owl-Listener). 451 words, ~883 tokens.
Download SKILL.mdSave it as
.claude/skills/readable-content/SKILL.md (or your agent's skills folder).- name
- readable-content
- description
- Write and structure content for diverse reading abilities and cognitive styles. Use when writing long-form content, help documentation, product descriptions, policies, terms, or any content that needs to be understood by a wide audience. Triggers on: readability, reading level, too long, too dense, wall of text, hard to read, simplify content, content accessibility, scannable, skimmable.
Readable Content Design
Structure and write content so that people with different reading abilities, attention spans, and cognitive styles can find what they need and understand it.
Core Principle
People don't read — they scan. Design your content for the scan first, the read second.
Content Structure
Inverted Pyramid
Put the most important information first. Assume the reader might stop at any point.
- Paragraph 1: the key message or answer
- Paragraph 2: the essential supporting detail
- Paragraph 3+: background, context, nuance
Chunking
- One topic per section
- One idea per paragraph
- Maximum 3–4 sentences per paragraph
- Maximum 5–7 paragraphs per section before a new heading
- Break walls of text with headings every 2–3 paragraphs
Scannable Elements
- Descriptive headings that summarise the section content
- Bold key terms (sparingly — if everything is bold, nothing is)
- Bulleted lists for 3+ related items (maximum 7 items per list)
- Tables for comparative information
- Pull-out boxes or callouts for critical information
Writing for Readability
Sentence Level
- Aim for 15–20 words per sentence
- One idea per sentence
- Active voice: "We'll send your order" not "Your order will be sent"
- Concrete language: "in 3 working days" not "shortly"
- Address the reader directly: "You can..." not "Users may..."
Word Level
- Use the simplest word that carries the meaning
- Define specialist terms on first use
- Spell out acronyms on first use: "Web Content Accessibility Guidelines (WCAG)"
- Avoid idioms, metaphors, and culturally specific references
- Avoid double negatives: "You can continue" not "You cannot not proceed"
Paragraph Level
- First sentence carries the key point (front-loading)
- Supporting sentences elaborate or provide evidence
- No paragraph should require reading the previous one to make sense
- Transition words help flow: "However," "For example," "This means"
Show full SKILL.md (174 more words)Show less
Content Types With Specific Needs
Instructions and How-To
- Numbered steps for sequential tasks
- One action per step
- Start each step with a verb: "Click", "Enter", "Select"
- Include what the user should see after each step
Policies, Terms, and Legal Content
- Plain language summary at the top
- Full text below for those who need it
- Define all legal terms in context
- Use examples to illustrate abstract concepts
Error and Warning Content
- What happened (specific)
- What it means for the user
- What to do next (single clear action)
- Grade 4–6 reading level always
Data and Numbers
- Round numbers where precision isn't needed (about 2 million, not 1,987,453)
- Provide context: "40% — nearly half"
- Use charts with text summaries for complex data
- Don't assume numeracy — explain what the numbers mean
Assessment Questions
- Is the most important information first?
- Can someone scanning only headings and bold text get the key message?
- Are sentences under 20 words on average?
- Is every paragraph under 4 sentences?
- Would someone with a grade 8 reading level understand this?
© Owl-Listener, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in accessible-content/skills/readable-content of Owl-Listener/inclusive-design-skills.
Open the folder on GitHubat commit 6e0740f
Compare with similar skills
Readable Content next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Readable Content this skillOwl-Listener/inclusive-design-skills | 103 | — | ~883 | Automated safety check: Pass | MIT | |
| UX Writingcontent-designer/ux-writing-skill | 222 | — | ~3.8k | Automated safety check: Pass | MIT | |
| Nbj Write Clearlydaniel-p-green/nbj-write-clearly | 117 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Asd Ste100danyuchn/asd-ste100-skill | 3.9k | — | ~4.1k | Automated safety check: Pass | MIT | |
| Plain Languagethedaviddias/Front-End-Checklist | 74k | — | ~493 | Automated safety check: Pass | MIT | |
| Orwell Writingtamdogood/builder-essential-skills | 218 | — | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
Nbj Write Clearly
daniel-p-green/nbj-write-clearly
Drafts, revises, and audits reader-first technical and product documentation.
Asd Ste100
danyuchn/asd-ste100-skill
A skill your agent uses when English text must be parsed without a human to resolve ambiguity — tool descriptions, error messages, inter-agent instructions, system prompts, status reports — and…
Plain Language
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing rendered HTML, interactive components, or design-system patterns related to Write in plain language.
Orwell Writing
tamdogood/builder-essential-skills
A skill your agent uses when an agent is asked to draft, rewrite, edit, review, polish, copyedit, simplify, humanize, or create written prose, including creative writing, essays, posts, scripts…
G2
brycewang-stanford/Auto-Empirical-Research-Skills
Publication Specialist - Writing, Review, Pre-registration & Quality Assurance Light VS applied: Avoids template-based writing + audience-specific message design Absorbed G3 (Peer Review…
More from Owl-Listener/inclusive-design-skills
All 55 skills in this repoAssistive Technology Scenarios
Owl-Listener/inclusive-design-skills
Writes usage scenarios, use cases and storyboards that show real people using screen readers, switches, voice control and other assistive technology to finish tasks.
Error Prevention and Recovery
Owl-Listener/inclusive-design-skills
Designs forgiving forms and flows: prevent input errors, write messages that say what happened and what to do, and add undo, confirmation and recovery paths.
Accessible Heading Structure
Owl-Listener/inclusive-design-skills
Designs heading hierarchies for screen reader navigation and cognitive accessibility on pages, articles, dashboards and forms.
Ability Spectrum Mapping
Owl-Listener/inclusive-design-skills
Maps a feature across a range of vision, hearing, motor and cognitive ability to find where the design starts to fail, and to explain accessibility scope to stakeholders.
Accessibility Debt Tracking
Owl-Listener/inclusive-design-skills
Track and manage accessibility debt — known accessibility issues that have been deferred.
Accessibility Testing Strategy
Owl-Listener/inclusive-design-skills
Plan what to test, how to test, and who should test for accessibility.
Related
Categories
Questions about Readable Content
What does Readable Content do?
Write and structure content for diverse reading abilities and cognitive styles. Readable Content is an agent skill from Owl-Listener/inclusive-design-skills. Write and structure content for diverse reading abilities and cognitive styles.
When should I use Readable Content?
Readable Content fits situations like: writing long-form content; help documentation; product descriptions; any content that needs to be understood by a wide audience.
How do I install Readable Content in Claude Code?
Run `npx skills add Owl-Listener/inclusive-design-skills --skill readable-content -a claude-code`. Or copy the skill folder (accessible-content/skills/readable-content in Owl-Listener/inclusive-design-skills) into .claude/skills/readable-content in your project. Claude Code loads it when a task matches its description.
How do I install Readable Content in Codex?
Run `npx skills add Owl-Listener/inclusive-design-skills --skill readable-content -a codex`. Or copy the skill folder (accessible-content/skills/readable-content in Owl-Listener/inclusive-design-skills) into .agents/skills/readable-content in your project. Codex loads it when a task matches its description.
Can I use Readable Content in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Owl-Listener/inclusive-design-skills --skill readable-content -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/readable-content, .gemini/skills/readable-content, .github/skills/readable-content and .opencode/skills/readable-content in your project.
What does Readable Content need to run?
SKILL.md names no scripts, command-line tools or credentials: Readable Content is instructions for the agent only.
Does Readable Content access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Readable Content safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Readable Content use?
Readable Content is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Readable Content use?
About 883 tokens (SKILL.md is roughly 3.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Readable Content?
Skills that share tags, products or a category with Readable Content: UX Writing (content-designer/ux-writing-skill, 222 stars), Nbj Write Clearly (daniel-p-green/nbj-write-clearly, 117 stars), Asd Ste100 (danyuchn/asd-ste100-skill, 3.9k stars) and Plain Language (thedaviddias/Front-End-Checklist, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Readable Content?
Owl-Listener (a GitHub user) maintains it in Owl-Listener/inclusive-design-skills, which has 103 GitHub stars. The repository holds 55 skills in this directory. The repository was last updated on June 9, 2026.
Source: Owl-Listener/inclusive-design-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.