[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79TFVB2DE2KYVNN2M8TF2Y7":3,"skill-same:01M79TFVB2DE2KYVNN2M8TF2Y7":58},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M79TFVB2DE2KYVNN2M8TF2Y7","write-simplified-technical-english",null,"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.","Mattie\u002Fmattie_skills","Mattie","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F566406?v=4","01M79TBXJN40A1D31YFHV26CY4","01M79TBXKXWGQ8X3YWDQZXDGQN",1,"MIT","https:\u002F\u002Fgithub.com\u002FMattie\u002Fmattie_skills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-simplified-technical-english\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: write-simplified-technical-english\ndescription: 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.\n---\n\n# Write Simplified Technical English\n\nApply ASD-STE100 Issue 9 to the user content.\n\n## Load the working reference\n\nBefore you use this skill, fully read the guide listed below.\n\nDo not read the guide again when both conditions are true:\n\n- You fully read the guide.\n- The full guide stays in the active context.\n\nRead [references\u002FSTE_AGENT_GUIDE.md](references\u002FSTE_AGENT_GUIDE.md).\n\nUse the guide as the primary working authority.\n\nFor an exact rule or dictionary lookup, use an official copy of ASD-STE100\nIssue 9. See\n[references\u002FASD-STE100.md](references\u002FASD-STE100.md)\nfor the official source and important usage limits.\n\nRead the complete rule or dictionary entry, including its help, examples, page\ncontinuation, and supplemental material.\n\nRead all 434 pages only when the user requests a full-standard review and an\nofficial copy is available.\n\n## Apply the standard\n\n1. Identify the source as procedural text, descriptive text, or text with both\n   types.\n2. Keep technical facts, safety meaning, identifiers, interface labels, code,\n   commands, measurements, and necessary terminology.\n3. Apply all applicable writing rules in Part 1.\n4. Use Part 2 to examine each word's meaning and part of speech.\n5. Use each approved word only with its approved meaning and part of speech.\n6. Use a permitted technical noun or technical verb only in an approved\n   category.\n7. Use one term for one concept.\n8. Remove ambiguity before you make the text shorter.\n9. Keep quoted material exact.\n10. Clearly identify quoted non-STE text.\n11. Obey project or customer rules that have more limits when the necessary\n    meaning does not change.\n12. If two rules do not agree, tell the user.\n\n## Examine the result\n\nDo the independent final compliance pass in Section 15 of the guide. This pass\nis mandatory:\n\n1. Start a fresh subagent that did not write the candidate text.\n2. Use a context-free subagent when the platform supports it. Give the\n   subagent only the source or requirements, the candidate text, the\n   unverified candidate terminology list, and the path to the guide. Give it\n   the official Issue 9 PDF when it is available.\n3. Tell the subagent to do only the reviewer role in Section 15 and not to\n   delegate the review.\n4. Require the subagent to examine and record every word occurrence as\n   specified in Section 15.\n5. If the reviewer changes or recommends a change to any wording, treat the\n   result as `CHANGES_REQUIRED`. Resolve each finding and send the complete\n   revised candidate to a different fresh subagent.\n6. Use the exact official entry when the guide does not resolve a word.\n\nGive the result only after the last subagent pass examines the exact final text\nwithout changing it and reports `PASS`, no unapproved ordinary word, and no\nunresolved word.\n\nDo not simulate or replace the subagent pass with a self-review. If you cannot\nstart an independent subagent or complete the pass, give only the incomplete\nreview status and its blocker. Do not include candidate text, partial rewritten\ntext, excerpts, or suggested wording. Do not describe the result as reviewed.\n\nIf the STE rules change necessary meaning or fixed text, give the most accurate\npermitted version. Identify the exact constraint that prevents correct text.\n\nGive only the requested content unless one of these conditions is true:\n\n- The user wants a compliance report.\n- Two rules do not agree.\n- The STE rules change necessary meaning or fixed text.\n","# Write Simplified Technical English\n\nApply ASD-STE100 Issue 9 to the user content.\n\n## Load the working reference\n\nBefore you use this skill, fully read the guide listed below.\n\nDo not read the guide again when both conditions are true:\n\n- You fully read the guide.\n- The full guide stays in the active context.\n\nRead [references\u002FSTE_AGENT_GUIDE.md](references\u002FSTE_AGENT_GUIDE.md).\n\nUse the guide as the primary working authority.\n\nFor an exact rule or dictionary lookup, use an official copy of ASD-STE100\nIssue 9. See\n[references\u002FASD-STE100.md](references\u002FASD-STE100.md)\nfor the official source and important usage limits.\n\nRead the complete rule or dictionary entry, including its help, examples, page\ncontinuation, and supplemental material.\n\nRead all 434 pages only when the user requests a full-standard review and an\nofficial copy is available.\n\n## Apply the standard\n\n1. Identify the source as procedural text, descriptive text, or text with both\n   types.\n2. Keep technical facts, safety meaning, identifiers, interface labels, code,\n   commands, measurements, and necessary terminology.\n3. Apply all applicable writing rules in Part 1.\n4. Use Part 2 to examine each word's meaning and part of speech.\n5. Use each approved word only with its approved meaning and part of speech.\n6. Use a permitted technical noun or technical verb only in an approved\n   category.\n7. Use one term for one concept.\n8. Remove ambiguity before you make the text shorter.\n9. Keep quoted material exact.\n10. Clearly identify quoted non-STE text.\n11. Obey project or customer rules that have more limits when the necessary\n    meaning does not change.\n12. If two rules do not agree, tell the user.\n\n## Examine the result\n\nDo the independent final compliance pass in Section 15 of the guide. This pass\nis mandatory:\n\n1. Start a fresh subagent that did not write the candidate text.\n2. Use a context-free subagent when the platform supports it. Give the\n   subagent only the source or requirements, the candidate text, the\n   unverified candidate terminology list, and the path to the guide. Give it\n   the official Issue 9 PDF when it is available.\n3. Tell the subagent to do only the reviewer role in Section 15 and not to\n   delegate the review.\n4. Require the subagent to examine and record every word occurrence as\n   specified in Section 15.\n5. If the reviewer changes or recommends a change to any wording, treat the\n   result as `CHANGES_REQUIRED`. Resolve each finding and send the complete\n   revised candidate to a different fresh subagent.\n6. Use the exact official entry when the guide does not resolve a word.\n\nGive the result only after the last subagent pass examines the exact final text\nwithout changing it and reports `PASS`, no unapproved ordinary word, and no\nunresolved word.\n\nDo not simulate or replace the subagent pass with a self-review. If you cannot\nstart an independent subagent or complete the pass, give only the incomplete\nreview status and its blocker. Do not include candidate text, partial rewritten\ntext, excerpts, or suggested wording. Do not describe the result as reviewed.\n\nIf the STE rules change necessary meaning or fixed text, give the most accurate\npermitted version. Identify the exact constraint that prevents correct text.\n\nGive only the requested content unless one of these conditions is true:\n\n- The user wants a compliance report.\n- Two rules do not agree.\n- The STE rules change necessary meaning or fixed text.\n",{"name":5,"description":7},"main","9d47db883531c45e29672090c38080c58434b2ac","skills\u002Fwrite-simplified-technical-english",0,"https:\u002F\u002Fgithub.com\u002FMattie\u002Fmattie_skills","https:\u002F\u002Fgithub.com\u002FMattie","2026-11-11 04:41:31",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add Mattie\u002Fmattie_skills --skill write-simplified-technical-english",{"tool":36,"command":37},"bunx","bunx skills add Mattie\u002Fmattie_skills --skill write-simplified-technical-english",{"tool":39,"command":40},"pnpm","pnpm dlx skills add Mattie\u002Fmattie_skills --skill write-simplified-technical-english","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMattie\u002Fmattie_skills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-simplified-technical-english\u002FSKILL.md",true,[44,50,54],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"agents\u002Fopenai.yaml","REFERENCE","参考文档",302,"https:\u002F\u002Fgithub.com\u002FMattie\u002Fmattie_skills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-simplified-technical-english\u002Fagents\u002Fopenai.yaml",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002FASD-STE100.md",1652,"https:\u002F\u002Fgithub.com\u002FMattie\u002Fmattie_skills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-simplified-technical-english\u002Freferences\u002FASD-STE100.md",{"path":55,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002FSTE_AGENT_GUIDE.md",38730,"https:\u002F\u002Fgithub.com\u002FMattie\u002Fmattie_skills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-simplified-technical-english\u002Freferences\u002FSTE_AGENT_GUIDE.md",[59,66,73,80,87,94],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M79TFMJCP75Z4GP1KYZAYS6D","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.","https:\u002F\u002Fgithub.com\u002FMattie\u002Fmattie_skills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-plainly\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M79TFBYC0GZ9YRR116EM267V","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.","https:\u002F\u002Fgithub.com\u002FMattie\u002Fmattie_skills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-humanly\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M79TF7FDRZT52QCH1CJEK578","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?","https:\u002F\u002Fgithub.com\u002FMattie\u002Fmattie_skills\u002Fblob\u002Fmain\u002Fskills\u002Fwhat-what\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M79TF445Z9P7WCN4B8C4QF4A","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.","https:\u002F\u002Fgithub.com\u002FMattie\u002Fmattie_skills\u002Fblob\u002Fmain\u002Fskills\u002Fwhat-huh\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":18},"01M79TF04KA3NCW5NFB34B7JP2","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.","https:\u002F\u002Fgithub.com\u002FMattie\u002Fmattie_skills\u002Fblob\u002Fmain\u002Fskills\u002Fverifier-system\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":18},"01M79TEW14B8Q8425XCJDJ7TXR","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\u002Fproject-management.md along with the projectbot skill if needed.","https:\u002F\u002Fgithub.com\u002FMattie\u002Fmattie_skills\u002Fblob\u002Fmain\u002Fskills\u002Ftodo\u002FSKILL.md",[],[]]