AgentSkillsCN

Keeper Test Talent Density

从手动编写代码语法，转向高层次的需求描述。适用于当你使用AI原生工具（如Cursor）构建软件、管理由AI生成的代码库，或当工程团队的重心从“如何编写”转向“要构建什么”时。

SKILL.md
yaml
---
name: keeper-test-talent-density
description: A framework for maintaining high talent density using the "Keeper Test" mental model. Use this skill when evaluating team performance, deciding on headcount retention, or preparing for candid performance conversations without traditional HR ratings.
---

Maintaining High Talent Density via the Keeper Test

High talent density is the prerequisite for all other high-performance culture traits (candor, freedom, and responsibility). This skill provides the mental framework and communication steps to ensure every team member is someone you would fight to keep, ensuring the organization remains world-class.

The Mental Framework: The Keeper Test

The "Keeper Test" is a gut-check for managers to hold themselves accountable for the quality of their team. Instead of waiting for annual reviews, ask yourself this question regularly:

"If this person on my team came to me and said they were leaving today for a different opportunity, would I do everything I could to keep them at the company?"

  • •If yes: They are a keeper. Continue to invest in their growth and provide "context, not control."
  • •If no: You must begin a candid conversation about whether the role or the company is the right fit. If you would feel "relieved" if they left, you are doing the team a disservice by not acting.

Operationalizing Talent Excellence

To maintain a high bar without creating a "Hunger Games" environment, follow this three-step cycle for every direct report:

1. Set the Bar (Expectation Setting)

Clearly define what excellence looks like before the work begins.

  • •Outcome over Polish: Distinguish between "world-class thinking" and "useless polish." (e.g., "I don't need a perfectly formatted deck; I need a document that identifies the three biggest risks in our live-streaming strategy.")
  • •The 5% Rule: Emphasize that the last 5% of effort is often where the most value and excellence reside.

2. Identify the Gap (Direct Candor)

When work falls below the bar, provide immediate, specific feedback in private.

  • •Avoid generic praise or criticism.
  • •Explain exactly where the output missed the mark (e.g., "This analysis identifies the 'what' but fails to explain the 'why' or the unintended incentives created for the user.")

3. Close the Gap (Jump In)

Don't just point out errors; help the employee level up through collaborative "osmosis."

  • •Hands-on Support: Jump into the document or the code with the employee.
  • •Show, Don't Just Tell: Work through the iteration together once to demonstrate the expected standard. This creates a "safe space" where the manager is a partner in success, not just a judge.

Examples

Example 1: High-Stakes Document Review

  • •Context: A PM submits a roadmap for a new product category (e.g., Live Events). The document is grammatically perfect but lacks strategic depth.
  • •Application: Use the feedback loop.
    • •Expectation: "We need this to build confidence with the Content team."
    • •Feedback: "You've listed the features, but not how we handle the technical failure of a live stream."
    • •Closing the Gap: Spend 30 minutes co-writing the "failure modes" section to show the required level of technical-to-non-technical translation.
  • •Output: The PM learns the new "bar" for strategic documents and the roadmap is approved by stakeholders.

Example 2: The Periodic Keeper Check

  • •Context: A manager realizes they would be "fine" if a specific Senior Engineer left. The engineer is "good" but doesn't raise the bar for the team.
  • •Application: The manager initiates a candid 1:1.
    • •Input: "If you told me today you were leaving, I'm not sure I would fight to keep you in this specific role because we need more proactive architectural leadership."
    • •Action: Set a 3-month goal for the engineer to lead a major system redesign, providing the "Jump In" support needed to see if they can meet the new bar.
  • •Output: The engineer either rises to the challenge (becoming a "Keeper") or both parties agree on an amicable exit.

Common Pitfalls

  • •The "Surprise" Exit: If someone is let go and they are surprised, the manager has failed the culture of candor. You must give the feedback that they are failing the Keeper Test before taking action.
  • •Confusing Hours with Excellence: Talent density is about the quality of outcomes and judgment, not the number of hours worked or "sacrificing vacations."
  • •Wait-and-See Mentality: Avoiding the "uncomfortable amount of candor" leads to toxic gaps in team skillsets. Address performance issues in a timely fashion; delay is a cost to the rest of the high-performing team.
  • •Using Process as a Crutch: Do not rely on "Performance Improvement Plans" or HR ratings to do the hard work of having a human conversation about fit.