Token导航 LogoToken导航

Agent Skill · 待分类

radical-candor(彻底的坦率)

radical-candor 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

radical-candor 是待分类类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在待分类类的 11,209 个 Skill 里排第 1,979。

总安装 2,007周安装 82GitHub Stars 85下载 643核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:radical-candor(彻底的坦率)
来源仓库:https://github.com/guia-matthieu/clawfu-skills
仓库路径:skills/radical-candor
安装命令:
npx skills add https://github.com/guia-matthieu/clawfu-skills --skill radical-candor
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/guia-matthieu/clawfu-skills --skill radical-candor

这个 Skill 是做什么的

这个 Skill 的分类还没最终确定,用法以来源仓库的说明为准。

彻底的坦率技能用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息。适合在团队反馈、代码审查或绩效沟通中提供建设性意见。可通过标准方式从 GitHub 仓库安装并在 AI 宿主中调用。使用时需注意语气控制与隐私保护,避免不当言论引发争议。

radical-candor 属于待分类类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/radical-candor

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/guia-matthieu/clawfu-skills --skill radical-ca…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

radical-candor 怎么安装?

在终端执行 npx skills add https://github.com/guia-matthieu/clawfu-skills --skill radical-candor。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

radical-candor 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

radical-candor 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

radical-candor 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

radical-candor 用的人多吗?

公开数据是累计安装 2,007 次,近一周安装 82 次,下载 643 次,GitHub 85 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

radical-candor 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理待分类类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

待分类类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
infsh-cli

infsh CLI · Codex、Claude

4,374,576382权限未标注未明确未收录
ai-video-generation

AI 视频生成 · Codex、Claude

4,313,376382调用外部服务未明确有提醒
lark-openapi-explorer

云雀 OpenAPI 浏览器 · Codex、Claude

2,064,1209,011需要联网未明确有提醒
lark-workflow-standup-report

Lark 工作流程站立报告 · Codex、Claude

2,041,6328,978需要联网未明确通过
use-my-browser

使用我的浏览器 · Codex、Claude

1,848,49140操作浏览器未明确未通过
radical-candor

彻底的坦率 · 本页

2,00785只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Radical Candor

Stop being a "nice" manager. Learn Kim Scott's framework for caring personally while challenging directly—the combination that builds trust and drives performance.

When to Use This Skill

  • Giving feedback (positive or constructive)
  • Building trust with direct reports
  • Performance conversations that need to happen
  • Team culture building for high performance
  • New manager development learning to have hard conversations
  • Preventing ruinous empathy in yourself or your organization

Methodology Foundation

AspectDetails
SourceKim Scott - Radical Candor (2017)
Core Principle"Radical Candor = Care Personally + Challenge Directly. You need both. Neither alone is enough."
BackgroundScott was a senior leader at Google and Apple, advised Twitter, Dropbox, and many others
Why This MattersMost managers fail by being too nice (Ruinous Empathy) or too harsh (Obnoxious Aggression). Radical Candor is the sweet spot that builds both trust and results.

What Claude Does vs What You Decide

Claude DoesYou Decide
Structures production workflowFinal creative direction
Suggests technical approachesEquipment and tool choices
Creates templates and checklistsQuality standards
Identifies best practicesBrand/voice decisions
Generates script outlinesFinal script approval

What This Skill Does

  1. Defines the four quadrants - Radical Candor, Ruinous Empathy, Obnoxious Aggression, Manipulative Insincerity
  2. Teaches caring personally - Building genuine relationships
  3. Develops challenging directly - Having necessary hard conversations
  4. Provides feedback frameworks - How to give effective criticism and praise
  5. Builds a feedback culture - Teams that can handle candor
  6. Avoids management traps - Especially "ruinous empathy"

How to Use

Give Difficult Feedback

I need to give feedback to [person] about [issue].
Help me structure this using Radical Candor principles.
Context: [relationship, situation]

Diagnose Your Management Style

Here's how I typically handle feedback: [describe].
Which quadrant am I in? How do I move toward Radical Candor?

Build a Feedback Culture

I want my team to be more candid with each other.
Apply Radical Candor to help me build this culture.

Instructions

Step 1: Understand the Framework

## The Radical Candor Framework

### The Two Dimensions

**Care Personally (Vertical Axis)**
- See people as whole humans, not just employees
- Build genuine relationships
- Invest in their growth and wellbeing
- Share about yourself, learn about them

**Challenge Directly (Horizontal Axis)**
- Tell people when their work isn't good enough
- Give clear, actionable feedback
- Don't sugarcoat to spare feelings
- Expect excellence and say so

