[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6P02DENRHN6KVGYC55FKASJ":3,"skill-same:01M6P02DENRHN6KVGYC55FKASJ":105},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":6,"ownerHtmlUrl":59,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":60,"install":61,"resources":74},"01M6P02DENRHN6KVGYC55FKASJ","writing-clearly-and-concisely",null,"Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.","mattonweb\u002Fai-assistant-foundry","mattonweb","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F2309734?v=4","01M6NQYCY846TKYN2ZCRS71WQ7","Matt Johnson","01M6NQYD2NPAQEFVD8TW9W0SVX",1,"MIT","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsoftaworks\u002Fwriting-clearly-and-concisely\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"concisely","writing clearly and concisely","writing","read","for","more","timeless","error","professional","prose","reports","use","Rules","text","commit messages","messages","error messages","ui","documentation","commit","2026-11-10 10:12:30",false,"---\nname: writing-clearly-and-concisely\ndescription: Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.\n---\n\n# Writing Clearly and Concisely\n\n## Overview\n\nWrite with clarity and force. This skill covers what to do (Strunk) and what not to do (AI patterns).\n\n## When to Use This Skill\n\nUse this skill whenever you write prose for humans:\n\n- Documentation, README files, technical explanations\n- Commit messages, pull request descriptions\n- Error messages, UI copy, help text, comments\n- Reports, summaries, or any explanation\n- Editing to improve clarity\n\n**If you're writing sentences for a human to read, use this skill.**\n\n## Limited Context Strategy\n\nWhen context is tight:\n\n1. Write your draft using judgment\n2. Dispatch a subagent with your draft and the relevant section file\n3. Have the subagent copyedit and return the revision\n\nLoading a single section (~1,000-4,500 tokens) instead of everything saves significant context.\n\n## Elements of Style\n\nWilliam Strunk Jr.'s *The Elements of Style* (1918) teaches you to write clearly and cut ruthlessly.\n\n### Rules\n\n**Elementary Rules of Usage (Grammar\u002FPunctuation)**:\n\n1. Form possessive singular by adding 's\n2. Use comma after each term in series except last\n3. Enclose parenthetic expressions between commas\n4. Comma before conjunction introducing co-ordinate clause\n5. Don't join independent clauses by comma\n6. Don't break sentences in two\n7. Participial phrase at beginning refers to grammatical subject\n\n**Elementary Principles of Composition**:\n\n8. One paragraph per topic\n9. Begin paragraph with topic sentence\n10. **Use active voice**\n11. **Put statements in positive form**\n12. **Use definite, specific, concrete language**\n13. **Omit needless words**\n14. Avoid succession of loose sentences\n15. Express co-ordinate ideas in similar form\n16. **Keep related words together**\n17. Keep to one tense in summaries\n18. **Place emphatic words at end of sentence**\n\n### Reference Files\n\nThe rules above are summarized from Strunk's original text. For complete explanations with examples:\n\n| Section | File | ~Tokens |\n|---------|------|---------|\n| Grammar, punctuation, comma rules | `02-elementary-rules-of-usage.md` | 2,500 |\n| Paragraph structure, active voice, concision | `03-elementary-principles-of-composition.md` | 4,500 |\n| Headings, quotations, formatting | `04-a-few-matters-of-form.md` | 1,000 |\n| Word choice, common errors | `05-words-and-expressions-commonly-misused.md` | 4,000 |\n\n**Most tasks need only `03-elementary-principles-of-composition.md`** — it covers active voice, positive form, concrete language, and omitting needless words.\n\n## AI Writing Patterns to Avoid\n\nLLMs regress to statistical means, producing generic, puffy prose. Avoid:\n\n- **Puffery:** pivotal, crucial, vital, testament, enduring legacy\n- **Empty \"-ing\" phrases:** ensuring reliability, showcasing features, highlighting capabilities\n- **Promotional adjectives:** groundbreaking, seamless, robust, cutting-edge\n- **Overused AI vocabulary:** delve, leverage, multifaceted, foster, realm, tapestry\n- **Formatting overuse:** excessive bullets, emoji decorations, bold on every other word\n\nBe specific, not grandiose. Say what it actually does.\n\nFor comprehensive research on why these patterns occur, see `signs-of-ai-writing.md`. Wikipedia editors developed this guide to detect AI-generated submissions — their patterns are well-documented and field-tested.\n\n## Bottom Line\n\nWriting for humans? Load the relevant section from `elements-of-style\u002F` and apply the rules. For most tasks, `03-elementary-principles-of-composition.md` covers what matters most.\n","# Writing Clearly and Concisely\n\n## Overview\n\nWrite with clarity and force. This skill covers what to do (Strunk) and what not to do (AI patterns).\n\n## When to Use This Skill\n\nUse this skill whenever you write prose for humans:\n\n- Documentation, README files, technical explanations\n- Commit messages, pull request descriptions\n- Error messages, UI copy, help text, comments\n- Reports, summaries, or any explanation\n- Editing to improve clarity\n\n**If you're writing sentences for a human to read, use this skill.**\n\n## Limited Context Strategy\n\nWhen context is tight:\n\n1. Write your draft using judgment\n2. Dispatch a subagent with your draft and the relevant section file\n3. Have the subagent copyedit and return the revision\n\nLoading a single section (~1,000-4,500 tokens) instead of everything saves significant context.\n\n## Elements of Style\n\nWilliam Strunk Jr.'s *The Elements of Style* (1918) teaches you to write clearly and cut ruthlessly.\n\n### Rules\n\n**Elementary Rules of Usage (Grammar\u002FPunctuation)**:\n\n1. Form possessive singular by adding 's\n2. Use comma after each term in series except last\n3. Enclose parenthetic expressions between commas\n4. Comma before conjunction introducing co-ordinate clause\n5. Don't join independent clauses by comma\n6. Don't break sentences in two\n7. Participial phrase at beginning refers to grammatical subject\n\n**Elementary Principles of Composition**:\n\n8. One paragraph per topic\n9. Begin paragraph with topic sentence\n10. **Use active voice**\n11. **Put statements in positive form**\n12. **Use definite, specific, concrete language**\n13. **Omit needless words**\n14. Avoid succession of loose sentences\n15. Express co-ordinate ideas in similar form\n16. **Keep related words together**\n17. Keep to one tense in summaries\n18. **Place emphatic words at end of sentence**\n\n### Reference Files\n\nThe rules above are summarized from Strunk's original text. For complete explanations with examples:\n\n| Section | File | ~Tokens |\n|---------|------|---------|\n| Grammar, punctuation, comma rules | `02-elementary-rules-of-usage.md` | 2,500 |\n| Paragraph structure, active voice, concision | `03-elementary-principles-of-composition.md` | 4,500 |\n| Headings, quotations, formatting | `04-a-few-matters-of-form.md` | 1,000 |\n| Word choice, common errors | `05-words-and-expressions-commonly-misused.md` | 4,000 |\n\n**Most tasks need only `03-elementary-principles-of-composition.md`** — it covers active voice, positive form, concrete language, and omitting needless words.\n\n## AI Writing Patterns to Avoid\n\nLLMs regress to statistical means, producing generic, puffy prose. Avoid:\n\n- **Puffery:** pivotal, crucial, vital, testament, enduring legacy\n- **Empty \"-ing\" phrases:** ensuring reliability, showcasing features, highlighting capabilities\n- **Promotional adjectives:** groundbreaking, seamless, robust, cutting-edge\n- **Overused AI vocabulary:** delve, leverage, multifaceted, foster, realm, tapestry\n- **Formatting overuse:** excessive bullets, emoji decorations, bold on every other word\n\nBe specific, not grandiose. Say what it actually does.\n\nFor comprehensive research on why these patterns occur, see `signs-of-ai-writing.md`. Wikipedia editors developed this guide to detect AI-generated submissions — their patterns are well-documented and field-tested.\n\n## Bottom Line\n\nWriting for humans? Load the relevant section from `elements-of-style\u002F` and apply the rules. For most tasks, `03-elementary-principles-of-composition.md` covers what matters most.\n",{"name":5,"description":7},"main","d8518247cb8ab8b2dac57a6be33543ffd23b97c5","write-technical\u002Fsoftaworks\u002Fwriting-clearly-and-concisely",0,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry","https:\u002F\u002Fgithub.com\u002Fmattonweb","2026-05-29 08:42:23",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add mattonweb\u002Fai-assistant-foundry --skill writing-clearly-and-concisely",{"tool":67,"command":68},"bunx","bunx skills add mattonweb\u002Fai-assistant-foundry --skill writing-clearly-and-concisely",{"tool":70,"command":71},"pnpm","pnpm dlx skills add mattonweb\u002Fai-assistant-foundry --skill writing-clearly-and-concisely","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsoftaworks\u002Fwriting-clearly-and-concisely\u002FSKILL.md",true,[75,81,85,89,93,97,101],{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"elements-of-style\u002F01-introductory.md","REFERENCE","参考文档",303,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsoftaworks\u002Fwriting-clearly-and-concisely\u002Felements-of-style\u002F01-introductory.md",{"path":82,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":83,"sourceHtmlUrl":84},"elements-of-style\u002F02-elementary-rules-of-usage.md",12168,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsoftaworks\u002Fwriting-clearly-and-concisely\u002Felements-of-style\u002F02-elementary-rules-of-usage.md",{"path":86,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":87,"sourceHtmlUrl":88},"elements-of-style\u002F03-elementary-principles-of-composition.md",33622,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsoftaworks\u002Fwriting-clearly-and-concisely\u002Felements-of-style\u002F03-elementary-principles-of-composition.md",{"path":90,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":91,"sourceHtmlUrl":92},"elements-of-style\u002F04-a-few-matters-of-form.md",4918,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsoftaworks\u002Fwriting-clearly-and-concisely\u002Felements-of-style\u002F04-a-few-matters-of-form.md",{"path":94,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":95,"sourceHtmlUrl":96},"elements-of-style\u002F05-words-and-expressions-commonly-misused.md",22310,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsoftaworks\u002Fwriting-clearly-and-concisely\u002Felements-of-style\u002F05-words-and-expressions-commonly-misused.md",{"path":98,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":99,"sourceHtmlUrl":100},"README.md",6078,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsoftaworks\u002Fwriting-clearly-and-concisely\u002FREADME.md",{"path":102,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":103,"sourceHtmlUrl":104},"signs-of-ai-writing.md",94774,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsoftaworks\u002Fwriting-clearly-and-concisely\u002Fsigns-of-ai-writing.md",[106,120,140,161,187,210],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":49},"01M6P0286HZ8RWMFCCPC8HF7SC","crafting-effective-readmes","Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsoftaworks\u002Fcrafting-effective-readmes\u002FSKILL.md",[],[113,114,115,116,117,40,118,119,31],"crafting effective readmes","type","project","guidance","files","README","templates",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":129,"publishedAt":49},"01M6P025A41BBTPWVTZ3GFQVG6","wiki-architect","You are a documentation architect that produces structured wiki catalogues and onboarding guides from codebases.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsickn33\u002Fwiki-architect\u002FSKILL.md",[126],{"categoryNo":127,"categoryName":128,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000038","人力资源",[130,131,132,133,134,135,136,137,138,139,47],"wiki","architect","wiki architect","documentation architect","unknown","you","guides","structured","community","onboarding",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":49},"01M6P01NSKPXP77NWB4K0PXRK5","readme","You are an expert technical writer creating comprehensive project documentation. Your goal is to write a README.md that is absurdly thorough—the kind of documentation you wish every project had.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsickn33\u002Freadme\u002FSKILL.md",[],[118,147,54,148,149,150,115,151,152,153,154,47,155,156,157,158,159,160,135],"write","expert","writer","wish","goal","technical writer","technical","https","github","safe","write a readme","project documentation","tree","kind",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":167,"publishedAt":49},"01M6P01GP0NEN8KT3A3SA6ZFVE","ubiquitous-language","Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions \"domain model\" or \"DDD\".","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fmattpocock\u002Fubiquitous-language\u002FSKILL.md",[],[168,169,170,171,172,173,174,175,176,177,178,179,40,180,181,182,183,184,185,186],"ubiquitous language","language","style","true","canonical","model","harden","domain model","domain","terminology","conversation","build","extract","user","glossary","define","terms","ddd","create",{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":191,"categories":192,"keywords":195,"publishedAt":49},"01M6P01BJBP9XP4TDRT7QD1ZVA","technical-writing-style","Enforce clear, direct writing in software development documents including OKRs, PRDs, tech specs, architecture decision records (ADRs), git commit messages, PR descriptions, READMEs, changelogs, runbooks, incident postmortems, API docs, and onboarding guides. Trigger whenever a user asks to write, edit, revise, or review any of these document types. Also trigger when the user says writing \"sounds like AI\", \"feels robotic\", \"needs polish\", or asks to \"make it sound more natural\" in the context of technical or professional prose. Do not trigger for fiction, poetry, creative writing, academic papers, or legal documents unless the user explicitly asks for a more natural tone.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fmattnebr\u002Ftechnical-writing-style\u002FSKILL.md",[193,194],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[153,196,31,197,198,170,199,200,44,201,202,48,203,204,205,206,207,37,208,209],"technical writing","technical writing style","writing style","decision","api","documents","architecture","review","Poetry","papers","types","runbooks","software development","incident",{"skillNo":211,"name":212,"nameZh":6,"description":213,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":214,"categories":215,"keywords":219,"publishedAt":49},"01M6P00VB9MFBY3FWYZ11V1783","tldr-prompt","Create tldr summaries for GitHub Copilot files (prompts, agents, instructions, collections), MCP servers, or documentation from URLs and queries.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fgithub\u002Ftldr-prompt\u002FSKILL.md",[216],{"categoryNo":217,"categoryName":218,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[220,221,222,223,224,225,226,33,227,117,228,229,230,186,47,231,232,155],"prompt","tldr","tldr prompt","MCP","collections","servers","summaries","queries","prompts","instructions","mcp servers","copilot","github copilot"]