giving-feedback

GitHub

将模糊担忧转化为具体、善意且可执行的反馈。基于SBI模型,区分观察与评判,提供情境-行为-影响结构、明确诉求、开场白及对话问题,适用于指导或告知他人工作表现。

exports/openclaw/giving-feedback/SKILL.md mohitagw15856/pm-claude-skills

Trigger Scenarios

请求给予反馈 撰写反馈笔记 准备告知他人棘手的工作问题 辅导下属或同事

Install

npx skills add mohitagw15856/pm-claude-skills --skill giving-feedback -g -y
More Options

Non-standard path

npx skills add https://github.com/mohitagw15856/pm-claude-skills/tree/main/exports/openclaw/giving-feedback -g -y

Use without installing

npx skills use mohitagw15856/pm-claude-skills@giving-feedback

指定 Agent (Claude Code)

npx skills add mohitagw15856/pm-claude-skills --skill giving-feedback -a claude-code -g -y

安装 repo 全部 skill

npx skills add mohitagw15856/pm-claude-skills --all -g -y

预览 repo 内 skill

npx skills add mohitagw15856/pm-claude-skills --list

SKILL.md

Frontmatter
{
    "name": "giving-feedback",
    "homepage": "https:\/\/mohitagw15856.github.io\/pm-claude-skills\/skill\/giving-feedback.html",
    "metadata": {
        "openclaw": {
            "emoji": "📨"
        }
    },
    "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.

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.

Version History

  • 54fad50 Current 2026-07-19 12:21

Same Skill Collection

exports/openclaw/360-feedback-template/SKILL.md
exports/openclaw/401k-plan-decoder/SKILL.md
exports/openclaw/ab-test-planner/SKILL.md
exports/openclaw/ab-test-readout/SKILL.md
exports/openclaw/accessibility-audit/SKILL.md
exports/openclaw/account-plan/SKILL.md
exports/openclaw/acquirer-red-team/SKILL.md
exports/openclaw/ad-copy/SKILL.md
exports/openclaw/aeo-optimizer/SKILL.md
exports/openclaw/agenda-or-cancel/SKILL.md
exports/openclaw/agent-design-review/SKILL.md
exports/openclaw/agent-observability-spec/SKILL.md
exports/openclaw/agent-spec/SKILL.md
exports/openclaw/ai-ethics-review/SKILL.md
exports/openclaw/ai-eval-plan/SKILL.md
exports/openclaw/ai-feature-prd/SKILL.md
exports/openclaw/ai-product-canvas/SKILL.md
exports/openclaw/air-quality/SKILL.md
exports/openclaw/altitude-shifter/SKILL.md
exports/openclaw/ambiguity-resolver/SKILL.md
exports/openclaw/analyst-relations-brief/SKILL.md
exports/openclaw/announcement-card/SKILL.md
exports/openclaw/api-docs-writer/SKILL.md
exports/openclaw/api-test-plan/SKILL.md
exports/openclaw/api-versioning-strategy/SKILL.md
exports/openclaw/apology-letter/SKILL.md
exports/openclaw/architecture-decision-record/SKILL.md
exports/openclaw/architecture-diagram/SKILL.md
exports/openclaw/archive-strategy/SKILL.md
exports/openclaw/assumption-bounty/SKILL.md
exports/openclaw/assumption-mapper/SKILL.md
exports/openclaw/async-update-format/SKILL.md
exports/openclaw/auto-repair-estimate-decoder/SKILL.md
exports/openclaw/autopilot-charter/SKILL.md
exports/openclaw/benefits-decoder/SKILL.md
exports/openclaw/bid-tender-review/SKILL.md
exports/openclaw/board-deck-narrative/SKILL.md
exports/openclaw/board-minutes/SKILL.md
exports/openclaw/board-pre-read/SKILL.md
exports/openclaw/bom-cost-review/SKILL.md
exports/openclaw/bookkeeping-categorization/SKILL.md
exports/openclaw/boolean-search-builder/SKILL.md
exports/openclaw/brag-doc/SKILL.md
exports/openclaw/brainstorming/SKILL.md
exports/openclaw/brief-builder/SKILL.md
exports/openclaw/briefing-note/SKILL.md
exports/openclaw/budget-builder/SKILL.md
exports/openclaw/budget-variance-analysis/SKILL.md
exports/openclaw/bug-diagnosis/SKILL.md
exports/openclaw/bug-report/SKILL.md

Metadata

Files
0
Version
471c606
Hash
741e823f
Indexed
2026-07-19 12:21

- 위키
Copyright © 2011-2026 iteam. Current version is 2.155.2. UTC+08:00, 2026-07-29 19:25
浙ICP备14020137号-1 $방문자$