[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6X10MSAXWD2E7D71SFXY32X":3,"skill-same:01M6X10MSAXWD2E7D71SFXY32X":60},{"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":18,"publishedAt":28,"linkOnly":29,"markdownContent":30,"markdownBody":31,"frontMatter":32,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":41,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":44,"updatedAt":45,"install":46,"resources":59},"01M6X10MSAXWD2E7D71SFXY32X","humanizer",null,"Tone enforcement patterns for external-facing community responses","github\u002Fsquad","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6X0MZ6B0WYMMDPK3Q61KER6",3391,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fsquad\u002Fblob\u002Fdev\u002F.squad-templates\u002Fskills\u002Fhumanizer\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27],"workflow","communication","enforcement","community","patterns","tone","communications","manual","for","2026-11-10 10:12:30",false,"---\nname: \"humanizer\"\ndescription: \"Tone enforcement patterns for external-facing community responses\"\ndomain: \"communication, tone, community\"\nconfidence: \"low\"\nsource: \"manual (external communications workflow)\"\n---\n\n## Context\n\nUse this skill whenever the communications owner drafts external-facing responses for issues or discussions.\n\n- Tone must be warm, helpful, and human-sounding — never robotic or corporate.\n- The repository's communication policy applies everywhere: **Humanized tone is mandatory**.\n- This applies to **all external-facing content** drafted by the communications owner in Phase 1 issues\u002Fdiscussions workflows.\n\n## Patterns\n\n1. **Warm opening** — Start with acknowledgment (\"Thanks for reporting this\", \"Great question!\")\n2. **Active voice** — \"We're looking into this\" not \"This is being investigated\"\n3. **Second person** — Address the person directly (\"you\" not \"the user\")\n4. **Conversational connectors** — \"That said...\", \"Here's what we found...\", \"Quick note:\"\n5. **Specific, not vague** — \"This affects the casting module in v0.8.x\" not \"We are aware of issues\"\n6. **Empathy markers** — \"I can see how that would be frustrating\", \"Good catch!\"\n7. **Action-oriented closes** — \"Let us know if that helps!\" not \"Please advise if further assistance is required\"\n8. **Uncertainty is OK** — \"We're not 100% sure yet, but here's what we think is happening...\" is better than false confidence\n9. **Profanity filter** — Never include profanity, slurs, or aggressive language, even when quoting\n10. **Baseline comparison** — Responses should align with tone of 5-10 \"gold standard\" responses (>80% similarity threshold)\n11. **Empathetic disagreement** — \"We hear you. That's a fair concern.\" before explaining the reasoning\n12. **Information request** — Ask for specific details, not open-ended \"can you provide more info?\"\n13. **No link-dumping** — Don't just paste URLs. Provide context: \"Check out the [getting started guide](url) — specifically the section on routing\" not just a bare link\n\n## Examples\n\n### 1. Welcome\n\n```text\nHey {author}! Welcome to Squad ? Thanks for opening this.\n{substantive response}\nLet us know if you have questions — happy to help!\n```\n\n### 2. Troubleshooting\n\n```text\nThanks for the detailed report, {author}!\nHere's what we think is happening: {explanation}\n{steps or workaround}\nLet us know if that helps, or if you're seeing something different.\n```\n\n### 3. Feature guidance\n\n```text\nGreat question! {context on current state}\n{guidance or workaround}\nWe've noted this as a potential improvement — {tracking info if applicable}.\n```\n\n### 4. Redirect\n\n```text\nThanks for reaching out! This one is actually better suited for {correct location}.\n{brief explanation of why}\nFeel free to open it there — they'll be able to help!\n```\n\n### 5. Acknowledgment\n\n```text\nGood catch, {author}. We've confirmed this is a real issue.\n{what we know so far}\nWe'll update this thread when we have a fix. Thanks for flagging it!\n```\n\n### 6. Closing\n\n```text\nThis should be resolved in {version\u002FPR}! ?\n{brief summary of what changed}\nThanks for reporting this, {author} — it made Squad better.\n```\n\n### 7. Technical uncertainty\n\n```text\nInteresting find, {author}. We're not 100% sure what's causing this yet.\nHere's what we've ruled out: {list}\nWe'd love more context if you have it — {specific ask}.\nWe'll dig deeper and update this thread.\n```\n\n## Anti-Patterns\n\n- ❌ Corporate speak: \"We appreciate your patience as we investigate this matter\"\n- ❌ Marketing hype: \"Squad is the BEST way to...\" or \"This amazing feature...\"\n- ❌ Passive voice: \"It has been determined that...\" or \"The issue is being tracked\"\n- ❌ Dismissive: \"This works as designed\" without empathy\n- ❌ Over-promising: \"We'll ship this next week\" without commitment from the team\n- ❌ Empty acknowledgment: \"Thanks for your feedback\" with no substance\n- ❌ Robot signatures: \"Best regards, Communications Team\" or \"Sincerely, The Squad Team\"\n- ❌ Excessive emoji: More than 1-2 emoji per response\n- ❌ Quoting profanity: Even when the original issue contains it, paraphrase instead\n- ❌ Link-dumping: Pasting URLs without context (\"See: https:\u002F\u002F...\")\n- ❌ Open-ended info requests: \"Can you provide more information?\" without specifying what information\n","## Context\n\nUse this skill whenever the communications owner drafts external-facing responses for issues or discussions.\n\n- Tone must be warm, helpful, and human-sounding — never robotic or corporate.\n- The repository's communication policy applies everywhere: **Humanized tone is mandatory**.\n- This applies to **all external-facing content** drafted by the communications owner in Phase 1 issues\u002Fdiscussions workflows.\n\n## Patterns\n\n1. **Warm opening** — Start with acknowledgment (\"Thanks for reporting this\", \"Great question!\")\n2. **Active voice** — \"We're looking into this\" not \"This is being investigated\"\n3. **Second person** — Address the person directly (\"you\" not \"the user\")\n4. **Conversational connectors** — \"That said...\", \"Here's what we found...\", \"Quick note:\"\n5. **Specific, not vague** — \"This affects the casting module in v0.8.x\" not \"We are aware of issues\"\n6. **Empathy markers** — \"I can see how that would be frustrating\", \"Good catch!\"\n7. **Action-oriented closes** — \"Let us know if that helps!\" not \"Please advise if further assistance is required\"\n8. **Uncertainty is OK** — \"We're not 100% sure yet, but here's what we think is happening...\" is better than false confidence\n9. **Profanity filter** — Never include profanity, slurs, or aggressive language, even when quoting\n10. **Baseline comparison** — Responses should align with tone of 5-10 \"gold standard\" responses (>80% similarity threshold)\n11. **Empathetic disagreement** — \"We hear you. That's a fair concern.\" before explaining the reasoning\n12. **Information request** — Ask for specific details, not open-ended \"can you provide more info?\"\n13. **No link-dumping** — Don't just paste URLs. Provide context: \"Check out the [getting started guide](url) — specifically the section on routing\" not just a bare link\n\n## Examples\n\n### 1. Welcome\n\n```text\nHey {author}! Welcome to Squad ? Thanks for opening this.\n{substantive response}\nLet us know if you have questions — happy to help!\n```\n\n### 2. Troubleshooting\n\n```text\nThanks for the detailed report, {author}!\nHere's what we think is happening: {explanation}\n{steps or workaround}\nLet us know if that helps, or if you're seeing something different.\n```\n\n### 3. Feature guidance\n\n```text\nGreat question! {context on current state}\n{guidance or workaround}\nWe've noted this as a potential improvement — {tracking info if applicable}.\n```\n\n### 4. Redirect\n\n```text\nThanks for reaching out! This one is actually better suited for {correct location}.\n{brief explanation of why}\nFeel free to open it there — they'll be able to help!\n```\n\n### 5. Acknowledgment\n\n```text\nGood catch, {author}. We've confirmed this is a real issue.\n{what we know so far}\nWe'll update this thread when we have a fix. Thanks for flagging it!\n```\n\n### 6. Closing\n\n```text\nThis should be resolved in {version\u002FPR}! ?\n{brief summary of what changed}\nThanks for reporting this, {author} — it made Squad better.\n```\n\n### 7. Technical uncertainty\n\n```text\nInteresting find, {author}. We're not 100% sure what's causing this yet.\nHere's what we've ruled out: {list}\nWe'd love more context if you have it — {specific ask}.\nWe'll dig deeper and update this thread.\n```\n\n## Anti-Patterns\n\n- ❌ Corporate speak: \"We appreciate your patience as we investigate this matter\"\n- ❌ Marketing hype: \"Squad is the BEST way to...\" or \"This amazing feature...\"\n- ❌ Passive voice: \"It has been determined that...\" or \"The issue is being tracked\"\n- ❌ Dismissive: \"This works as designed\" without empathy\n- ❌ Over-promising: \"We'll ship this next week\" without commitment from the team\n- ❌ Empty acknowledgment: \"Thanks for your feedback\" with no substance\n- ❌ Robot signatures: \"Best regards, Communications Team\" or \"Sincerely, The Squad Team\"\n- ❌ Excessive emoji: More than 1-2 emoji per response\n- ❌ Quoting profanity: Even when the original issue contains it, paraphrase instead\n- ❌ Link-dumping: Pasting URLs without context (\"See: https:\u002F\u002F...\")\n- ❌ Open-ended info requests: \"Can you provide more information?\" without specifying what information\n",{"name":5,"domain":33,"source":34,"confidence":35,"description":7},"communication, tone, community","manual (external communications workflow)","low","dev","7b731ec97f35346bdc4fa87c3edaf16b808fc0ae",".squad-templates\u002Fskills\u002Fhumanizer",520,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fsquad","https:\u002F\u002Fgithub.github.io\u002Fsquad\u002F","https:\u002F\u002Fgithub.com\u002Fgithub","https:\u002F\u002Fgithub.com\u002Fabout","How people build software.","2026-11-15 02:13:59",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add github\u002Fsquad --skill humanizer",{"tool":52,"command":53},"bunx","bunx skills add github\u002Fsquad --skill humanizer",{"tool":55,"command":56},"pnpm","pnpm dlx skills add github\u002Fsquad --skill humanizer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fsquad\u002Fblob\u002Fdev\u002F.squad-templates\u002Fskills\u002Fhumanizer\u002FSKILL.md",true,[],[61,69,76,83,90,97],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":68},"01M76752CVNE7K6NWD59CRAYNJ","windows-compatibility","Cross-platform path handling and command patterns","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fsquad\u002Fblob\u002Fdev\u002Fplugins\u002Fsquad\u002Fskills\u002Fwindows-compatibility\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":68},"01M767508W8A4G83NX1FKEW5VN","versioning-policy","SemVer rules for Squad's stable, preview, insider, and local package versions","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fsquad\u002Fblob\u002Fdev\u002Fplugins\u002Fsquad\u002Fskills\u002Fversioning-policy\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":68},"01M7674X5JJKNJ74B3SS8PGXG2","tiered-memory","Three-tier agent memory model (hot\u002Fcold\u002Fwiki) for context reduction per spawn","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fsquad\u002Fblob\u002Fdev\u002Fplugins\u002Fsquad\u002Fskills\u002Ftiered-memory\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":68},"01M7674V3S9H03A76H75M1KSAF","test-discipline","Design assertions that prove the actual contract and fail on realistic regressions","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fsquad\u002Fblob\u002Fdev\u002Fplugins\u002Fsquad\u002Fskills\u002Ftest-discipline\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":68},"01M7674QB8CA61RNDX2Z0NAK71","squad","Squad's command catalog and interactive menu. Invoke via \u002Fsquad (slash command) or natural language (\"squad commands\", \"what can squad do\", \"show me squad options\"). Presents categorized operations (Install & Upgrade, Team Management, Issues & PRs, Plugins & Skills, Model & Cost, Sessions & State) as an interactive picker. Routes to the right squad CLI command or the Squad coordinator agent.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fsquad\u002Fblob\u002Fdev\u002Fplugins\u002Fsquad\u002Fskills\u002Fsquad\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":68},"01M7674KTQ632N30HQB1TP7TXH","squad-version-check","Internals of how @bradygaster\u002Fsquad-cli stamps its version, how `squad upgrade` works (what it preserves vs overwrites), and how to probe the npm registry for the latest version from a coordinator prompt.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fsquad\u002Fblob\u002Fdev\u002Fplugins\u002Fsquad\u002Fskills\u002Fsquad-version-check\u002FSKILL.md",[],[]]