Communitygithub.com

amplitude/builder-skills

Develop a strategy using the Playing to Win cascade — Winning Aspiration, Where to Play, How to Win, Capabilities, and Management Systems. Use when you need to make strategic choices about markets, positioning, and competitive advantage.

builder-skills 是什么?

builder-skills is a Claude Code agent skill that develop a strategy using the Playing to Win cascade — Winning Aspiration, Where to Play, How to Win, Capabilities, and Management Systems. Use when you need to make strategic choices about markets, positioning, and competitive advantage.

兼容平台~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/amplitude/builder-skills/tree/HEAD/product-skills/skills/playing-to-win

在你喜欢的 AI 中提问

打开一个已预加载此 Agent Skill 的新对话。

文档

Playing to Win

Strategy is an integrated set of choices that positions you to win. Make those choices explicit.

You have a business, product, or initiative that needs a real strategy — not a to-do list dressed up as one. This skill applies A.G. Lafley and Roger Martin's Playing to Win framework to force the five essential strategic choices and check that they reinforce each other.

For detailed definitions and diagnostic questions for each choice, consult framework.md.


Workflow

  1. Clarify the subject: Identify what needs a strategy — a company, product line, feature area, or new market entry. Ask the user if ambiguous. Also identify the time horizon (6 months? 3 years?).

  2. Walk the cascade — Work through all five choices in order. Each choice constrains the next:

    Choice 1: What is our Winning Aspiration? Define what winning looks like in concrete, measurable terms. Not "be the best" — what specific outcome for which customers? A winning aspiration sets the purpose and frames every subsequent choice.

    Choice 2: Where to Play? Choose the playing field. This is the most important strategic choice — where you choose NOT to play matters as much as where you do. Dimensions: customer segments, geographies, product categories, channels, vertical stages of production.

    Choice 3: How to Win? Define the competitive advantage within the chosen playing field. There are only two generic strategies: cost leadership or differentiation. Which one, and specifically how? What's the unique value proposition that makes you the obvious choice?

    Choice 4: What Capabilities Must Be in Place? Identify the 3-5 core capabilities required to win where you've chosen to play. These should be reinforcing — each capability makes the others more valuable. Distinguish between capabilities you have today and those you need to build.

    Choice 5: What Management Systems Are Required? Define the systems, structures, and processes needed to build and maintain the capabilities. This is where strategy becomes operational — measurement systems, org structure, talent, processes, and culture.

  3. Test the cascade for coherence: The five choices must reinforce each other. Check:

    • Does the Where to Play choice match the Winning Aspiration?
    • Does the How to Win choice create genuine advantage in the chosen arena?
    • Do the Capabilities actually enable the How to Win?
    • Do the Management Systems build and sustain the Capabilities?
    • Would a competitor reading this strategy know exactly how to compete with you? (If yes, your How to Win isn't distinctive enough.)
  4. Identify the key strategic tension: Every strategy involves a core tension or tradeoff. Name it explicitly — what are you giving up? What bet are you making? What has to be true for this strategy to work?

  5. Reverse-engineer the must-be-true conditions: For each choice, list 2-3 conditions that must hold for the choice to be valid. These become your strategic risks and the hypotheses you need to validate.

Output Template

# Playing to Win: [Subject]

## Strategic Context
[2-3 sentences on the current situation, competitive landscape, and why strategic clarity is needed now]

## The Strategy Cascade

### 1. Winning Aspiration
[What does winning look like? For whom? By when? Be specific and measurable.]

### 2. Where to Play
**Chosen arena:**
- Customer segments: [who specifically]
- Geographies: [where]
- Product categories: [what]
- Channels: [how you reach them]
- Value chain position: [which parts]

**Explicitly NOT playing:**
- [What you're choosing to leave out — this is equally important]

### 3. How to Win
**Strategic positioning:** [Cost leadership / Differentiation — pick one]
**Unique value proposition:** [1-2 sentences — why customers choose you over alternatives]
**Key differentiators:**
- [Differentiator 1]
- [Differentiator 2]
- [Differentiator 3]

### 4. Core Capabilities
| Capability | Have Today? | Gap to Close | Priority |
|------------|-------------|-------------|----------|
| [Capability 1] | Yes/Partial/No | [what's missing] | Critical/Important |
| [Capability 2] | ... | ... | ... |

### 5. Management Systems
| System | Purpose | Status |
|--------|---------|--------|
| [System 1] | [what it enables] | Exists/Needs work/Missing |
| [System 2] | ... | ... |

## Cascade Coherence Check
[Does each level reinforce the others? Flag any misalignments.]

## Key Strategic Tension
[What's the core tradeoff? What are you betting on?]

## Must-Be-True Conditions
| Choice | Condition | Confidence | How to Validate |
|--------|-----------|------------|-----------------|
| Where to Play | [condition] | High/Med/Low | [test or evidence] |
| How to Win | [condition] | ... | ... |
| ... | ... | ... | ... |

## Recommended Next Steps
1. [Validate the riskiest must-be-true condition]
2. [Close the most critical capability gap]
3. [Build or fix the most important management system]

Adapting the Analysis

For a new product or market entry: Spend most time on Where to Play and How to Win. The temptation is to play everywhere — resist it. Narrow choices win.

For an existing product losing momentum: Start from the Winning Aspiration and check whether the current Where to Play still makes sense. Markets shift — your choices should too.

For a platform or multi-product company: Run the cascade for each product/segment independently, then check for strategic coherence across the portfolio. Shared capabilities across cascades are your leverage points.


Tips

  • The hardest part is choosing where NOT to play. If your Where to Play includes everyone, you don't have a strategy.
  • "How to Win" is not a feature list. It's the reason customers choose you, stated at the level a CEO would explain it.
  • If you can't identify the key strategic tension, the strategy isn't making hard enough choices.
  • Pair this with 7-powers to validate that your How to Win can become a durable competitive advantage.
  • Use amazon-working-backwards to test whether your Winning Aspiration translates into a compelling customer narrative.
  • Run pre-mortem on the must-be-true conditions to stress-test the riskiest assumptions.

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

amplitude/builder-skills

Performs deep analysis of a specific Amplitude chart to explain trends, anomalies, and likely drivers. Use when a metric looks unusual, investigating a spike or drop, or understanding the "why" behind numbers.

amplitude/builder-skills

Deeply analyze Amplitude dashboards by analyzing key charts, surfacing top areas for concern and takeaways, identify anomalies, then explain changes using customer feedback trends.

amplitude/builder-skills

Designs A/B tests with proper metrics and variants, analyzes running or completed experiments, and interprets results with statistical rigor. Use when setting up experiments, checking experiment status, analyzing results, or making ship decisions.

amplitude/builder-skills

Synthesizes customer feedback into actionable themes including feature requests, bugs, pain points, and praise. Use when planning product roadmap, understanding user sentiment, investigating specific issues, or preparing voice-of-customer reports.

amplitude/builder-skills

Analyze MCP server usage instrumented with Amplitude's MCP Analytics SDK: break usage and errors down by tool, read the rationales within each tool to see what callers are trying to do, and produce a prioritized write-up of actionable fixes. Use this skill whenever the user asks to understand how their MCP server is being used, what agents/users are trying to do with it, why tool calls are failing, what to fix or improve in their MCP server, or asks for an "MCP usage report", "tool error analysis", "intent analysis", "rationale clustering", or "MCP insights". Also trigger when the user mentions [MCP]-prefixed events, tool rationale, tool call errors, or just finished instrumenting their MCP server and wants to see what the data says. Requires the Amplitude MCP connector.

amplitude/builder-skills

Read lost deals and churned accounts from your CRM, extract reasons clustered by theme (missing features, pricing, competitors, UX), and write a prioritized weekly analysis with product improvement recommendations. Use before roadmap planning or to build the case for prioritizing retention work.

amplitude/builder-skills

Creates Amplitude charts from natural language descriptions, handling event selection, filters, groupings, and visualization choices. Use when you know what you want to measure but prefer not to build the chart manually.

amplitude/builder-skills

Guide an Amplitude user through building a custom agent by suggesting use cases grounded in their role and data, shaping the idea into a well-formed spec, and generating a ready-to-run Global Agent deeplink that creates it. Use to create, build, or set up a custom agent, automate a recurring analysis, or put a repeated report on a schedule.

amplitude/builder-skills

Builds comprehensive Amplitude dashboards from requirements or goals, organizing charts into logical sections with appropriate layouts. Use when creating a complete dashboard from scratch or assembling existing charts into a cohesive view.

amplitude/builder-skills

Monitors all active and recently completed experiments across Amplitude projects, triages them by importance, then runs deep analysis and reporting on the most impactful ones. Use when the user asks to "check on experiments", "experiment status", "experiment review", "what experiments are running", or wants a periodic experiment health report.

amplitude/builder-skills

Pull Intercom tickets and Slack support messages from the past 7 days, classify each signal, enrich with CRM data (ARR, plan, renewal), score by customer value and churn risk, and output a tiered priority report saved to Drive. Use when you need a fast, data-driven view of what support signals matter most.

amplitude/builder-skills

Use this skill whenever a user wants to improve existing pages on their website to get cited more by AI models — whether they say "our pages aren't getting cited", "improve this page for AI visibility", "which of our pages should we update", "make this article more cite-worthy", "our competitors are getting cited instead of us", "update our content for AI search", or any variation where the goal is improving an existing asset rather than creating something new. This skill pulls owned pages from AI Visibility, identifies which ones have citation potential but are underperforming, compares them against the external pages that are winning citations on the same topics, and produces section-level rewrites or a full-page update — then pushes the revision to the CMS as a draft. Trigger even if the user just says "help me get cited more" or "why is [competitor] getting cited instead of us".

amplitude/builder-skills

Use this skill whenever a user wants to win AI citations on prompts that competitors currently dominate — whether they say "competitors are getting cited instead of us", "we're losing on these prompts", "how do I outrank [competitor] in AI answers", "find prompts where we should be winning", "create content to beat [competitor]", or any variation where the goal is capturing AI share on prompts a competitor currently owns. This skill pulls competitor visibility data from AI Visibility, identifies the specific prompts where competitors win and Amplitude is absent, clusters them by intent, and produces targeted comparison pages, alternatives content, or rebuttal assets — then pushes drafts to CMS. Trigger on any mention of competitor, prompt hijack, outrank, or "why is [competitor] getting cited instead of us".

amplitude/builder-skills

Use this skill whenever a user wants to turn AI Visibility data into published content — whether they say "find content gaps", "what should we write about", "which topics have low visibility", "help me get cited by AI models", "create a blog post from our AI Visibility gaps", "we're losing to competitors on these prompts", or any variation where they want to go from AI visibility weakness to a draft article, landing page, or FAQ. This skill connects directly to Amplitude AI Visibility data (topics, prompts, visibility scores, citations, competitor data, full LLM responses and sources) and produces a publish-ready content brief plus full article draft. If the user mentions CMS (WordPress, Webflow, Contentful, Sanity, HubSpot, Ghost, Shopify), also trigger this skill to push the draft directly. Trigger even if they just say something vague like "what content should we create?" in an AI Visibility context.

amplitude/builder-skills

Use this skill whenever a user wants to test content variants before publishing to find which one will get cited most by AI models — whether they say "which version of this content will perform better", "test this article before we publish", "simulate how AI will respond to this content", "which angle should we use", "generate content variants and pick the winner", "run a simulation before publishing", or any variation where the goal is data-driven content selection rather than gut-feel publishing. This skill takes an identified content opportunity, generates 2–3 distinct variants with different angles or structures, scores them against actual AI model responses from AI Visibility, references the Simulate Changes feature for pre-publish validation, and produces a clear recommendation on which variant to publish — then pushes the winner to CMS. Trigger on any mention of "simulate", "test variants", "which performs better", "A/B content", or "before we publish".

amplitude/builder-skills

Use this skill whenever a user wants to understand which external sources are being cited by AI models on topics relevant to their brand, and wants to create content that will outrank those sources — whether they say "what sources are AI models citing", "why is [third-party site] being cited instead of us", "we want to be the definitive source on X", "build something that gets cited more than G2 or TechRadar", "create an authoritative asset", or any variation where the goal is producing a new reference asset (definition page, benchmark, methodology, glossary, comparison hub) designed to beat existing top-cited sources. This skill analyzes AI Visibility source data, reverse-engineers what makes top-cited pages authoritative, and produces a superior source asset — then pushes it to CMS as a draft. Trigger on any mention of "sources", "third-party citations", "authoritative content", "definitional pages", or "outrank".

amplitude/builder-skills

Instrument a Node/TypeScript MCP server with Amplitude's @amplitude/mcp-analytics SDK so tool calls, sessions, and rationale are tracked as Amplitude events. Use this skill whenever the user wants to add Amplitude analytics to their MCP server, mentions "MCP Analytics", "@amplitude/mcp-analytics", "instrument my MCP server", "track MCP tool calls", "add rationale to my MCP tools", or wants agent traffic (Claude, Cursor, ChatGPT) attributed back to Amplitude. Also use for adding UTM tagging to MCP-returned links, or for troubleshooting identity/user_id mismatches between MCP events and web/mobile Amplitude data.

amplitude/builder-skills

Instruments a pull request with Amplitude analytics that conform to the project's existing taxonomy. Reads the tracking plan via the Amplitude MCP server (events, properties, naming conventions), analyzes the PR diff to find the few user actions genuinely worth tracking, detects the codebase's SDK and tracking patterns, and adds instrumentation that matches both. Optionally (opt-in) stages new events and properties on an Amplitude tracking-plan branch for data-governance review. Use when asked to "instrument this PR", "add analytics to this change", "add tracking", "add Amplitude events", "instrument this feature", or "what should I track here".

amplitude/builder-skills

Diagnoses product health by cross-referencing Amplitude analytics (dashboards, charts, funnels, feedback, AI agent analytics), optionally Datadog (errors, latency, stack traces), and optionally Slack (qualitative feedback, bug reports, feature requests). Identifies what's broken, what's working, and what to do about it — with root causes, not just symptoms. Use when asked to "diagnose my product", "what's going on", "product health check", "what's broken", "where are users struggling", "give me a product diagnosis", or "what should I focus on".

amplitude/builder-skills

Summarizes B2B account health by analyzing usage patterns, engagement trends, risk signals, and expansion opportunities. Use for customer success reviews, renewal preparation, QBRs, or account prioritization.

相关技能