write-simplified-technical-english
Write, rewrite, or review technical content with ASD-STE100 Simplified Technical English (STE), Issue 9. Use only when the user explicitly invokes $write-simplified-technical-english. Common requests mention ASD-STE100, STE, or "write STE"; do not use for general requests for clear, simple, concise, or technical writing.
- License 许可
- MIT
- 最近更新
- 2026-11-11
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- write-simplified-technical-english
- description
- Write, rewrite, or review technical content with ASD-STE100 Simplified Technical English (STE), Issue 9. Use only when the user explicitly invokes $write-simplified-technical-english. Common requests mention ASD-STE100, STE, or "write STE"; do not use for general requests for clear, simple, concise, or technical writing.
02 资源文件 3
- 参考文档agents/openai.yaml302 B
- 参考文档references/ASD-STE100.md1.6 KB
- 参考文档references/STE_AGENT_GUIDE.md37.8 KB
03 SKILL.md 正文
Write Simplified Technical English
Apply ASD-STE100 Issue 9 to the user content.
Load the working reference
Before you use this skill, fully read the guide listed below.
Do not read the guide again when both conditions are true:
- You fully read the guide.
- The full guide stays in the active context.
Read references/STE_AGENT_GUIDE.md.
Use the guide as the primary working authority.
For an exact rule or dictionary lookup, use an official copy of ASD-STE100 Issue 9. See references/ASD-STE100.md for the official source and important usage limits.
Read the complete rule or dictionary entry, including its help, examples, page continuation, and supplemental material.
Read all 434 pages only when the user requests a full-standard review and an official copy is available.
Apply the standard
- Identify the source as procedural text, descriptive text, or text with both types.
- Keep technical facts, safety meaning, identifiers, interface labels, code, commands, measurements, and necessary terminology.
- Apply all applicable writing rules in Part 1.
- Use Part 2 to examine each word's meaning and part of speech.
- Use each approved word only with its approved meaning and part of speech.
- Use a permitted technical noun or technical verb only in an approved category.
- Use one term for one concept.
- Remove ambiguity before you make the text shorter.
- Keep quoted material exact.
- Clearly identify quoted non-STE text.
- Obey project or customer rules that have more limits when the necessary meaning does not change.
- If two rules do not agree, tell the user.
Examine the result
Do the independent final compliance pass in Section 15 of the guide. This pass is mandatory:
- Start a fresh subagent that did not write the candidate text.
- Use a context-free subagent when the platform supports it. Give the subagent only the source or requirements, the candidate text, the unverified candidate terminology list, and the path to the guide. Give it the official Issue 9 PDF when it is available.
- Tell the subagent to do only the reviewer role in Section 15 and not to delegate the review.
- Require the subagent to examine and record every word occurrence as specified in Section 15.
- If the reviewer changes or recommends a change to any wording, treat the
result as
CHANGES_REQUIRED. Resolve each finding and send the complete revised candidate to a different fresh subagent. - Use the exact official entry when the guide does not resolve a word.
Give the result only after the last subagent pass examines the exact final text
without changing it and reports PASS, no unapproved ordinary word, and no
unresolved word.
Do not simulate or replace the subagent pass with a self-review. If you cannot start an independent subagent or complete the pass, give only the incomplete review status and its blocker. Do not include candidate text, partial rewritten text, excerpts, or suggested wording. Do not describe the result as reviewed.
If the STE rules change necessary meaning or fixed text, give the most accurate permitted version. Identify the exact constraint that prevents correct text.
Give only the requested content unless one of these conditions is true:
- The user wants a compliance report.
- Two rules do not agree.
- The STE rules change necessary meaning or fixed text.
04 同仓库更多 Skills
write-plainly
Write, rewrite, or review prose in plain language for its intended reader while preserving technical meaning, constraints, uncertainty, and protected literals. Use when the user asks for plain language or plain English, audience-appropriate clarity, an easier-to-understand explanation, or a meaning-preserving simplification of technical prose. When one of those triggers applies, use for public information, documentation, instructions, explanations, notices, and interface text. Do not invoke solely for proofreading, shortening, generic copyediting, humanizing prose, removing AI tells, marketing voice, or creative rewriting. When the user explicitly requests ASD-STE100, STE, or invokes $write-simplified-technical-english, use that skill instead.
write-humanly
Draft, rewrite, or review prose so it sounds like a particular human had a reason to write it. Use when the user asks for human-sounding or less AI-ish writing, dislikes the wording or tone, wants anti-AI prose review or voice matching from supplied human text, needs an existing document's voice preserved, or wants familiar LLM habits removed, such as corrective antithesis, triplets, stock metaphors, prestige filler, needless em dashes, generic assistant language, and performative confidence. Do not invoke solely for plain language, proofreading, shortening, generic copyediting, or a change in formality. Use only when the request concerns human voice, authorial character, or generated-prose texture.
what-what
The user is asking: What is this thread (or main thread) asking for here? Give it to me and $write-humanly. What is even the context? What changes?
what-huh
Make final responses understandable to a reader who cannot see the agent's working text, especially when reporting progress, explaining findings, or asking for a decision.
verifier-system
Establish and keep a project's verification practice useful through Surface, Answer Key, and Comparison. Use for setup verifier-system, choosing how to verify agentic changes, or updating a project's verification guidance as its components evolve.
todo
Manage local .todo lists for bugs, ideas, features, and tasks. When explicitly asked to manage project progress, queues, or project chiefs, use the included references/project-management.md along with the projectbot skill if needed.