### The Four Quadrants
            CHALLENGE DIRECTLY
                  ↑
                  |
┌─────────────────┼─────────────────┐
│                 │                 │
│   OBNOXIOUS     │    RADICAL      │
│   AGGRESSION    │    CANDOR       │
│                 │                 │

────│─────────────────┼─────────────────│──── │ │ │ CARE │ MANIPULATIVE │ RUINOUS │ PERSONALLY │ INSINCERITY │ EMPATHY │ → │ │ │ └─────────────────┴─────────────────┘

### Quadrant Definitions

**Radical Candor (Care + Challenge)**
"I'm going to tell you the truth because I care about you."
- Direct but kind
- Honest about problems
- Helps people grow
- Builds trust over time

**Ruinous Empathy (Care, No Challenge)**
"I don't want to hurt their feelings."
- Too nice
- Avoids hard conversations
- Problems fester
- People don't improve

**Obnoxious Aggression (Challenge, No Care)**
"I'm just being honest."
- Harsh and hurtful
- Doesn't consider feelings
- Wins battles, loses people
- Creates fear, not trust

**Manipulative Insincerity (Neither)**
"I'll say what they want to hear."
- Political and fake
- Talking behind backs
- Avoiding real issues
- Toxic culture

Step 2: Move Toward Radical Candor

## Getting to Radical Candor

### Most Common Trap: Ruinous Empathy

**Why it's the most common:**
- We're taught to be nice
- We don't want to hurt people
- Conflict feels uncomfortable
- It's easier to avoid

**Why it's ruinous:**
- Problems don't get fixed
- People don't grow
- Small issues become big
- You lose respect

**Example:**
Bob's presentations are unclear. You say nothing because
you don't want to hurt his feelings. Bob never improves.
His career stalls. Eventually you have to fire him.

If you'd given feedback early, Bob could have improved.
Your "kindness" was actually cruel.

### Moving from Ruinous Empathy to Radical Candor

**Step 1: Reframe caring**
True caring = helping them succeed
Not = protecting them from discomfort

**Step 2: Practice small challenges**
Start with low-stakes feedback.
Build the muscle before big conversations.

**Step 3: Be immediate**
Feedback in the moment, not weeks later.
"Can I share something?" right after the meeting.

**Step 4: Be specific**
Not: "Your presentation wasn't great."
Yes: "When you skipped the data slide, the execs got confused."

### Moving from Obnoxious Aggression to Radical Candor

**Step 1: Show vulnerability**
Share your own mistakes and growth areas.
Makes you human, not just a critic.

**Step 2: Ask before telling**
"How do you think that went?"
Let them self-assess first.

**Step 3: Praise more**
Obnoxious Aggressors often skip praise.
Catch people doing things right.

**Step 4: Check impact**
"How did that land for you?"
Care about how your message is received.

Step 3: Give Effective Feedback

## The Feedback Framework

### Kim Scott's Guidelines

**1. Humble**
You might be wrong. Present observations, not verdicts.

**2. Helpful**
Your intent is to help, not punish.
Make that clear.

**3. Immediate**
Give feedback ASAP while context is fresh.
"Can I share something?" after the meeting.

**4. In person**
(Or video call) Never by email for criticism.
Tone matters too much.

**5. Private for criticism, public for praise**
Criticism in private protects dignity.
Praise in public amplifies impact.

**6. Don't personalize**
Criticize the work, not the person.
Not: "You're disorganized."
Yes: "The project plan was missing key dates."

### The HHIPP Framework

**H**umble
**H**elpful
**I**mmediate
**I**n-person
**P**rivate criticism
**P**ublic praise

### Feedback Structure

**For Criticism:**

1. **Context:** "In yesterday's meeting..."
2. **Observation:** "I noticed that..."
3. **Impact:** "This mattered because..."
4. **Expectation:** "Here's what I'd like to see..."
5. **Support:** "How can I help?"

**For Praise:**

1. **Context:** "In yesterday's meeting..."
2. **Observation:** "I noticed that..."
3. **Impact:** "This mattered because..."
4. **Appreciation:** "Thank you / Great job"
5. **Encouragement:** "Keep doing this"

### Praise Specifically

**Bad praise:**
"Great job on the project!"

**Good praise:**
"In yesterday's presentation, the way you handled the CFO's
objection by pulling up the cost analysis in real-time was
excellent. It showed you were prepared and it built confidence.
The deal progressed because of that moment."

