rewrite

Name: rewrite
Author: Owl-Listener

82stars25forks

How to install rewrite?

owl-listener/inclusive-design-skills/rewrite

$npx -y skills add Owl-Listener/inclusive-design-skills --skill rewrite

Installs into the current project.

Summary

Rewrite content in plain language while preserving meaning. Chains: readable-content, link-text-design. Use when given content that is too complex, jargon-heavy, or inaccessible for the target audience.

Files · 1

View on GitHub

SKILL.md

1	# Rewrite for Accessibility
2
3	Take existing content and rewrite it to be accessible to people with
4	diverse cognitive abilities and literacy levels — without losing
5	accuracy or meaning.
6
7	## Process
8
9	### Step 1: Assess Current Readability
10	Using readable-content, evaluate:
11	- Current reading level
12	- Sentence and paragraph length
13	- Jargon and specialist terms
14	- Content structure and scannability
15
16	### Step 2: Identify the Core Message
17	For each section, answer: what is the one thing the reader must
18	understand? Write that down in one plain sentence. This becomes the
19	opening line of the rewritten section.
20
21	### Step 3: Rewrite
22	- Replace jargon with plain alternatives
23	- Shorten sentences to 15–20 words
24	- One idea per sentence, one topic per paragraph
25	- Front-load each paragraph with the key point
26	- Use active voice throughout
27	- Address the reader as "you"
28	- Add examples to clarify abstract concepts
29
30	### Step 4: Fix Links
31	Using link-text-design, rewrite any link text that doesn't make
32	sense on its own. Replace "click here" and "read more" with
33	descriptive link text.
34
35	### Step 5: Present Before and After
36	Show the original alongside the rewrite with annotations explaining
37	each change. Include the reading level of both versions.
38
39	## Rules
40
41	- Never sacrifice accuracy for simplicity — if a term is essential,
42	keep it and define it
43	- Don't condescend — plain language is clear language, not childish
44	language
45	- Preserve the author's intent and tone where possible
46	- Flag any content where simplification might change the legal or
47	technical meaning — let the team decide those tradeoffs
48
49	## Output
50
51	Deliver the rewritten content with:
52	- Reading level of original vs. rewrite
53	- Change log of significant edits with rationale
54	- Flagged passages where meaning may have shifted

People who liked this also viewed

6 picks

Type

rewrite

82stars25forks

View on GitHub

How to install rewrite?

owl-listener/inclusive-design-skills/rewrite

$npx -y skills add Owl-Listener/inclusive-design-skills --skill rewrite

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Rewrite for Accessibility
2
3	Take existing content and rewrite it to be accessible to people with
4	diverse cognitive abilities and literacy levels — without losing
5	accuracy or meaning.
6
7	## Process
8
9	### Step 1: Assess Current Readability
10	Using readable-content, evaluate:
11	- Current reading level
12	- Sentence and paragraph length
13	- Jargon and specialist terms
14	- Content structure and scannability
15
16	### Step 2: Identify the Core Message
17	For each section, answer: what is the one thing the reader must
18	understand? Write that down in one plain sentence. This becomes the
19	opening line of the rewritten section.
20
21	### Step 3: Rewrite
22	- Replace jargon with plain alternatives
23	- Shorten sentences to 15–20 words
24	- One idea per sentence, one topic per paragraph
25	- Front-load each paragraph with the key point
26	- Use active voice throughout
27	- Address the reader as "you"
28	- Add examples to clarify abstract concepts
29
30	### Step 4: Fix Links
31	Using link-text-design, rewrite any link text that doesn't make
32	sense on its own. Replace "click here" and "read more" with
33	descriptive link text.
34
35	### Step 5: Present Before and After
36	Show the original alongside the rewrite with annotations explaining
37	each change. Include the reading level of both versions.
38
39	## Rules
40
41	- Never sacrifice accuracy for simplicity — if a term is essential,
42	keep it and define it
43	- Don't condescend — plain language is clear language, not childish
44	language
45	- Preserve the author's intent and tone where possible
46	- Flag any content where simplification might change the legal or
47	technical meaning — let the team decide those tradeoffs
48
49	## Output
50
51	Deliver the rewritten content with:
52	- Reading level of original vs. rewrite
53	- Change log of significant edits with rationale
54	- Flagged passages where meaning may have shifted

People who liked this also viewed

6 picks

Type