kangarooking/no-rules-rules-skill · Archived

4a-feedback

当用户需要给予或接受建设性反馈时触发。适用于避?

First seen Apr 17, 2026

Installation

$ npx skills add kangarooking/no-rules-rules-skill --skill 4a-feedback

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from kangarooking/no-rules-rules-skill.

npx skills add kangarooking/no-rules-rules-skill

Browse all from kangarooking/no-rules-rules-skill

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 11
License LICENSE
Default branch main
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 4,371 B
  • docs SUMMARY.md 236 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 20 installs

SKILL.md

R - 原文摘录 (Reading)

"目的在于帮助(Aim to assist)、反馈应具有可行性(Actionable)、感激与赞赏(Appreciate)、接受或拒绝(Accept or discard)。"

I - 诠释理解 (Interpretation)

The 4A framework has two sides. GIVING side: (1) Aim to assist — feedback must intend to help, not vent; (2) Actionable — must tell receiver what specifically to change. RECEIVING side: (3) Appreciate — listen with gratitude, suppress defensive instinct; (4) Accept or discard — receiver decides whether to act, but must thank the giver. The framework creates a structured bilateral contract for feedback.

4A框架将反馈从"单向指责"重构为"双向契约"。给予方承担意图和可行性的责任,接收方承担倾听和感恩的责任,但不承担执行的责任——这消除了反馈中最大的心理负担。

A1 - 过往案例 (Past Application)

  1. Doug给Jordan的反馈:Doug gave feedback to Jordan about his behavior in India — Jordan accepted and changed. 这说明当反馈符合4A标准时,即使是跨文化敏感问题也能被有效传达和接受。
  1. Roselle邮件反馈Reed:Roselle emailed Reed about his tone toward Patty — Reed thanked her. CEO级别也能接受来自下属的反馈,关键在于Reed执行了第3A(Appreciate)和第4A(Accept)。
  1. Erin的Cuba演讲反馈:Erin received feedback during her Cuba speech about only calling on Americans — she adjusted immediately. 即时反馈 + 即时修正的案例,展示了4A框架在公开场合的效力。

A2 - 触发条件 (Future Trigger)

当出现以下场景时激活本技能:

  • User is giving or receiving feedback and wants to do it constructively
  • User is avoiding a difficult conversation
  • User asks "how do I tell my colleague/manager..."
  • User's team has feedback avoidance culture
  • 用户在纠结"要不要说"或"怎么说才好"
  • 团队中出现回避批评、只说好话的文化倾向

E - 执行步骤 (Execution)

Step 1: 给予反馈前的自检

Before giving feedback, check: Is my intent to help? Can I state the specific change I'm suggesting? If not, don't give it yet.

  • 问自己两个问题:我的目的是帮助对方吗?我能说出具体建议改变什么吗?
  • 如果任一答案为"否",先不要给反馈——整理思路后再来。

Step 2: 接收反馈时的第一反应

When receiving feedback, first say "thank you" — suppress the urge to explain or defend.

  • 收到反馈时,第一句话说"谢谢"。
  • 压制住解释、辩解、反驳的冲动。不需要当场回应内容,只需要表达感谢。

Step 3: 处理反馈后的决策

After processing, decide: accept and act, or discard — but always thank the giver. You don't owe compliance, you owe gratitude.

  • 消化反馈后,自主决定:接受并执行,还是拒绝。
  • 无论是否采纳,都必须感谢给予者。
  • 你不欠对方"照做",你欠对方"感恩"。

B - 边界与限制 (Boundary)

  • Don't give corrective feedback while angry ("还在气头上切勿发表批评意见")。情绪激动时的反馈违反第1A(Aim to assist),因为真实意图已变成发泄而非帮助。
  • Don't confuse impulsiveness with candor。坦率不等于冲动。真正的坦率是经过思考的、有建设性的诚实。
  • Not suitable for cultures where direct feedback is considered rude without adaptation (see cross-cultural-feedback skill)。在重视面子和谐的文化中,4A框架需要适配——但核心原则不变。
  • The "brilliant jerk" trap:用"我只是直率"为借口进行人身攻击,违反4A第1条原则。4A不是"毒舌许可证"。
  • 不适用于紧急危机场景:当时间紧迫需要立即行动时,先执行再反馈,不要在火灾现场讨论谁放的火。