iso-24495

Solid

Use when text must be easy for its intended reader to find, understand, and act on — reports, emails, documentation, UI text, announcements, explanations, AI output that reads as dense or bureaucratic. Applies ISO 24495-1 plain language principles with dedicated technique layers for English and Traditional Chinese. Triggers: plain language rewrite, apply ISO 24495, make this clearer for readers, de-jargon this, 淺白改寫, 白話改寫, 去公文腔, 讓讀者一次看懂. Not for creative or literary writing.

Data & Documents 143 stars 5 forks Updated 1 months ago MIT

Install

View on GitHub

Quality Score: 84/100

Stars 20%
72
Recency 20%
75
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# ISO 24495-1 Plain Language (English + Traditional Chinese) ISO 24495-1:2023 is the international standard for plain language. It defines plain language by reader outcome, not by word lists: a document is plain when its intended readers can get what they need (relevant), find it (findable), understand it on first reading (understandable), and act on it (usable). This skill rewrites text so it meets those four outcomes. The principles are language-independent — ISO states the standard "applies to most, if not all, written languages" — so this skill ships one shared principle layer and two language technique layers: - **English** → apply `references/english-techniques.md` - **Traditional Chinese(繁體中文)** → apply `references/chinese-techniques.md` The Chinese layer is not a translation of the English layer. It is a separate technique set for problems Chinese text actually has (歐化長句、公文腔、 成語堆疊、中英夾雜、被字句濫用). As of this skill's release, no national standards body has published a Chinese adaptation of ISO 24495-1; this layer is an original implementation of the principles for Chinese. ## When to Use This Skill - A reader-facing text (report, email, doc page, UI string, announcement, policy, explanation) reads as dense, bureaucratic, hedged, or jargon-heavy. - AI-generated output is technically correct but hard to read. - Text must work for non-specialist readers, non-native readers, or busy readers who will scan rather than study. - You want a before/after with the violated ...

Details

Author
danyuchn
Repository
danyuchn/iso-24495-skill
Created
1 months ago
Last Updated
1 months ago
Language
N/A
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

plain-language

Apply ISO 24495-1:2023 (Plain Language — Part 1: Governing principles and guidelines) to any document or communication. Use when Shane says: "make this plain language", "apply plain language to this", "review for ISO 24495-1 compliance", "plain language pass", "plain english this", "make this clearer for readers", "simplify this for the audience". Also invoke proactively when reviewing policy, legal, form, or instructional text that a general audience must act on. Distinct from ms-style-pass (term/heading conventions) and humanize (Shane's voice) — this restructures for a reader's task.

0 Updated 5 days ago
slogsdon
AI & Automation Listed

plain-language-iso-24495

Write documents that conform to ISO 24495-1:2023 (Plain Language — Governing principles and guidelines). Use when the user asks for a document, memo, proposal, RFC, PRD, design doc, runbook, postmortem, one-pager, or explanation to be written in "plain language", "clear language", "accessible language", or "ISO 24495"; when they ask a document to be understandable by a mixed or non-specialist audience; when they ask to make an existing document clearer, more readable, or easier to scan; when they mention audiences like legal, executive, or cross-functional stakeholders who need to skim and decide; or when they ask to reduce jargon.

2 Updated 1 months ago
nikdumroese
AI & Automation Listed

plain-speak

Translate technical jargon, code concepts, or dense engineering text into plain language a non-technical colleague or manager can follow. Use when the user asks to "explain in plain language", "白話文", "翻成人話", "用白話解釋", "explain like I'm a PM", "make this non-technical", "simplify this term", "what does this term mean", pastes technical text for a business-audience version, or asks whether an existing plain-language draft works for a non-technical reader ("這樣夠白話嗎", "幫我看非技術主管看不看得懂", "is this clear enough for a PM"). Also use mid-conversation for requests to re-explain preceding content ("上面那段用白話再講一次", "你剛剛講的我看不懂", "剛剛那幾個選項差在哪", "講人話"), including a question just put to the user. Reply in the user's language. Do NOT invoke for removing AI-isms / 潤��語氣 (use humanizer-zh), structuring a formal business document (簽呈/會議紀錄/報告; use formal-doc-structure), or RFP / 需求規格書 / 招���規格 (use rfp-writing). This skill lowers audience complexity, not voice, structure, or document type.

1 Updated 2 weeks ago
leoluyi