[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AF2GFN45ETBQAZ0VTQQ0D8":3,"skill-same:01M6AF2GFN45ETBQAZ0VTQQ0D8":101},{"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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":60,"ownerHtmlUrl":61,"ownerBlogUrl":62,"ownerDescription":63,"updatedAt":64,"install":65,"resources":78},"01M6AF2GFN45ETBQAZ0VTQQ0D8","professional-communication",null,"Guide technical communication for software developers. Covers email structure, team messaging etiquette, meeting agendas, and adapting messages for technical vs non-technical audiences. Use when drafting professional messages, preparing meeting communications, or improving written communication.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33418,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fprofessional-communication\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"professional communication","professional","communication","use","drafting","when","for","meeting","non-technical","communications","software","structure","guide","read","technical","grep","team","messages","email","messaging","2026-11-10 10:12:30",false,"---\nname: professional-communication\ndescription: Guide technical communication for software developers. Covers email structure, team messaging etiquette, meeting agendas, and adapting messages for technical vs non-technical audiences. Use when drafting professional messages, preparing meeting communications, or improving written communication.\nallowed-tools: Read, Glob, Grep\n---\n\n# Professional Communication\n\n## Overview\n\nThis skill provides frameworks and guidance for effective professional communication in software development contexts. Whether you're writing an email to stakeholders, crafting a team chat message, or preparing meeting agendas, these principles help you communicate clearly and build professional credibility.\n\n**Core principle:** Effective communication isn't about proving how much you know - it's about ensuring your message is received and understood.\n\n## When to Use This Skill\n\nUse this skill when:\n\n- Writing emails to teammates, managers, or stakeholders\n- Crafting team chat messages or async communications\n- Preparing meeting agendas or summaries\n- Translating technical concepts for non-technical audiences\n- Structuring status updates or reports\n- Improving clarity of written communication\n\n**Keywords**: email, chat, teams, slack, discord, message, writing, communication, meeting, agenda, status update, report\n\n## Core Frameworks\n\n### The What-Why-How Structure\n\nUse this universal framework to organize any professional message:\n\n| Component | Purpose | Example |\n| --- | --- | --- |\n| **What** | State the topic\u002Frequest clearly | \"We need to delay the release by one week\" |\n| **Why** | Explain the reasoning | \"Critical bug found in payment processing\" |\n| **How** | Outline next steps\u002Faction items | \"QA will retest by Thursday; I'll update stakeholders Friday\" |\n\n**Apply to**: Emails, status updates, meeting talking points, technical explanations\n\n### Three Golden Rules for Written Communication\n\n1. **Start with a clear subject\u002Fpurpose** - Recipients should immediately grasp what your message is about\n2. **Use bullets, headlines, and scannable formatting** - Nobody wants a wall of text\n3. **Key messages first** - Busy people appreciate efficiency; state your main point upfront\n\n### Audience Calibration\n\nBefore communicating, ask yourself:\n\n1. **Who** are you writing to? (Technical peers, managers, stakeholders, customers)\n2. **What level of detail** do they need? (High-level overview vs implementation details)\n3. **What's the value** for them? (How does this affect their work\u002Fdecisions?)\n\n## Email Best Practices\n\n### Subject Line Formula\n\n| Instead of | Try |\n| --- | --- |\n| \"Project updates\" | \"Project X: Status Update and Next Steps\" |\n| \"Question\" | \"Quick question: API rate limiting approach\" |\n| \"FYI\" | \"FYI: Deployment scheduled for Tuesday 3pm\" |\n\n### Email Structure Template\n\n```markdown\n**Subject:** [Project\u002FTopic]: [Specific Purpose]\n\nHi [Name],\n\n[1-2 sentences stating the key point or request upfront]\n\n**Context\u002FBackground:**\n- [Bullet point 1]\n- [Bullet point 2]\n\n**What I need from you:**\n- [Specific action or decision needed]\n- [Timeline if applicable]\n\n[Optional: Brief next steps or follow-up plan]\n\nBest,\n[Your name]\n```\n\n### Common Email Types\n\n| Type | Key Elements |\n| --- | --- |\n| **Status Update** | Progress summary, blockers, next steps, timeline |\n| **Request** | Clear ask, context, deadline, why it matters |\n| **Escalation** | Issue summary, impact, attempted solutions, needed decision |\n| **FYI\u002FAnnouncement** | What changed, who's affected, any required action |\n\n**For templates**: See `references\u002Femail-templates.md`\n\n## Team Messaging Etiquette\n\n> **Note:** Examples use Slack terminology, but these principles apply equally to Microsoft Teams, Discord, or any team messaging platform.\n\n### When to Use Chat vs Email\n\n| Use Chat | Use Email |\n| --- | --- |\n| Quick questions with short answers | Detailed documentation needing records |\n| Real-time coordination | Formal communications to stakeholders |\n| Informal team discussions | Messages requiring careful review |\n| Time-sensitive updates | Complex explanations with multiple parts |\n\n### Team Messaging Best Practices\n\n1. **Use threads** - Keep main channels scannable; follow-ups go in threads\n2. **@mention thoughtfully** - Don't notify people unnecessarily\n3. **Channel organization** - Right channel for right topic\n4. **Be direct** - \"Can you review my PR?\" beats \"Hey, are you busy?\"\n5. **Async-friendly** - Write messages that don't require immediate response\n\n### The \"No Hello\" Principle\n\nInstead of:\n\n```text\nYou: Hi\nYou: Are you there?\nYou: Can I ask you something?\n[waiting...]\n```\n\nTry:\n\n```text\nYou: Hi Sarah - quick question about the deployment script.\n     Getting a permission error on line 42. Have you seen this before?\n     Here's the error: [paste error]\n```\n\n## Technical vs Non-Technical Communication\n\n### When to Be Technical vs Accessible\n\n| Audience | Approach |\n| --- | --- |\n| **Engineering peers** | Technical details, code examples, architecture specifics |\n| **Technical managers** | Balance of detail and high-level impact |\n| **Non-technical stakeholders** | Business impact, analogies, outcomes over implementation |\n| **Customers** | Plain language, what it means for them, avoid jargon |\n\n### Three Strategies for Simplification\n\n1. **Start with the big picture before details** - People process \"why\" before \"how\"\n2. **Simplify without losing accuracy** - Use analogies; replace jargon with plain language\n3. **Know when to switch** - Read the room; adjust based on questions and engagement\n\n### Jargon Translation Examples\n\n| Technical | Plain Language |\n| --- | --- |\n| \"Microservices architecture\" | \"Our system is split into smaller, independent pieces that can scale separately\" |\n| \"Asynchronous message processing\" | \"Tasks are queued and processed in the background\" |\n| \"CI\u002FCD pipeline\" | \"Automated process that tests and deploys our code\" |\n| \"Database migration\" | \"Updating how our data is organized and stored\" |\n\n**For more examples**: See `references\u002Fjargon-simplification.md`\n\n## Writing Clarity Principles\n\n### Active Voice Over Passive Voice\n\nActive voice is clearer, more direct, and conveys authority:\n\n| Passive (avoid) | Active (prefer) |\n| --- | --- |\n| \"A bug was identified by the team\" | \"The team identified a bug\" |\n| \"The feature will be implemented\" | \"We will implement the feature\" |\n| \"Errors were found during testing\" | \"Testing revealed errors\" |\n\n### Eliminate Filler Words\n\n| Instead of | Use |\n| --- | --- |\n| \"At this point in time\" | \"Now\" |\n| \"In the event that\" | \"If\" |\n| \"Due to the fact that\" | \"Because\" |\n| \"In order to\" | \"To\" |\n| \"I just wanted to check if\" | \"Can you\" |\n\n### The \"So What?\" Test\n\nAfter writing, ask: \"So what? Why does this matter to the reader?\"\n\nIf you can't answer clearly, restructure your message to lead with the value\u002Fimpact.\n\n## Meeting Communication\n\n### Before: Agenda Best Practices\n\nEvery meeting invite should include:\n\n1. **Clear objective** - What will be accomplished?\n2. **Agenda items** - Topics to cover with time estimates\n3. **Preparation required** - What should attendees bring\u002Freview?\n4. **Expected outcome** - Decision needed? Information sharing? Brainstorm?\n\n### During: Facilitation Tips\n\n- **Time-box discussions** - \"Let's spend 5 minutes on this, then move on\"\n- **Capture action items live** - Who does what by when\n- **Parking lot** - Note off-topic items for later\n\n### After: Summary Format\n\n```markdown\n**Meeting: [Topic] - [Date]**\n\n**Attendees:** [Names]\n\n**Key Decisions:**\n- [Decision 1]\n- [Decision 2]\n\n**Action Items:**\n- [ ] [Person]: [Task] - Due [Date]\n- [ ] [Person]: [Task] - Due [Date]\n\n**Next Steps:**\n- [Follow-up meeting if needed]\n- [Documents to share]\n```\n\n**For structures by meeting type**: See `references\u002Fmeeting-structures.md`\n\n## Quick Reference: Communication Checklist\n\nBefore sending any professional communication:\n\n- [ ] **Clear purpose** - Can the recipient understand intent in 5 seconds?\n- [ ] **Right audience** - Is this the appropriate person\u002Fchannel?\n- [ ] **Key message first** - Is the main point upfront?\n- [ ] **Scannable** - Are there bullets, headers, short paragraphs?\n- [ ] **Action clear** - Does the recipient know what (if anything) they need to do?\n- [ ] **Jargon check** - Will the audience understand all terminology?\n- [ ] **Tone appropriate** - Is it professional but not cold?\n- [ ] **Proofread** - Any typos or unclear phrasing?\n\n## Additional Tools\n\n- `references\u002Femail-templates.md` - Ready-to-use email templates by type\n- `references\u002Fmeeting-structures.md` - Structures for standups, retros, reviews\n- `references\u002Fjargon-simplification.md` - Technical-to-plain-language translations\n\n## Companion Skills\n\n- `feedback-mastery` - For difficult conversations and feedback delivery\n- `\u002Fdraft-email` - Generate emails using these frameworks\n\n---\n\n**Last Updated:** 2025-12-22\n\n## Version History\n\n- **v1.0.0** (2025-12-26): Initial release\n\n---\n","# Professional Communication\n\n## Overview\n\nThis skill provides frameworks and guidance for effective professional communication in software development contexts. Whether you're writing an email to stakeholders, crafting a team chat message, or preparing meeting agendas, these principles help you communicate clearly and build professional credibility.\n\n**Core principle:** Effective communication isn't about proving how much you know - it's about ensuring your message is received and understood.\n\n## When to Use This Skill\n\nUse this skill when:\n\n- Writing emails to teammates, managers, or stakeholders\n- Crafting team chat messages or async communications\n- Preparing meeting agendas or summaries\n- Translating technical concepts for non-technical audiences\n- Structuring status updates or reports\n- Improving clarity of written communication\n\n**Keywords**: email, chat, teams, slack, discord, message, writing, communication, meeting, agenda, status update, report\n\n## Core Frameworks\n\n### The What-Why-How Structure\n\nUse this universal framework to organize any professional message:\n\n| Component | Purpose | Example |\n| --- | --- | --- |\n| **What** | State the topic\u002Frequest clearly | \"We need to delay the release by one week\" |\n| **Why** | Explain the reasoning | \"Critical bug found in payment processing\" |\n| **How** | Outline next steps\u002Faction items | \"QA will retest by Thursday; I'll update stakeholders Friday\" |\n\n**Apply to**: Emails, status updates, meeting talking points, technical explanations\n\n### Three Golden Rules for Written Communication\n\n1. **Start with a clear subject\u002Fpurpose** - Recipients should immediately grasp what your message is about\n2. **Use bullets, headlines, and scannable formatting** - Nobody wants a wall of text\n3. **Key messages first** - Busy people appreciate efficiency; state your main point upfront\n\n### Audience Calibration\n\nBefore communicating, ask yourself:\n\n1. **Who** are you writing to? (Technical peers, managers, stakeholders, customers)\n2. **What level of detail** do they need? (High-level overview vs implementation details)\n3. **What's the value** for them? (How does this affect their work\u002Fdecisions?)\n\n## Email Best Practices\n\n### Subject Line Formula\n\n| Instead of | Try |\n| --- | --- |\n| \"Project updates\" | \"Project X: Status Update and Next Steps\" |\n| \"Question\" | \"Quick question: API rate limiting approach\" |\n| \"FYI\" | \"FYI: Deployment scheduled for Tuesday 3pm\" |\n\n### Email Structure Template\n\n```markdown\n**Subject:** [Project\u002FTopic]: [Specific Purpose]\n\nHi [Name],\n\n[1-2 sentences stating the key point or request upfront]\n\n**Context\u002FBackground:**\n- [Bullet point 1]\n- [Bullet point 2]\n\n**What I need from you:**\n- [Specific action or decision needed]\n- [Timeline if applicable]\n\n[Optional: Brief next steps or follow-up plan]\n\nBest,\n[Your name]\n```\n\n### Common Email Types\n\n| Type | Key Elements |\n| --- | --- |\n| **Status Update** | Progress summary, blockers, next steps, timeline |\n| **Request** | Clear ask, context, deadline, why it matters |\n| **Escalation** | Issue summary, impact, attempted solutions, needed decision |\n| **FYI\u002FAnnouncement** | What changed, who's affected, any required action |\n\n**For templates**: See `references\u002Femail-templates.md`\n\n## Team Messaging Etiquette\n\n> **Note:** Examples use Slack terminology, but these principles apply equally to Microsoft Teams, Discord, or any team messaging platform.\n\n### When to Use Chat vs Email\n\n| Use Chat | Use Email |\n| --- | --- |\n| Quick questions with short answers | Detailed documentation needing records |\n| Real-time coordination | Formal communications to stakeholders |\n| Informal team discussions | Messages requiring careful review |\n| Time-sensitive updates | Complex explanations with multiple parts |\n\n### Team Messaging Best Practices\n\n1. **Use threads** - Keep main channels scannable; follow-ups go in threads\n2. **@mention thoughtfully** - Don't notify people unnecessarily\n3. **Channel organization** - Right channel for right topic\n4. **Be direct** - \"Can you review my PR?\" beats \"Hey, are you busy?\"\n5. **Async-friendly** - Write messages that don't require immediate response\n\n### The \"No Hello\" Principle\n\nInstead of:\n\n```text\nYou: Hi\nYou: Are you there?\nYou: Can I ask you something?\n[waiting...]\n```\n\nTry:\n\n```text\nYou: Hi Sarah - quick question about the deployment script.\n     Getting a permission error on line 42. Have you seen this before?\n     Here's the error: [paste error]\n```\n\n## Technical vs Non-Technical Communication\n\n### When to Be Technical vs Accessible\n\n| Audience | Approach |\n| --- | --- |\n| **Engineering peers** | Technical details, code examples, architecture specifics |\n| **Technical managers** | Balance of detail and high-level impact |\n| **Non-technical stakeholders** | Business impact, analogies, outcomes over implementation |\n| **Customers** | Plain language, what it means for them, avoid jargon |\n\n### Three Strategies for Simplification\n\n1. **Start with the big picture before details** - People process \"why\" before \"how\"\n2. **Simplify without losing accuracy** - Use analogies; replace jargon with plain language\n3. **Know when to switch** - Read the room; adjust based on questions and engagement\n\n### Jargon Translation Examples\n\n| Technical | Plain Language |\n| --- | --- |\n| \"Microservices architecture\" | \"Our system is split into smaller, independent pieces that can scale separately\" |\n| \"Asynchronous message processing\" | \"Tasks are queued and processed in the background\" |\n| \"CI\u002FCD pipeline\" | \"Automated process that tests and deploys our code\" |\n| \"Database migration\" | \"Updating how our data is organized and stored\" |\n\n**For more examples**: See `references\u002Fjargon-simplification.md`\n\n## Writing Clarity Principles\n\n### Active Voice Over Passive Voice\n\nActive voice is clearer, more direct, and conveys authority:\n\n| Passive (avoid) | Active (prefer) |\n| --- | --- |\n| \"A bug was identified by the team\" | \"The team identified a bug\" |\n| \"The feature will be implemented\" | \"We will implement the feature\" |\n| \"Errors were found during testing\" | \"Testing revealed errors\" |\n\n### Eliminate Filler Words\n\n| Instead of | Use |\n| --- | --- |\n| \"At this point in time\" | \"Now\" |\n| \"In the event that\" | \"If\" |\n| \"Due to the fact that\" | \"Because\" |\n| \"In order to\" | \"To\" |\n| \"I just wanted to check if\" | \"Can you\" |\n\n### The \"So What?\" Test\n\nAfter writing, ask: \"So what? Why does this matter to the reader?\"\n\nIf you can't answer clearly, restructure your message to lead with the value\u002Fimpact.\n\n## Meeting Communication\n\n### Before: Agenda Best Practices\n\nEvery meeting invite should include:\n\n1. **Clear objective** - What will be accomplished?\n2. **Agenda items** - Topics to cover with time estimates\n3. **Preparation required** - What should attendees bring\u002Freview?\n4. **Expected outcome** - Decision needed? Information sharing? Brainstorm?\n\n### During: Facilitation Tips\n\n- **Time-box discussions** - \"Let's spend 5 minutes on this, then move on\"\n- **Capture action items live** - Who does what by when\n- **Parking lot** - Note off-topic items for later\n\n### After: Summary Format\n\n```markdown\n**Meeting: [Topic] - [Date]**\n\n**Attendees:** [Names]\n\n**Key Decisions:**\n- [Decision 1]\n- [Decision 2]\n\n**Action Items:**\n- [ ] [Person]: [Task] - Due [Date]\n- [ ] [Person]: [Task] - Due [Date]\n\n**Next Steps:**\n- [Follow-up meeting if needed]\n- [Documents to share]\n```\n\n**For structures by meeting type**: See `references\u002Fmeeting-structures.md`\n\n## Quick Reference: Communication Checklist\n\nBefore sending any professional communication:\n\n- [ ] **Clear purpose** - Can the recipient understand intent in 5 seconds?\n- [ ] **Right audience** - Is this the appropriate person\u002Fchannel?\n- [ ] **Key message first** - Is the main point upfront?\n- [ ] **Scannable** - Are there bullets, headers, short paragraphs?\n- [ ] **Action clear** - Does the recipient know what (if anything) they need to do?\n- [ ] **Jargon check** - Will the audience understand all terminology?\n- [ ] **Tone appropriate** - Is it professional but not cold?\n- [ ] **Proofread** - Any typos or unclear phrasing?\n\n## Additional Tools\n\n- `references\u002Femail-templates.md` - Ready-to-use email templates by type\n- `references\u002Fmeeting-structures.md` - Structures for standups, retros, reviews\n- `references\u002Fjargon-simplification.md` - Technical-to-plain-language translations\n\n## Companion Skills\n\n- `feedback-mastery` - For difficult conversations and feedback delivery\n- `\u002Fdraft-email` - Generate emails using these frameworks\n\n---\n\n**Last Updated:** 2025-12-22\n\n## Version History\n\n- **v1.0.0** (2025-12-26): Initial release\n\n---\n",{"name":5,"description":7,"allowed-tools":54},"Read, Glob, Grep","main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fprofessional-communication",3926,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates","https:\u002F\u002Faitmpl.com","https:\u002F\u002Fgithub.com\u002Fdavila7","https:\u002F\u002Fdanielavila.me","Building AI dev tools with LLMs","2026-11-12 14:45:56",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add davila7\u002Fclaude-code-templates --skill professional-communication",{"tool":71,"command":72},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill professional-communication",{"tool":74,"command":75},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill professional-communication","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fprofessional-communication\u002FSKILL.md",true,[79,85,89,93,97],{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"README.md","REFERENCE","参考文档",6609,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fprofessional-communication\u002FREADME.md",{"path":86,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Femail-templates.md",5783,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fprofessional-communication\u002Freferences\u002Femail-templates.md",{"path":90,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fjargon-simplification.md",8071,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fprofessional-communication\u002Freferences\u002Fjargon-simplification.md",{"path":94,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fmeeting-structures.md",8834,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fprofessional-communication\u002Freferences\u002Fmeeting-structures.md",{"path":98,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fremote-async-communication.md",8075,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fprofessional-communication\u002Freferences\u002Fremote-async-communication.md",[102,129,155,186,221,245],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":111,"publishedAt":49},"01M70NHBTQ8BV0A2SCAZXEPHCX","wealthville-pool-scoring","Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter\u002FHold\u002FExit\u002FReduce\u002FAvoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-data\u002Fwealthville-pool-scoring\u002FSKILL.md",[108],{"categoryNo":109,"categoryName":110,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[112,113,114,115,116,35,117,118,32,34,119,120,121,122,123,124,125,126,127,128],"scoring","pool","wealthville pool scoring","liquidity","which","exit","now","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":136,"publishedAt":49},"01M70MB6VR8ERJ4EM8D5KHBMEV","technical-debt-auditor","Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO\u002FFIXME\u002FHACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like \"where should I focus refactoring\", \"find code smells\", \"audit my codebase\", \"what technical debt do we have\", \"prioritize cleanup work\", or asks about code quality metrics. Also trigger when the user mentions \"code rot\", \"legacy cleanup\", \"refactoring priorities\", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say \"technical debt\" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ftechnical-debt-auditor\u002FSKILL.md",[135],{"categoryNo":109,"categoryName":110,"taxonomyType":21,"taxonomyTypeDesc":22},[137,138,43,139,140,141,142,143,144,145,146,34,147,148,149,150,151,152,153,154],"technical debt","debt","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":168,"publishedAt":49},"01M70KPYH9QNHCNME5GJQGE22K","readonly-sql-guard","Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production\u002FERP\u002Fanalytics database (a \"query\" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write\u002FDDL\u002Fside-effect\u002Ftransaction-escape risks. Checks what a statement CALLS, not just its shape.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdatabase\u002Freadonly-sql-guard\u002FSKILL.md",[161,164,165],{"categoryNo":162,"categoryName":163,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":109,"categoryName":110,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":166,"categoryName":167,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000033","数据分析师",[169,170,171,172,173,174,175,35,176,177,178,179,180,181,182,32,183,184,34,185],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":190,"licenseFileUrl":191,"sourceHtmlUrl":192,"categories":193,"keywords":197,"publishedAt":49},"01M6AFY6F7CC2BBZP1QD6VTNVC","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[194],{"categoryNo":195,"categoryName":196,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[198,199,200,201,202,203,204,205,206,207,208,209,210,211,212,213,214,215,216,217,218,219,35,220],"artifacts builder","web","web artifacts builder","artifacts","builder","state","routing","state management","component","css","frontend","ui","Tools","file","components","shadcn","react","Tailwind","suite","jsx","html","single-file","ui components",{"skillNo":222,"name":223,"nameZh":6,"description":224,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":190,"licenseFileUrl":225,"sourceHtmlUrl":226,"categories":227,"keywords":232,"publishedAt":49},"01M6AFWF33SFV9Z3SF4PEEE4BF","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[228,231],{"categoryNo":229,"categoryName":230,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":195,"categoryName":196,"taxonomyType":21,"taxonomyTypeDesc":22},[233,234,235,236,237,199,238,208,209,239,240,241,242,35,243,120,244],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":246,"name":247,"nameZh":6,"description":248,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":190,"licenseFileUrl":249,"sourceHtmlUrl":250,"categories":251,"keywords":259,"publishedAt":49},"01M6AF67Q67JJJ5V51JR2P52KA","discernment-nudge","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FSKILL.md",[252,255,256],{"categoryNo":253,"categoryName":254,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":109,"categoryName":110,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":257,"categoryName":258,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者",[260,261,262,263,264,265,266,267,201,268,211,147,269,270,271,272,273,181,274,34,275,276,277,278,279,126,280],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]