plain-english-content SKILL.md skillA
plain-english-content from openhands/extensions is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add openhands/extensions/plain-english-content@git:20260629.6e46834Pins git:20260629.6e46834 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- openhands/extensions
- Path
skills/plain-english-content/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260629.6e46834, committed Jun 29, 2026
- Size
- 6,023 bytes
- Repository stars
- 179
- License
- MIT
This skill should be used when the user asks to "write in plain English", "make this easier to read", "rewrite guidance", "improve report clarity", or produce accessible public-facing prose. It applies plain English content design principles: active voice, front-loaded content, sentence case, and no bold or italics for emphasis.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
Open content up so anyone can understand it the first time they read it, without losing substance, nuance or precision. Aim to open up, not dumb down. Apply the GOV.UK style guide approach: plain English, user needs first, active voice, front-loaded structure and accessible formatting. Use this skill for reports, research write-ups, guidance, documentation, summaries, and public-facing prose where clarity and accessibility matter. When writing a report, default to this style. When briefing a research agent, pass this skill so the report follows the same style. ## Content design principles - Start from the user need. Write what the reader needs to know to do or decide something, not what the writer wants to say. - Front-load everything. Put the most important point first in the document, each section, each paragraph and each sentence. Use the inverted pyramid: conclusion first, then detail, then background. - Keep one idea per sentence and one topic per paragraph. Split sentences that contain more than one idea. - Be specific and concrete. Give the number, name and date. Cut vague abstractions like "a range of", "going forward" and "in terms of". …
Read the whole file at its exact version.
How to install
mdr add openhands/extensions/plain-english-content@sha256:2ef939ec154a2555The line at the top of this page pins the label git:20260629.6e46834, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_uweom7zdzzfutfm5)
6 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jun 29, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6023 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
openhands/extensions · 179 stars · license MIT · pushed 2026-11-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_uweom7zdzzfutfm5 GET https://markdownregistry.com/api/v1/resolve?ref=openhands/extensions/plain-english-content GET https://markdownregistry.com/api/v1/blob/2ef939ec154a2555a1018233ab818a4b0c92b16668c747b1ad9886a567c04ca2
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.