[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6R7C46HB06DZ6F1F09SDGPN":3,"skill-same:01M6R7C46HB06DZ6F1F09SDGPN":55},{"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":13,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":40,"install":41,"resources":54},"01M6R7C46HB06DZ6F1F09SDGPN","humanizer",null,"Tone enforcement patterns for external-facing community responses","barichter\u002Fsquad","barichter","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F96797186?v=4","01M6R712K8ESMDF089BFENBR16","01M6R712R74BSQQSG2GTXBWR8P",0,"MIT","https:\u002F\u002Fgithub.com\u002Fbarichter\u002Fsquad\u002Fblob\u002Fdev\u002Fpackages\u002Fsquad-cli\u002Ftemplates\u002Fskills\u002Fhumanizer\u002FSKILL.md",[],[5,18,19,20,21,22,23,24,25,26],"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":32,"source":33,"confidence":34,"description":7},"communication, tone, community","manual (RFC #426 — PAO External Communications)","low","dev","ec19f5e92325e634e3c6eff500e3cefa56131cc9","packages\u002Fsquad-cli\u002Ftemplates\u002Fskills\u002Fhumanizer","https:\u002F\u002Fgithub.com\u002Fbarichter\u002Fsquad","https:\u002F\u002Fgithub.com\u002Fbarichter","2026-04-13 22:53:46",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add barichter\u002Fsquad --skill humanizer",{"tool":47,"command":48},"bunx","bunx skills add barichter\u002Fsquad --skill humanizer",{"tool":50,"command":51},"pnpm","pnpm dlx skills add barichter\u002Fsquad --skill humanizer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbarichter\u002Fsquad\u002Fblob\u002Fdev\u002Fpackages\u002Fsquad-cli\u002Ftemplates\u002Fskills\u002Fhumanizer\u002FSKILL.md",true,[],[56,72,80,95,118,124],{"skillNo":57,"name":58,"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":59,"categories":60,"keywords":66,"publishedAt":27},"01M6R7VE8SZD1E37WWJN4ZFPWB","My Skill","https:\u002F\u002Fgithub.com\u002Fbarichter\u002Fsquad\u002Fblob\u002Fdev\u002Ftest-fixtures\u002Fskills-test-abb30454\u002Fmy-skill\u002FSKILL.md",[61],{"categoryNo":62,"categoryName":63,"taxonomyType":64,"taxonomyTypeDesc":65},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[67,68,69,70,71],"my","my skill","tester","vitest","testing",{"skillNo":73,"name":74,"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":75,"categories":76,"keywords":77,"publishedAt":27},"01M6R7VD19M4TMAA74XGD6QSZX","bad-skill","https:\u002F\u002Fgithub.com\u002Fbarichter\u002Fsquad\u002Fblob\u002Fdev\u002Ftest-fixtures\u002Fskills-test-abb30454\u002Fbad-skill\u002FSKILL.md",[],[78,79],"bad skill","bad",{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":27},"01M6R7V9TYTX6Z621V6RWA51G6","squad-conventions","Core conventions and patterns used in the Squad codebase","https:\u002F\u002Fgithub.com\u002Fbarichter\u002Fsquad\u002Fblob\u002Fdev\u002Ftemplates\u002Fskills\u002Fsquad-conventions\u002FSKILL.md",[],[87,88,89,90,91,22,92,25,93,94],"squad conventions","squad","conventions","project-conventions","core","project","high","codebase",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":27},"01M6R7TTF0ABMGSVWASVYF6D51","rework-rate","Measure and interpret PR rework rate — the emerging 5th DORA metric","https:\u002F\u002Fgithub.com\u002Fbarichter\u002Fsquad\u002Fblob\u002Fdev\u002Ftemplates\u002Fskills\u002Frework-rate\u002FSKILL.md",[],[102,103,104,105,106,107,108,109,110,93,88,111,112,113,114,115,116,117,25],"rate","rework rate","metric","efficiency","prs","when","pr","review","code quality","code","code-review","metrics","health","team","analyze","quality",{"skillNo":119,"name":120,"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":121,"categories":122,"keywords":123,"publishedAt":27},"01M6R7TRZPET44JRCSQF08EEA8","nap","https:\u002F\u002Fgithub.com\u002Fbarichter\u002Fsquad\u002Fblob\u002Fdev\u002Ftemplates\u002Fskills\u002Fnap\u002FSKILL.md",[],[120],{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":131,"publishedAt":27},"01M6R7TK10WCT77A52E27GR5R3","{skill-name}","{what this skill teaches agents}","https:\u002F\u002Fgithub.com\u002Fbarichter\u002Fsquad\u002Fblob\u002Fdev\u002Ftemplates\u002Fskill.md",[130],{"categoryNo":62,"categoryName":63,"taxonomyType":64,"taxonomyTypeDesc":65},[132,133,134,135,136,137,138,139,140,141,25,93,71],"{skill name}","skill name","name","design","api","how","error-handling","learned","error","api-design"]