Specific praise teaches. Vague praise is noise.

Step 4: Have Hard Conversations

## The Hard Conversation Framework

### Before the Conversation

**1. Check your intent**
- Am I trying to help or punish?
- Do I care about this person?
- Am I in the right headspace?

**2. Gather facts**
- What specifically happened?
- What was the impact?
- What evidence do I have?

**3. Consider their perspective**
- What might they be dealing with?
- What context might I be missing?
- How might they see this differently?

### The Conversation Structure

**1. Open with care**
"I want to talk about something because I care about your success here."

**2. Describe observations (not judgments)**
"In the last three sprints, you've missed the deadline."
Not: "You're unreliable."

**3. Share impact**
"This has caused the team to scramble and missed our launch date."

**4. Ask for their perspective**
"Help me understand what's been going on."
Listen genuinely. You might learn something.

**5. Discuss path forward**
"How do we make sure this doesn't happen again?"
"What support do you need?"

**6. Agree on specifics**
"So we're agreeing to [X]. Let's check in on [date]."

### Common Mistakes

**Sandwich feedback:**
Praise → Criticism → Praise
Problems: Confusing, feels manipulative, people learn to
ignore praise because they're waiting for the "but."

**"But" statements:**
"You did great, but..."
The "but" erases everything before it.
Use: "You did great. And separately, I have feedback on..."

**Delayed feedback:**
Waiting for the "right moment" that never comes.
The best time for feedback is now (or very soon).

**Third-party feedback:**
"Some people have said..."
Own your feedback. "I noticed..." or "I heard from X..."

Step 5: Build a Candor Culture

## Creating a Culture of Radical Candor

### Start with Yourself

**1. Ask for feedback first**
Before you give feedback, ask for it.
"What could I do better?"
"What's something I don't see about myself?"

**2. Reward the candor**
When someone gives you hard feedback:
- Thank them
- Don't get defensive
- Take action
- Follow up

**3. Show vulnerability**
Share your mistakes publicly.
Admit what you're working on.
Model that it's safe to be imperfect.

### Establish Feedback Norms

**1. Make it expected**
"On this team, we give each other feedback.
It's how we improve."

**2. Make it safe**
"Feedback here is about helping, not judging.
We assume good intent."

**3. Make it frequent**
Don't save it for performance reviews.
Feedback should happen constantly.

### Team Practices

**1. Start meetings with "What I'm Working On"**
Each person shares one thing they're trying to improve.
Normalizes growth and opens door for feedback.

**2. "Clean escalation"**
If you have a problem with someone, tell them first.
No going around people or venting to others.

**3. Feedback retrospectives**
Regularly ask: "How are we doing with candor?"
"What's being left unsaid?"

**4. Permission to push**
"If I'm not being direct enough, push me."
"If I'm being too harsh, tell me."

### Warning Signs

**Low candor culture:**
- Meetings after the meeting
- Conflict avoidance
- Surprises at review time
- Politics and factions
- Venting but not addressing

**High candor culture:**
- Direct conversations
- Rapid feedback
- Trust even in disagreement
- Continuous improvement
- Healthy conflict

Examples

Example 1: Giving Difficult Feedback

Input:

"I need to tell my top performer that their communication in meetings has been abrasive. They're defensive about feedback. Help me structure this conversation."

Output:

Radical Candor Conversation: Abrasive Communication

Pre-Conversation Prep

