Agent skill

Giving Feedback

by mohitagw15856 in mohitagw15856/pm-claude-skills

Turn a vague concern into specific, kind, actionable feedback.

MITAuto-check passed

Install Giving Feedback

skills CLI
$ npx skills add mohitagw15856/pm-claude-skills --skill giving-feedback -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mohitagw15856/pm-claude-skills giving-feedback --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/giving-feedback .claude/skills/giving-feedback && rm -rf skills-src

Use ~/.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/

Facts

Skill name
giving-feedback
GitHub stars
1.4k
Token cost
~897 tokens
SKILL.md length
453 words
Files
1
Skills in repo
1,348
Repo updated
First seen
Licence
MIT

At a glance

Turn a vague concern into specific, kind, actionable feedback.

  • Asked to give feedback
  • SKILL.md covers Required Inputs, Output Format, Quality Checks and Anti-Patterns, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Write a feedback note

What it does

Giving Feedback is an agent skill from mohitagw15856/pm-claude-skills. Turn a vague concern into specific, kind, actionable feedback. Use when asked to give feedback, write a feedback note, prepare to tell someone something hard about their work, or coach a report/peer. Produces ready-to-deliver feedback structured on situation–behaviour–impact, separating observation from judgement, with the change requested and an opening line — calibrated to praise or constructive.

Its SKILL.md is about 900 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.

When your agent uses it

  • Asked to give feedback
  • Write a feedback note
  • Prepare to tell someone something hard about their work
  • Coach a report/peer

Example prompts

  • “/giving-feedback”

What it can do on your machine

Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    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

Giving Feedback loads about 897 tokens when it runs. Until then it costs about 104 tokens; SKILL.md has 453 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~104
When it runs · the whole SKILL.md, loaded when a task matches
~897

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 mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 453 words, ~897 tokens.

