iso-24495-skill README

The project's README from github.com/danyuchn/iso-24495-skill. As one markdown file: README.md.

ISO 24495 Skill — Plain Language for English and Traditional Chinese

A Claude Code skill that rewrites text into plain language per ISO 24495-1:2023 — the international standard that defines plain language by reader outcome: the intended readers can find what they need, understand it on first reading, and use it.

Two things make this skill different from a one-line "write plainly" prompt:

  1. It implements the standard's actual structure — reader-first content selection (relevant), document structure (findable), wording (understandable), and actionability (usable) — not just shorter sentences.
  2. It ships a real Traditional Chinese technique layer（繁體中文層）. ISO 24495-1 is explicitly language-independent, but as of this release the official translation list contains no East Asian language at all. The Chinese layer here is an original implementation of the four principles for Chinese — targeting the problems Chinese text actually has（歐化長句、公文腔、成語堆疊、中英夾雜、 被字句濫用）, not a translation of the English rules.

Before / After

Before After
"It is expected that the reimbursement form should be completed and submitted in a timely manner in order for processing to be initiated." "Submit your reimbursement form by the 25th. We start processing it the day we receive it."
「相關費用之核銷單據應儘速填妥並繳交，俾利後續作業之進行。」 「請在每月 25 日前把核銷單交給財務部的王小姐。我們收到當天就開始處理。」
"The team will make a determination as to whether an implementation of the proposed solution may potentially be feasible in some circumstances." "The team will decide whether the proposed solution is feasible."
「請先 review 這份 proposal 的 scope，確認 stakeholder 的 alignment 沒問題之後，我們再 kick off 這個 project。」 「請先看過這份提案的範圍，確認相關的人都同意了，我們再開始做。」

More pairs, each naming the principle applied: examples/before-after-en.md · examples/before-after-zh.md.

What This Skill Does

  1. Identifies the intended reader and purpose — the standard's first principle requires it, and every cut/keep decision follows from it.
  2. Detects the text language and loads the matching technique layer: references/english-techniques.md or references/chinese-techniques.md.
  3. Rewrites against the four principles (relevant → findable → understandable → usable) without dropping any fact, number, condition, or honest hedge. Where plainness would cost precision, it keeps the precision and flags the trade-off.
  4. Returns the rewritten text alone — no preamble, no lecture. Ask for "show the diff" and it returns a before/after table naming the principle behind each change instead.

Architecture: one shared layer, per-language technique layers

SKILL.md                          shared layer (English): principles, procedure, routing
references/principles.md          the four principles, interpretation, sources
references/english-techniques.md  English techniques (in English)
references/chinese-techniques.md  中文手法（以中文撰寫）

The shared layer is language-independent, mirroring the standard itself. Technique layers are written in their own language, because plain language techniques do not translate: English fights nominalization and passive voice; Chinese fights Europeanized long sentences and bureaucratic register. Adding another language = adding one technique file. Contributions welcome.

Installation

git clone https://github.com/danyuchn/iso-24495-skill ~/.claude/skills/iso-24495

Usage

Rewrite this in plain language
Apply ISO 24495 to this announcement
把這段改成淺白中文
幫我去掉這封信的公文腔

You get the rewritten text back and nothing else. Add "show the diff" / 「列出改了什麼」 to see the per-change principle table.

Scope

Built for: reader-facing text — reports, emails, documentation, UI strings, announcements, policies, explanations, and AI output that reads as dense or bureaucratic. Works on English and Traditional Chinese; the principles apply to other languages but no technique layer exists for them yet.

Not built for: creative or literary writing (voice is the point there), and not for agent-facing text where a machine must parse without ambiguity — that is controlled-language territory; use the companion skill asd-ste100-skill instead. Rule of thumb: reader is a person → this skill; reader is a machine or a maintenance manual → STE.

Relationship to the ISO Standard

This is an unofficial project, not affiliated with, endorsed by, or approved by ISO. The full ISO 24495-1 text is a licensed document and is not reproduced here. The skill is built from the standard's publicly documented principle framework (ISO's published abstract and scope, and the International Plain Language Federation's freely published materials). Every quantitative rule in the technique files is this project's own working proxy, not a clause of the standard. For certified conformance, buy and consult the standard.

Sources

License

MIT — see LICENSE. The license covers this repository's original text; it grants no rights to any ISO publication.

iso-24495-skill (danyuchn/iso-24495-skill)

Searching Database…

154 ·GitHub
Iso-24495-skill
What is this?A Claude Code skill that rewrites your text into plain language following ISO 24495-1:2023 — the standard that defines plain language by reader outcome: readers can find what they need, understand it on first reading, and use it. It works on English and Traditional Chinese.
Is it a separate app, or something that lives inside Claude Code?It lives inside Claude Code — a skill you install, not an app with an interface. You hand it text in a conversation and get back only the rewritten text, no preamble or lecture.
How do I get it set up?Install it into Claude Code as a skill — the README's Installation section covers the steps. After that you simply give it the text you want rewritten.
Do I need anything besides Claude Code itself?No. The repo is just skill instructions plus markdown technique files such as references/english-techniques.md — no package dependencies or build step.
When would it be the wrong tool?For creative or literary writing, where voice is the point, and for agent-facing text a machine must parse unambiguously — for that second case the author points to the companion controlled-language skill asd-ste100-skill.
What kind of text is it built for?Reader-facing text: reports, emails, documentation, UI strings, announcements, policies, explanations — including AI output that reads as dense or bureaucratic.
Is this an official ISO tool?No — it's unofficial and unaffiliated, built from the standard's public principle framework, and the quantitative rules in its technique files are the project's own proxies, not ISO clauses. The MIT license covers only this repo's original text and grants no rights to ISO publications.
What does it actually do to my text, step by step?It first pins down the intended reader and purpose — every cut/keep decision follows from that — then detects the language, loads the matching technique layer, and rewrites along four principles: content relevant to that reader, structure they can navigate, wording they understand on first reading, and text they can act on. No fact, number, condition, or honest hedge gets dropped; where plainness would cost precision, it keeps the precision and flags the trade-off.
Why does a plain-language skill need a separate Traditional Chinese layer?ISO 24495-1 is language-independent, but the official translation list has no East Asian language. This layer is an original implementation aimed at problems Chinese text actually has — Europeanized long sentences, bureaucratic register, idiom stacking, mixed Chinese-English — not a translation of the English rules.
What do I get if I ask it to 'show the diff'?Instead of just the rewritten text, a before/after table naming the plain-language principle behind each change.
Can I see rewrite examples before installing?Yes — the README opens with before/after pairs in both languages, and more pairs, each naming the principle applied, are in examples/before-after-en.md and examples/before-after-zh.md.
What are similar projects?iso-24495, simplified-technical-english, asd-ste100-skill, im-not-ai, Tech-Doc-Style-Chinese, ai-aug-edu, linkedin-agent-skill, human-writing
Which topics is it in?technical-writing, chinese-traditional, bilingual, text-processing, english, claude-skill, writing, claude-code-skill, accessibility, documentation, agent-skills, productivity
Creator
danyuchn
Size
<0.1 MB
Stars
154
Updated
CommitAug 13
Age
2mo
Commits · 90 Days