Skip to content
Skills Library
Documents & office · Writing

plain-language

/plain-language

Shorten and clarify text in plain language while preserving its exact meaning. Use when text is too long, jargon-dense, or overwrought for its reader, such as specs, instructions, docs, or UI copy.

Repository
skills ↗
Licence
MIT
Last repository change
09.11.2026

Assessment and security

81/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content16 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
2
Deprecation

No signals detected. Repository changed on 09.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Shorten and clarify text in plain language while preserving its exact meaning. Use when text is too long, jargon-dense, or overwrought for its reader, such as specs, instructions, docs, or UI copy.

Original author description

Shorten and clarify text in plain language while preserving its exact meaning. Use when text is too long, jargon-dense, or overwrought for its reader, such as specs, instructions, docs, or UI copy.

How it works

SKILL.md has no level-two headings · 24 lines, 228 words

SKILL.md preview
---
name: plain-language
disable-model-invocation: true
description: "Shorten and clarify text in plain language while preserving its exact meaning. Use when text is too long, jargon-dense, or overwrought for its reader, such as specs, instructions, docs, or UI copy."
---

# Plain Language

From [ASD-STE100, Simplified Technical English, Issue 9](https://www.asd-ste100.org/assets/files/ASD-STE100_ISSUE9.pdf), Part 1, §§4 and 9:

> Rule 4.1 Write short and clear sentences.

> Rule 9.1 Use a different sentence construction to write a sentence when a word-for-word replacement is not sufficient.

> When you use different sentence constructions, always make sure that you use approved words that do not change the meaning of the sentence.

> Rule 9.4 When you select terminology or wording, always use a consistent style.

From [Orwell, Politics and the English Language](https://www.orwell.ru/library/essays/politics/english/e_polit):

> 1. Never use a metaphor, simile, or other figure of speech which you are used to seeing in print.
> 2. Never use a long word where a short one will do.
> 3. If it is possible to cut a word out, always cut it out.
> 4. Never use the passive where you can use the active.
> 5. Never use a foreign phrase, a scientific word, or a jargon word if you can think of an everyday English equivalent.
> 6. Break any of these rules sooner than say anything outright barbarous.

Keep articles, prepositions, and connectors needed to prevent ambiguity, and preserve every actor, action, object, condition, obligation level, degree, and uncertainty. Leave already-tight sentences alone. When the source text's meaning is missing or ambiguous, name the gap and sync with the user instead of guessing.

Versions

RepositoryScoreLicence
This page · hebtcd/skills81MIT
zts212653/clowder-ai100MIT
oborchers/fractional-cto100MIT
scratchpad-sh/skills100MIT
pandysp/claude-plugins100MIT
slogsdon/skills-writing100MIT
thedaviddias/front-end-checklist100MIT
mgifford/accessibility-skills100AGPL-3.0
surendranb/writing-skills100MIT

Database snapshot: 13.11.2026 · package version c96240689065 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100rewrite
    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.
  • 100plain-language-rewriting
    Rewrites dense, bureaucratic, or jargon-heavy text so the intended reader can find, understand, and act on it on first reading, while preserving meaning, obligations, and qualifiers. Use for policies, notices, documentation, emails, letters, and instructions aimed at non-specialists or busy readers.
  • 100write-plain
    Holds the rules for plain, short international English and rewrites or checks a text against them, so that busy and non-native readers understand it on the first read. Use when the user says "make it plainer", asks to simplify, shorten or clarify a text, asks whether others will…
  • 90plain-writing
    Write and clean up text with no emoji, filler, machine tells, invented facts or jargon. Use for docs, READMEs, PRs, release notes, UI copy.
  • 100deslop-writing
    Rewrites prose in plain, human language and strips the tells of AI writing, keeping the meaning and the writer's voice. Use for "deslop this", "make this plainer", or "tighten this". Not for code cleanup.
  • 95human-language
    Use when writing or editing any agent-written text: replies, copy, tool-call prose, and handoffs. Also use when asked to remove AI slop, write plain or natural prose for a grade 6 reader, keep the author's meaning, or check facts, voice, flow, and exact data before release.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.