ai-analyst-lab
40 verified skills5,869 total stars
.claude/skills/TEMPLATE
# Skill: {{BLANK_1_SKILL_NAME}} ## Purpose {{BLANK_2_WHEN_TO_FIRE}} ## When to Use Fires automatically when the user asks Claude to do something that matches the trigger condition above. ## Instructions 1. Detect the trigger condition 2. Execute your guardrail check 3. If the check matters, print a clear, visible warning with "{{BLANK_3_SIGNATURE_PHRASE}}" as the first line 4. Continue with the analysis, incorporating the warning into the output ## Anti-Patterns - Do not fire when the condit
testing175
.claude/skills/architect
# Skill: /architect Run the multi-persona planning methodology to produce a master plan for a new project or feature. ## Parameters - **brief** (required): What are we building? Can be a sentence, a paragraph, or "read [file]" to pull from an existing doc. - **--personas** (optional): Override persona count. Default: 5. - **--skip-debate** (optional): Skip Phase 2 debate and go straight to synthesis. Faster but lower quality. - **--output-dir** (optional): Where to write plans. Default: auto-
development146
.claude/skills/archive-analysis
# Skill: Archive Analysis ## Purpose Save a completed analysis to the knowledge system's analysis archive for future recall. Captures key findings, metrics used, agents invoked, and output file paths so that past work can be referenced in future sessions. ## When to Use - After completing an L3+ analysis (post-validation) - After `/run-pipeline` completes successfully - User says "save this analysis" or "archive this" - Automatically triggered at the end of Step 18 (Close the Loop) ## Instruc
devops146
.claude/skills/business
# /business — Business Context Browser > Interactive browser for your organization's knowledge system. Explore terms, > products, metrics, objectives, and team structure. ## Trigger Invoked as `/business` or `/business {subcommand}` ## Prerequisites - Organization context must exist at `.knowledge/organizations/{org}/` - Read `.knowledge/setup-state.yaml` to find active organization - If no org configured: "No organization context found. Run `/setup` Phase 3 to configure business context, or
data-ai146
.claude/skills/close-the-loop
# Skill: Close-the-Loop ## Purpose Ensure every analysis that includes a recommendation ends with a clear follow-up plan — who decides, what metric tracks success, when to check back, and what to do if the expected outcome doesn't materialize. ## When to Use Apply this skill at the end of any analysis that produces a recommendation or action item. If the analysis concludes with "we should do X," this skill ensures X actually gets tracked and evaluated. Skip only for pure exploratory analyses w
testing146
.claude/skills/compare-datasets
# Skill: Compare Datasets ## Purpose Compare metrics, findings, and patterns across two or more connected datasets. Helps identify cross-dataset patterns (e.g., "conversion funnel behavior is similar across both product lines") and dataset-specific anomalies. ## When to Use - User says `/compare-datasets` or "compare across datasets" - After analyzing multiple datasets, to find commonalities - When the user asks "is this pattern unique to this dataset?" ## Invocation `/compare-datasets` — com
testing146
.claude/skills/connect-data
# Skill: Connect Data ## Purpose Guided wizard to connect a new dataset. Walks the user through selecting a connection type, configuring credentials, validating the connection, profiling the schema, and setting up the knowledge brain. ## When to Use - User says `/connect-data` or "connect my database" or "add a new dataset" - First-run welcome suggests connecting data - After `/switch-dataset` when the target dataset doesn't exist yet ## Invocation `/connect-data` — start the connection wizar
documentation146
.claude/skills/data-profiling
# Skill: Data Profiling ## Purpose Deep-profile the active dataset to understand schema structure, value distributions, temporal patterns, correlations, completeness gaps, and anomalies. Produces a comprehensive profile report that serves as the foundation for analysis planning and data quality assessment. ## When to Use - After connecting a new dataset (post-bootstrap, pre-analysis) - Before the first analysis on any dataset - When explicitly invoked by the user - When the existing profile is
testing146
.claude/skills/datasets
# Skill: Datasets ## Purpose List all connected datasets with their status, table counts, and last analysis date. ## When to Use Invoke as `/datasets` when the user wants to see what datasets are available. ## Instructions ### Step 1: Read the source registry Read `data_sources.yaml` to get the list of registered sources. ### Step 2: Read the active pointer Read `.knowledge/active.yaml` to determine which dataset is currently active. ### Step 3: Enrich with brain data For each registere
data-ai146
.claude/skills/explore
# Skill: Explore Data ## Purpose Quick, interactive data exploration without the full pipeline. Lets users poke around the active dataset — preview tables, check distributions, spot patterns, and form hypotheses before committing to a formal analysis. ## When to Use - User says `/explore` or "let me explore the data" or "what's in this dataset?" - After connecting a new dataset, before any formal analysis - When the user wants to understand data shape without a specific question ## Invocation
testing146
.claude/skills/export
# Skill: Export ## Purpose Export analysis results in different formats for different audiences. Converts pipeline outputs into ready-to-share deliverables. ## When to Use - User says `/export` or "export this as..." or "send this to..." - After completing an analysis or pipeline run - When the user needs results in a specific format ## Invocation `/export slides` — generate/refresh Marp slide deck from latest analysis `/export email` — write an executive summary email (markdown) `/export sla
development146
.claude/skills/feedback-capture
# Skill: Feedback Capture ## Purpose Pre-router interceptor that runs BEFORE the Question Router on every user message. Detects correction signals, methodology learnings, and positive feedback, captures them to `.knowledge/`, then passes through to normal routing. ## When to Use - On every incoming user message, before Question Router classification - Runs silently — the user should never notice this skill executing ## Instructions ### Step 0: Intercept (runs before Question Router) Wrap al
databases146
.claude/skills/guardrails
# Skill: Guardrails Awareness ## Purpose Ensure that every success metric is paired with at least one guardrail metric, and that positive findings are checked for trade-offs before being presented as wins. ## When to Use Apply this skill in two situations: 1. **When defining metrics** — after using the Metric Spec skill, check whether the metric has a guardrail pair 2. **When reporting positive findings** — before presenting any improvement, check whether a related guardrail metric degraded #
testing146
.claude/skills/history
# Skill: History ## Purpose Browse and search past analyses from the analysis archive. Helps users recall what they've analyzed before, find prior findings, and build on previous work. ## When to Use - User says `/history` or "what have I analyzed before?" - At session start, to provide context on prior work - When framing a new question, to check if similar analysis exists ## Invocation `/history` — list recent analyses (last 10) `/history {id}` — show full details for a specific analysis `/
development146
.claude/skills/log-correction
# Skill: Log Correction ## Purpose Record analyst mistakes and their fixes so future analyses learn from past errors. Manual counterpart to automatic feedback capture. ## When to Use - User says "log a correction", "that was wrong because...", or similar - Feedback-capture skill routes here for detailed correction entry - After discovering and fixing an error mid-analysis ## Instructions ### Step 1: Gather Details Extract from conversation context or ask the user: 1. **What was wrong?** —
data-ai146
.claude/skills/metric-spec
# Skill: Metric Spec ## Purpose Define any metric clearly and completely using a standardized template so there is no ambiguity about what is being measured, how it's calculated, or how to interpret it. ## When to Use Apply this skill when defining a new metric, when a metric is referenced without a clear definition, or when different people are using the same metric name to mean different things. Every metric used in an analysis should have a spec. ## Instructions ### Metric Spec Template
research146
.claude/skills/notion-ingest
# /notion-ingest — Notion Workspace Crawler > Crawls a Notion workspace to extract business terms, metrics, product docs, > and team structure. Populates the organization knowledge system. ## Trigger Invoked as `/notion-ingest` or `/notion-ingest {workspace_url}` ## Prerequisites - Notion integration token configured in `.knowledge/user/integrations.yaml` - Organization directory exists at `.knowledge/organizations/{org}/` - If no token: "Notion integration token not found. Add it to `.knowle
documentation146
.claude/skills/patterns
# Skill: Patterns ## Purpose Browse and search recurring patterns discovered across analyses. Patterns are auto-extracted after each analysis archive and represent behaviors that appear consistently in the data. ## When to Use - User says `/patterns` or "what patterns have we seen?" - During analysis, to check if a finding matches a known pattern - At session start, to remind the user of established behaviors ## Invocation `/patterns` — list patterns for the active dataset `/patterns --global
testing146
.claude/skills/presentation-themes
# Skill: Presentation Themes ## Purpose Generate slide decks that look professional, tell a coherent analytical story, and follow consistent theme standards matching the visualization patterns. ## When to Use Apply this skill whenever creating a presentation, slide deck, or structured output intended for stakeholders. Always apply the active theme. Default theme: `corporate`. ## Instructions ### Slide Structure Templates Every presentation follows this arc: ``` Title → Executive Summary →
content-media146
.claude/skills/question-router
# Skill: Question Router ## Purpose Classify incoming user questions into complexity levels (L1-L5) and route them to the appropriate response path. This replaces the old "skip-step" logic with a structured classification that adapts the workflow depth to the question's actual needs. ## When to Use - At the start of every user interaction that looks like an analytical request - Before launching the full 18-step pipeline - When the user asks a follow-up question mid-analysis ## Classification
devops146
.claude/skills/resume-pipeline
# Skill: Resume Pipeline ## Purpose Resume an interrupted analysis pipeline by reading `working/pipeline_state.json`, determining which agents completed, and continuing from the next READY agents using the DAG walker. ## When to Use Invoke as `/resume-pipeline` when: - A previous analysis session was interrupted (context limit, user break, connection issue) - The user wants to continue an analysis started in a prior conversation - Pipeline state file exists from a partially completed run - A p
devops146
.claude/skills/run-pipeline
# Skill: Run Pipeline ## Purpose Single entry point for end-to-end analysis — from raw data to finished slide deck. Uses a DAG-based execution engine that reads agent dependencies from `agents/registry.yaml`, resolves execution order automatically, and supports parallel agent execution, resume from failure, and execution plan pruning. ## When to Use Invoke with: `/run-pipeline`, "run the full pipeline", "analyze end-to-end", or "take this data through the full workflow". ## Accepted Arguments
testing146
.claude/skills/runs
# Skill: Runs ## Purpose Browse, inspect, compare, and clean up past pipeline runs. Each run is a self-contained directory under `working/runs/` with its own working files, outputs, and pipeline state. ## When to Use - User says `/runs`, `/runs list`, `/runs latest`, `/runs clean`, or `/runs compare` - When the user wants to see what analyses have been executed ## Invocation - `/runs` or `/runs list` -- list all past runs - `/runs latest` -- show details of the most recent run - `/runs {id}`
testing146
.claude/skills/semantic-validation
# Skill: Semantic Validation ## Purpose Orchestrate the full 4-layer validation stack plus confidence scoring to produce a comprehensive data quality assessment for any analysis output. ## When to Use - After analysis agents produce findings (before Storytelling agent) - When the Validation agent runs its enhanced checks (Step 5a-5e) - When a user asks "how confident should I be in these results?" ## Invocation Applied automatically as part of the Validation agent workflow. Can also be invoke
testing146
.claude/skills/setup-dev-context
# /setup-dev-context — Developer Context Setup > Standalone skill for teams integrating AI Analyst into development workflows. > Most users (PMs, execs, DS) never need this — only teams doing codebase integration. ## Trigger Invoked as `/setup-dev-context` ## Purpose Collects codebase-specific context to help AI Analyst understand your development environment. This enables more accurate SQL generation, schema awareness, and integration with your existing data infrastructure. ## Prerequisites
development146
.claude/skills/stakeholder-communication
# Skill: Stakeholder Communication Matrix ## Purpose Adapt analytical findings to the audience — same insight, different framing, detail level, and format depending on who will read it. Ensures that executives get the bottom line, PMs get the implications, engineers get the specifics, and data teams get the methodology. ## When to Use Apply this skill when producing a narrative (Storytelling agent), creating a deck (Deck Creator agent), or whenever the user specifies an audience. If no audienc
development146
.claude/skills/switch-dataset
# Skill: Switch Dataset ## Purpose Change the active dataset. Updates the active pointer, validates the target dataset exists, and confirms with a summary of what's now active. ## When to Use Invoke as `/switch-dataset {name}` when the user wants to analyze a different dataset than the currently active one. ## Instructions ### Step 1: Validate the target dataset 1. Read `data_sources.yaml` to check if `{name}` exists as a registered source 2. If not found, try fuzzy matching (case-insensiti
testing146
.claude/skills/tracking-gaps
# Skill: Tracking Gap Identification ## Purpose Assess whether the data needed for an analysis actually exists, identify what's missing, and produce prioritized instrumentation requests for engineering when gaps are found. ## When to Use Apply this skill after the Data Explorer agent inventories available data, when an analysis requires data that might not exist, or when initial query results suggest incomplete tracking. Run before committing to an analysis approach. ## Instructions ### Gap
data-ai146
.claude/skills/triangulation
# Skill: Triangulation / Sanity Check ## Purpose Cross-reference analytical findings against multiple data sources, external benchmarks, and common sense to catch errors before they become bad decisions. ## When to Use Apply this skill after every analysis, before presenting findings to stakeholders, and whenever a result seems surprising. If a finding would change a decision, it MUST be triangulated first. ## Instructions ### Triangulation Framework Every finding gets checked through four
development146
.claude/skills/visualization-patterns
# Skill: Visualization Patterns ## Purpose Ensure every chart Claude Code produces follows high-quality design standards with named themes, consistent styling, and clear data communication. ## When to Use Apply this skill whenever generating a chart, graph, or data visualization. Always apply the active theme unless the user specifies otherwise. Default theme: `minimal`. ## Instructions ### Pre-flight: Load Learnings Before executing, check `.knowledge/learnings/index.md` for relevant entrie
development146
.claude/skills/setup
# Skill: /setup Run a 4-phase conversational interview that populates the knowledge system from the user's real context. Turns a blank `.knowledge/` directory into a fully configured analytical environment. ## Parameters - **No arguments**: Start from Phase 1 (or resume from last incomplete phase) - `/setup status`: Show current setup state - `/setup reset`: Reset profile and preferences (Tier 1) - `/setup reset everything`: Full reset including dataset connections (Tier 2) ## Trigger Phrase
data-ai146
.claude/skills/data-quality-check
# Skill: Data Quality Check ## Purpose Validate data completeness, consistency, and coverage before any analysis begins, flagging issues with severity ratings so the analyst knows what blocks analysis vs. what to note as a caveat. ## When to Use Apply this skill at the start of every new analysis, when connecting to a new data source, or when results look suspicious. Run quality checks BEFORE drawing conclusions from data. ## Instructions ### Check Sequence Run these checks in order. Stop a
testing146
.claude/skills/first-run-welcome
# Skill: First-Run Welcome ## Purpose Provide an adaptive welcome experience based on setup state. Routes new users through `/setup` for guided onboarding. Welcomes returning users with context about their active dataset and quick actions. ## When to Use - Session start (triggered by Knowledge Bootstrap) - Before any analysis work begins ## Instructions ### Step 1: Detect setup state Read `.knowledge/setup-state.yaml`. Classify into one of three states: 1. **Cold start** — file does not ex
documentation146
.claude/skills/forecast
# Skill: Forecast ## Purpose Generate time-series forecasts for key metrics using the forecast_helpers library. Supports naive baselines, seasonality detection, and exponential smoothing — enough to answer "what should we expect next?" without complex modeling. ## When to Use - User asks "what will revenue look like next month?" or "forecast DAU" - After trend analysis reveals a pattern worth projecting - When sizing an opportunity that depends on future values - Invoked as `/forecast` ## Inv
tools146
.claude/skills/question-framing
# Skill: Question Framing ## Purpose Structure analytical questions using the Question Ladder framework so every analysis starts with a clear decision context, measurable success criteria, and testable hypotheses. ## When to Use Apply this skill when starting any new analysis, when a user asks a vague question ("How are we doing?"), or when an analysis request lacks decision context. Always frame before analyzing. ## Instructions ### Pre-flight: Load Learnings Before executing, check `.knowl
development146
.claude/skills/archaeology
# Skill: Query Archaeology Retrieval ## Purpose Retrieve proven SQL patterns, table cheatsheets, and join patterns from the query archaeology store so agents reuse validated work instead of writing SQL from scratch. ## When to Use - **Automatically** before any analysis agent writes SQL (pre-flight step) - **Manually** when the user asks about known patterns for a table or join ## Instructions ### Step 1: Check the Index Read `.knowledge/query-archaeology/curated/index.yaml`. Parse counters
testing146
.claude/skills/knowledge-bootstrap
# Skill: Knowledge Bootstrap ## Purpose Initialize all 7 knowledge subsystems for a new session. Loads setup state, dataset, user profile, integrations, org context, corrections, learnings, query archaeology, and analysis archive into working memory. ## When to Use - At the start of any session - After `/connect-data` or `/switch-dataset` - When the system detects missing or stale knowledge files ## Instructions Load each subsystem in order. Every file read MUST gracefully degrade: if the fi
data-ai146
.claude/skills/metrics
# Skill: Metrics ## Purpose Browse, search, and display metric definitions from the active dataset's metric dictionary. Provides quick access to how metrics are defined, computed, and validated. ## When to Use - User says `/metrics` or "show me the metrics" or "what metrics do we track?" - During analysis, to confirm a metric's definition before computing it - When writing a metric spec, to check for existing definitions ## Invocation `/metrics` — list all metrics for the active dataset `/met
testing146
.claude/skills/analysis-design-spec
# Skill: Analysis Design Spec ## Purpose Ensure every analysis starts with a clear plan — what question it answers, what decision it informs, what data it needs, and what "done" looks like — before any queries are written or data is explored. ## When to Use Apply this skill at the start of every new analysis, before running the Data Explorer or any analysis agent. If a user asks you to analyze something, produce an Analysis Design Spec first. Skip only if the user provides a request that alrea
testing146
.claude/skills/data-inspect
# Skill: Data Inspect ## Purpose Show the active dataset's schema — tables, columns, row counts, and relationships. Optionally drill into a specific table. ## When to Use Invoke as `/data` to see the full schema summary, or `/data {table}` to see column details for a specific table. ## Instructions ### Mode 1: `/data` (full schema overview) 1. Read `.knowledge/active.yaml` to get the active dataset 2. Read `.knowledge/datasets/{active}/schema.md` 3. Display a condensed summary: ``` Active
testing146