[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M753YJM6MP6YQFRE021917RB":3,"skill-same:01M753YJM6MP6YQFRE021917RB":68},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":13,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M753YJM6MP6YQFRE021917RB","internal-comms",null,"A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).","ASoudy\u002FAGS","ASoudy","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F40639702?v=4","01M74G5NTCW8MWDNRTAF303PA1","01M74G5NTZXSE6T0GZR5BCB6V0",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fanthropic-skills\u002Fskills\u002Finternal-comms\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fanthropic-skills\u002Fskills\u002Finternal-comms\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: internal-comms\ndescription: A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).\nlicense: Complete terms in LICENSE.txt\n---\n\n## When to use this skill\nTo write internal communications, use this skill for:\n- 3P updates (Progress, Plans, Problems)\n- Company newsletters\n- FAQ responses\n- Status reports\n- Leadership updates\n- Project updates\n- Incident reports\n\n## How to use this skill\n\nTo write any internal communication:\n\n1. **Identify the communication type** from the request\n2. **Load the appropriate guideline file** from the `examples\u002F` directory:\n    - `examples\u002F3p-updates.md` - For Progress\u002FPlans\u002FProblems team updates\n    - `examples\u002Fcompany-newsletter.md` - For company-wide newsletters\n    - `examples\u002Ffaq-answers.md` - For answering frequently asked questions\n    - `examples\u002Fgeneral-comms.md` - For anything else that doesn't explicitly match one of the above\n3. **Follow the specific instructions** in that file for formatting, tone, and content gathering\n\nIf the communication type doesn't match any existing guideline, ask for clarification or more context about the desired format.\n\n## Keywords\n3P updates, company newsletter, company comms, weekly update, faqs, common questions, updates, internal comms\n","## When to use this skill\nTo write internal communications, use this skill for:\n- 3P updates (Progress, Plans, Problems)\n- Company newsletters\n- FAQ responses\n- Status reports\n- Leadership updates\n- Project updates\n- Incident reports\n\n## How to use this skill\n\nTo write any internal communication:\n\n1. **Identify the communication type** from the request\n2. **Load the appropriate guideline file** from the `examples\u002F` directory:\n    - `examples\u002F3p-updates.md` - For Progress\u002FPlans\u002FProblems team updates\n    - `examples\u002Fcompany-newsletter.md` - For company-wide newsletters\n    - `examples\u002Ffaq-answers.md` - For answering frequently asked questions\n    - `examples\u002Fgeneral-comms.md` - For anything else that doesn't explicitly match one of the above\n3. **Follow the specific instructions** in that file for formatting, tone, and content gathering\n\nIf the communication type doesn't match any existing guideline, ask for clarification or more context about the desired format.\n\n## Keywords\n3P updates, company newsletter, company comms, weekly update, faqs, common questions, updates, internal comms\n",{"name":5,"license":24,"description":7},"Complete terms in LICENSE.txt","main","cd1d94757d590093507ef8ac26299eab8bc20478","claude_skills_libraries\u002Fanthropic-skills\u002Fskills\u002Finternal-comms","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS","https:\u002F\u002Fgithub.com\u002FASoudy","2026-05-23 09:43:12",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add ASoudy\u002FAGS --skill internal-comms",{"tool":37,"command":38},"bunx","bunx skills add ASoudy\u002FAGS --skill internal-comms",{"tool":40,"command":41},"pnpm","pnpm dlx skills add ASoudy\u002FAGS --skill internal-comms","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fanthropic-skills\u002Fskills\u002Finternal-comms\u002FSKILL.md",true,[45,51,55,59,63],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"examples\u002F3p-updates.md","REFERENCE","参考文档",3274,"https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fanthropic-skills\u002Fskills\u002Finternal-comms\u002Fexamples\u002F3p-updates.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"examples\u002Fcompany-newsletter.md",3295,"https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fanthropic-skills\u002Fskills\u002Finternal-comms\u002Fexamples\u002Fcompany-newsletter.md",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"examples\u002Ffaq-answers.md",2366,"https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fanthropic-skills\u002Fskills\u002Finternal-comms\u002Fexamples\u002Ffaq-answers.md",{"path":60,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":61,"sourceHtmlUrl":62},"examples\u002Fgeneral-comms.md",602,"https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fanthropic-skills\u002Fskills\u002Finternal-comms\u002Fexamples\u002Fgeneral-comms.md",{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":15},"LICENSE.txt","LICENSE","许可证",11345,[69,77,84,91,98,105],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":73,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M756BTEVC407T0QR8S420JWD","web-typography","Select, pair, and implement typefaces for web projects. Use when the user mentions \"font pairing\", \"which typeface\", \"line height\", \"responsive typography\", \"web font loading\", \"type hierarchy\", \"variable fonts\", \"FOUT\u002FFOIT\", or \"typographic scale\". Also trigger when choosing between system fonts and web fonts, optimizing font loading performance, or designing readable long-form content layouts. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.","MIT","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Fweb-typography\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":73,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M756B4RYF2CB17C33X6ZJQT5","ux-heuristics","Evaluate and improve interface usability using heuristic analysis. Use when the user mentions \"usability audit\", \"UX review\", \"users are confused\", \"heuristic evaluation\", \"form usability\", \"navigation problems\", \"Nielsen heuristics\", \"cognitive walkthrough\", or \"usability testing\". Also trigger when reviewing a design for usability issues, improving form completion rates, or evaluating information architecture and navigation. Covers Nielsens 10 heuristics, severity ratings, and information architecture. For visual design fixes, see refactoring-ui. For conversion-focused audits, see cro-methodology.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Fux-heuristics\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":73,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M756ANVFT0T6BAPV6Y93EPR6","traction-eos","Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions \"EOS\", \"V\u002FTO\", \"quarterly rocks\", \"Level 10 meetings\", \"accountability chart\", \"IDS process\", \"Entrepreneurial Operating System\", or \"business operating system\". Also trigger when a growing company needs meeting structure, goal-setting frameworks, or a systematic approach to solving recurring organizational issues. Covers the six EOS components: Vision, People, Data, Issues, Process, Traction. For team motivation design, see drive-motivation. For lean experimentation, see lean-startup.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Ftraction-eos\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":73,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M756A7NZZMNJN9KZ33QGFHV6","top-design","Create award-winning, immersive web experiences at the level of Awwwards-featured agencies. Use when the user mentions \"premium website\", \"portfolio site\", \"scroll animations\", \"Awwwards quality\", \"brand experience\", \"cinematic web design\", \"parallax storytelling\", or \"agency-quality site\". Also trigger when building landing pages that need to impress, designing creative portfolios, or elevating a standard website to a memorable digital experience. Covers dramatic typography, purposeful motion, scroll-based composition, and performance-optimized animation. For foundational UI, see refactoring-ui. For type selection, see web-typography.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Ftop-design\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":73,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M7569J5G1NXM3RR194D52SGB","system-design","Design scalable distributed systems using structured approaches for load balancing, caching, database scaling, and message queues. Use when the user mentions \"system design\", \"scale this\", \"high availability\", \"rate limiter\", \"design a URL shortener\", \"system design interview\", \"capacity planning\", or \"distributed architecture\". Also trigger when estimating infrastructure requirements, choosing between microservices and monoliths, or designing for millions of concurrent users. Covers common system designs and back-of-the-envelope estimation. For data fundamentals, see ddia-systems. For resilience, see release-it.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Fsystem-design\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":73,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":19},"01M75691MJKE6PBA1EC398EKQT","storybrand-messaging","Clarify brand messaging using narrative structure that positions the customer as hero. Use when the user mentions \"brand message\", \"website copy\", \"elevator pitch\", \"one-liner\", \"messaging isnt resonating\", \"brand script\", \"StoryBrand framework\", or \"customer as hero\". Also trigger when rewriting homepage copy, crafting email nurture sequences, or creating consistent messaging across sales collateral and marketing materials. Covers landing page copy, marketing collateral, and consistent communication. For memorable messaging, see made-to-stick. For product positioning, see obviously-awesome.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Fstorybrand-messaging\u002FSKILL.md",[],[]]