Skip to content
Back to search

iso-24495

SkillWorks with Claude CodeGitHub

"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."

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/danyuchn--iso-24495-skill/badge.svg)](/listings/danyuchn--iso-24495-skill)

HTML

<a href="/listings/danyuchn--iso-24495-skill"><img src="/api/listings/danyuchn--iso-24495-skill/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

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

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

SKILL.md · Manifest · 100 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. ---
  2. name: iso-24495
  3. description: "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."
  4. version: 0.1.0
  5. ---
  6. # ISO 24495-1 Plain Language (English + Traditional Chinese)
  7. ISO 24495-1:2023 is the international standard for plain language. It defines
  8. plain language by reader outcome, not by word lists: a document is plain when
  9. its intended readers can get what they need (relevant), find it (findable),
  10. understand it on first reading (understandable), and act on it (usable).
  11. This skill rewrites text so it meets those four outcomes. The principles are
  12. language-independent — ISO states the standard "applies to most, if not all,
  13. written languages" — so this skill ships one shared principle layer and two
  14. language technique layers:
  15. - **English** → apply `references/english-techniques.md`
  16. - **Traditional Chinese(繁體中文)** → apply `references/chinese-techniques.md`
  17. The Chinese layer is not a translation of the English layer. It is a separate
  18. technique set for problems Chinese text actually has (歐化長句、公文腔、
  19. 成語堆疊、中英夾雜、被字句濫用). As of this skill's release, no national
  20. standards body has published a Chinese adaptation of ISO 24495-1; this layer
  21. is an original implementation of the principles for Chinese.
  22. ## When to Use This Skill
  23. - A reader-facing text (report, email, doc page, UI string, announcement,
  24. policy, explanation) reads as dense, bureaucratic, hedged, or jargon-heavy.
  25. - AI-generated output is technically correct but hard to read.
  26. - Text must work for non-specialist readers, non-native readers, or busy
  27. readers who will scan rather than study.
  28. - You want a before/after with the violated principle named per change —
  29. ask for it; the default output is the rewritten text alone.
  30. Not for creative or literary writing, and not for agent-facing controlled
  31. language — for text a machine must parse without ambiguity, use a controlled
  32. language standard such as ASD-STE100 instead (see Scope Boundary below).
  33. ## Procedure
  34. 1. **Identify the reader and purpose** (Principle 1 requires it). If the user
  35. named an audience, use it. Otherwise assume a busy, intelligent,
  36. non-specialist adult reader and state that assumption in one line only
  37. when it changes the rewrite materially.
  38. 2. **Detect the text language.** English → English techniques file. Chinese →
  39. Chinese techniques file. Mixed text → the dominant language's file, and
  40. handle embedded foreign terms per that file's rules. Other languages →
  41. apply the four principles directly and say the technique layer for that
  42. language does not exist yet.
  43. 3. **Read the whole text for meaning before touching a sentence.**
  44. 4. **Rewrite against the four principles**, using the language file's
  45. techniques. Never drop a fact, condition, number, or scope qualifier.
  46. If plainness would cost precision, keep the precision and flag the
  47. trade-off in one line.
  48. 5. **Run the language file's self-check list** before returning.
  49. ## Output Format
  50. Return the rewritten text alone — no preamble, no principle lecture, no
  51. change summary. Append a one-line `Kept as-is:` note only when something was
  52. deliberately left unsimplified for precision.
  53. When the user asks to "show the diff", "explain the changes", or "which
  54. principles", return a before/after table instead, one row per change, naming
  55. the principle (relevant / findable / understandable / usable) and the
  56. technique applied.
  57. ## The Four Principles (working definitions)
  58. | Principle | The reader outcome it protects |
  59. |---|---|
  60. | Relevant | The text contains what this reader needs for this purpose — and nothing else. Cutting is a rewrite tool, not just rearranging. |
  61. | Findable | The reader can locate the part they need without reading everything: informative headings, front-loaded key points, lists for parallel items, one topic per paragraph. |
  62. | Understandable | The reader gets it on first reading: common words, short sentences, active constructions, defined terms, no unexplained jargon. |
  63. | Usable | The reader can act: concrete instructions, explicit actors and deadlines, next steps stated as steps. |
  64. Full interpretation, sources, and copyright boundaries:
  65. `references/principles.md`.
  66. ## Scope Boundary: Plain Language vs Controlled Language
  67. ISO 24495-1 optimizes text for **human readers** and permits full natural
  68. language. Controlled-language standards such as ASD-STE100 optimize for
  69. **zero-ambiguity parsing** (originally by maintenance technicians, now also
  70. by AI agents) and restrict vocabulary and grammar hard. If the reader is a
  71. machine or the cost of one misread word is high, use a controlled-language
  72. skill. If the reader is a person who needs to find, understand, and act,
  73. use this one.
  74. ## Copyright Note
  75. This is an unofficial project, not affiliated with or endorsed by ISO. The
  76. full ISO 24495-1 text is a licensed document and is not reproduced here. This
  77. skill is built from the standard's publicly documented principles and public
  78. plain-language practice; every quantitative rule in the technique files is
  79. this project's own working proxy, not a clause of the standard. For certified
  80. conformance work, buy and consult the standard itself.
