125 skills · sorted by relevance
Plan and validate tracking for marketing and product decisions. Define events, configure GA4 and Google Tag Manager, standardize campaign link labels, and calculate metrics using matching time periods to produce dependable measurement plans and findings.
Plan A/B tests to compare page changes using clear hypotheses and meaningful measures. The skill helps define sample size, duration, traffic allocation, and result interpretation, and organize a continuing program of prioritized experiments.
Review marketing pages and forms to identify obstacles to purchases, inquiries, or other desired actions. Get prioritized recommendations, alternative headlines and button text, and experiment ideas based on the page’s purpose and traffic sources.
Design recurring marketing workflows for SEO checks, ad reviews, and churn monitoring. Define when an agent checks, when it acts, what requires human approval, and when it stops, using reusable workflow templates.
Plan A/B tests to compare page or messaging changes. Helps define hypotheses, choose success metrics, estimate sample sizes, allocate traffic, and interpret results, while also organizing a repeatable process for prioritizing and documenting experiments.
Plan an A/B test to compare product changes, with a clear hypothesis, variants, sample estimates, and tracking checks. Define success metrics and stopping rules before launch, then document results and decisions.
Plan, implement, and audit website or app analytics with GA4 and Google Tag Manager. Define meaningful events, standardize campaign tags, and validate data collection so marketing and product decisions use consistent measurements.
Plan A/B tests that compare page or product changes, with clear hypotheses, sample sizes, success metrics, and traffic allocation. Get a structured test plan and guidance for interpreting results and deciding what to try next.
Plan A/B tests that compare page variations, from headlines to pricing layouts. Define a hypothesis, choose success metrics, calculate sample size and duration, and prepare launch checks and results reports to support decisions.
Analyze A/B test results to decide whether to launch a change, extend testing, stop, or investigate further. Check sample size, statistical significance, uncertainty ranges, and effects on other important metrics, then summarize the recommendation and next steps.
Turn A/B tests and product experiment records into decision reports. Organize hypotheses, setup, and metrics, explain findings and uncertainty, then recommend shipping, iterating, extending, or stopping, with follow-up experiments based only on supplied data.
Statistical significance calculator for A/B test results with sample size requirements, segment breakdowns, and hypothesis generation. Use when feeding test results, checking statistical significance, calculating sample sizes, analyzing experiment outcomes, or generating next test ideas based on results. Platform: Google and Meta.
The English summary is being prepared. Showing the original description.
Designs statistically valid split tests for ads, audiences, landing pages, or bid strategies. Calculates required sample sizes before you start, monitors results during the test, and calls winners when statistical significance is actually reached — not when you feel like one is winning. Platform: Google and Meta.
The English summary is being prepared. Showing the original description.
Run an explicitly requested Zephyr control/treatment benchmark on the same pre-normalized sample and compare Finelog stage metrics.
The English summary is being prepared. Showing the original description.
When the user wants to plan, script, produce, or optimize App Store Preview videos or Google Play promo videos — the autoplay videos that show in App Store/Play Store search and product pages. Use when the user mentions "App Preview", "preview video", "app store video", "promo video", "Play Store video", "video poster frame", "YouTube promo for Play Store", "30 second app video", "video script", "video specs", or "should I add a preview video". For static screenshots, see screenshot-optimization. For A/B testing the video, see ab-test-store-listing. For broader creative briefs, see screenshot-optimization (covers stills).
The English summary is being prepared. Showing the original description.
When the user wants to design, optimize, or evaluate App Store screenshots and preview videos. Also use when the user mentions "screenshots", "app preview", "product page design", "screenshot design", "creative assets", or "what should my screenshots show". For A/B testing screenshots, see ab-test-store-listing. For full ASO audit, see aso-audit.
The English summary is being prepared. Showing the original description.
When the user wants to design, test, or improve their app icon to increase tap-through rate and conversions in App Store search and browse. Use when the user mentions "app icon", "icon design", "icon A/B test", "icon variants", "tap-through rate", "icon conversion", "icon refresh", or wants to know what makes a good app icon. For screenshot optimization, see screenshot-optimization. For full listing A/B tests, see ab-test-store-listing.
The English summary is being prepared. Showing the original description.
When the user wants to A/B test App Store product page elements to improve conversion rate. Also use when the user mentions "A/B test", "product page optimization", "test my screenshots", "test my icon", "conversion rate optimization", "CPP", or "custom product pages". For screenshot design, see screenshot-optimization. For metadata optimization, see metadata-optimization.
The English summary is being prepared. Showing the original description.
When the user wants to design, deploy, or measure Apple Custom Product Pages (CPP) — the alternate App Store product pages with different screenshots, preview videos, and promo text shown to users coming from specific URLs (typically ad campaigns or social posts). Use when the user mentions "Custom Product Page", "CPP", "alternate product page", "App Store URL variant", "ASA CPP", "campaign-specific landing page", "product page per audience", "App Store Connect CPP", "ppoUrl", "?cpp=" parameter, or "show different screenshots to different ad audiences". For App Store A/B tests on the default page, see ab-test-store-listing. For paid ad campaigns that route to CPPs, see apple-search-ads or ua-campaign.
The English summary is being prepared. Showing the original description.
When the user wants to set up, interpret, or improve their app analytics and tracking. Also use when the user mentions "analytics", "tracking", "metrics", "KPIs", "App Store Connect analytics", "install tracking", "funnel", "attribution", or "how is my app performing". For A/B testing, see ab-test-store-listing. For retention metrics, see retention-optimization.
The English summary is being prepared. Showing the original description.
Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.
The English summary is being prepared. Showing the original description.
Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.
The English summary is being prepared. Showing the original description.
Generate 3-5 messaging variants for a value proposition, design structured A/B tests, and analyze results to determine which framing resonates most with ICP. Tests can run via LinkedIn organic posts, cold email subject line splits, or both. Pure reasoning for variant generation and analysis — the user deploys the tests through their own tools. Use when a team can't decide between messaging angles and needs data, not opinions.
The English summary is being prepared. Showing the original description.
Plan an A/B test by script: sample size per variant, days to run, stopping rules. "how many visitors per variant"
The English summary is being prepared. Showing the original description.