ali-demirbas
UserA/B testing and CRO playbook for Claude Code: 205 experiment scenarios for e-commerce, mobile and SaaS, single-variable test design, plan auditing, real z-test statistics, and a rendered HTML card per scenario.
Categories
Indexed Skills (17)
ab-test-audit
Audit an existing A/B test plan, running experiment or mockup pair for methodological flaws. Use when the user says "review my experiment", "is this test set up correctly", "what is wrong with this test", "check my A/B test", "is my test valid", "did I set this up right", "why did my test fail", "does this test have a confound", "test planımı denetle", "bu test doğru mu kurulmuş", "testimde sorun var mı", or shares variant designs, a test brief or a running experiment asking what is wrong. Checks confounds and multi-variable changes, missing or wrong primary metric, absent guardrails, p-hacking and peeking risk, sample ratio mismatch, selective attrition, novelty effect, unrealistic duration and overlapping concurrent tests. To interpret numbers from a finished test, see ab-test-results.
ab-test-card
Render an A/B test scenario as a single-file HTML card in the archive's visual style — a Variant A/B mockup pair with the tested element boxed, plus the three coloured boxes. Use when the user says "make a card for this test", "turn this into a card", "visualise this test", "render this scenario", "make a slide out of this", "show me the two variants side by side", "kart yap", "görselleştir", "slayt formatına çevir", "bunu karta bas". Runs automatically for every scenario produced by ab-test-suggest and ab-test-design (CLAUDE.md rule 9), so it rarely needs to be invoked directly. Output is self-contained HTML with no external assets, built deterministically by scripts/build_card.py.
ab-test-design
Design a NEW single-variable A/B test for the user's specific page, feature or funnel step, in the archive's three-box framework. Use when the user shares a page, screenshot, URL, wireframe or feature description and asks "design an experiment for this", "design a test for this page", "how should I test this", "set up an A/B test for this", "create a test plan", "write a hypothesis for this", "what variant should I try", "bunun için test tasarla", "bu akışta ne test edilir", "hipotez kur", "buna nasıl test kurarım". Produces the hypothesis, Variant A/B definitions, a tool-agnostic setup spec, and an HTML card per scenario. For ready-made ideas from the archive instead, see ab-test-suggest. To check a plan you already wrote, see ab-test-audit.
ab-test-results
Interpret A/B test results and run the statistics on real numbers. Use when the user pastes visitor and conversion counts per variant, or asks "is this significant", "interpret these results", "did my test win", "which variant won", "calculate statistical significance", "what is the p-value", "confidence interval", "how many visitors do I need", "what sample size do I need", "how long should I run this test", "minimum detectable effect", "is my traffic split off", "sample ratio mismatch", "SRM", "sonuçları yorumla", "test bitti ne çıktı", "anlamlı mı", "kaç ziyaretçi lazım", "örneklem hesapla". Runs a real two-proportion z-test, confidence interval, required sample size, revenue and margin check, and an SRM check through scripts/analyze_results.py — the math is computed, never estimated — then states the decision and what happens next. To check whether the test was set up correctly in the first place, see ab-test-audit.
ab-test-suggest
Suggest proven A/B test scenarios for a given page or journey stage, ranked by ICE. Use when the user asks "what should I test", "what should I A/B test on my checkout / cart / product page / pricing page / homepage", "give me A/B test ideas", "experiment ideas", "split test ideas", "CRO ideas", "which tests should I run first", "what tests are worth running", "test öner", "hangi testleri yapmalıyım", "checkout için hangi testler", "anasayfam için test fikirleri", "ne test edeyim". Picks matching scenarios from the curated archive in knowledge/scenarios/ (e-commerce, mobile app, SaaS/B2B, search and filtering, forms, pricing) and delivers each as an HTML card via ab-test-card. For a test designed specifically for a page or screenshot you share, see ab-test-design. To review a plan you already have, see ab-test-audit.
ab-test
A/B test engine router. Use when the user says "abtest", "/abtest", "A/B test", "split test", "experiment", "CRO", "conversion rate optimization", "test öner", "hangi testi yapmalıyım", "test planımı denetle", "deney tasarla", "sonuçları yorumla", "örneklem hesapla", "CRO testi" or any /ab-test subcommand — or when a request plausibly matches more than one ab-test-* skill, in which case the router disambiguates instead of guessing. Also use when the request sounds like experimentation but may not be an A/B question at all (a diagnosis, a measurement setup, an already-made decision, or a page whose traffic cannot support a split), so the wrong tool is not applied silently. Routes to ab-test-suggest (ideas from the archive), ab-test-design (a new test for your page), ab-test-audit (review a plan), ab-test-results (statistics on real numbers) and ab-test-card (render a scenario).
academic-research
Use when the user asks to find research papers, check what a study found, look up peer-reviewed literature, or verify a scientific/technical claim against published research. Triggers on "find papers on", "what does the research say", "peer-reviewed studies on", "academic research", "literature on X". Produces evidence records (DOI/URL + verbatim quote + peer-review status), never conclusions. Do NOT use for a blog's summary or interpretation of a paper (use blog-research, then cross-check against this skill when the claim is load-bearing), or for general web content (use web-research).
blog-research
Use when the user asks to check what a specific blogger/expert has written, find tutorial or how-to content, or research opinion/practitioner writing on a topic. Triggers on "check their blog", "find a tutorial for", "what do practitioners say", "blog research". Produces evidence records (URL + verbatim quote + author credibility note), never conclusions. Do NOT use for official company documentation (use official-source-research), news coverage (use news-research), or general web pages with no identifiable author (use web-research).
github-research
Use when the user asks to search GitHub, find repositories, check what a project's code/issues/PRs/releases say, or look up how something is implemented in open source. Triggers on "search GitHub", "find a repo for", "check the issues on", "how do they implement X", "github research". Produces evidence records (URL pinned to a commit SHA + verbatim quote + date), never conclusions. Do NOT use for general web search (use web-research), Reddit/community discussion (use reddit-research), or when the user just wants you to write code (that's normal coding, not research).
news-research
Use when the user asks to find news coverage of an event, check what press outlets reported, or research how an announcement was covered. Triggers on "find news about", "what did press say", "news coverage of", "news research". Produces evidence records (URL + verbatim quote + wire/syndication check), never conclusions. Do NOT use for the underlying official announcement itself (use official-source-research — trace to it, don't just cite the reprint), blog opinion pieces (use blog-research), or academic coverage (use academic-research).
official-source-research
Use when the user asks to check official documentation, a company's own announcement, a government/regulatory filing, or a standards body's specification. Triggers on "check the official docs", "what does the filing say", "official announcement", "regulatory source", "official-source research". Produces tier-1 evidence records (URL + verbatim quote), never conclusions. Do NOT use for press coverage of an official source (use news-research, which should trace back here anyway) or community discussion about an official source (use reddit-research/social-research).
reddit-research
Use when the user asks to search Reddit, check what people are saying on a subreddit, find complaints or pain points, validate a product idea against community discussion, or track sentiment/trends on Reddit. Triggers on "search Reddit", "check r/", "what are people saying about", "Reddit complaints", "pain points on Reddit", "reddit research". Produces community-signal evidence records (permalink + verbatim quote + timestamp), never conclusions. Do NOT use for GitHub content (use github-research) or general web search (use web-research) — Reddit discussion ABOUT a GitHub project still belongs here, not github-research.
research-intelligence
Use when the user wants a research question investigated with a verifiable, cited evidence trail — "research X", "deep research on Y", "investigate Z and show sources", "give me a report with citations", or wants a synthesized answer with confidence levels rather than a raw search dump. For a single named source only ("just search the web", "just check GitHub", "just check Reddit"), let that specific source skill trigger directly instead — don't route those through this orchestrator.
research-planner
Use when a research question needs to be broken into sub-questions, matched to which source skills apply, and given a search budget and stopping condition — before any source skill starts collecting. Triggers on "plan this research", "break this question down", or is invoked automatically by the research-intelligence orchestrator as its first stage. Do NOT use this to collect evidence yourself (dispatch the source skills for that) or to judge evidence quality (that's source-verify and the validator).
social-research
Use when the user asks to search X/Twitter, LinkedIn, Hacker News, Discord, or general forums for discussion of a topic (not Reddit — that's reddit-research). Triggers on "search Twitter/X", "check Hacker News", "LinkedIn discussion", "forum discussion about", "social research". Produces community-signal evidence records (URL + verbatim quote + timestamp), never conclusions. Do NOT use for Reddit (use reddit-research, which has its own dedicated access chain), GitHub discussion (use github-research), or general web pages (use web-research).
source-verify
Use when evidence records exist with verification_status pending and need to be checked before synthesis — either because the user asks to "verify these sources", "check if this quote actually supports the claim", "audit this evidence", or because the orchestrator has just finished a collection pass and is handing off to verification before synthesis. This is the mandatory station between any source skill and the synthesizer — no source skill's evidence reaches findings.jsonl without passing through here first. Do NOT use this to collect new evidence (that's the individual source skills) or to compute finding status (that's the deterministic validator, scripts/validate_run.py — this skill only resolves evidence-level verification_status).
web-research
Use when the user asks to search the web, look something up online, find articles or pages about a topic, or check what a website/documentation page says. Triggers on "web search", "search online", "look up", "find articles about", "check the docs for", "what does the website say". Produces evidence records (URL + verbatim quote + archive link), never conclusions — for synthesized findings with confidence status, the orchestrator routes to the full research-intelligence pipeline instead. Do NOT use for GitHub-specific queries (repos, code, issues — use github-research), Reddit/community queries (use reddit-research), or academic paper search (use academic-research).
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.