
readable-content
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.
- Installs
- 80
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/owl-listener/inclusive-design-skills --skill readable-content- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads readable-content automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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"
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?
FAQ
What does the readable-content skill do?
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.
How do I install readable-content?
Run npx skills add https://github.com/owl-listener/inclusive-design-skills --skill readable-content in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/readable-content/ (personal) or .claude/skills/readable-content/ (project).
Which AI agents can use readable-content?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is readable-content safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains readable-content?
It is published by owl-listener in owl-listener/inclusive-design-skills. It has 80 recorded installs.
More from owl-listener/inclusive-design-skills
plain-language-design
owl-listener/inclusive-design-skills
Open the skill to read its SKILL.md instructions.
keyboard-navigation
owl-listener/inclusive-design-skills
Open the skill to read its SKILL.md instructions.
cognitive-load-assessment
owl-listener/inclusive-design-skills
Open the skill to read its SKILL.md instructions.
responsive-review
owl-listener/inclusive-design-skills
Open the skill to read its SKILL.md instructions.
user-preference-respect
owl-listener/inclusive-design-skills
Open the skill to read its SKILL.md instructions.
error-prevention-recovery
owl-listener/inclusive-design-skills
Open the skill to read its SKILL.md instructions.
Popular docs & writing skills
grill-with-docs
mattpocock/skills
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
lark-markdown
open.feishu.cn
飞书 Markdown:查看、创建、上传、编辑和比较飞书中的原生 Markdown 文件。当用户要操作飞书 Markdown 文件,或比较其远端版本及本地草稿时使用。纯本地 Markdown 文件操作不触发本 skill。不负责将 Markdown 导入为飞书在线文档,也不负责文件搜索、权限、评论、移动、删除等云空间管理操作。
writing-beats
mattpocock/skills
Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.
writing-shape
mattpocock/skills
Writing, exploit: shape raw material into an article, paragraph by paragraph.
writing-fragments
mattpocock/skills
Writing, explore: mine raw fragments, no structure yet.
writing-for-agents
mattpocock/skills
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.