Individual skill

giving-feedback

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.

plugins/pm-comms/skills/giving-feedback/SKILL.md

Read pinned source

Source commit f7c90bc09ee05dc25cf257bdb1826f2c2552c2cb

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,539
Repository last updated
Nov 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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.
Back to top