[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AF1F5GT1RC0WET6MMKZQQP":3,"skill-same:01M6AF1F5GT1RC0WET6MMKZQQP":88},{"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":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":47,"ownerHtmlUrl":48,"ownerBlogUrl":49,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M6AF1F5GT1RC0WET6MMKZQQP","difficult-workplace-conversations",null,"Structured approach to workplace conflicts, performance discussions, and challenging feedback using preparation-delivery-followup framework. Use when preparing for tough conversations, addressing conflicts, giving critical feedback, or navigating sensitive workplace discussions.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33481,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fdifficult-workplace-conversations\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35],"difficult workplace conversations","conversations","workplace","delivery","when","preparation","for","followup","critical","structured","performance","conflicts","use","read","grep","feedback","framework","2026-11-10 10:12:30",false,"---\nname: difficult-workplace-conversations\ndescription: Structured approach to workplace conflicts, performance discussions, and challenging feedback using preparation-delivery-followup framework. Use when preparing for tough conversations, addressing conflicts, giving critical feedback, or navigating sensitive workplace discussions.\nallowed-tools: Read, Glob, Grep\n---\n\n# Difficult Conversations Skill\n\nA structured framework for approaching challenging workplace conversations including conflicts, performance issues, sensitive feedback, and emotionally charged discussions.\n\n## When to Use This Skill\n\n- Preparing for a challenging conversation with a colleague\n- Addressing performance issues with a team member\n- Delivering difficult feedback to a peer or manager\n- Navigating conflict between team members\n- Discussing sensitive topics (salary, promotion, termination)\n- Handling emotional or defensive reactions\n- Following up after difficult discussions\n\n## Core Framework: Preparation-Delivery-Followup\n\nDifficult conversations succeed or fail based on three phases:\n\n### Phase 1: Preparation (Before)\n\n**Purpose:** Set yourself up for a productive conversation\n\n1. **Clarify the Issue**\n   - What specifically happened? (Observable facts only)\n   - What is the impact? (On you, team, work)\n   - What do you need to change?\n\n2. **Check Your Emotions**\n   - What am I feeling? Why?\n   - Am I calm enough to have this conversation?\n   - What might trigger me during this conversation?\n\n3. **Consider Their Perspective**\n   - How might they see this situation?\n   - What constraints or pressures might they have?\n   - What do they care about that I can acknowledge?\n\n4. **Define Your Goal**\n   - What outcome do I want?\n   - What is the minimum acceptable result?\n   - What am I willing to compromise on?\n\n### Phase 2: Delivery (During)\n\n**Purpose:** Have the conversation effectively\n\n1. **Open Neutrally**\n   - Start with facts, not judgments\n   - Express intent to understand, not accuse\n   - Create psychological safety\n\n2. **Share Your Perspective**\n   - Describe behavior, not character\n   - Focus on impact, not intention\n   - Use \"I\" statements, not \"you always\"\n\n3. **Listen Actively**\n   - Ask clarifying questions\n   - Acknowledge their viewpoint\n   - Look for shared interests\n\n4. **Seek Resolution**\n   - Propose specific actions\n   - Agree on next steps\n   - Set check-in timeline\n\n### Phase 3: Followup (After)\n\n**Purpose:** Ensure lasting resolution\n\n1. **Document Agreements**\n   - What was agreed?\n   - Who does what by when?\n   - How will you measure success?\n\n2. **Check Progress**\n   - Follow up as promised\n   - Acknowledge improvements\n   - Address continued issues promptly\n\n3. **Maintain Relationship**\n   - Separate issue from person\n   - Rebuild trust over time\n   - Watch for regression\n\n## Key Principles\n\n### Separate Impact from Intent\n\n**What happened:** Observable behavior\n**What I felt:** Your emotional response\n**What I assume:** Their intention (often wrong)\n\nFocus conversation on behavior and impact, not assumed intentions.\n\n### The SBI Model\n\n**Situation:** When and where did this happen?\n**Behavior:** What specifically did they do\u002Fsay?\n**Impact:** What was the effect on you, the team, or the work?\n\n### Managing Emotions\n\n| If You Feel | Before Acting |\n| ----------- | ------------- |\n| Angry | Wait 24 hours, write but don't send |\n| Hurt | Talk to neutral party first |\n| Anxious | Practice the conversation |\n| Defensive | Identify your contribution |\n\n### When to Escalate\n\nEscalate when:\n\n- Safety is at risk\n- Legal issues involved\n- Repeated conversations haven't worked\n- Power dynamics prevent resolution\n- You need documentation\n\n## Conversation Types\n\n### Performance Feedback\n\n- Lead with specific examples\n- Connect to expectations\u002Fstandards\n- Focus on future improvement\n- Offer support and resources\n\n### Conflict Resolution\n\n- Hear both sides separately first\n- Identify underlying interests\n- Look for win-win solutions\n- Document agreements\n\n### Sensitive Topics\n\n- Choose private, neutral setting\n- Allow time for processing\n- Be direct but compassionate\n- Respect confidentiality\n\n### Receiving Feedback\n\n- Thank them for feedback\n- Ask clarifying questions\n- Don't defend immediately\n- Reflect before responding\n\n## References (Load When Needed)\n\n### Detailed Frameworks\n\n- **[Conversation Framework](references\u002Fconversation-framework.md)**: Complete three-phase framework with scripts and examples\n- **[Preparation Template](references\u002Fpreparation-template.md)**: Worksheet for preparing before difficult conversations\n- **[Delivery Scripts](references\u002Fdelivery-scripts.md)**: Opening lines, response handling, reframing techniques\n- **[Emotional Regulation](references\u002Femotional-regulation.md)**: Managing your own emotions before and during\n\n## See Also\n\n- `feedback-mastery` skill - SBI feedback model (overlaps but more feedback-focused)\n- `professional-effective-communication` skill - General communication patterns\n\n## Example Scenarios\n\n### Scenario 1: Addressing Missed Deadlines\n\n```markdown\n**Issue:** Team member missed 3 deadlines in past month\n**Impact:** Project delayed, others blocked\n**Goal:** Understand root cause, agree on prevention plan\n\n**Opening:** \"I wanted to check in about the recent deliverables. I've noticed\nthe last three have come in past deadline, and I'd like to understand what's\nhappening and how we can address it together.\"\n```\n\n### Scenario 2: Peer Conflict\n\n```markdown\n**Issue:** Colleague publicly criticized your work in meeting\n**Impact:** Embarrassed, trust damaged\n**Goal:** Address behavior, rebuild working relationship\n\n**Opening:** \"I'd like to talk about what happened in yesterday's standup.\nWhen you said my code 'missed obvious issues,' I felt called out in front\nof the team. I'd like to understand your concerns and find a better way\nto handle code quality feedback.\"\n```\n\n### Scenario 3: Asking Manager for Raise\n\n```markdown\n**Issue:** Feel underpaid relative to market\u002Fcontribution\n**Impact:** Demotivation, considering leaving\n**Goal:** Discuss compensation, get timeline or adjustment\n\n**Opening:** \"I'd like to discuss my compensation. I've been here two years,\ntaken on the payments project leadership, and want to make sure my salary\nreflects my contributions and the current market.\"\n```\n\n## Anti-Patterns to Avoid\n\n### In Preparation\n\n- **Scripting every word** - You'll sound robotic; prepare themes, not scripts\n- **Building a case** - This isn't a trial; seek understanding, not winning\n- **Waiting too long** - Issues compound; address promptly\n\n### In Delivery\n\n- **Starting with \"You always...\"** - Triggers defensiveness immediately\n- **Burying the lead** - Get to the point; don't soften excessively\n- **Asking leading questions** - \"Don't you think...\" isn't asking\n\n### In Followup\n\n- **Forgetting to check in** - Without follow-up, nothing changes\n- **Holding grudges** - Issue resolved means relationship continues\n- **Over-documenting** - Not everything needs written record\n\n## Success Metrics\n\nA successful difficult conversation:\n\n- Both parties feel heard\n- Specific actions are agreed\n- Relationship is preserved or improved\n- The issue doesn't recur (or has clear escalation)\n- Neither party is blindsided later\n","# Difficult Conversations Skill\n\nA structured framework for approaching challenging workplace conversations including conflicts, performance issues, sensitive feedback, and emotionally charged discussions.\n\n## When to Use This Skill\n\n- Preparing for a challenging conversation with a colleague\n- Addressing performance issues with a team member\n- Delivering difficult feedback to a peer or manager\n- Navigating conflict between team members\n- Discussing sensitive topics (salary, promotion, termination)\n- Handling emotional or defensive reactions\n- Following up after difficult discussions\n\n## Core Framework: Preparation-Delivery-Followup\n\nDifficult conversations succeed or fail based on three phases:\n\n### Phase 1: Preparation (Before)\n\n**Purpose:** Set yourself up for a productive conversation\n\n1. **Clarify the Issue**\n   - What specifically happened? (Observable facts only)\n   - What is the impact? (On you, team, work)\n   - What do you need to change?\n\n2. **Check Your Emotions**\n   - What am I feeling? Why?\n   - Am I calm enough to have this conversation?\n   - What might trigger me during this conversation?\n\n3. **Consider Their Perspective**\n   - How might they see this situation?\n   - What constraints or pressures might they have?\n   - What do they care about that I can acknowledge?\n\n4. **Define Your Goal**\n   - What outcome do I want?\n   - What is the minimum acceptable result?\n   - What am I willing to compromise on?\n\n### Phase 2: Delivery (During)\n\n**Purpose:** Have the conversation effectively\n\n1. **Open Neutrally**\n   - Start with facts, not judgments\n   - Express intent to understand, not accuse\n   - Create psychological safety\n\n2. **Share Your Perspective**\n   - Describe behavior, not character\n   - Focus on impact, not intention\n   - Use \"I\" statements, not \"you always\"\n\n3. **Listen Actively**\n   - Ask clarifying questions\n   - Acknowledge their viewpoint\n   - Look for shared interests\n\n4. **Seek Resolution**\n   - Propose specific actions\n   - Agree on next steps\n   - Set check-in timeline\n\n### Phase 3: Followup (After)\n\n**Purpose:** Ensure lasting resolution\n\n1. **Document Agreements**\n   - What was agreed?\n   - Who does what by when?\n   - How will you measure success?\n\n2. **Check Progress**\n   - Follow up as promised\n   - Acknowledge improvements\n   - Address continued issues promptly\n\n3. **Maintain Relationship**\n   - Separate issue from person\n   - Rebuild trust over time\n   - Watch for regression\n\n## Key Principles\n\n### Separate Impact from Intent\n\n**What happened:** Observable behavior\n**What I felt:** Your emotional response\n**What I assume:** Their intention (often wrong)\n\nFocus conversation on behavior and impact, not assumed intentions.\n\n### The SBI Model\n\n**Situation:** When and where did this happen?\n**Behavior:** What specifically did they do\u002Fsay?\n**Impact:** What was the effect on you, the team, or the work?\n\n### Managing Emotions\n\n| If You Feel | Before Acting |\n| ----------- | ------------- |\n| Angry | Wait 24 hours, write but don't send |\n| Hurt | Talk to neutral party first |\n| Anxious | Practice the conversation |\n| Defensive | Identify your contribution |\n\n### When to Escalate\n\nEscalate when:\n\n- Safety is at risk\n- Legal issues involved\n- Repeated conversations haven't worked\n- Power dynamics prevent resolution\n- You need documentation\n\n## Conversation Types\n\n### Performance Feedback\n\n- Lead with specific examples\n- Connect to expectations\u002Fstandards\n- Focus on future improvement\n- Offer support and resources\n\n### Conflict Resolution\n\n- Hear both sides separately first\n- Identify underlying interests\n- Look for win-win solutions\n- Document agreements\n\n### Sensitive Topics\n\n- Choose private, neutral setting\n- Allow time for processing\n- Be direct but compassionate\n- Respect confidentiality\n\n### Receiving Feedback\n\n- Thank them for feedback\n- Ask clarifying questions\n- Don't defend immediately\n- Reflect before responding\n\n## References (Load When Needed)\n\n### Detailed Frameworks\n\n- **[Conversation Framework](references\u002Fconversation-framework.md)**: Complete three-phase framework with scripts and examples\n- **[Preparation Template](references\u002Fpreparation-template.md)**: Worksheet for preparing before difficult conversations\n- **[Delivery Scripts](references\u002Fdelivery-scripts.md)**: Opening lines, response handling, reframing techniques\n- **[Emotional Regulation](references\u002Femotional-regulation.md)**: Managing your own emotions before and during\n\n## See Also\n\n- `feedback-mastery` skill - SBI feedback model (overlaps but more feedback-focused)\n- `professional-effective-communication` skill - General communication patterns\n\n## Example Scenarios\n\n### Scenario 1: Addressing Missed Deadlines\n\n```markdown\n**Issue:** Team member missed 3 deadlines in past month\n**Impact:** Project delayed, others blocked\n**Goal:** Understand root cause, agree on prevention plan\n\n**Opening:** \"I wanted to check in about the recent deliverables. I've noticed\nthe last three have come in past deadline, and I'd like to understand what's\nhappening and how we can address it together.\"\n```\n\n### Scenario 2: Peer Conflict\n\n```markdown\n**Issue:** Colleague publicly criticized your work in meeting\n**Impact:** Embarrassed, trust damaged\n**Goal:** Address behavior, rebuild working relationship\n\n**Opening:** \"I'd like to talk about what happened in yesterday's standup.\nWhen you said my code 'missed obvious issues,' I felt called out in front\nof the team. I'd like to understand your concerns and find a better way\nto handle code quality feedback.\"\n```\n\n### Scenario 3: Asking Manager for Raise\n\n```markdown\n**Issue:** Feel underpaid relative to market\u002Fcontribution\n**Impact:** Demotivation, considering leaving\n**Goal:** Discuss compensation, get timeline or adjustment\n\n**Opening:** \"I'd like to discuss my compensation. I've been here two years,\ntaken on the payments project leadership, and want to make sure my salary\nreflects my contributions and the current market.\"\n```\n\n## Anti-Patterns to Avoid\n\n### In Preparation\n\n- **Scripting every word** - You'll sound robotic; prepare themes, not scripts\n- **Building a case** - This isn't a trial; seek understanding, not winning\n- **Waiting too long** - Issues compound; address promptly\n\n### In Delivery\n\n- **Starting with \"You always...\"** - Triggers defensiveness immediately\n- **Burying the lead** - Get to the point; don't soften excessively\n- **Asking leading questions** - \"Don't you think...\" isn't asking\n\n### In Followup\n\n- **Forgetting to check in** - Without follow-up, nothing changes\n- **Holding grudges** - Issue resolved means relationship continues\n- **Over-documenting** - Not everything needs written record\n\n## Success Metrics\n\nA successful difficult conversation:\n\n- Both parties feel heard\n- Specific actions are agreed\n- Relationship is preserved or improved\n- The issue doesn't recur (or has clear escalation)\n- Neither party is blindsided later\n",{"name":5,"description":7,"allowed-tools":41},"Read, Glob, Grep","main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fdifficult-workplace-conversations",3931,"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-14 06:14:46",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add davila7\u002Fclaude-code-templates --skill difficult-workplace-conversations",{"tool":58,"command":59},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill difficult-workplace-conversations",{"tool":61,"command":62},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill difficult-workplace-conversations","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fdifficult-workplace-conversations\u002FSKILL.md",true,[66,72,76,80,84],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"README.md","REFERENCE","参考文档",9260,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fdifficult-workplace-conversations\u002FREADME.md",{"path":73,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fconversation-framework.md",9460,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fdifficult-workplace-conversations\u002Freferences\u002Fconversation-framework.md",{"path":77,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fdelivery-scripts.md",8854,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fdifficult-workplace-conversations\u002Freferences\u002Fdelivery-scripts.md",{"path":81,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Femotional-regulation.md",8812,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fdifficult-workplace-conversations\u002Freferences\u002Femotional-regulation.md",{"path":85,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fpreparation-template.md",7357,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fdifficult-workplace-conversations\u002Freferences\u002Fpreparation-template.md",[89,118,145,178,213,237],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":100,"publishedAt":36},"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",[95],{"categoryNo":96,"categoryName":97,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[101,102,103,104,105,25,106,107,31,23,108,109,110,111,112,113,114,115,116,117],"scoring","pool","wealthville pool scoring","liquidity","which","exit","now","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":125,"publishedAt":36},"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",[124],{"categoryNo":96,"categoryName":97,"taxonomyType":98,"taxonomyTypeDesc":99},[126,127,128,129,130,131,132,133,134,135,136,23,137,138,139,140,141,142,143,144],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":160,"publishedAt":36},"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",[151,154,155],{"categoryNo":152,"categoryName":153,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":96,"categoryName":97,"taxonomyType":98,"taxonomyTypeDesc":99},{"categoryNo":156,"categoryName":157,"taxonomyType":158,"taxonomyTypeDesc":159},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[161,162,163,164,165,166,167,25,168,169,170,171,172,173,174,31,175,176,23,177],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":182,"licenseFileUrl":183,"sourceHtmlUrl":184,"categories":185,"keywords":189,"publishedAt":36},"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",[186],{"categoryNo":187,"categoryName":188,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000009","前端开发",[190,191,192,193,194,195,196,197,198,199,200,201,202,203,204,205,206,207,208,209,210,211,25,212],"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":214,"name":215,"nameZh":6,"description":216,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":182,"licenseFileUrl":217,"sourceHtmlUrl":218,"categories":219,"keywords":224,"publishedAt":36},"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",[220,223],{"categoryNo":221,"categoryName":222,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":187,"categoryName":188,"taxonomyType":98,"taxonomyTypeDesc":99},[225,226,227,228,229,191,230,200,201,231,232,233,234,25,235,109,236],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":238,"name":239,"nameZh":6,"description":240,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":182,"licenseFileUrl":241,"sourceHtmlUrl":242,"categories":243,"keywords":251,"publishedAt":36},"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",[244,247,248],{"categoryNo":245,"categoryName":246,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":96,"categoryName":97,"taxonomyType":98,"taxonomyTypeDesc":99},{"categoryNo":249,"categoryName":250,"taxonomyType":158,"taxonomyTypeDesc":159},"01JBSEEDCAT000000000000036","内容创作者",[252,253,254,255,256,257,258,259,193,260,203,137,261,262,263,264,265,173,266,23,267,268,269,270,271,115,272],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]