README.md · README · 119 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # ISO 24495 Skill — Plain Language for English and Traditional Chinese
  2. A Claude Code skill that rewrites text into plain language per
  3. [ISO 24495-1:2023](https://www.iso.org/standard/78907.html) — the
  4. international standard that defines plain language by reader outcome: the
  5. intended readers can **find** what they need, **understand** it on first
  6. reading, and **use** it.
  7. Two things make this skill different from a one-line "write plainly" prompt:
  8. 1. **It implements the standard's actual structure** — reader-first content
  9. selection (relevant), document structure (findable), wording
  10. (understandable), and actionability (usable) — not just shorter sentences.
  11. 2. **It ships a real Traditional Chinese technique layer(繁體中文層).**
  12. ISO 24495-1 is explicitly language-independent, but as of this release the
  13. [official translation list](https://www.iplfederation.org/standard-translations/)
  14. contains no East Asian language at all. The Chinese layer here is an
  15. original implementation of the four principles for Chinese — targeting the
  16. problems Chinese text actually has(歐化長句、公文腔、成語堆疊、中英夾雜、
  17. 被字句濫用), not a translation of the English rules.
  18. ## Before / After
  19. | Before | After |
  20. |---|---|
  21. | "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." |
  22. | 「相關費用之核銷單據應儘速填妥並繳交,俾利後續作業之進行。」 | 「請在每月 25 日前把核銷單交給財務部的王小姐。我們收到當天就開始處理。」 |
  23. | "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." |
  24. | 「請先 review 這份 proposal 的 scope,確認 stakeholder 的 alignment 沒問題之後,我們再 kick off 這個 project。」 | 「請先看過這份提案的範圍,確認相關的人都同意了,我們再開始做。」 |
  25. More pairs, each naming the principle applied:
  26. [`examples/before-after-en.md`](examples/before-after-en.md) ·
  27. [`examples/before-after-zh.md`](examples/before-after-zh.md).
  28. ## What This Skill Does
  29. 1. Identifies the intended reader and purpose — the standard's first
  30. principle requires it, and every cut/keep decision follows from it.
  31. 2. Detects the text language and loads the matching technique layer:
  32. [`references/english-techniques.md`](references/english-techniques.md) or
  33. [`references/chinese-techniques.md`](references/chinese-techniques.md).
  34. 3. Rewrites against the four principles (relevant → findable →
  35. understandable → usable) without dropping any fact, number, condition, or
  36. honest hedge. Where plainness would cost precision, it keeps the
  37. precision and flags the trade-off.
  38. 4. Returns the rewritten text alone — no preamble, no lecture. Ask for
  39. "show the diff" and it returns a before/after table naming the principle
  40. behind each change instead.
  41. ## Architecture: one shared layer, per-language technique layers
  42. ```
  43. SKILL.md shared layer (English): principles, procedure, routing
  44. references/principles.md the four principles, interpretation, sources
  45. references/english-techniques.md English techniques (in English)
  46. references/chinese-techniques.md 中文手法(以中文撰寫)
  47. ```
  48. The shared layer is language-independent, mirroring the standard itself.
  49. Technique layers are written in their own language, because plain language
  50. techniques do not translate: English fights nominalization and passive
  51. voice; Chinese fights Europeanized long sentences and bureaucratic register.
  52. Adding another language = adding one technique file. Contributions welcome.
  53. ## Installation
  54. ```bash
  55. git clone https://github.com/danyuchn/iso-24495-skill ~/.claude/skills/iso-24495
  56. ```
  57. ## Usage
  58. ```
  59. Rewrite this in plain language
  60. Apply ISO 24495 to this announcement
  61. 把這段改成淺白中文
  62. 幫我去掉這封信的公文腔
  63. ```
  64. You get the rewritten text back and nothing else. Add "show the diff" /
  65. 「列出改了什麼」 to see the per-change principle table.
  66. ## Scope
  67. Built for: reader-facing text — reports, emails, documentation, UI strings,
  68. announcements, policies, explanations, and AI output that reads as dense or
  69. bureaucratic. Works on English and Traditional Chinese; the principles apply
  70. to other languages but no technique layer exists for them yet.
  71. Not built for: creative or literary writing (voice is the point there), and
  72. not for **agent-facing** text where a machine must parse without ambiguity —
  73. that is controlled-language territory; use the companion skill
  74. [asd-ste100-skill](https://github.com/danyuchn/asd-ste100-skill) instead.
  75. Rule of thumb: reader is a person → this skill; reader is a machine or a
  76. maintenance manual → STE.
  77. ## Relationship to the ISO Standard
  78. This is an unofficial project, not affiliated with, endorsed by, or approved
  79. by ISO. The full ISO 24495-1 text is a licensed document and is **not**
  80. reproduced here. The skill is built from the standard's publicly documented
  81. principle framework (ISO's published abstract and scope, and the
  82. International Plain Language Federation's freely published materials). Every
  83. quantitative rule in the technique files is this project's own working
  84. proxy, not a clause of the standard. For certified conformance, buy and
  85. consult the standard.
  86. ## Sources
  87. - [ISO 24495-1:2023 — Plain language, Part 1](https://www.iso.org/standard/78907.html)
  88. - [International Plain Language Federation — ISO standard](https://www.iplfederation.org/iso-standard/)
  89. - [IPLF — national adoptions and translations](https://www.iplfederation.org/standard-translations/)
  90. - [AccessibleEU — ISO 24495-1 summary](https://accessible-eu-centre.ec.europa.eu/content-corner/digital-library/iso-24495-12023-plain-language-part-1-governing-principles-and-guidelines_en)
  91. - Companion controlled-language skill: [asd-ste100-skill](https://github.com/danyuchn/asd-ste100-skill)
  92. ## License
  93. MIT — see [LICENSE](LICENSE). The license covers this repository's original
  94. text; it grants no rights to any ISO publication.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.