← ClaudeAtlas

ste-explainlisted

Makes explanations and rewritten text easy for a non-expert to read in one pass, with the sentence rules of Simplified Technical English (ASD-STE100). Use this skill whenever the user asks for a simple, plain, or jargon-free explanation, or is new to the topic they want explained, code included. Also use it when an explanation is for a reader outside the field, such as a manager, a parent, or a class. Check this skill before you answer such a request, even a short question you can answer at once. It sets only the wording, so for such a request, use it with any skill that makes slides, charts, or documents. Use it to simplify or rewrite text for readability, to write steps or docs that others must follow, and whenever the user mentions STE. Do not use it for summaries, tone changes, or translation into another language. Do not use it for proofreading that fixes only grammar.
ryanjmichie-git/ste-explain · ★ 3 · AI & Automation · score 76
Install: claude install-skill ryanjmichie-git/ste-explain
# Explain in Simplified Technical English STE (ASD-STE100) is a controlled language from aerospace maintenance manuals. Its rules remove ambiguity and filler, which makes any explanation easier to read. Apply the rules below to every sentence you write while this skill is active. The goal is text a tired reader can parse in one pass. ## Modes - **Default — 80% STE.** Apply all structure rules below. Technical terms the topic needs (API, tensor, amortization) are allowed. This is the default because full STE vocabulary targets aircraft maintenance, and strict compliance makes general prose stilted. - **Strict.** If the user says "strict", "full STE", or "100%", apply vocabulary discipline too. Read `references/rules.md` first. Prefer the simple words it lists, and keep domain terms to the minimum the topic needs. - **Rewrite.** If the user supplies text rather than a topic, return the STE version. Keep every fact. Do not summarize or drop content unless asked. After a rewrite, end with one sentence of fewer than 20 words that names the two or three rules that did the most work. Example: "The rules that did the most work were short sentences, active voice, and simple words." Do not list the words you changed. If the user will send the rewrite to someone else, leave the note out. ## Structure rules (apply always) 1. Keep sentences short: at most 20 words in instructions, 25 in descriptions. 2. Give one instruction per sentence. Start instructions with the ver