[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ADABDP0JHHJHB1SXR7PB3Z":3,"skill-same:01M6ADABDP0JHHJHB1SXR7PB3Z":66},{"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},"01M6ADABDP0JHHJHB1SXR7PB3Z","humanizer",null,"Tone enforcement patterns for external-facing community responses","github\u002Fgh-aw","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3VCZ4WKQSFSRTPN7N9DN",5636,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Fhumanizer\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27],"communication","RFC","enforcement","community","patterns","tone","communications","manual","for","2026-11-10 10:12:30",false,"---\r\nname: \"humanizer\"\r\ndescription: \"Tone enforcement patterns for external-facing community responses\"\r\ndomain: \"communication, tone, community\"\r\nconfidence: \"low\"\r\nsource: \"manual (RFC #426 — PAO External Communications)\"\r\n---\r\n\r\n## Context\r\n\r\nUse this skill whenever PAO drafts external-facing responses for issues or discussions.\r\n\r\n- Tone must be warm, helpful, and human-sounding — never robotic or corporate.\r\n- Brady's constraint applies everywhere: **Humanized tone is mandatory**.\r\n- This applies to **all external-facing content** drafted by PAO in Phase 1 issues\u002Fdiscussions workflows.\r\n\r\n## Patterns\r\n\r\n1. **Warm opening** — Start with acknowledgment (\"Thanks for reporting this\", \"Great question!\")\r\n2. **Active voice** — \"We're looking into this\" not \"This is being investigated\"\r\n3. **Second person** — Address the person directly (\"you\" not \"the user\")\r\n4. **Conversational connectors** — \"That said...\", \"Here's what we found...\", \"Quick note:\"\r\n5. **Specific, not vague** — \"This affects the casting module in v0.8.x\" not \"We are aware of issues\"\r\n6. **Empathy markers** — \"I can see how that would be frustrating\", \"Good catch!\"\r\n7. **Action-oriented closes** — \"Let us know if that helps!\" not \"Please advise if further assistance is required\"\r\n8. **Uncertainty is OK** — \"We're not 100% sure yet, but here's what we think is happening...\" is better than false confidence\r\n9. **Profanity filter** — Never include profanity, slurs, or aggressive language, even when quoting\r\n10. **Baseline comparison** — Responses should align with tone of 5-10 \"gold standard\" responses (>80% similarity threshold)\r\n11. **Empathetic disagreement** — \"We hear you. That's a fair concern.\" before explaining the reasoning\r\n12. **Information request** — Ask for specific details, not open-ended \"can you provide more info?\"\r\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\r\n\r\n## Examples\r\n\r\n### 1. Welcome\r\n\r\n```text\r\nHey {author}! Welcome to Squad ? Thanks for opening this.\r\n{substantive response}\r\nLet us know if you have questions — happy to help!\r\n```\r\n\r\n### 2. Troubleshooting\r\n\r\n```text\r\nThanks for the detailed report, {author}!\r\nHere's what we think is happening: {explanation}\r\n{steps or workaround}\r\nLet us know if that helps, or if you're seeing something different.\r\n```\r\n\r\n### 3. Feature guidance\r\n\r\n```text\r\nGreat question! {context on current state}\r\n{guidance or workaround}\r\nWe've noted this as a potential improvement — {tracking info if applicable}.\r\n```\r\n\r\n### 4. Redirect\r\n\r\n```text\r\nThanks for reaching out! This one is actually better suited for {correct location}.\r\n{brief explanation of why}\r\nFeel free to open it there — they'll be able to help!\r\n```\r\n\r\n### 5. Acknowledgment\r\n\r\n```text\r\nGood catch, {author}. We've confirmed this is a real issue.\r\n{what we know so far}\r\nWe'll update this thread when we have a fix. Thanks for flagging it!\r\n```\r\n\r\n### 6. Closing\r\n\r\n```text\r\nThis should be resolved in {version\u002FPR}! ?\r\n{brief summary of what changed}\r\nThanks for reporting this, {author} — it made Squad better.\r\n```\r\n\r\n### 7. Technical uncertainty\r\n\r\n```text\r\nInteresting find, {author}. We're not 100% sure what's causing this yet.\r\nHere's what we've ruled out: {list}\r\nWe'd love more context if you have it — {specific ask}.\r\nWe'll dig deeper and update this thread.\r\n```\r\n\r\n## Anti-Patterns\r\n\r\n- ❌ Corporate speak: \"We appreciate your patience as we investigate this matter\"\r\n- ❌ Marketing hype: \"Squad is the BEST way to...\" or \"This amazing feature...\"\r\n- ❌ Passive voice: \"It has been determined that...\" or \"The issue is being tracked\"\r\n- ❌ Dismissive: \"This works as designed\" without empathy\r\n- ❌ Over-promising: \"We'll ship this next week\" without commitment from the team\r\n- ❌ Empty acknowledgment: \"Thanks for your feedback\" with no substance\r\n- ❌ Robot signatures: \"Best regards, PAO\" or \"Sincerely, The Squad Team\"\r\n- ❌ Excessive emoji: More than 1-2 emoji per response\r\n- ❌ Quoting profanity: Even when the original issue contains it, paraphrase instead\r\n- ❌ Link-dumping: Pasting URLs without context (\"See: https:\u002F\u002F...\")\r\n- ❌ Open-ended info requests: \"Can you provide more information?\" without specifying what information\r\n","## Context\r\n\r\nUse this skill whenever PAO drafts external-facing responses for issues or discussions.\r\n\r\n- Tone must be warm, helpful, and human-sounding — never robotic or corporate.\r\n- Brady's constraint applies everywhere: **Humanized tone is mandatory**.\r\n- This applies to **all external-facing content** drafted by PAO in Phase 1 issues\u002Fdiscussions workflows.\r\n\r\n## Patterns\r\n\r\n1. **Warm opening** — Start with acknowledgment (\"Thanks for reporting this\", \"Great question!\")\r\n2. **Active voice** — \"We're looking into this\" not \"This is being investigated\"\r\n3. **Second person** — Address the person directly (\"you\" not \"the user\")\r\n4. **Conversational connectors** — \"That said...\", \"Here's what we found...\", \"Quick note:\"\r\n5. **Specific, not vague** — \"This affects the casting module in v0.8.x\" not \"We are aware of issues\"\r\n6. **Empathy markers** — \"I can see how that would be frustrating\", \"Good catch!\"\r\n7. **Action-oriented closes** — \"Let us know if that helps!\" not \"Please advise if further assistance is required\"\r\n8. **Uncertainty is OK** — \"We're not 100% sure yet, but here's what we think is happening...\" is better than false confidence\r\n9. **Profanity filter** — Never include profanity, slurs, or aggressive language, even when quoting\r\n10. **Baseline comparison** — Responses should align with tone of 5-10 \"gold standard\" responses (>80% similarity threshold)\r\n11. **Empathetic disagreement** — \"We hear you. That's a fair concern.\" before explaining the reasoning\r\n12. **Information request** — Ask for specific details, not open-ended \"can you provide more info?\"\r\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\r\n\r\n## Examples\r\n\r\n### 1. Welcome\r\n\r\n```text\r\nHey {author}! Welcome to Squad ? Thanks for opening this.\r\n{substantive response}\r\nLet us know if you have questions — happy to help!\r\n```\r\n\r\n### 2. Troubleshooting\r\n\r\n```text\r\nThanks for the detailed report, {author}!\r\nHere's what we think is happening: {explanation}\r\n{steps or workaround}\r\nLet us know if that helps, or if you're seeing something different.\r\n```\r\n\r\n### 3. Feature guidance\r\n\r\n```text\r\nGreat question! {context on current state}\r\n{guidance or workaround}\r\nWe've noted this as a potential improvement — {tracking info if applicable}.\r\n```\r\n\r\n### 4. Redirect\r\n\r\n```text\r\nThanks for reaching out! This one is actually better suited for {correct location}.\r\n{brief explanation of why}\r\nFeel free to open it there — they'll be able to help!\r\n```\r\n\r\n### 5. Acknowledgment\r\n\r\n```text\r\nGood catch, {author}. We've confirmed this is a real issue.\r\n{what we know so far}\r\nWe'll update this thread when we have a fix. Thanks for flagging it!\r\n```\r\n\r\n### 6. Closing\r\n\r\n```text\r\nThis should be resolved in {version\u002FPR}! ?\r\n{brief summary of what changed}\r\nThanks for reporting this, {author} — it made Squad better.\r\n```\r\n\r\n### 7. Technical uncertainty\r\n\r\n```text\r\nInteresting find, {author}. We're not 100% sure what's causing this yet.\r\nHere's what we've ruled out: {list}\r\nWe'd love more context if you have it — {specific ask}.\r\nWe'll dig deeper and update this thread.\r\n```\r\n\r\n## Anti-Patterns\r\n\r\n- ❌ Corporate speak: \"We appreciate your patience as we investigate this matter\"\r\n- ❌ Marketing hype: \"Squad is the BEST way to...\" or \"This amazing feature...\"\r\n- ❌ Passive voice: \"It has been determined that...\" or \"The issue is being tracked\"\r\n- ❌ Dismissive: \"This works as designed\" without empathy\r\n- ❌ Over-promising: \"We'll ship this next week\" without commitment from the team\r\n- ❌ Empty acknowledgment: \"Thanks for your feedback\" with no substance\r\n- ❌ Robot signatures: \"Best regards, PAO\" or \"Sincerely, The Squad Team\"\r\n- ❌ Excessive emoji: More than 1-2 emoji per response\r\n- ❌ Quoting profanity: Even when the original issue contains it, paraphrase instead\r\n- ❌ Link-dumping: Pasting URLs without context (\"See: https:\u002F\u002F...\")\r\n- ❌ Open-ended info requests: \"Can you provide more information?\" without specifying what information\r\n",{"name":5,"domain":33,"source":34,"confidence":35,"description":7},"communication, tone, community","manual (RFC #426 — PAO External Communications)","low","main","8541229759617347888641eba917d3b0ad66a984",".squad\u002Ftemplates\u002Fskills\u002Fhumanizer",626,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw","https:\u002F\u002Fgh.io\u002Fgh-aw","https:\u002F\u002Fgithub.com\u002Fgithub","https:\u002F\u002Fgithub.com\u002Fabout","How people build software.","2026-11-15 06:45:15",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add github\u002Fgh-aw --skill humanizer",{"tool":52,"command":53},"bunx","bunx skills add github\u002Fgh-aw --skill humanizer",{"tool":55,"command":56},"pnpm","pnpm dlx skills add github\u002Fgh-aw --skill humanizer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Fhumanizer\u002FSKILL.md",true,[60],{"path":61,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":64,"sourceHtmlUrl":65},"agents\u002Fopenai.yaml","REFERENCE","参考文档",141,"https:\u002F\u002Fgithub.com\u002Fajrussellaudio\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002F.claude\u002Fskills\u002Fhandoff\u002Fagents\u002Fopenai.yaml",[67,95,112,137,163,181],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":81,"publishedAt":28},"01M6ADC942STTXHFV410J4DH0X","GitHub Agentic Workflows","GitHub Agentic Workflows (`gh-aw`) is a GitHub CLI extension for writing Agentic Workflows in markdown and compiling them to GitHub Actions.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002FSKILL.md",[73,78],{"categoryNo":74,"categoryName":75,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",{"categoryNo":79,"categoryName":80,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000023","Skill与智能体开发",[9,82,83,84,85,86,87,88,27,89,90,91,92,93,94],"agentic","agentic workflows","github agentic workflows","workflows","github cli","gh","extension","compiling","cli","writing","actions","github actions","markdown",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":28},"01M6ADC6ZXSA46N9XD6VNAP1MS","windows-compatibility","Cross-platform path handling and command patterns","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Fwindows-compatibility\u002FSKILL.md",[],[102,103,104,105,106,107,108,109,23,110,111],"windows","windows compatibility","compatibility","bugs","path","high","platform","cross-platform","command","git",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":28},"01M6ADC44957SVQF96R5YY247P","versioning-policy","Semver versioning rules for Squad SDK and CLI — prevents prerelease version incidents","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Fversioning-policy\u002FSKILL.md",[],[119,120,121,122,123,124,125,126,127,128,129,130,131,132,133,134,27,135,90,136],"policy","versioning policy","versioning","incident","gate","implementation","version","Rules","workspace","pr","ci","npm","semver","release","squad","resolution","incidents","sdk",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":147,"publishedAt":28},"01M6ADC1PHMEAEVR87F8PDR89X","tiered-memory","Three-tier agent memory model (hot\u002Fcold\u002Fwiki) for context reduction per spawn","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Ftiered-memory\u002FSKILL.md",[143,146],{"categoryNo":144,"categoryName":145,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":79,"categoryName":80,"taxonomyType":76,"taxonomyTypeDesc":77},[148,149,150,151,27,152,153,154,155,156,157,158,159,160,161,162],"tiered memory","memory","memory-management","model","cold","proposal","runtime","three","spawn","management","context","wiki","agent memory","performance","design",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":172,"publishedAt":28},"01M6ADBZTDGFM0E25EWRQEMYEH","test-discipline","Update tests when changing APIs — no exceptions","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Ftest-discipline\u002FSKILL.md",[169],{"categoryNo":170,"categoryName":171,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000008","测试与质量",[173,174,175,176,177,107,178,122,179,180],"test discipline","discipline","test","sync","when","tests","quality","update",{"skillNo":182,"name":133,"nameZh":6,"description":183,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":184,"categories":185,"keywords":186,"publishedAt":28},"01M6ADBX5MJP4Z7CG4XTV8ZVT8","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\u002Fgh-aw\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Fsquad\u002FSKILL.md",[],[133,187,188,189,190,191,192,193,194,195,196,197,198,110,151,199,200,201,202,203,204,205,90],"show","interactive menu","invoke","coordinator","as","commands","upgrade","options","me","natural language","do","install","team","show me","plugins","issues","state","squad commands","sessions"]