[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M719KR3DD9NRV7HTVG9SWEXZ":3,"skill-same:01M719KR3DD9NRV7HTVG9SWEXZ":56},{"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":27,"linkOnly":28,"markdownContent":29,"markdownBody":30,"frontMatter":31,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":41,"install":42,"resources":55},"01M719KR3DD9NRV7HTVG9SWEXZ","humanizer",null,"Tone enforcement patterns for external-facing community responses","DeDuva\u002Fsquad","DeDuva","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F8153108?v=4","01M719BQB25861D0TKS3RVHMN2","01M719BQBSWR380PSYDD5M9YD4",1,"MIT","https:\u002F\u002Fgithub.com\u002FDeDuva\u002Fsquad\u002Fblob\u002Fdev\u002Fpackages\u002Fsquad-sdk\u002Ftemplates\u002Fskills\u002Fhumanizer\u002FSKILL.md",[],[5,18,19,20,21,22,23,24,25,26],"communications","community","enforcement","communication","for","manual","patterns","RFC","tone","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":32,"source":33,"confidence":34,"description":7},"communication, tone, community","manual (RFC #426 — PAO External Communications)","low","dev","4ffda80d1bb1043d9169688cf161e53097345c72","packages\u002Fsquad-sdk\u002Ftemplates\u002Fskills\u002Fhumanizer",0,"https:\u002F\u002Fgithub.com\u002FDeDuva\u002Fsquad","https:\u002F\u002Fgithub.com\u002FDeDuva","2026-11-09 20:24:44",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add DeDuva\u002Fsquad --skill humanizer",{"tool":48,"command":49},"bunx","bunx skills add DeDuva\u002Fsquad --skill humanizer",{"tool":51,"command":52},"pnpm","pnpm dlx skills add DeDuva\u002Fsquad --skill humanizer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDeDuva\u002Fsquad\u002Fblob\u002Fdev\u002Fpackages\u002Fsquad-sdk\u002Ftemplates\u002Fskills\u002Fhumanizer\u002FSKILL.md",true,[],[57,73,81,96,120,135],{"skillNo":58,"name":59,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":67,"publishedAt":27},"01M719NE6ZPZT80MKVWFDECJZ3","My Skill","https:\u002F\u002Fgithub.com\u002FDeDuva\u002Fsquad\u002Fblob\u002Fdev\u002Ftest-fixtures\u002Fskills-test-abb30454\u002Fmy-skill\u002FSKILL.md",[62],{"categoryNo":63,"categoryName":64,"taxonomyType":65,"taxonomyTypeDesc":66},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[68,69,70,71,72],"my","my skill","testing","vitest","tester",{"skillNo":74,"name":75,"nameZh":6,"description":6,"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":27},"01M719NDJAMEWM8D9H355SCNA8","bad-skill","https:\u002F\u002Fgithub.com\u002FDeDuva\u002Fsquad\u002Fblob\u002Fdev\u002Ftest-fixtures\u002Fskills-test-abb30454\u002Fbad-skill\u002FSKILL.md",[],[79,80],"bad skill","bad",{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":27},"01M719NCC1AZ02GHZ1V71YPEV7","squad-conventions","Core conventions and patterns used in the Squad codebase","https:\u002F\u002Fgithub.com\u002FDeDuva\u002Fsquad\u002Fblob\u002Fdev\u002Ftemplates\u002Fskills\u002Fsquad-conventions\u002FSKILL.md",[],[88,89,90,91,92,93,23,94,95,24],"conventions","squad","squad conventions","project-conventions","core","project","high","codebase",{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":27},"01M719NAYM17B7X8MGP681EHKQ","rework-rate","Measure and interpret PR rework rate — the emerging 5th DORA metric","https:\u002F\u002Fgithub.com\u002FDeDuva\u002Fsquad\u002Fblob\u002Fdev\u002Ftemplates\u002Fskills\u002Frework-rate\u002FSKILL.md",[],[103,104,105,106,94,107,108,109,89,110,111,112,113,23,114,115,116,117,118,119],"rate","rework rate","health","analyze","review efficiency","quality","metric","metrics","efficiency","code quality","pr","prs","when","code","team","code-review","review",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":27},"01M719NA136PDC3SQ10R4R88TH","nap","Context hygiene — compress, prune, archive .squad\u002F state","https:\u002F\u002Fgithub.com\u002FDeDuva\u002Fsquad\u002Fblob\u002Fdev\u002Ftemplates\u002Fskills\u002Fnap\u002FSKILL.md",[],[122,127,128,129,130,131,132,133,89,134],"prune","state","maintenance","context hygiene","archive","hygiene","compress","context",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":145,"publishedAt":27},"01M719N7B4PBQPNXW78TEJY4HQ","e2e-template-testing","End-to-end validation of coordinator and agent template changes","https:\u002F\u002Fgithub.com\u002FDeDuva\u002Fsquad\u002Fblob\u002Fdev\u002Ftemplates\u002Fskills\u002Fe2e-template-testing\u002FSKILL.md",[141,144],{"categoryNo":142,"categoryName":143,"taxonomyType":65,"taxonomyTypeDesc":66},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":63,"categoryName":64,"taxonomyType":65,"taxonomyTypeDesc":66},[70,146,147,148,149,150,151,23,152,94,153],"e2e template testing","e2e","template","end","coordinator","development","changes","validation"]