Auto-generate a structured experiment brief when a user expresses intent to test something. Use this skill whenever users mention testing, experiments, A/B tests, or want to validate a product change with data. Trigger on phrases like "I want to test...", "Let's experiment with...", "Should we A/B test...", "Can we…
The analysis and lifecycle owner for experiments. Full experiment lifecycle: design, power analysis, statistical analysis, interpretation, reporting, and monitoring of A/B tests. Invoke as /experiment. Trigger on "A/B test", "experiment", "treatment vs control", "sample size", "MDE", "statistical significance", "ship…
Quick, interactive data exploration without the full pipeline. Use this skill whenever a user wants to explore data, understand what's in a dataset, browse tables or columns, check data distributions, spot patterns, or get familiar with data before analysis. Trigger on phrases like "/explore", "let me explore the…
Export analysis results in different formats for different audiences — email summaries, Slack updates, decision briefs, Google Docs with embedded charts, Word documents, slide decks, or raw data CSVs. Use this skill whenever someone says /export, "export this as...", "send this to...", "share this analysis", "create a…
Generate time-series forecasts and projections for metrics over future time periods. Use this skill whenever the user asks about future values, predictions, or projections — phrases like "what will X look like next month?", "forecast DAU for Q2", "project revenue", "estimate future growth", "what should we expect?"…
Create properly formatted Google Docs via the MCP API. This skill prevents common issues like text/image overlap, broken heading hierarchy, excessive whitespace, and inconsistent formatting. Use this skill automatically whenever you're building a Google Doc, calling any Google Docs MCP tool on the google-workspace…
Create properly formatted Google Slides presentations via the MCP API. Use this skill whenever you're building Google Slides decks, calling batchupdatepresentation, designing slide layouts, or the google-slides-creator or google-slides-reviewer agents are running. This skill prevents common API errors (zero-weight…
Ensure every success metric is paired with guardrail metrics and check for trade-offs before presenting improvements as wins. Guardrails protect against winning the metric game while losing the business game. Apply this skill whenever you define a metric, create a metric spec, document a KPI, report positive findings…
Browse and search past analyses from the knowledge system's analysis archive. Use this skill whenever the user invokes /history or variants like /history search=X, /history {id}, /history --all, /history dataset=X, or asks questions about their analytical work history such as "what have I analyzed before?", "what…
Diagnose a context-related analytical failure, propose the smallest relevant change, compare the same evaluation cases before and after, and produce an accept, revise, or revert receipt. Use when the user asks to improve context, fix a definition or example, test whether context helped, or invokes /improve-context.
Initialize session context, resolve the active dataset and context source, load resident instructions, and inventory the context available for question-specific selection. Run at the start of every session and again after /connect-data or /switch-dataset. Handles missing files gracefully, so running it when unsure is…
Record analyst mistakes, fixes, and reusable learnings so future analyses never repeat an error. Fires automatically when the user corrects work ("actually it's Y", "that's wrong") or teaches a rule ("always use X", "never include test users", "remember that our fiscal year starts in February"), and manually on "log a…
Define any metric completely with a standardized template: calculation, denominator, time window, filters, interpretation. Trigger on "define this metric", "how should we measure X?", "what's the right way to calculate Y?", "document our metrics", "create a metric definition", "different teams are measuring this…
Browse, search, and display metric definitions from the active dataset's metric dictionary. This skill provides quick access to how metrics are defined, computed, and validated. Use this skill whenever the user wants to see metric definitions, understand how a metric is calculated, check what metrics are available, or…
Review evaluation history, distinguish system, data, suite, and evaluator changes, and apply an operating response. Use for regressions, eval monitoring, release gates, or trend questions.
Export analysis results to a Notion page with proper structure, embedded charts, data stamps, and provenance toggle blocks. Use this skill whenever the user says "/export notion", "export to Notion", "create a Notion page", "share this in Notion", "put this in Notion", "send to Notion", or mentions wanting analysis…
Change how visibly Claude surfaces analytical work during L3+ analyses. Three modes — guided (announce each phase and pause for /continue), narrated (announce each phase and run end-to-end), autopilot (silent end-to-end, final output only). Use this skill whenever the user invokes /pace, /pace guided, /pace narrated…
Browse, search, and leverage recurring analytical patterns discovered across past analyses. Use this skill when users want to see what patterns have emerged from previous work, check if a current finding matches a known pattern, search for patterns by keyword or metric, view pattern details, understand established…
Classify every analytical request (anything about data, metrics, trends, segments, funnels, revenue, retention, experiments, or "why did X change") into complexity levels L1-L5 and route it before any analytical workflow starts, including follow-ups mid-analysis and chart requests. Simple lookups get a direct answer…
Run one analytics task through several fresh trials to measure what repeats and what varies. Use for reliability, repeatability, variance, or repeated-run requests. This measures stability, not correctness.
Browse, inspect, compare, and clean up past pipeline runs. This skill is your window into analysis history — every /run-pipeline execution creates a tracked run with its own working directory, outputs, and state. Use this skill whenever the user wants to see what analyses have been executed, review past work, compare…
★not rated 298▲
+1 3d agoC229 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: