Wp Performance Review
elvismdev/claude-wordpress-skills
WordPress performance code review and optimization analysis.
Navigate difficult conversations and deliver constructive feedback using structured frameworks.
Install Feedback Mastery
$ npx skills add davila7/claude-code-templates --skill feedback-mastery -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install davila7/claude-code-templates feedback-mastery --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/davila7/claude-code-templates.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cli-tool/components/skills/enterprise-communication/feedback-mastery .claude/skills/feedback-mastery && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "feedback-mastery" agent skill from https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/enterprise-communication/feedback-mastery into .claude/skills/feedback-mastery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feedback-mastery", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/enterprise-communication/feedback-masteryType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add davila7/claude-code-templates --skill feedback-mastery -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install davila7/claude-code-templates feedback-mastery --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/davila7/claude-code-templates.git skills-src && mkdir -p .agents/skills && cp -r skills-src/cli-tool/components/skills/enterprise-communication/feedback-mastery .agents/skills/feedback-mastery && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "feedback-mastery" agent skill from https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/enterprise-communication/feedback-mastery into .agents/skills/feedback-mastery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feedback-mastery", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add davila7/claude-code-templates --skill feedback-mastery -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install davila7/claude-code-templates feedback-mastery --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/davila7/claude-code-templates.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/cli-tool/components/skills/enterprise-communication/feedback-mastery .cursor/skills/feedback-mastery && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "feedback-mastery" agent skill from https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/enterprise-communication/feedback-mastery into .cursor/skills/feedback-mastery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feedback-mastery", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/davila7/claude-code-templates.git --path cli-tool/components/skills/enterprise-communication/feedback-mastery--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add davila7/claude-code-templates --skill feedback-mastery -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install davila7/claude-code-templates feedback-mastery --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/davila7/claude-code-templates.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/cli-tool/components/skills/enterprise-communication/feedback-mastery .gemini/skills/feedback-mastery && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "feedback-mastery" agent skill from https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/enterprise-communication/feedback-mastery into .gemini/skills/feedback-mastery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feedback-mastery", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install davila7/claude-code-templates feedback-masteryInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add davila7/claude-code-templates --skill feedback-mastery -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/davila7/claude-code-templates.git skills-src && mkdir -p .github/skills && cp -r skills-src/cli-tool/components/skills/enterprise-communication/feedback-mastery .github/skills/feedback-mastery && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "feedback-mastery" agent skill from https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/enterprise-communication/feedback-mastery into .github/skills/feedback-mastery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feedback-mastery", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add davila7/claude-code-templates --skill feedback-mastery -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install davila7/claude-code-templates feedback-mastery --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/davila7/claude-code-templates.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/cli-tool/components/skills/enterprise-communication/feedback-mastery .opencode/skills/feedback-mastery && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "feedback-mastery" agent skill from https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/enterprise-communication/feedback-mastery into .opencode/skills/feedback-mastery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feedback-mastery", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
feedback-mastery- GitHub stars
- 32k
- Used in
- 2 other repos
- Token cost
- ~2.9k tokens
- SKILL.md length
- 1,403 words
- Files
- 5 (incl. references)
- Skills in repo
- 477
- Repo updated
- First seen
- Licence
- MIT
At a glance
Navigate difficult conversations and deliver constructive feedback using structured frameworks.
- Works in 3 steps: Understand the Issue → Define Your Goals → Manage Your Emotions
- Preparing for difficult conversations
- SKILL.md covers Overview, When to Use This Skill, Core Frameworks and Preparation Phase, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Feedback Mastery is an agent skill from davila7/claude-code-templates. 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.
Its SKILL.md is about 2.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `README.md`, `references/difficult-conversation-scripts.md` and `references/expectation-alignment.md`).
It sits in Business, Finance & HR, covering Performance reviews. The repository describes itself as: CLI tool for configuring and monitoring Claude Code. The licence is MIT.
When your agent uses it
- Preparing for difficult conversations
- Giving feedback
- Managing conflicts
Example prompts
- “/feedback-mastery”
Requirements
- Pre-approved tools (allowed-tools): Read, Glob, Grep
Workflow steps
3 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 14680ec. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadGlobGrep
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Feedback Mastery loads about 2.9k tokens when it runs, and up to ~9.7k if it reads all its reference files. Until then it costs about 76 tokens; SKILL.md has 1,403 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from davila7/claude-code-templates at commit 14680ec, republished under its MIT licence (© davila7). 1,403 words, ~2,886 tokens.
Download SKILL.mdSave it as
.claude/skills/feedback-mastery/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- feedback-mastery
- description
- 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.
- allowed-tools
- Read, Glob, Grep
Feedback Conversations
Overview
This 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.
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.
When to Use This Skill
Use this skill when:
- Preparing to give feedback to a colleague or direct report
- Addressing performance issues or missed expectations
- Navigating conflict between team members
- Having 1:1 conversations about sensitive topics
- Receiving feedback and wanting to respond constructively
- Managing expectations with stakeholders
Keywords: feedback, difficult conversation, 1:1, one-on-one, performance, conflict, expectations, behavior, confrontation
Core Frameworks
The Preparation-Delivery-Follow-up Model
A three-part structure for difficult conversations:
| Phase | Focus | Key Questions |
|---|---|---|
| Preparation | Understand the issue, define goals, manage emotions | What's the problem? What outcome do I want? Am I calm? |
| Delivery | Open neutrally, use facts not blame, encourage dialogue | How do I start? What evidence do I have? How do I involve them? |
| Follow-up | Document actions, set check-ins, provide support | What did we agree to? When will we check in? How do I support? |
The SBI Feedback Model
Situation-Behavior-Impact (SBI) structures feedback to be specific, objective, and actionable:
| Component | Description | Example |
|---|---|---|
| Situation | Describe the specific context | "During yesterday's code review..." |
| Behavior | State the observable action (not interpretation) | "...you interrupted Sarah three times while she was explaining her approach..." |
| Impact | Explain the effect on team/project/person | "...which made her hesitate to share ideas and slowed down our discussion." |
Why it works: SBI removes assumptions and focuses on observable facts, reducing defensiveness.
Preparation Phase
Step 1: Understand the Issue
Ask yourself:
- What exactly is the problem? (Be specific, not vague)
- How does it impact the team, project, or company?
- Have I gathered all relevant facts?
- Is this a pattern or a one-time event?
Step 2: Define Your Goals
Before the conversation, clarify what you're seeking:
| Goal Type | Example |
|---|---|
| Behavior change | "I want them to submit code reviews on time" |
| Mutual understanding | "I want to understand what's blocking them" |
| Expectation setting | "I want to clarify what 'done' means for features" |
| Problem solving | "I want to find a solution together" |
Tip: Use if-then statements to clarify stakes:
"If this behavior continues, then the project timeline will suffer, leading to missed deliverables."
Step 3: Manage Your Emotions
High emotional intensity reduces cognitive processing by 30%. Before the conversation:
- Am I calm and in control?
- Have I separated facts from personal frustrations?
- Have I considered their perspective?
- Can I present this without accusation?
Reframing technique:
| Accusatory | Constructive |
|---|---|
| "You always miss deadlines and it slows everyone down" | "I've noticed some recent delays and want to understand any challenges you're facing" |
| "You never test your code properly" | "I've seen a few bugs slip through recently. Let's talk about our testing process" |
Delivery Phase
The Three-Step Delivery Formula
- Open with neutrality and intent
- Present the issue using facts, not blame
- Encourage dialogue and solutions
Opening Lines That Work
| Context | Opening |
|---|---|
| General | "I want to talk about something important to our team's success, and I'd love to hear your perspective." |
| Performance | "I've noticed some patterns I'd like to discuss. My goal is to support you, not criticize." |
| Conflict | "I sense there might be some tension, and I'd like to understand what's happening from your side." |
| Expectations | "I want to make sure we're aligned on expectations. Can we talk through how this project is going?" |
Facts, Not Blame
| Blaming | Factual |
|---|---|
| "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?" |
| "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" |
| "You're always late" | "The standup started at 9:00 and you joined at 9:15 the last three days. What's going on?" |
Key principles:
- Use specific examples, not generalizations ("always," "never")
- Stick to observable behaviors, not assumptions about motives
- Focus on impact, not character
Encouraging Dialogue
After stating your observation, shift to collaboration:
| Situation | Dialogue Prompt |
|---|---|
| Understanding barriers | "What's been challenging about this?" |
| Seeking their view | "How do you see the situation?" |
| Finding solutions | "What would help you succeed here?" |
| Checking alignment | "Does this match your understanding of what happened?" |
Follow-up Phase
Even successful conversations need follow-through to create lasting change.
Follow-up Checklist
- Document agreed-upon action items - What specifically will change?
- Set check-in dates - When will you revisit this?
- Provide ongoing support - How will you help them succeed?
- Celebrate progress - Recognize improvements when they happen
Sample Follow-up Message
Hi [Name],
Thanks for the conversation yesterday. I appreciated your openness.
**What we agreed to:**
- [Action item 1] - [Timeline]
- [Action item 2] - [Timeline]
**Check-in:** Let's reconnect [date] to see how things are going.
I'm here if you need any support. Thanks for working through this with me.
Best,
[Your name]SBI Examples for Software Teams
Positive Feedback
Code Review:
Situation: "During Tuesday's code review for the authentication module..." Behavior: "...you provided detailed comments on potential security vulnerabilities and suggested efficient fixes..." Impact: "...which strengthened our security posture and saved the team hours of debugging later."
Collaboration:
Situation: "In yesterday's architecture discussion..." Behavior: "...you asked clarifying questions and built on others' ideas instead of pushing your own solution..." Impact: "...which helped us reach consensus faster and made everyone feel heard."
Show full SKILL.md (552 more words)Show less
Constructive Feedback
Missed Deadlines:
Situation: "When we were finalizing the API deployment last Thursday..." Behavior: "...your testing results came in two hours after our agreed cutoff..." Impact: "...which delayed the release, risked our SLA, and caused the QA team to work overtime."
Meeting Behavior:
Situation: "In our sprint planning yesterday..." Behavior: "...you were on your phone for most of the discussion and didn't contribute when we asked for estimates..." Impact: "...which left the team without your expertise on the backend stories and made others feel their time wasn't valued."
For more examples: See references/feedback-sbi-model.md
Common Difficult Scenarios
Scenario: Performance Issue
Situation: A developer consistently delivers code with bugs.
Approach:
- Prepare: Gather specific examples (PRs, bug counts, timelines)
- Deliver: "I've noticed [X bugs in last Y PRs]. I want to understand what's happening and how I can support you."
- Explore: Ask about workload, clarity of requirements, testing confidence
- Collaborate: "What would help you feel more confident about code quality?"
- Follow-up: Check in after agreed changes, recognize improvements
Scenario: Conflict Between Team Members
Situation: Two engineers disagree on technical approach and it's affecting the team.
Approach:
- Meet separately first: Understand each perspective
- Find common ground: What do they both want? (Working product, good code, etc.)
- Facilitate together: Focus on facts and trade-offs, not personalities
- Establish decision process: How will the team decide when there's disagreement?
- Follow-up: Check that the solution is working
Scenario: Unrealistic Expectations
Situation: Leadership wants a feature in half the time needed.
Approach:
- Prepare: Data on similar past work, breakdown of required tasks
- Deliver: "I want to make sure we're aligned on what's realistic. Here's what I'm seeing..."
- Present trade-offs: "We can hit that date if we [reduce scope/add people/accept risk]"
- Collaborate: "What's most important here - the date or the full feature set?"
- Document: Get agreement in writing to avoid future misalignment
For detailed scripts: See references/difficult-conversation-scripts.md
Receiving Feedback Well
When you're on the receiving end:
During the Conversation
- Listen fully - Don't prepare your defense while they're talking
- Ask clarifying questions - "Can you give me a specific example?"
- Paraphrase to confirm - "So what you're saying is..."
- Acknowledge impact - Even if intent was different: "I can see how that affected you"
- Don't get defensive - Thank them for raising it
After the Conversation
- Reflect honestly - Is there truth in the feedback?
- Identify actions - What will you do differently?
- Follow up - Let them know what you're changing
- Ask for ongoing feedback - Show you're committed to growth
Quick Reference: Difficult Conversation Checklist
Before
- I understand the specific issue
- I have concrete examples
- I've defined my goal for the conversation
- I'm emotionally regulated
- I've considered their perspective
During
- I opened with neutrality and intent
- I stated facts, not blame
- I used SBI for specific feedback
- I asked for their perspective
- I focused on solutions, not just problems
- I documented agreed actions
After
- I sent a follow-up summary
- I scheduled a check-in
- I'm providing ongoing support
- I'm recognizing progress
Companion Resources
references/feedback-sbi-model.md- Full SBI framework with more examplesreferences/difficult-conversation-scripts.md- Opening lines and responsesreferences/expectation-alignment.md- Managing stakeholder expectations
Recommended Reading
- "Crucial Conversations" by Kerry Patterson & Joseph Grenny
- "Difficult Conversations" by Stone, Patton, Heen
- "Radical Candor" by Kim Scott
- Amy Edmondson's research on psychological safety
© davila7, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (references) in cli-tool/components/skills/enterprise-communication/feedback-mastery of davila7/claude-code-templates.
- SKILL.md
- README.md
- references/difficult-conversation-scripts.md
- references/expectation-alignment.md
- references/feedback-sbi-model.md
Open the folder on GitHubat commit 14680ec
Used in 2 other repositories
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in davila7/claude-code-templates, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Feedback Mastery next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Feedback Mastery this skilldavila7/claude-code-templates | 32k | 2 repos | ~2.9k | Automated safety check: Pass | MIT | |
| Wp Performance Reviewelvismdev/claude-wordpress-skills | 235 | 1 repos | ~4.5k | Automated safety check: Pass | MIT | |
| Align Humanagentscope-ai/OpenJudge | 868 | — | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| Performance ReportAffitor/affiliate-skills | 699 | 1 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Run Mv Hoi Reconstructionnvidia-isaac/video_to_data | 850 | — | ~1.5k | Automated safety check: Pass | Custom licence | |
| Company Analysiszhu1090093659/dsh-trading | 231 | — | ~4.2k | Automated safety check: Pass | Custom licence |
Similar skills
Align Human
agentscope-ai/OpenJudge
A skill your agent uses when the user has a judge/grader and human-labeled data, and wants to measure how well the judge agrees with humans, detect systematic biases, determine whether automatic…
Performance Report
Affitor/affiliate-skills
Generate affiliate performance reports with KPIs and recommendations.
Run Mv Hoi Reconstruction
nvidia-isaac/video_to_data
Run and validate the repository-local multi-view camera calibration and human-object reconstruction pipelines.
Company Analysis
zhu1090093659/dsh-trading
A skill your agent uses when the user wants to analyze a listed company, stock, business, or investment target; challenge or revise an existing company report; compare A/H or primary-listing/ADR…
- Official
Windbg Diagnostic Method
microsoft/win-dev-skills
Use with every WinDbg plugin investigation to apply evidence-first reasoning, confidence calibration, contrarian review, structured reporting, and deterministic validation.
More from davila7/claude-code-templates
All 477 skills in this repoPerplexity Web Search
davila7/claude-code-templates
Runs web-grounded searches through Perplexity's Sonar models over OpenRouter for current events, recent literature and cited facts beyond the model's training cutoff.
Neuropixels Data Analysis
davila7/claude-code-templates
Analyzes Neuropixels recordings from SpikeGLX or Open Ephys through preprocessing, drift correction, Kilosort4 spike sorting, quality metrics and curation.
Scientific Venue Templates
davila7/claude-code-templates
Supplies LaTeX templates and formatting rules for journals, conferences, posters, and grant proposals, then can check a draft against them.
Brand Voice Content Creator
davila7/claude-code-templates
Analyzes a brand's existing writing to lock in a consistent voice, then builds SEO blog posts and platform-specific social content around it.
CAPA Officer
davila7/claude-code-templates
Guides corrective and preventive action (CAPA) work in a quality management system, from initiation and root cause analysis through effectiveness verification.
Fda Consultant Specialist
davila7/claude-code-templates
Senior FDA consultant and specialist for medical device companies including HIPAA compliance and requirement management.
Related
Categories
Questions about Feedback Mastery
What does Feedback Mastery do?
Navigate difficult conversations and deliver constructive feedback using structured frameworks. Feedback Mastery is an agent skill from davila7/claude-code-templates. Navigate difficult conversations and deliver constructive feedback using structured frameworks.
When should I use Feedback Mastery?
Feedback Mastery fits situations like: preparing for difficult conversations; giving feedback; managing conflicts.
How do I install Feedback Mastery in Claude Code?
Run `npx skills add davila7/claude-code-templates --skill feedback-mastery -a claude-code`. Or copy the skill folder (cli-tool/components/skills/enterprise-communication/feedback-mastery in davila7/claude-code-templates) into .claude/skills/feedback-mastery in your project. Claude Code loads it when a task matches its description.
How do I install Feedback Mastery in Codex?
Run `npx skills add davila7/claude-code-templates --skill feedback-mastery -a codex`. Or copy the skill folder (cli-tool/components/skills/enterprise-communication/feedback-mastery in davila7/claude-code-templates) into .agents/skills/feedback-mastery in your project. Codex loads it when a task matches its description.
Can I use Feedback Mastery in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add davila7/claude-code-templates --skill feedback-mastery -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/feedback-mastery, .gemini/skills/feedback-mastery, .github/skills/feedback-mastery and .opencode/skills/feedback-mastery in your project.
What does Feedback Mastery need to run?
SKILL.md names no scripts, command-line tools or credentials: Feedback Mastery is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Glob, Grep.
Does Feedback Mastery access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Feedback Mastery safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Feedback Mastery use?
Feedback Mastery is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Feedback Mastery use?
About 2.9k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 6.8k tokens, read only when the agent opens those files.
What are the alternatives to Feedback Mastery?
Skills that share tags, products or a category with Feedback Mastery: Wp Performance Review (elvismdev/claude-wordpress-skills, 235 stars), Align Human (agentscope-ai/OpenJudge, 868 stars), Performance Report (Affitor/affiliate-skills, 699 stars) and Run Mv Hoi Reconstruction (nvidia-isaac/video_to_data, 850 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Feedback Mastery?
davila7 (a GitHub user) maintains it in davila7/claude-code-templates, which has 32,463 GitHub stars. The repository holds 477 skills in this directory. The repository was last updated on October 8, 2026.
Source: davila7/claude-code-templates on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.