Download SKILL.mdSave it as .claude/skills/giving-feedback/SKILL.md (or your agent's skills folder).
name
giving-feedback
description
Turn a vague concern into specific, kind, actionable feedback. Use when asked to give feedback, write a feedback note, prepare to tell someone something hard about their work, or coach a report/peer. Produces ready-to-deliver feedback structured on situation–behaviour–impact, separating observation from judgement, with the change requested and an opening line — calibrated to praise or constructive.

Giving Feedback Skill

Most feedback is useless because it's vague ("be more proactive"), judgemental ("you're careless"), or sandwiched into mush. Good feedback is specific, describes behaviour not character, names the impact, and makes the ask clear. This skill turns a fuzzy concern into feedback the person can actually act on — delivered with enough care that they hear it.

Required Inputs

Ask for these only if they aren't already provided:

  • What happened — the specific situation and the observable behaviour (not your conclusion about them).
  • The impact — what it caused (for the work, the team, the customer, you).
  • Type — reinforcing (praise worth repeating) or constructive (change needed). Both deserve specificity.
  • The relationship & context — report, peer, manager; and any relevant history.

Output Format

Feedback: [topic] for [who]

1. The core (SBI) — the spine of good feedback:

  • Situation — when/where, specifically ("In yesterday's client review…").
  • Behaviour — what they did, observable and neutral ("…the demo skipped the pricing slide").
  • Impact — the effect ("…so the client left unsure what it costs, and emailed to ask").

2. The ask — for constructive: the specific change ("next time, walk the pricing slide before Q&A"). For praise: name what to keep doing and why it mattered (praise that's specific gets repeated).

3. Opening line — how to start so they're ready to hear it (ask permission / state intent: "Can I share something from the review? I want the next one to land even better.").

4. Make it a dialogue — 1–2 questions to invite their view ("How did it feel from your side?"), because feedback is a conversation, not a verdict.

Calibration note — keep it timely (soon, not saved for the review), private if constructive, and about the behaviour, never the person.

Show full SKILL.md (174 more words)Show less

Quality Checks

  • Built on situation–behaviour–impact, with each part concrete
  • Behaviour is observable, separated from judgement of character
  • The requested change (or the keep-doing) is explicit and actionable
  • It opens in a way that lowers defensiveness
  • It invites the other person's perspective — a dialogue, not a verdict
  • Praise is as specific as criticism (vague praise doesn't reinforce)

Anti-Patterns

  • Do not judge character ("you're disorganised") — describe behaviour ("the doc was missing the dates")
  • Do not use the feedback sandwich — burying the point in praise muddles both; be direct and kind
  • Do not be vague ("be more strategic") — if they can't picture the change, it's not feedback
  • Do not save it for the review — feedback works when it's timely and low-stakes, not stockpiled
  • Do not make praise generic ("great job!") — specific praise is what gets the behaviour repeated

Based On

SBI feedback model (Center for Creative Leadership) and Radical Candor (Kim Scott) — care personally, challenge directly.

Example Trigger Phrases

  • "Give feedback."
  • "Write a feedback note."
  • "Prepare to tell someone something hard about their work."
  • "Coach a report/peer."

© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/giving-feedback of mohitagw15856/pm-claude-skills.

Open the folder on GitHubat commit 1cbf1f0

Compare with similar skills

Giving Feedback 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.

Giving Feedback compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Giving Feedback this skillmohitagw15856/pm-claude-skills1.4k—~897Automated safety check: PassMIT
Giving FeedbackRefoundAI/lenny-skills1.4k—~2.2kAutomated safety check: PassMIT
Feedbackcodewhale-hq/Codewhale41k—~272Automated safety check: PassMIT
ActionsJetBrains/intellij-community21k—~341Automated safety check: PassCustom licence
Laravel Actionscoollabsio/coolify63k—~2.4kAutomated safety check: PassApache-2.0
ActionsBuilderIO/agent-native7.1k—~4.5kAutomated safety check: PassNone

Similar skills

  • Giving Feedback

    RefoundAI/lenny-skills

    Help users deliver high-impact feedback that drives behavior change while maintaining strong relationships and psychological safety through proven frameworks like GAIN and Radical Candor.

    1.4k GitHub stars~2.2k tokensUpdated 2 mo ago
    Auto-check passed
  • Feedback

    codewhale-hq/Codewhale

    Report a Codewhale bug or idea as a GitHub issue. An agent skill from codewhale-hq/Codewhale.

    41k GitHub stars~272 tokensUpdated today
    Auto-check passed
  • Actions

    JetBrains/intellij-community

    Official

    Implement or change IntelliJ AnAction actions and registrations.

    21k GitHub stars~341 tokensUpdated today
    MobileAuto-check passed
  • Laravel Actions

    coollabsio/coolify

    Build, refactor, and troubleshoot Laravel Actions using lorisleiva/laravel-actions.

    63k GitHub stars~2.4k tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • Actions

    BuilderIO/agent-native

    How to create and run agent actions. An agent skill from BuilderIO/agent-native.

    7.1k GitHub stars~4.5k tokensUpdated today
    Backend & APIsAuto-check passed
  • Feedback

    nexu-io/nexu

    Send feedback to the Nexu team. An agent skill from nexu-io/nexu.

    3.3k GitHub stars~660 tokensUpdated 5 mo ago
    Productivity & AutomationAuto-check: warnings

More from mohitagw15856/pm-claude-skills

All 1,348 skills in this repo
  • Car Tco

    mohitagw15856/pm-claude-skills

    Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Cs Health Scorecard

    mohitagw15856/pm-claude-skills

    Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.

    1.4k GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed
  • Exit Waterfall

    mohitagw15856/pm-claude-skills

    Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Feature Prioritisation

    mohitagw15856/pm-claude-skills

    Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.

    1.4k GitHub stars~2k tokensUpdated yesterday
    Auto-check passed
  • Fire Number

    mohitagw15856/pm-claude-skills

    Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Freelance Rate

    mohitagw15856/pm-claude-skills

    Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.

    1.4k GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

Questions about Giving Feedback

What does Giving Feedback do?

Turn a vague concern into specific, kind, actionable feedback. Giving Feedback is an agent skill from mohitagw15856/pm-claude-skills. Turn a vague concern into specific, kind, actionable feedback.

When should I use Giving Feedback?

Giving Feedback fits situations like: asked to give feedback; write a feedback note; prepare to tell someone something hard about their work; coach a report/peer.

How do I install Giving Feedback in Claude Code?

Run `npx skills add mohitagw15856/pm-claude-skills --skill giving-feedback -a claude-code`. Or copy the skill folder (skills/giving-feedback in mohitagw15856/pm-claude-skills) into .claude/skills/giving-feedback in your project. Claude Code loads it when a task matches its description.

How do I install Giving Feedback in Codex?

Run `npx skills add mohitagw15856/pm-claude-skills --skill giving-feedback -a codex`. Or copy the skill folder (skills/giving-feedback in mohitagw15856/pm-claude-skills) into .agents/skills/giving-feedback in your project. Codex loads it when a task matches its description.

Can I use Giving Feedback 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 mohitagw15856/pm-claude-skills --skill giving-feedback -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/giving-feedback, .gemini/skills/giving-feedback, .github/skills/giving-feedback and .opencode/skills/giving-feedback in your project.

What does Giving Feedback need to run?

SKILL.md names no scripts, command-line tools or credentials: Giving Feedback is instructions for the agent only.

Does Giving Feedback 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 Giving Feedback 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 Giving Feedback use?

Giving Feedback 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 Giving Feedback use?

About 897 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Giving Feedback?

Skills that share tags, products or a category with Giving Feedback: Giving Feedback (RefoundAI/lenny-skills, 1.4k stars), Feedback (codewhale-hq/Codewhale, 41k stars), Actions (JetBrains/intellij-community, 21k stars) and Laravel Actions (coollabsio/coolify, 63k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Giving Feedback?

mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.

Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.