Simple English: write docs in ASD-STE100 plain language
Draft and rewrite documentation in controlled Simplified Technical English — short sentences, active voice, no jargon — with a self-check discipline
- What
- Draft and rewrite documentation in controlled Simplified Technical English — short sentences, active voice, no jargon — with a self-check discipline
- Cost
- Free
- Needs
- nothing — the skill is guidance only, no accounts or keys required
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @aminblg's plain-language writing discipline for agents: draft and rewrite documentation, runbooks, error messages, release notes, API guides and incident reports in ASD-STE100 Simplified Technical English — short sentences (20/25 words), active voice, one word one meaning, condition before command, every technical term defined at first use, no AI slop — with a separate prose-only rule set for chat replies and a self-check checklist before delivery. By @aminblg, listed here with credit to its creator. Honest caveats: the rules target facts and instructions, not marketing or brand copy (the skill says so and offers itself for docs instead); Strict mode needs the reference vocabulary files and the skill warns no tool can guarantee ASD-STE100 compliance; MIT-licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: nothing — the skill is guidance only, no accounts or keys required Install "Simple English: write docs in ASD-STE100 plain language" for me. It teaches the agent to draft and rewrite documentation in controlled Simplified Technical English — short sentences, active voice, one word one meaning, every technical term defined at first use — with a separate prose-only rule set for chat replies and a self-check checklist before delivery. Repository: https://github.com/aminblg/simpleenglish/blob/main/skills/simple-english/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "simple-english". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. nothing — it is a writing guide; copy its companion reference files if you want Strict mode vocabulary discipline). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.