Check your intent: ✓ I want them to succeed (they're a top performer) ✓ This feedback will help them grow ✓ I'm in a calm headspace

Gather facts:

  • In Tuesday's meeting, they interrupted Sarah three times
  • Last week, raised voice when Alex questioned their approach
  • Two team members have mentioned feeling shut down

Consider their perspective:

  • They care deeply about quality
  • May not realize how they're landing
  • Might be stressed about project pressures

The Conversation

Opening: "Hey [Name], I want to talk about something because you're one of our best people and I want to see you continue to grow here. Is now a good time, or should we schedule something?"

Observations: "I've noticed something in recent meetings that I want to share. In Tuesday's sprint planning, you interrupted Sarah three times when she was explaining the design approach. And last week, when Alex questioned the timeline, your voice got louder and the conversation shut down.

I'm sharing specific examples because I want to be clear about what I'm observing."

Impact: "Here's why this matters: You have great ideas, but when team members feel interrupted or shut down, they stop contributing. I've heard from two people that they've hesitated to challenge your thinking because of how past challenges have gone.

You end up with worse outcomes because you're not getting the full benefit of the team's input."

Their perspective: "I'd love to hear your take on this. What's going on for you in those moments?"

[Listen genuinely. They might share stress, frustration, or not realize the impact at all.]

Path forward: "I know this is hard to hear, especially because your technical work is excellent. What I'm asking for:

  1. In meetings, let people finish their thoughts before responding
  2. When you feel strongly, say 'I disagree because...' rather than raising your voice
  3. Actively ask quieter team members for input

I'm not asking you to be less passionate or less direct. I'm asking you to make sure your passion doesn't shut others out."

Support: "What would help you with this? Do you want me to give you a signal in meetings if I notice it happening? Would it help to do a quick debrief after meetings for a few weeks?"

Close: "I'm telling you this because I care about your career here. This is the thing that could hold you back from the next level. Let's check in next week on how it's going."

Anticipating Defensiveness

If they push back:

"I hear that you don't see it that way. I could be wrong. But I've gotten this feedback from multiple sources, and I've observed it myself. I'd ask you to consider that your intent might not match your impact.

Would you be open to asking a trusted colleague for their perspective?"

If they get emotional:

"I can see this is hard to hear. That's okay—this is hard feedback. Take some time to sit with it. We can talk more tomorrow if you want."


Example 2: Moving from Ruinous Empathy

Input:

"I realize I've been in 'Ruinous Empathy' with an underperformer for months. Now I need to have a serious conversation. How do I shift?"

Output:

Escaping Ruinous Empathy: Underperformance Conversation

Recognize the Pattern

What you've been doing:

  • Avoiding direct conversation about performance
  • Hoping it would get better on its own
  • Protecting their feelings at expense of results
  • Maybe covering for them with others

What it's cost:

  • Team resents the lower standard
  • Person hasn't had chance to improve
  • Problem has gotten worse
  • Your credibility is affected

Own Your Part First

In the conversation, acknowledge: "I need to be honest with you, and I also need to own my part. I should have had this conversation with you months ago. By not being direct, I haven't given you a fair chance to address this. That's on me. I'm sorry for that."

Why this matters:

  • Shows humility
  • Builds trust even in hard moment
  • Models accountability
  • Makes them more receptive

The Conversation

Frame: "I want to have a direct conversation about your performance. I care about you, and that's exactly why I need to be honest about what I'm seeing."

Be specific about the gap: "The expectation for this role is [X]. Over the past three months, here's what I've observed:

  • [Specific example 1]
  • [Specific example 2]
  • [Specific example 3]

There's a significant gap between where you are and where you need to be."

Be clear about stakes: "I want to be direct about what this means. If we don't see improvement in [timeframe], we'll need to consider whether this role is the right fit.

I'm not saying this to threaten you. I'm saying it because you deserve to know the truth about where things stand."

Offer support: "Here's what I can commit to:

  • Clear expectations documented this week
  • Weekly check-ins on progress
  • Specific feedback in real-time
  • Resources for [training/support if appropriate]

What support do you need from me?"

Get commitment: "I need you to commit to [specific improvements]. Can you do that?"

After the Conversation

Document:

  • What was discussed
  • What was agreed
  • Timeline
  • Next check-in

Follow through:

  • Give the real-time feedback you promised
  • Hold the check-ins
  • Praise progress
  • Address backsliding immediately

Don't go back to Ruinous Empathy: This conversation was hard. You'll be tempted to back off. Don't. They need continued candor to succeed or to understand that it's not working.


Example 3: Building Team Candor Culture

Input:

"My team avoids conflict. People don't speak up in meetings but complain afterwards. How do I build more candor?"

Output:

Building Candor: Team Transformation

Diagnose the Current State

Symptoms you described:

  • Silent meetings
  • Complaining afterwards
  • Conflict avoidance
  • Triangulation (talking about, not to)

Root causes to consider:

  • Safety: People don't feel safe speaking up
  • Skill: People don't know HOW to be candid
  • Norms: No expectation of directness
  • History: Past candor punished

Phase 1: Model Vulnerability (Weeks 1-2)

As the leader, go first:

  1. Share your own development area In team meeting: "Something I'm working on is [X]. I'd appreciate feedback when you see me doing it."
  2. Publicly receive feedback well Ask in meetings: "What could I have done better?" When you get feedback: Thank them. Don't defend.
  3. Admit mistakes publicly "I made a bad call on [X]. Here's what I learned."

Why this works: If you can be imperfect and still be respected, so can everyone else.

Phase 2: Create Permission Structures (Weeks 2-4)

1. Pre-meeting prompt: "In this meeting, I'm going to ask everyone for their honest reaction to [topic]. Disagreement is valuable here."

2. Ask directly for dissent: "What might we be missing?" "Who disagrees with this approach?" "[Quiet person], I'd value your perspective."

3. Celebrate candor when it happens: "Thank you for pushing back on that. That kind of challenge makes us better."

4. Establish clean escalation norm: "On this team, if you have a problem with someone, you tell them directly first. No exceptions. If you need help with the conversation, come to me and I'll help you figure out how to have it."

Phase 3: Build Feedback Skills (Weeks 4-8)

Team training session:

  • Explain Radical Candor framework
  • Practice scenarios
  • Create shared language

Introduce feedback rituals:

Ritual 1: Weekly "Plus/Delta" End of each week, everyone shares:

  • Plus: One piece of praise for a teammate
  • Delta: One suggestion for improvement (to anyone, including leader)

Ritual 2: "Feedback Friday" Each person gives one piece of feedback to someone. Creates habit and expectation.

Ritual 3: Retrospective candor In retros, explicitly ask: "What are we not saying?" "What elephants are in the room?"

Phase 4: Sustain and Reinforce (Ongoing)

Call out triangulation: If someone complains to you about someone else: "Have you told them this directly?" "I'd encourage you to talk to them first."

Praise directness publicly: "I really appreciate how you brought that concern up directly in the meeting."

Address backsliding: If someone gets punished for candor (by you or others), fix it immediately and visibly.

Metrics to Watch

Improving:

  • More questions/pushback in meetings
  • Faster issue resolution
  • Less venting outside meetings
  • People saying "I disagree" constructively

Concerning:

  • People still silent
  • Issues discovered late
  • Conflict avoided then exploding
  • Turnover in candid people

Checklists & Templates

Feedback Checklist

## Before Giving Feedback

□ Intent is to help, not punish
□ I have specific examples
□ I've considered their perspective
□ I'm in a calm emotional state
□ Timing is appropriate (not public for criticism)

## During Feedback

□ Started with context
□ Described observations (not judgments)
□ Explained impact
□ Asked for their perspective
□ Discussed path forward
□ Offered support
□ Agreed on specifics

## After Feedback

□ Documented key points
□ Follow-up scheduled
□ Recognized improvement (if any)

Quadrant Self-Assessment

## Which Quadrant Am I In?

### Answer Honestly:

1. When someone does poor work, I:
   a) Say nothing to avoid hurting them [RE]
   b) Tell them bluntly it's bad [OA]
   c) Hint at it indirectly [MI]
   d) Tell them clearly and offer to help [RC]

