[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DNHTP9MMC8RW3FTMKJP387":3,"skill-same:01M7DNHTP9MMC8RW3FTMKJP387":57},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":13,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7DNHTP9MMC8RW3FTMKJP387","plain-english",null,"Write English in ASD-STE100 Simplified Technical English at a chosen strictness - 80% of the way to ASD-STE100 by default, 50% or 100% on request. Use when the user asks for ASD-STE100, STE, Simplified Technical English, \"80% of the way to ASD-STE100\", or for plain, simple, clear or controlled English; when the user asks to clean up, simplify or rewrite text in plain English (a PR description, docs, a summary, a status update, an error message); and when you write text that a busy reader or another agent must parse fast.","oshnilia\u002Fclaude-plugins","oshnilia","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F217062862?v=4","01M7DNH04C4VFXNF03F26WERDY","01M7DNH050H4ZTPVYZP0S6SHAY",0,"MIT","https:\u002F\u002Fgithub.com\u002Foshnilia\u002Fclaude-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Flegible\u002Fskills\u002Fplain-english\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: plain-english\ndescription: Write English in ASD-STE100 Simplified Technical English at a chosen strictness - 80% of the way to ASD-STE100 by default, 50% or 100% on request. Use when the user asks for ASD-STE100, STE, Simplified Technical English, \"80% of the way to ASD-STE100\", or for plain, simple, clear or controlled English; when the user asks to clean up, simplify or rewrite text in plain English (a PR description, docs, a summary, a status update, an error message); and when you write text that a busy reader or another agent must parse fast.\nlicense: MIT\nmetadata:\n  version: 0.2.0\n---\n\n# Plain English: ASD-STE100, 80% of the way\n\nWrite in **ASD-STE100 Simplified Technical English**. You know this standard: its writing rules and its approved\nwords, each with one meaning. Use that knowledge. The level sets how far you go:\n\n| Level | Ask yourself for | Use for |\n|---|---|---|\n| plain-50 | about 50% of the way to ASD-STE100 | chat, a light polish |\n| **plain-80** (default) | 80% of the way to ASD-STE100 | answers, docs, PRs, summaries |\n| plain-100 | ASD-STE100 in full: its rules and its approved words only | procedures, safety text, agent-to-agent text |\n\nAt plain-80 the sentences follow STE, but the text still reads like normal prose: keep a precise technical word when\nthe approved word would lose meaning. At plain-100 use only words you know to be approved, and only can, will or must.\n\nThe STE sentence rules hold at plain-80 and plain-100: one verb, never a phrasal verb (\"configure\", not \"set up\";\n\"do\", not \"go through\"); active voice; simple tenses; no contractions; no semicolons; one instruction per sentence,\nthe condition first; 20 words or fewer for an instruction, 25 for a description; no more than 3 nouns in a row.\n\n## What must not change\n\n1. Keep every fact of the source and add none. The rewrite does not say more than the source.\n2. Do not invent who acts. If the source names no actor, make the receiver the subject (\"the person on call gets a\n   notification\"), use an imperative step, or keep the passive for that one sentence. Never \"we\", \"the system\".\n3. Keep the strength of every hedge at plain-50 and plain-80: \"should probably fix\" stays \"probably fixes\", \"may have\n   failed\" stays. At plain-100, keep the uncertainty with \"can\" or a word such as \"possibly\".\n4. Keep code identifiers, file names, commands and product names exactly as they are.\n5. Put the answer first. Then the reasons.\n\n## What to output\n\n- The text only. No preamble, no list of changes, no rule table, unless the user asks why.\n- If you kept a longer phrase on purpose because a shorter one loses precision, add one last line:\n  `Kept as-is: \"\u003Cphrase>\" - \u003Cwhat would be lost>`. Leave the line out when there is nothing to report.\n- At plain-100, mark each sentence where you had to break a rule with `‡`, and end with one line\n  `STE deviations: \u003Crule> - \u003Cwhy>`.\n- Never say or imply that a text complies with ASD-STE100, conforms to it or is certified. ASD-STE100 is a trademark of\n  ASD. You may say \"written to ASD-STE100, 80% of the way\".\n- Write your own words in the same style: no contractions, no semicolons, in any note you add.\n\n## Measure, if you have a shell\n\nWhen a shell tool (Bash) is available and the user asked for a level or a score, run the structural scorer and fix\nwhat it reports:\n\n```bash\npython3 \"${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fste_score.py\" --level 80 draft.md\n```\n\nUse `-` for stdin and `--json` for machine output. On Windows, when `python3` is not found, use `python` or `py -3`.\nThen end with one line: `plain-80: 92%`.\n\nWhen there is no shell tool, do not try to run the scorer in any other way, do not start a subagent for it, and say\nnothing about it. Give no number. The scorer checks only sentence structure. It cannot check words.\n\nRules in our own words, with what the scorer checks: [references\u002Frules.md](references\u002Frules.md).\n","# Plain English: ASD-STE100, 80% of the way\n\nWrite in **ASD-STE100 Simplified Technical English**. You know this standard: its writing rules and its approved\nwords, each with one meaning. Use that knowledge. The level sets how far you go:\n\n| Level | Ask yourself for | Use for |\n|---|---|---|\n| plain-50 | about 50% of the way to ASD-STE100 | chat, a light polish |\n| **plain-80** (default) | 80% of the way to ASD-STE100 | answers, docs, PRs, summaries |\n| plain-100 | ASD-STE100 in full: its rules and its approved words only | procedures, safety text, agent-to-agent text |\n\nAt plain-80 the sentences follow STE, but the text still reads like normal prose: keep a precise technical word when\nthe approved word would lose meaning. At plain-100 use only words you know to be approved, and only can, will or must.\n\nThe STE sentence rules hold at plain-80 and plain-100: one verb, never a phrasal verb (\"configure\", not \"set up\";\n\"do\", not \"go through\"); active voice; simple tenses; no contractions; no semicolons; one instruction per sentence,\nthe condition first; 20 words or fewer for an instruction, 25 for a description; no more than 3 nouns in a row.\n\n## What must not change\n\n1. Keep every fact of the source and add none. The rewrite does not say more than the source.\n2. Do not invent who acts. If the source names no actor, make the receiver the subject (\"the person on call gets a\n   notification\"), use an imperative step, or keep the passive for that one sentence. Never \"we\", \"the system\".\n3. Keep the strength of every hedge at plain-50 and plain-80: \"should probably fix\" stays \"probably fixes\", \"may have\n   failed\" stays. At plain-100, keep the uncertainty with \"can\" or a word such as \"possibly\".\n4. Keep code identifiers, file names, commands and product names exactly as they are.\n5. Put the answer first. Then the reasons.\n\n## What to output\n\n- The text only. No preamble, no list of changes, no rule table, unless the user asks why.\n- If you kept a longer phrase on purpose because a shorter one loses precision, add one last line:\n  `Kept as-is: \"\u003Cphrase>\" - \u003Cwhat would be lost>`. Leave the line out when there is nothing to report.\n- At plain-100, mark each sentence where you had to break a rule with `‡`, and end with one line\n  `STE deviations: \u003Crule> - \u003Cwhy>`.\n- Never say or imply that a text complies with ASD-STE100, conforms to it or is certified. ASD-STE100 is a trademark of\n  ASD. You may say \"written to ASD-STE100, 80% of the way\".\n- Write your own words in the same style: no contractions, no semicolons, in any note you add.\n\n## Measure, if you have a shell\n\nWhen a shell tool (Bash) is available and the user asked for a level or a score, run the structural scorer and fix\nwhat it reports:\n\n```bash\npython3 \"${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fste_score.py\" --level 80 draft.md\n```\n\nUse `-` for stdin and `--json` for machine output. On Windows, when `python3` is not found, use `python` or `py -3`.\nThen end with one line: `plain-80: 92%`.\n\nWhen there is no shell tool, do not try to run the scorer in any other way, do not start a subagent for it, and say\nnothing about it. Give no number. The scorer checks only sentence structure. It cannot check words.\n\nRules in our own words, with what the scorer checks: [references\u002Frules.md](references\u002Frules.md).\n",{"name":5,"license":14,"metadata":23,"description":7},{"version":24},"0.2.0","main","023dab66d8d3e858a741fdb858c7fdecbb2b01bd","plugins\u002Flegible\u002Fskills\u002Fplain-english","https:\u002F\u002Fgithub.com\u002Foshnilia\u002Fclaude-plugins","https:\u002F\u002Fgithub.com\u002Foshnilia","2026-10-10 15:05:44",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add oshnilia\u002Fclaude-plugins --skill plain-english",{"tool":37,"command":38},"bunx","bunx skills add oshnilia\u002Fclaude-plugins --skill plain-english",{"tool":40,"command":41},"pnpm","pnpm dlx skills add oshnilia\u002Fclaude-plugins --skill plain-english","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Foshnilia\u002Fclaude-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Flegible\u002Fskills\u002Fplain-english\u002FSKILL.md",true,[45,51],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"references\u002Frules.md","REFERENCE","参考文档",3034,"https:\u002F\u002Fgithub.com\u002Foshnilia\u002Fclaude-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Flegible\u002Fskills\u002Fplain-english\u002Freferences\u002Frules.md",{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"scripts\u002Fste_score.py","SCRIPT","脚本",15334,"https:\u002F\u002Fgithub.com\u002Foshnilia\u002Fclaude-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Flegible\u002Fskills\u002Fplain-english\u002Fscripts\u002Fste_score.py",[58,65,72,79,85,91],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":18},"01M7DNJYZBP8FPEH7HYH9336Y9","take","Take a ticket from the project's Obsidian board into work - pick it, turn it into the task brief, set its status. Use when the person asks to take, start or pick up a ticket or task from the Obsidian board, asks what is next on the board (\"возьми тикет\", \"что дальше по доске\"), names a card or a note of the bound board, or runs \u002Fobsidian-tasks:take.","https:\u002F\u002Fgithub.com\u002Foshnilia\u002Fclaude-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fobsidian-tasks\u002Fskills\u002Ftake\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M7DNJV4T31K53KH1PWEXT7MG","setup","Bind this project to a task board in an Obsidian vault (a Kanban plugin board or a Bases board), or create one, and choose how Claude reaches the vault - its folder, the Obsidian CLI or an Obsidian MCP server. Use when the person asks to connect an Obsidian board or vault to the project, to change the board, or to check the binding (\"подключи доску из Obsidian\", \"настрой obsidian-tasks\"), or runs \u002Fobsidian-tasks:setup.","https:\u002F\u002Fgithub.com\u002Foshnilia\u002Fclaude-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fobsidian-tasks\u002Fskills\u002Fsetup\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M7DNJR08R8A3XE5APDHGYM49","rules","The rules for this project's Obsidian task board - keep the ticket's status, write the closing report, file new tickets for what is out of scope. The start hook prints them when the project is bound to a board; load them when you work with a ticket and they are not in your context.","https:\u002F\u002Fgithub.com\u002Foshnilia\u002Fclaude-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fobsidian-tasks\u002Fskills\u002Frules\u002FSKILL.md",[],[],{"skillNo":80,"name":60,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M7DNJMBY8899ARANRNRGGGRC","Take a ticket from the project's Notion board into work - pick it, turn it into the task brief, set its status. Use when the person asks to take, start or pick up a ticket or task from Notion, asks what is next on the board (\"возьми тикет\", \"что дальше по доске\"), gives a link to a ticket on the bound board, or runs \u002Fnotion-tasks:take.","https:\u002F\u002Fgithub.com\u002Foshnilia\u002Fclaude-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fnotion-tasks\u002Fskills\u002Ftake\u002FSKILL.md",[],[],{"skillNo":86,"name":67,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M7DNJH33S1F8XJ7H3AJ12P9G","Bind this project to a Notion task board, or create a new board, and save the binding in the project. Use when the person asks to connect Notion tasks or a Notion board to the project, to change the board, or to check the binding (\"подключи доску Notion\", \"настрой notion-tasks\"), or runs \u002Fnotion-tasks:setup.","https:\u002F\u002Fgithub.com\u002Foshnilia\u002Fclaude-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fnotion-tasks\u002Fskills\u002Fsetup\u002FSKILL.md",[],[],{"skillNo":92,"name":74,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":18},"01M7DNJE0QY3BMAC7894K37PBW","The rules for this project's Notion task board - keep the ticket's status, write the closing report, file new tickets for what is out of scope. The start hook prints them when the project is bound to a board; load them when you work with a ticket and they are not in your context.","https:\u002F\u002Fgithub.com\u002Foshnilia\u002Fclaude-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fnotion-tasks\u002Fskills\u002Frules\u002FSKILL.md",[],[]]