Loading...
Loading...
Found 7 Skills
Write and rewrite technical documents in ASD-STE100 Simplified Technical English. Use this skill when the user asks for STE, ASD-STE100, Simplified Technical English, simplified English, controlled language, or plain technical English. Also use it for aircraft, defense, machine, or industrial maintenance procedures, work instructions, warnings, cautions, safety notices, and manuals that must be easy to translate or easy to read for non-native readers.
Write prose in "Simplified Technical English". This applies to documentation, READMEs, commits, pull request, plans and release notes. It does not apply to code, identifiers, marketing copy, essays, or anything that needs a voice.
Hold on. The previous message wasn't clear enough—please rephrase it.
Write or rewrite English into ASD-STE100 Simplified Technical English and strip AI artifacts (decorative emojis, Markdown residue) from technical documentation — maintenance manuals, procedures, medical device instructions, and API docs read by non-native speakers or machine translation. Enforces approved word meanings, technical noun and verb categories, the 20/25-word sentence limits, banned verb tenses, and passive-voice restrictions. Trigger on simplified technical english, STE, ASD-STE100, controlled language, translation-ready docs, de-slop this manual. Do NOT use for marketing copy, brand voice, or narrative writing; for French text use samber/cc-skills@humaniseur-fr instead.
Turn any explanation, summary, or AI/agent output into the format a human can understand fastest. Picks from a ladder of formats (controlled-language writing in the style of ASD-STE100 Simplified Technical English, diagrams, interactive HTML pages, narrated explainer videos) and produces it. Use this skill whenever the user asks to explain, summarize, simplify, or "help me understand" something; asks for "STE", "ASD-STE100", "Simplified Technical English", "plain/clear/readable" writing, or "80% STE"; asks to "diagram it", "show me", "make it in HTML", "make an explainer", or a "3Blue1Brown / 3b1b style video"; or needs to review, audit, or oversee what an LLM or agent produced (diffs, logs, long reports, research output). Use it even when the user does not name a format but the content is complex enough that plain prose would be hard to read.
Report a finished task as its result, not its transcript. Or tell the user what happened since their last message. Read this skill before your final report on a task that changed files, made an artifact, or ran a check. Examples are a build, a workflow, a background agent, an implement or verify run, or a release. Use it also when the user asks what happened since their last message. Use it when the user asks to catch up on this session.
Write or revise explanations in concise English inspired by Karpathy's ASD-STE100 suggestion. Use for clear prose, technical explanations, or an explicitly requested STE draft.