2. My team would say I:
   a) Am really nice but don't give honest feedback [RE]
   b) Am intimidating and harsh [OA]
   c) Say different things to different people [MI]
   d) Am direct but fair and caring [RC]

3. When I have to give hard feedback:
   a) I delay or avoid it [RE]
   b) I just say it and move on [OA]
   c) I hint around it or tell someone else [MI]
   d) I prepare, deliver directly, and support [RC]

4. The last time I gave critical feedback was:
   a) Can't remember / too long ago [RE]
   b) Recently, and it was blunt [OA]
   c) In a review or through someone else [MI]
   d) Recently, in private, with support [RC]

### My primary quadrant: _________

### My action to move toward Radical Candor:
_________________________________

Skill Boundaries

What This Skill Does Well

  • Structuring audio production workflows
  • Providing technical guidance
  • Creating quality checklists
  • Suggesting creative approaches

What This Skill Cannot Do

  • Replace audio engineering expertise
  • Make subjective creative decisions
  • Access or edit audio files directly
  • Guarantee commercial success

References

  • Scott, Kim. "Radical Candor: Be a Kick-Ass Boss Without Losing Your Humanity" (2017)
  • Radical Candor podcast
  • Kim Scott's talks at Google, First Round, etc.
  • Candor, Inc. resources

Related Skills


Skill Metadata

  • Mode: cyborg
name: radical-candor
category: leadership
subcategory: feedback
version: 1.0
author: MKTG Skills
source_expert: Kim Scott
source_work: Radical Candor
difficulty: intermediate
estimated_value: $3,000+ leadership coaching
tags: [leadership, feedback, management, candor, Kim Scott, Google, Apple, culture]
created: 2026-01-25
updated: 2026-01-25

平台分布

Codex

36.36%
按下载量换算234

Claude

28.93%
按下载量换算186

Cursor

16.17%
按下载量换算104

Gemini CLI

9.65%
按下载量换算62

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills