本文へ移動
cccskills
無料GitHub で公開

team-multiplier

Assess whether your leadership behaviors amplify or diminish your team using Liz Wiseman's Multipliers framework. Use when a leader asks "am I a good manager", "why isn't my team performing at their potential", "I feel like I'm doing all the thinking for my team", "my team seems dependent on me", "I want to be a better leader", "how do I empower my people", or "my team is smart but underperforming". Also trigger when someone describes always having the best ideas in the room, team members not taking initiative, reports waiting for direction before acting, or a leader who feels exhausted from carrying the team. Diminisher patterns are often invisible to the leader exhibiting them.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md8.8 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Overview

Based on "Multipliers: How the Best Leaders Make Everyone Smarter" by Liz Wiseman. Wiseman's research found that Multiplier leaders get 2x the output from their teams compared to Diminishers - not by working the team harder, but by creating conditions where people think and contribute at full capacity. The insight that challenges most well-intentioned leaders: Diminishers often don't know they are Diminishers. They think they're helping. Accidental Diminisher behaviors - being too helpful, too enthusiastic, too expert - suppress the intelligence around them.

The Five Multiplier vs. Diminisher Archetypes

MultiplierDiminisher
Talent Magnet - attracts and deploys talent optimallyEmpire Builder - hoards talent, blocks movement
Liberator - creates intense but safe environment to thinkTyrant - creates anxiety that shuts down thinking
Challenger - stretches the team toward better outcomesKnow-It-All - tells people what to do, limits their thinking
Debate Maker - drives rigorous decisions through full teamDecision Maker - makes decisions with input from a few
Investor - gives ownership, accountability, and resourcesMicromanager - takes back work, owns all decisions

Workflow

Step 1: Run the Self-Assessment

Score yourself honestly (1 = rarely, 5 = consistently):

Talent Magnet

  • Do you know each team member's peak talent and actively deploy it?
  • When someone outgrows your team, do you celebrate it or resist it?
  • Do your best people want to work with you, or do they leave?

Score: ___/5

Liberator

  • Do you create space for others to think before sharing your own view?
  • Can people disagree with you without consequences?
  • Do you distinguish between your "best thinking" and a final decision?

Score: ___/5

Challenger

  • Do you ask questions that stretch the team beyond the obvious solution?
  • Do you give problems (not solutions) and let the team figure out the path?
  • Are your team members operating at the edge of their capability?

Score: ___/5

Debate Maker

  • Are decisions made with input from the people closest to the work?
  • Do you facilitate debate, or do you advocate for your own position?
  • Do people feel the final decision reflects real consideration of their input?

Score: ___/5

Investor

  • Do you give people ownership of outcomes, not just tasks?
  • When someone struggles, do you coach or do you take the work back?
  • Are people on your team growing in their ability to work independently?

Score: ___/5

Step 2: Identify Your Accidental Diminisher Patterns

Wiseman identifies the most common patterns leaders exhibit without realizing they're diminishing:

PatternLooks LikeActual Impact
Always OnSharing every idea, always presentTeam stops generating ideas because yours come first
RescuerHelping when people struggleTeam learns not to persist - you'll take over
PacesetterModeling the standard by doing it yourselfTeam can't keep up; they become spectators
Rapid ResponderQuick answers to every questionTeam stops thinking before asking
Optimist"This is totally doable!"Team doesn't feel safe raising problems
PerfectionistHigh standards, detailed correctionsTeam waits for your approval; doesn't trust own judgment

Check which of these patterns appear in your behavior. Accidental Diminishers score high on intent but low on impact.

Step 3: Identify Your Lowest Multiplier Score

The lowest score is your primary development area. Pick one multiplier to focus on - trying to improve all five simultaneously produces shallow change in none.

If lowest score is Talent Magnet:

  • Map each team member's "native genius" - the thing they do effortlessly and love doing
  • Give a stretch assignment that plays to each person's native genius
  • When a team member is ready for a bigger role, help them find it (even if it means losing them)

If lowest score is Liberator:

  • In your next meeting, ask three questions before sharing any opinion
  • When you have a strong view, label it: "This is my current thinking, not a final decision"
  • Create a "soft opinion" signal - e.g., "I'm 60% confident in this; I want to hear what I'm missing"

If lowest score is Challenger:

  • Replace "here's what I think we should do" with "what would need to be true for [outcome] to happen?"
  • Give your next assignment as a problem statement, not a deliverable spec
  • Set a "stretch goal" that requires the team to invent something new, not just execute harder

If lowest score is Debate Maker:

  • Before your next consequential decision, run a structured debate: assign someone to argue the opposite position
  • Hold your opinion until others have spoken
  • After a decision, ask: "Who wasn't in the room that should have been?"

If lowest score is Investor:

  • For each report, identify one decision that you currently make that they could make
  • When someone brings you a problem, ask: "What do you think we should do?" before offering your view
  • Set a 90-day goal to transfer one complete ownership area per report

Step 4: Run the Team Impact Check

Beyond your own assessment, get external signal. Ask 3-5 team members these questions (anonymously or 1:1):

  1. "When you have an idea in a meeting, do you typically share it?"
  2. "When you're stuck, what do you do - figure it out or bring it to me?"
  3. "When I have a strong opinion, do you feel free to disagree?"
  4. "What's something you haven't brought up to me recently?"

Patterns in the answers reveal what your behavior produces, not what you intend.

Step 5: Write the Multiplier Plan

Multiplier Assessment - [date]

Scores:
  Talent Magnet:  [x/5]
  Liberator:      [x/5]
  Challenger:     [x/5]
  Debate Maker:   [x/5]
  Investor:       [x/5]

Accidental Diminisher patterns identified:
  [list 1-2 patterns from Step 2]

Focus area for next 90 days: [lowest-scoring multiplier]

Specific behavior change:
  Stop doing: [one concrete action to eliminate]
  Start doing: [one concrete action to add]
  Experiment: [one thing to try in the next 2 weeks]

How I'll measure progress:
  [what I'll observe in the team that would indicate improvement]

Reassessment date: [90 days out]

Anti-Patterns

1. Confusing activity with impact Bad: "I'm always helping my team, I must be a multiplier." Good: Multiplier impact is measured in what the team produces, not what you do. High-activity managers are often diminishing - every hour they spend solving for the team is an hour the team didn't develop that capability.

2. Sharing your view too early Bad: Opening a problem discussion with "Here's what I think we should do." Good: The first opinion stated in a meeting anchors the entire discussion. When the leader speaks first, the team optimizes to agree, not to think. Ask first, share last.

3. Rescuing as a reflex Bad: Jumping in to help when a team member struggles. Good: Struggle is the learning mechanism. Rescuing feels supportive but removes the exact experience that builds capability. Coach instead: "What have you tried? What would happen if you tried X?"

4. Trying to fix all five simultaneously Bad: Writing five improvement goals across all five multiplier archetypes. Good: Deep change in one area is more valuable than shallow change in five. Pick the lowest-scoring archetype. Work it for 90 days. Then move to the next.

5. Ignoring team signal Bad: Self-assessing high because your intent is good. Good: Intent is irrelevant. What matters is how the team experiences your behavior. If people aren't speaking up, aren't taking initiative, or are waiting for direction - that is the data, regardless of your score.

Quality Checklist

  • All five archetypes scored honestly, not aspirationally
  • At least one Accidental Diminisher pattern identified
  • Single focus area selected (not all five)
  • One concrete behavior to stop and one to start identified
  • External team signal gathered (not just self-assessment)
  • Multiplier plan written with a specific 2-week experiment
  • Reassessment date set at 90 days

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Rate any product, feature, or experience on the 11-star scale (Brian Chesky's Airbnb thought experiment). Use when user says "rate this experience", "11-star", "star rating", "experience audit", "how good is this", "experience rating", "product audit", "quality assessment", or wants to evaluate product quality and identify improvement paths. Also trigger when user wants to benchmark a feature, assess where a product stands, or map out what "great" looks like - even if they don't explicitly say "11-star".

日本語の概要は準備中です。原文の説明を表示しています。

qa-aman/claude-skills202026年9月10日 更新

Generate A/B copy variants grounded in Eugene Schwartz's awareness and market-sophistication stages and John Caples' tested-headline discipline. Every variant declares its angle, the awareness stage it targets, and a falsifiable hypothesis, and the skill recommends which pair to test first and what delta counts as signal. Use when the user says "A/B test this", "write variants", "give me options", "test different angles", "copy variants", "ab copy", "test this headline", "multiple versions", "which version is better", or wants to test copy before publishing. For reviewing copy that already exists, see copy-review. For sample size and stopping rules, see growth-experiment. For diagnosing a page rather than its words, see page-cro. For full paid ad sets by platform, see ad-campaign-writer.

日本語の概要は準備中です。原文の説明を表示しています。

qa-aman/claude-skills202026年9月10日 更新

Write measurable acceptance criteria for requirements or user stories. Use when the user says "write acceptance criteria", "definition of done", "how do we test this", "fit criteria", "given when then", "Gherkin scenarios", "what does done look like", "testable conditions", "how will we know this works" - even if they don't explicitly say "acceptance criteria".

日本語の概要は準備中です。原文の説明を表示しています。

qa-aman/claude-skills202026年9月10日 更新

Build a strategic account plan for winning, retaining, or expanding a named account. Use when the user says "build an account plan", "strategic account planning", "how do I grow this account", "account expansion strategy", "whitespace analysis", "QBR prep", "key account review", "map the stakeholders in this account", "land and expand plan", "how do I break into [company]", or wants a structured strategy for a specific account.

日本語の概要は準備中です。原文の説明を表示しています。

qa-aman/claude-skills202026年9月10日 更新

Write paid ad copy for LinkedIn, Google, Meta, and YouTube. Produces multiple variants per platform, each targeting a different Eugene Schwartz awareness level and Cialdini persuasion principle. Use when the user asks for ad copy, ad variants, "write LinkedIn ads", Google ads, Meta ads, paid social copy, ad headlines, or wants creative for a paid campaign. Reads brand voice, ICP, and positioning from knowledge/. For organic social posts, see linkedin-post or social-calendar. For the landing page the ad points at, see landing-page-writer. For testing variants, see ab-copy-writer.

日本語の概要は準備中です。原文の説明を表示しています。

qa-aman/claude-skills202026年9月10日 更新

Design clean and consistent APIs. Use when the user says "design an API", "API design review", "design these endpoints", "REST API for X", "GraphQL schema", "API contract", "how should this endpoint work", "review my API design", or wants to create or improve an API interface - even if they don't explicitly say "API design".

日本語の概要は準備中です。原文の説明を表示しています。

qa-aman/claude-skills202026年9月10日 更新

qa-aman のスキルをすべて見る

このスキルの問題を報告する