[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AF1TE1P2AECWKMXABC3X2P":3,"skill-same:01M6AF1TE1P2AECWKMXABC3X2P":109},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M6AF1TE1P2AECWKMXABC3X2P","feedback-mastery",null,"Navigate difficult conversations and deliver constructive feedback using structured frameworks. Covers the Preparation-Delivery-Follow-up model and Situation-Behavior-Impact (SBI) feedback technique. Use when preparing for difficult conversations, giving feedback, or managing conflicts.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33332,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Ffeedback-mastery\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"feedback","feedback mastery","delivery","deliver","when","navigate","preparation","for","follow-up","conversations","impact","structured","frameworks","conflicts","up","use","behavior","read","grep","model","2026-11-10 10:12:30",false,"---\nname: feedback-mastery\ndescription: Navigate difficult conversations and deliver constructive feedback using structured frameworks. Covers the Preparation-Delivery-Follow-up model and Situation-Behavior-Impact (SBI) feedback technique. Use when preparing for difficult conversations, giving feedback, or managing conflicts.\nallowed-tools: Read, Glob, Grep\n---\n\n# Feedback Conversations\n\n## Overview\n\nThis skill provides frameworks for navigating difficult workplace conversations and delivering effective feedback. Whether you're addressing performance issues, resolving conflicts, or giving constructive feedback, these structured approaches lead to better outcomes.\n\n**Core insight:** Research shows that employees who approach difficult conversations with preparation and a clear framework are **60% more likely to reach a positive resolution** than those who engage without a plan.\n\n## When to Use This Skill\n\nUse this skill when:\n\n- Preparing to give feedback to a colleague or direct report\n- Addressing performance issues or missed expectations\n- Navigating conflict between team members\n- Having 1:1 conversations about sensitive topics\n- Receiving feedback and wanting to respond constructively\n- Managing expectations with stakeholders\n\n**Keywords**: feedback, difficult conversation, 1:1, one-on-one, performance, conflict, expectations, behavior, confrontation\n\n## Core Frameworks\n\n### The Preparation-Delivery-Follow-up Model\n\nA three-part structure for difficult conversations:\n\n| Phase | Focus | Key Questions |\n| --- | --- | --- |\n| **Preparation** | Understand the issue, define goals, manage emotions | What's the problem? What outcome do I want? Am I calm? |\n| **Delivery** | Open neutrally, use facts not blame, encourage dialogue | How do I start? What evidence do I have? How do I involve them? |\n| **Follow-up** | Document actions, set check-ins, provide support | What did we agree to? When will we check in? How do I support? |\n\n### The SBI Feedback Model\n\n**Situation-Behavior-Impact (SBI)** structures feedback to be specific, objective, and actionable:\n\n| Component | Description | Example |\n| --- | --- | --- |\n| **Situation** | Describe the specific context | \"During yesterday's code review...\" |\n| **Behavior** | State the observable action (not interpretation) | \"...you interrupted Sarah three times while she was explaining her approach...\" |\n| **Impact** | Explain the effect on team\u002Fproject\u002Fperson | \"...which made her hesitate to share ideas and slowed down our discussion.\" |\n\n**Why it works:** SBI removes assumptions and focuses on observable facts, reducing defensiveness.\n\n## Preparation Phase\n\n### Step 1: Understand the Issue\n\nAsk yourself:\n\n- **What exactly is the problem?** (Be specific, not vague)\n- **How does it impact the team, project, or company?**\n- **Have I gathered all relevant facts?**\n- **Is this a pattern or a one-time event?**\n\n### Step 2: Define Your Goals\n\nBefore the conversation, clarify what you're seeking:\n\n| Goal Type | Example |\n| --- | --- |\n| Behavior change | \"I want them to submit code reviews on time\" |\n| Mutual understanding | \"I want to understand what's blocking them\" |\n| Expectation setting | \"I want to clarify what 'done' means for features\" |\n| Problem solving | \"I want to find a solution together\" |\n\n**Tip:** Use if-then statements to clarify stakes:\n> \"If this behavior continues, then the project timeline will suffer, leading to missed deliverables.\"\n\n### Step 3: Manage Your Emotions\n\nHigh emotional intensity reduces cognitive processing by 30%. Before the conversation:\n\n- [ ] Am I calm and in control?\n- [ ] Have I separated facts from personal frustrations?\n- [ ] Have I considered their perspective?\n- [ ] Can I present this without accusation?\n\n**Reframing technique:**\n\n| Accusatory | Constructive |\n| --- | --- |\n| \"You always miss deadlines and it slows everyone down\" | \"I've noticed some recent delays and want to understand any challenges you're facing\" |\n| \"You never test your code properly\" | \"I've seen a few bugs slip through recently. Let's talk about our testing process\" |\n\n## Delivery Phase\n\n### The Three-Step Delivery Formula\n\n1. **Open with neutrality and intent**\n2. **Present the issue using facts, not blame**\n3. **Encourage dialogue and solutions**\n\n### Opening Lines That Work\n\n| Context | Opening |\n| --- | --- |\n| General | \"I want to talk about something important to our team's success, and I'd love to hear your perspective.\" |\n| Performance | \"I've noticed some patterns I'd like to discuss. My goal is to support you, not criticize.\" |\n| Conflict | \"I sense there might be some tension, and I'd like to understand what's happening from your side.\" |\n| Expectations | \"I want to make sure we're aligned on expectations. Can we talk through how this project is going?\" |\n\n### Facts, Not Blame\n\n| Blaming | Factual |\n| --- | --- |\n| \"You're not committed to this project\" | \"I've noticed your updates have been brief in our last three meetings. Is something affecting your workload?\" |\n| \"You don't care about code quality\" | \"This PR had 12 bugs caught in QA. Let's talk about what happened and how we can improve\" |\n| \"You're always late\" | \"The standup started at 9:00 and you joined at 9:15 the last three days. What's going on?\" |\n\n**Key principles:**\n\n- Use specific examples, not generalizations (\"always,\" \"never\")\n- Stick to observable behaviors, not assumptions about motives\n- Focus on impact, not character\n\n### Encouraging Dialogue\n\nAfter stating your observation, shift to collaboration:\n\n| Situation | Dialogue Prompt |\n| --- | --- |\n| Understanding barriers | \"What's been challenging about this?\" |\n| Seeking their view | \"How do you see the situation?\" |\n| Finding solutions | \"What would help you succeed here?\" |\n| Checking alignment | \"Does this match your understanding of what happened?\" |\n\n## Follow-up Phase\n\nEven successful conversations need follow-through to create lasting change.\n\n### Follow-up Checklist\n\n- [ ] **Document agreed-upon action items** - What specifically will change?\n- [ ] **Set check-in dates** - When will you revisit this?\n- [ ] **Provide ongoing support** - How will you help them succeed?\n- [ ] **Celebrate progress** - Recognize improvements when they happen\n\n### Sample Follow-up Message\n\n```markdown\nHi [Name],\n\nThanks for the conversation yesterday. I appreciated your openness.\n\n**What we agreed to:**\n- [Action item 1] - [Timeline]\n- [Action item 2] - [Timeline]\n\n**Check-in:** Let's reconnect [date] to see how things are going.\n\nI'm here if you need any support. Thanks for working through this with me.\n\nBest,\n[Your name]\n```\n\n## SBI Examples for Software Teams\n\n### Positive Feedback\n\n**Code Review:**\n> **Situation:** \"During Tuesday's code review for the authentication module...\"\n> **Behavior:** \"...you provided detailed comments on potential security vulnerabilities and suggested efficient fixes...\"\n> **Impact:** \"...which strengthened our security posture and saved the team hours of debugging later.\"\n\n**Collaboration:**\n> **Situation:** \"In yesterday's architecture discussion...\"\n> **Behavior:** \"...you asked clarifying questions and built on others' ideas instead of pushing your own solution...\"\n> **Impact:** \"...which helped us reach consensus faster and made everyone feel heard.\"\n\n### Constructive Feedback\n\n**Missed Deadlines:**\n> **Situation:** \"When we were finalizing the API deployment last Thursday...\"\n> **Behavior:** \"...your testing results came in two hours after our agreed cutoff...\"\n> **Impact:** \"...which delayed the release, risked our SLA, and caused the QA team to work overtime.\"\n\n**Meeting Behavior:**\n> **Situation:** \"In our sprint planning yesterday...\"\n> **Behavior:** \"...you were on your phone for most of the discussion and didn't contribute when we asked for estimates...\"\n> **Impact:** \"...which left the team without your expertise on the backend stories and made others feel their time wasn't valued.\"\n\n**For more examples:** See `references\u002Ffeedback-sbi-model.md`\n\n## Common Difficult Scenarios\n\n### Scenario: Performance Issue\n\n**Situation:** A developer consistently delivers code with bugs.\n\n**Approach:**\n\n1. **Prepare:** Gather specific examples (PRs, bug counts, timelines)\n2. **Deliver:** \"I've noticed [X bugs in last Y PRs]. I want to understand what's happening and how I can support you.\"\n3. **Explore:** Ask about workload, clarity of requirements, testing confidence\n4. **Collaborate:** \"What would help you feel more confident about code quality?\"\n5. **Follow-up:** Check in after agreed changes, recognize improvements\n\n### Scenario: Conflict Between Team Members\n\n**Situation:** Two engineers disagree on technical approach and it's affecting the team.\n\n**Approach:**\n\n1. **Meet separately first:** Understand each perspective\n2. **Find common ground:** What do they both want? (Working product, good code, etc.)\n3. **Facilitate together:** Focus on facts and trade-offs, not personalities\n4. **Establish decision process:** How will the team decide when there's disagreement?\n5. **Follow-up:** Check that the solution is working\n\n### Scenario: Unrealistic Expectations\n\n**Situation:** Leadership wants a feature in half the time needed.\n\n**Approach:**\n\n1. **Prepare:** Data on similar past work, breakdown of required tasks\n2. **Deliver:** \"I want to make sure we're aligned on what's realistic. Here's what I'm seeing...\"\n3. **Present trade-offs:** \"We can hit that date if we [reduce scope\u002Fadd people\u002Faccept risk]\"\n4. **Collaborate:** \"What's most important here - the date or the full feature set?\"\n5. **Document:** Get agreement in writing to avoid future misalignment\n\n**For detailed scripts:** See `references\u002Fdifficult-conversation-scripts.md`\n\n## Receiving Feedback Well\n\nWhen you're on the receiving end:\n\n### During the Conversation\n\n1. **Listen fully** - Don't prepare your defense while they're talking\n2. **Ask clarifying questions** - \"Can you give me a specific example?\"\n3. **Paraphrase to confirm** - \"So what you're saying is...\"\n4. **Acknowledge impact** - Even if intent was different: \"I can see how that affected you\"\n5. **Don't get defensive** - Thank them for raising it\n\n### After the Conversation\n\n1. **Reflect honestly** - Is there truth in the feedback?\n2. **Identify actions** - What will you do differently?\n3. **Follow up** - Let them know what you're changing\n4. **Ask for ongoing feedback** - Show you're committed to growth\n\n## Quick Reference: Difficult Conversation Checklist\n\n### Before\n\n- [ ] I understand the specific issue\n- [ ] I have concrete examples\n- [ ] I've defined my goal for the conversation\n- [ ] I'm emotionally regulated\n- [ ] I've considered their perspective\n\n### During\n\n- [ ] I opened with neutrality and intent\n- [ ] I stated facts, not blame\n- [ ] I used SBI for specific feedback\n- [ ] I asked for their perspective\n- [ ] I focused on solutions, not just problems\n- [ ] I documented agreed actions\n\n### After\n\n- [ ] I sent a follow-up summary\n- [ ] I scheduled a check-in\n- [ ] I'm providing ongoing support\n- [ ] I'm recognizing progress\n\n## Companion Resources\n\n- `references\u002Ffeedback-sbi-model.md` - Full SBI framework with more examples\n- `references\u002Fdifficult-conversation-scripts.md` - Opening lines and responses\n- `references\u002Fexpectation-alignment.md` - Managing stakeholder expectations\n\n\n## Recommended Reading\n\n- \"Crucial Conversations\" by Kerry Patterson & Joseph Grenny\n- \"Difficult Conversations\" by Stone, Patton, Heen\n- \"Radical Candor\" by Kim Scott\n- Amy Edmondson's research on psychological safety\n\n---\n","# Feedback Conversations\n\n## Overview\n\nThis skill provides frameworks for navigating difficult workplace conversations and delivering effective feedback. Whether you're addressing performance issues, resolving conflicts, or giving constructive feedback, these structured approaches lead to better outcomes.\n\n**Core insight:** Research shows that employees who approach difficult conversations with preparation and a clear framework are **60% more likely to reach a positive resolution** than those who engage without a plan.\n\n## When to Use This Skill\n\nUse this skill when:\n\n- Preparing to give feedback to a colleague or direct report\n- Addressing performance issues or missed expectations\n- Navigating conflict between team members\n- Having 1:1 conversations about sensitive topics\n- Receiving feedback and wanting to respond constructively\n- Managing expectations with stakeholders\n\n**Keywords**: feedback, difficult conversation, 1:1, one-on-one, performance, conflict, expectations, behavior, confrontation\n\n## Core Frameworks\n\n### The Preparation-Delivery-Follow-up Model\n\nA three-part structure for difficult conversations:\n\n| Phase | Focus | Key Questions |\n| --- | --- | --- |\n| **Preparation** | Understand the issue, define goals, manage emotions | What's the problem? What outcome do I want? Am I calm? |\n| **Delivery** | Open neutrally, use facts not blame, encourage dialogue | How do I start? What evidence do I have? How do I involve them? |\n| **Follow-up** | Document actions, set check-ins, provide support | What did we agree to? When will we check in? How do I support? |\n\n### The SBI Feedback Model\n\n**Situation-Behavior-Impact (SBI)** structures feedback to be specific, objective, and actionable:\n\n| Component | Description | Example |\n| --- | --- | --- |\n| **Situation** | Describe the specific context | \"During yesterday's code review...\" |\n| **Behavior** | State the observable action (not interpretation) | \"...you interrupted Sarah three times while she was explaining her approach...\" |\n| **Impact** | Explain the effect on team\u002Fproject\u002Fperson | \"...which made her hesitate to share ideas and slowed down our discussion.\" |\n\n**Why it works:** SBI removes assumptions and focuses on observable facts, reducing defensiveness.\n\n## Preparation Phase\n\n### Step 1: Understand the Issue\n\nAsk yourself:\n\n- **What exactly is the problem?** (Be specific, not vague)\n- **How does it impact the team, project, or company?**\n- **Have I gathered all relevant facts?**\n- **Is this a pattern or a one-time event?**\n\n### Step 2: Define Your Goals\n\nBefore the conversation, clarify what you're seeking:\n\n| Goal Type | Example |\n| --- | --- |\n| Behavior change | \"I want them to submit code reviews on time\" |\n| Mutual understanding | \"I want to understand what's blocking them\" |\n| Expectation setting | \"I want to clarify what 'done' means for features\" |\n| Problem solving | \"I want to find a solution together\" |\n\n**Tip:** Use if-then statements to clarify stakes:\n> \"If this behavior continues, then the project timeline will suffer, leading to missed deliverables.\"\n\n### Step 3: Manage Your Emotions\n\nHigh emotional intensity reduces cognitive processing by 30%. Before the conversation:\n\n- [ ] Am I calm and in control?\n- [ ] Have I separated facts from personal frustrations?\n- [ ] Have I considered their perspective?\n- [ ] Can I present this without accusation?\n\n**Reframing technique:**\n\n| Accusatory | Constructive |\n| --- | --- |\n| \"You always miss deadlines and it slows everyone down\" | \"I've noticed some recent delays and want to understand any challenges you're facing\" |\n| \"You never test your code properly\" | \"I've seen a few bugs slip through recently. Let's talk about our testing process\" |\n\n## Delivery Phase\n\n### The Three-Step Delivery Formula\n\n1. **Open with neutrality and intent**\n2. **Present the issue using facts, not blame**\n3. **Encourage dialogue and solutions**\n\n### Opening Lines That Work\n\n| Context | Opening |\n| --- | --- |\n| General | \"I want to talk about something important to our team's success, and I'd love to hear your perspective.\" |\n| Performance | \"I've noticed some patterns I'd like to discuss. My goal is to support you, not criticize.\" |\n| Conflict | \"I sense there might be some tension, and I'd like to understand what's happening from your side.\" |\n| Expectations | \"I want to make sure we're aligned on expectations. Can we talk through how this project is going?\" |\n\n### Facts, Not Blame\n\n| Blaming | Factual |\n| --- | --- |\n| \"You're not committed to this project\" | \"I've noticed your updates have been brief in our last three meetings. Is something affecting your workload?\" |\n| \"You don't care about code quality\" | \"This PR had 12 bugs caught in QA. Let's talk about what happened and how we can improve\" |\n| \"You're always late\" | \"The standup started at 9:00 and you joined at 9:15 the last three days. What's going on?\" |\n\n**Key principles:**\n\n- Use specific examples, not generalizations (\"always,\" \"never\")\n- Stick to observable behaviors, not assumptions about motives\n- Focus on impact, not character\n\n### Encouraging Dialogue\n\nAfter stating your observation, shift to collaboration:\n\n| Situation | Dialogue Prompt |\n| --- | --- |\n| Understanding barriers | \"What's been challenging about this?\" |\n| Seeking their view | \"How do you see the situation?\" |\n| Finding solutions | \"What would help you succeed here?\" |\n| Checking alignment | \"Does this match your understanding of what happened?\" |\n\n## Follow-up Phase\n\nEven successful conversations need follow-through to create lasting change.\n\n### Follow-up Checklist\n\n- [ ] **Document agreed-upon action items** - What specifically will change?\n- [ ] **Set check-in dates** - When will you revisit this?\n- [ ] **Provide ongoing support** - How will you help them succeed?\n- [ ] **Celebrate progress** - Recognize improvements when they happen\n\n### Sample Follow-up Message\n\n```markdown\nHi [Name],\n\nThanks for the conversation yesterday. I appreciated your openness.\n\n**What we agreed to:**\n- [Action item 1] - [Timeline]\n- [Action item 2] - [Timeline]\n\n**Check-in:** Let's reconnect [date] to see how things are going.\n\nI'm here if you need any support. Thanks for working through this with me.\n\nBest,\n[Your name]\n```\n\n## SBI Examples for Software Teams\n\n### Positive Feedback\n\n**Code Review:**\n> **Situation:** \"During Tuesday's code review for the authentication module...\"\n> **Behavior:** \"...you provided detailed comments on potential security vulnerabilities and suggested efficient fixes...\"\n> **Impact:** \"...which strengthened our security posture and saved the team hours of debugging later.\"\n\n**Collaboration:**\n> **Situation:** \"In yesterday's architecture discussion...\"\n> **Behavior:** \"...you asked clarifying questions and built on others' ideas instead of pushing your own solution...\"\n> **Impact:** \"...which helped us reach consensus faster and made everyone feel heard.\"\n\n### Constructive Feedback\n\n**Missed Deadlines:**\n> **Situation:** \"When we were finalizing the API deployment last Thursday...\"\n> **Behavior:** \"...your testing results came in two hours after our agreed cutoff...\"\n> **Impact:** \"...which delayed the release, risked our SLA, and caused the QA team to work overtime.\"\n\n**Meeting Behavior:**\n> **Situation:** \"In our sprint planning yesterday...\"\n> **Behavior:** \"...you were on your phone for most of the discussion and didn't contribute when we asked for estimates...\"\n> **Impact:** \"...which left the team without your expertise on the backend stories and made others feel their time wasn't valued.\"\n\n**For more examples:** See `references\u002Ffeedback-sbi-model.md`\n\n## Common Difficult Scenarios\n\n### Scenario: Performance Issue\n\n**Situation:** A developer consistently delivers code with bugs.\n\n**Approach:**\n\n1. **Prepare:** Gather specific examples (PRs, bug counts, timelines)\n2. **Deliver:** \"I've noticed [X bugs in last Y PRs]. I want to understand what's happening and how I can support you.\"\n3. **Explore:** Ask about workload, clarity of requirements, testing confidence\n4. **Collaborate:** \"What would help you feel more confident about code quality?\"\n5. **Follow-up:** Check in after agreed changes, recognize improvements\n\n### Scenario: Conflict Between Team Members\n\n**Situation:** Two engineers disagree on technical approach and it's affecting the team.\n\n**Approach:**\n\n1. **Meet separately first:** Understand each perspective\n2. **Find common ground:** What do they both want? (Working product, good code, etc.)\n3. **Facilitate together:** Focus on facts and trade-offs, not personalities\n4. **Establish decision process:** How will the team decide when there's disagreement?\n5. **Follow-up:** Check that the solution is working\n\n### Scenario: Unrealistic Expectations\n\n**Situation:** Leadership wants a feature in half the time needed.\n\n**Approach:**\n\n1. **Prepare:** Data on similar past work, breakdown of required tasks\n2. **Deliver:** \"I want to make sure we're aligned on what's realistic. Here's what I'm seeing...\"\n3. **Present trade-offs:** \"We can hit that date if we [reduce scope\u002Fadd people\u002Faccept risk]\"\n4. **Collaborate:** \"What's most important here - the date or the full feature set?\"\n5. **Document:** Get agreement in writing to avoid future misalignment\n\n**For detailed scripts:** See `references\u002Fdifficult-conversation-scripts.md`\n\n## Receiving Feedback Well\n\nWhen you're on the receiving end:\n\n### During the Conversation\n\n1. **Listen fully** - Don't prepare your defense while they're talking\n2. **Ask clarifying questions** - \"Can you give me a specific example?\"\n3. **Paraphrase to confirm** - \"So what you're saying is...\"\n4. **Acknowledge impact** - Even if intent was different: \"I can see how that affected you\"\n5. **Don't get defensive** - Thank them for raising it\n\n### After the Conversation\n\n1. **Reflect honestly** - Is there truth in the feedback?\n2. **Identify actions** - What will you do differently?\n3. **Follow up** - Let them know what you're changing\n4. **Ask for ongoing feedback** - Show you're committed to growth\n\n## Quick Reference: Difficult Conversation Checklist\n\n### Before\n\n- [ ] I understand the specific issue\n- [ ] I have concrete examples\n- [ ] I've defined my goal for the conversation\n- [ ] I'm emotionally regulated\n- [ ] I've considered their perspective\n\n### During\n\n- [ ] I opened with neutrality and intent\n- [ ] I stated facts, not blame\n- [ ] I used SBI for specific feedback\n- [ ] I asked for their perspective\n- [ ] I focused on solutions, not just problems\n- [ ] I documented agreed actions\n\n### After\n\n- [ ] I sent a follow-up summary\n- [ ] I scheduled a check-in\n- [ ] I'm providing ongoing support\n- [ ] I'm recognizing progress\n\n## Companion Resources\n\n- `references\u002Ffeedback-sbi-model.md` - Full SBI framework with more examples\n- `references\u002Fdifficult-conversation-scripts.md` - Opening lines and responses\n- `references\u002Fexpectation-alignment.md` - Managing stakeholder expectations\n\n\n## Recommended Reading\n\n- \"Crucial Conversations\" by Kerry Patterson & Joseph Grenny\n- \"Difficult Conversations\" by Stone, Patton, Heen\n- \"Radical Candor\" by Kim Scott\n- Amy Edmondson's research on psychological safety\n\n---\n",{"name":5,"description":7,"allowed-tools":44},"Read, Glob, Grep","main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Ffeedback-mastery",3911,"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-11 21:38:31",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add davila7\u002Fclaude-code-templates --skill feedback-mastery",{"tool":61,"command":62},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill feedback-mastery",{"tool":64,"command":65},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill feedback-mastery","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Ffeedback-mastery\u002FSKILL.md",true,[69,75,79,83,87,91,97,101,105],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"README.md","REFERENCE","参考文档",9924,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Ffeedback-mastery\u002FREADME.md",{"path":76,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":77,"sourceHtmlUrl":78},"reference\u002Fevidence.md",21910,"https:\u002F\u002Fgithub.com\u002Fnoirelab\u002Flinux-setup\u002Fblob\u002Fmain\u002Fconfigs\u002Fcommon\u002Fclaude\u002Fskills\u002Fcraft-ladder\u002Freference\u002Fevidence.md",{"path":80,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fdifficult-conversation-scripts.md",10232,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Ffeedback-mastery\u002Freferences\u002Fdifficult-conversation-scripts.md",{"path":84,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fexpectation-alignment.md",8398,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Ffeedback-mastery\u002Freferences\u002Fexpectation-alignment.md",{"path":88,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Ffeedback-sbi-model.md",8623,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Ffeedback-mastery\u002Freferences\u002Ffeedback-sbi-model.md",{"path":92,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"tools\u002Fextract2.py","SCRIPT","脚本",5614,"https:\u002F\u002Fgithub.com\u002Fnoirelab\u002Flinux-setup\u002Fblob\u002Fmain\u002Fconfigs\u002Fcommon\u002Fclaude\u002Fskills\u002Fcraft-ladder\u002Ftools\u002Fextract2.py",{"path":98,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":99,"sourceHtmlUrl":100},"tools\u002Fkiwi.py",4573,"https:\u002F\u002Fgithub.com\u002Fnoirelab\u002Flinux-setup\u002Fblob\u002Fmain\u002Fconfigs\u002Fcommon\u002Fclaude\u002Fskills\u002Fcraft-ladder\u002Ftools\u002Fkiwi.py",{"path":102,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":103,"sourceHtmlUrl":104},"tools\u002Fmotion.py",3741,"https:\u002F\u002Fgithub.com\u002Fnoirelab\u002Flinux-setup\u002Fblob\u002Fmain\u002Fconfigs\u002Fcommon\u002Fclaude\u002Fskills\u002Fcraft-ladder\u002Ftools\u002Fmotion.py",{"path":106,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":107,"sourceHtmlUrl":108},"tools\u002FREADME.md",655,"https:\u002F\u002Fgithub.com\u002Fnoirelab\u002Flinux-setup\u002Fblob\u002Fmain\u002Fconfigs\u002Fcommon\u002Fclaude\u002Fskills\u002Fcraft-ladder\u002Ftools\u002FREADME.md",[110,139,166,199,234,257],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":121,"publishedAt":39},"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",[116],{"categoryNo":117,"categoryName":118,"taxonomyType":119,"taxonomyTypeDesc":120},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[122,123,124,125,126,26,127,128,34,23,129,130,131,132,133,134,135,136,137,138],"scoring","pool","wealthville pool scoring","liquidity","which","exit","now","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":146,"publishedAt":39},"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",[145],{"categoryNo":117,"categoryName":118,"taxonomyType":119,"taxonomyTypeDesc":120},[147,148,149,150,151,152,153,154,155,156,157,23,158,159,160,161,162,163,164,165],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":181,"publishedAt":39},"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",[172,175,176],{"categoryNo":173,"categoryName":174,"taxonomyType":119,"taxonomyTypeDesc":120},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":117,"categoryName":118,"taxonomyType":119,"taxonomyTypeDesc":120},{"categoryNo":177,"categoryName":178,"taxonomyType":179,"taxonomyTypeDesc":180},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[182,183,184,185,186,187,188,26,189,190,191,192,193,194,195,34,196,197,23,198],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":200,"name":201,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":203,"licenseFileUrl":204,"sourceHtmlUrl":205,"categories":206,"keywords":210,"publishedAt":39},"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",[207],{"categoryNo":208,"categoryName":209,"taxonomyType":119,"taxonomyTypeDesc":120},"01JBSEEDCAT000000000000009","前端开发",[211,212,213,214,215,216,217,218,219,220,221,222,223,224,225,226,227,228,229,230,231,232,26,233],"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":235,"name":236,"nameZh":6,"description":237,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":203,"licenseFileUrl":238,"sourceHtmlUrl":239,"categories":240,"keywords":245,"publishedAt":39},"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",[241,244],{"categoryNo":242,"categoryName":243,"taxonomyType":119,"taxonomyTypeDesc":120},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":208,"categoryName":209,"taxonomyType":119,"taxonomyTypeDesc":120},[246,247,248,249,250,212,251,221,222,252,253,254,255,26,256,130,35],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local",{"skillNo":258,"name":259,"nameZh":6,"description":260,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":203,"licenseFileUrl":261,"sourceHtmlUrl":262,"categories":263,"keywords":271,"publishedAt":39},"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",[264,267,268],{"categoryNo":265,"categoryName":266,"taxonomyType":119,"taxonomyTypeDesc":120},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":117,"categoryName":118,"taxonomyType":119,"taxonomyTypeDesc":120},{"categoryNo":269,"categoryName":270,"taxonomyType":179,"taxonomyTypeDesc":180},"01JBSEEDCAT000000000000036","内容创作者",[272,273,274,275,276,277,278,279,214,280,224,158,281,282,283,284,33,194,285,23,286,287,288,289,290,136,291],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","invoke","you","analysis","claims","argument","assemble","recommendations"]