Communitygithub.com

실험 설계

가설을 작성하고, 성공 지표를 정의하며, 홀드아웃 전략을 계획합니다. A/B 테스트 또는 실험 계획을 설계할 때 사용하세요.

실험 설계란 무엇인가요?

이 스킬은 A/B 테스트 또는 기타 실험을 설계할 때 필요한 구조화된 템플릿을 제공합니다. 사용자가 '이걸 테스트해야 한다'는 막연한 아이디어에서 팀과 데이터 과학자가 검토할 수 있는 체계적인 실험 설계로 전환할 수 있도록 돕습니다. 프롬프트 템플릿을 기반으로 가설, 기본 지표, 보조 지표, 가드레일 지표, 대상 및 할당 비율, 홀드아웃 전략, 기간 추정, 위험 및 고려 사항을 생성합니다. 제품 관리자, 실험 전문가, 또는 데이터 기반 의사 결정을 원하는 모든 개발자에게 유용하며, Amplitude 플랫폼과 같은 실험 플랫폼과 함께 사용할 수 있습니다. 이 스킬은 특히 가설을 '만약 우리가 [변경]한다면, [결과]가 발생할 것이다. 왜냐하면 [근거]이기 때문이다' 형식의 반증 가능한 문장으로 작성하도록 요구하여 실험의 과학적 엄격성을 높입니다.

지원 대상~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/amplitude/builder-skills/tree/HEAD/product-skills/skills/craft-experiment-design

즐겨 사용하는 AI에게 물어보기

이 에이전트 스킬이 미리 로드된 새 채팅을 엽니다.

문서

실험 설계은(는) 무엇을 하나요?

가설을 작성하고, 성공 지표를 정의하며, 홀드아웃 전략을 계획합니다.

A/B 테스트를 실행하고 싶지만 먼저 계획을 명확히 세워야 합니다. 이 스킬은 '이걸 테스트해야 한다'는 아이디어에서 팀과 데이터 과학자가 검토할 수 있는 체계적인 실험 설계로 전환하는 데 도움을 줍니다.


프롬프트 템플릿

당신은 경험이 풍부한 제품 관리자이자 실험 전문가입니다.

제가 테스트하고 싶은 내용은 다음과 같습니다:

<context>
$ARGUMENTS
</context>

> 위 내용이 비어 있으면 사용자에게 다음과 같이 질문하세요: "{{테스트하려는 변경 사항과 그 이유를 설명해 주세요}}"

다음을 포함하는 실험 계획을 설계하도록 도와주세요:

1. **가설** — '만약 우리가 [변경]한다면, [결과]가 발생할 것이다. 왜냐하면 [근거]이기 때문이다' 형식의 명확하고 반증 가능한 문장.
2. **기본 지표** — 성공 또는 실패를 결정하는 단일 지표.
3. **보조 지표** — 의도하지 않은 효과를 관찰하기 위한 2-3개의 지원 지표.
4. **가드레일 지표** — 저하되어서는 안 되는 지표 (예: 오류율, 지연 시간, 유지율).
5. **대상 및 할당** — 테스트에 포함되어야 하는 대상은 누구인가? 권장 분할 비율은?
6. **홀드아웃 전략** — 테스트 후에도 홀드아웃 그룹을 유지해야 하는가? 그 이유는?
7. **기간 추정** — 테스트를 얼마나 오래 실행해야 하는가? 이를 결정하는 가정은 무엇인가?
8. **위험 및 고려 사항** — 무엇이 잘못되거나 결과에 편향을 초래할 수 있는가?

구체적으로 작성하세요. 가능한 경우 실제 지표 이름을 사용하세요. 데이터나 엔지니어링 팀과 검증해야 할 가정을 명시하세요.

팁

  • 보유한 사전 데이터나 맥락(전환율, 트래픽 볼륨, 이전 테스트 결과)을 포함하세요. 기간 및 할당 권장 사항에 도움이 됩니다.
  • 가드레일 지표에 대해 확신이 서지 않으면 스킬에 제품 영역을 기반으로 몇 가지를 제안해 달라고 요청하세요.

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.

관련 스킬