- Adapter Skills Annotate ReferencesUse when annotating fs adapter implementations with upstream dbt-adapters Python reference links. Triggers whenever you need to add or audit GitHub permalink comments in adapter_impl.rs, trace an fs adapter method back to its Python origin in dbt-adapters, or when working on adapter divergence and want to know where a method came from. Also use when asked to "annotate references", "add upstream links", or "link adapter methods".dbt-labs/dbt13,984
- Adapters CriticUse in a reviewer agent in agent loops or when reviewing your own code.dbt-labs/dbt13,984
- Adapter Skills Annotate ReferencesUse when annotating fs adapter implementations with upstream dbt-adapters Python reference links. Triggers whenever you need to add or audit GitHub permalink comments in adapter_impl.rs, trace an fs adapter method back to its Python origin in dbt-adapters, or when working on adapter divergence and want to know where a method came from. Also use when asked to "annotate references", "add upstream links", or "link adapter methods".dbt-labs/dbt-core13,784
- Adapters CriticUse in a reviewer agent in agent loops or when reviewing your own code.dbt-labs/dbt-core13,784
- Adding Dbt Unit TestCreates unit test YAML definitions that mock upstream model inputs and validate expected outputs. Use when adding unit tests for a dbt model or practicing test-driven development (TDD) in dbt.dbt-labs/dbt-agent-skills727
- Answering Natural Language Questions With DbtWrites and executes SQL queries against the data warehouse using dbt's Semantic Layer or ad-hoc SQL to answer business questions. Use when a user asks about analytics, metrics, KPIs, or data (e.g., "What were total sales last quarter?", "Show me top customers by revenue"). NOT for validating, testing, or building dbt models during development.dbt-labs/dbt-agent-skills727
- Auditing SkillsUse when checking skills for security or quality issues, reviewing audit results from skills.sh or Tessl, or remediating findings across published skills.dbt-labs/dbt-agent-skills727
- Building Dbt Semantic LayerUse when creating or modifying dbt Semantic Layer components — semantic models, metrics, dimensions, entities, measures, or time spines. Covers MetricFlow configuration, metric types (simple, derived, cumulative, ratio, conversion), and validation for both latest and legacy YAML specs.dbt-labs/dbt-agent-skills727
- Configuring Dbt Mcp ServerGenerates MCP server configuration JSON, resolves authentication setup, and validates server connectivity for dbt. Use when setting up, configuring, or troubleshooting the dbt MCP server for AI tools like Claude Desktop, Claude Code, Cursor, or VS Code.dbt-labs/dbt-agent-skills727
- Creating Mermaid Dbt DagGenerates a Mermaid flowchart diagram of dbt model lineage using MCP tools, manifest.json, or direct code parsing as fallbacks. Use when visualizing dbt model lineage and dependencies as a Mermaid diagram in markdown format.dbt-labs/dbt-agent-skills727
- Fetching Dbt DocsRetrieves and searches dbt documentation pages in LLM-friendly markdown format. Use when fetching dbt documentation, looking up dbt features, or answering questions about dbt Cloud, dbt Core, or the dbt Semantic Layer.dbt-labs/dbt-agent-skills727
- Maintaining Dbt DocumentationAudits dbt documentation coverage and drafts missing model/column descriptions in the project's own house style, one folder at a time, for human review. Use when documenting undocumented models, backfilling missing YAML descriptions, auditing doc coverage, or keeping schema YAML in sync with model SQL — especially on multi-contributor projects where new models routinely land undocumented.dbt-labs/dbt-agent-skills727
- Migrating Dbt Core To V2Use when a user needs help triaging dbt-core to dbt v2 migration errors. Runs dbt-autofix first, then classifies remaining errors into actionable categories (auto-fixable, guided fixes, needs input, blocked).dbt-labs/dbt-agent-skills727
- Migrating Dbt Project Across PlatformsUse when migrating a dbt project from one data platform or data warehouse to another (e.g., Snowflake to Databricks, Databricks to Snowflake) using dbt Fusion's real-time compilation to identify and fix SQL dialect differences.dbt-labs/dbt-agent-skills727
- Running Dbt CommandsFormats and executes dbt CLI commands, selects the correct dbt executable, and structures command parameters. Use when running models, tests, builds, compiles, or show queries via dbt CLI. Use when unsure which dbt executable to use or how to format command parameters.dbt-labs/dbt-agent-skills727
- Troubleshooting Dbt Job ErrorsDiagnoses dbt Cloud/platform job failures by analyzing run logs, querying the Admin API, reviewing git history, and investigating data issues. Use when a dbt Cloud/platform job fails and you need to diagnose the root cause, especially when error messages are unclear or when intermittent failures occur. Do not use for local dbt development errors.dbt-labs/dbt-agent-skills727
- Upgrading DbtUse when a user wants to upgrade, update, or migrate a dbt project to the latest version — e.g. "upgrade my dbt project," "migrate this off dbt 1.5," "get this project running on the latest dbt," "bump the dbt version." Upgrades a dbt v1 project (on 1.3, 1.4, 1.5, 1.6, or 1.7) all the way to 1.12, applying the required breaking, behavior, and deprecated changes from a data-driven issue corpus. Inputs — starting_version (the project's current dbt minor, one of 1.3/1.4/1.5/1.6/1.7) and adapter_typdbt-labs/dbt-agent-skills727
- Using Dbt For Analytics EngineeringBuilds and modifies dbt models, writes SQL transformations using ref() and source(), creates tests, and validates results with dbt show. Use when doing any dbt work - building or modifying models, debugging errors, exploring unfamiliar data sources, writing tests, or evaluating impact of changes.dbt-labs/dbt-agent-skills727
- Using Dbt StateUse when a user is enabling, configuring, optimizing, or debugging dbt State (the server-backed reuse mechanism that clones or skips nodes instead of rebuilding them). Use when they conflate dbt State with the `state:modified` selector or `--state` deferral. Use when asked about models rebuilding unexpectedly, views with `select *` rebuilding, volatile SQL (`current_timestamp()`, `random()`) rebuilding or not, cross-developer cloning, lag_tolerance.dbt-labs/dbt-agent-skills727
- Working With Dbt MeshUse when changing a dbt model in a way that could break its consumers — renaming, removing, or retyping a column, or changing a model that downstream models, exposures, dashboards, or BI tools depend on — to judge whether the change is breaking and who it affects. Also use when versioning a model (model versions, latest_version, latest_version_pointer, deprecation_date, migration windows), enforcing contracts, setting access or groups, or doing multi-project dbt Mesh work (cross-project refs viadbt-labs/dbt-agent-skills727
- Release Dbt McpRelease a new version of dbt-mcp to PyPidbt-labs/dbt-mcp607
- Analyst RunbookThe analyst process wrapped around anything you build: triage the request, reuse existing work, pick the response shape, verify the answer, then deliver it with a written read — observations plus where to look next. Use at the start of an analytical request ("show me…", "why did X change") and again when handing the work back. Not for chart-type or layout decisions (use {{ s_skill_name_design_board }}).dbt-labs/dbt-charts546
- Before After ComparisonPattern for placing two metric series on the same axis to compare baseline vs current, plan vs actual, or A vs B. Use when the question is "how does current compare to baseline?" for the same set of categories or time periods. Triggers on: 'compare', 'baseline vs current', 'plan vs actual', 'before after', 'A/B', 'target vs actual', 'layered bars'. Both series share the same x-axis encoding. Do NOT use for time-series trend (use time-series-trend). Do NOT use for more than 3 series (chart becomedbt-labs/dbt-charts546
- Board BuildBuild-test-iterate workflow for dbt charts boards and reports: edit board YAML, add charts, write parameterized queries, duplicate an existing board. Use for 'build a dashboard', 'add a chart', 'duplicate this dashboard'. Do NOT use for errors after something breaks ({{ s_skill_name_troubleshooting }}) or for chart-type and layout choices ({{ s_skill_name_design_board }}).dbt-labs/dbt-charts546
- Board DesignDesign principles for at-a-glance dbt charts boards: chart selection, information hierarchy, layout, color, dashboard vs report. Use for 'what chart type', 'how should I lay this out', 'dashboard design'. Do NOT use for narrative analyses ({{ s_skill_name_design_report }}) or the build-test-iterate cycle ({{ s_skill_name_build }}).dbt-labs/dbt-charts546
- Board Pack ScaffoldingExperimental internal workflow for evaluating multi-dashboard scaffolding: propose a folder structure, review with the user, then apply through the Python agent API. Use only when explicitly evaluating pack-level scaffolding for a data source or project. Do NOT use for a single-dashboard request (use {{ s_skill_name_build }}). Do NOT use for normal CLI guidance, chart edits, or bug fixes in one board file.dbt-labs/dbt-charts546
- Board ReplicateReproduce a dashboard the user supplies as a screenshot, image, or export — its structure and data, in dbt charts' own styling. Use for 'replicate', 'recreate', 'rebuild this in dbt charts', 'migrate from Looker', or when an image of a dashboard is attached. Do NOT use for building from scratch, or for copying a board already in this project ({{ s_skill_name_build }}).dbt-labs/dbt-charts546
- Board ReviewEntry point for reviewing a board: runs the structural pass, adds the visual pass when needed, and merges both into one ranked findings list. Use for 'review this dashboard', 'is this dashboard good', or before delivering a board you just built. Do NOT use when one pass is enough — invoke {{ s_skill_structural_review }} or {{ s_skill_visual_review }} directly.dbt-labs/dbt-charts546
- Board Structural ReviewReview a dbt charts board's YAML structure and content choices without rendering. Reads the board file, runs schema validation, then evaluates the YAML against a design checklist (chart-data shape match, layout intent, variable wiring, descriptive naming, anti-patterns). Use when asked to 'review this dashboard', 'check this board', 'is this YAML well-shaped', 'find problems in this dashboard', or after editing a board before delivery. Cheap — no rendering, no PNG, no LLM judge in the loop. Do Ndbt-labs/dbt-charts546
- Board Visual ReviewRender a dbt charts board to PNG and review the image against a visual-design checklist using vision. Catches problems YAML inspection can't see — overlapping text, contrast failures, axis-label collisions, whitespace imbalance, KPI precision mismatches. Use when asked to 'visually review', 'check how it looks', 'is this rendered correctly', 'review the rendered output', or when structural review surfaces ambiguous 'feels off but I can't say why' findings. More expensive than structural review (dbt-labs/dbt-charts546
- Cloud SetupSet up a fresh dbt charts Cloud org end to end from the terminal: authenticate, connect a project, wire a warehouse connection, map sources, and render — driven by `dct cloud status` until it reports done. Use when the user says 'set me up with dbt charts cloud', 'deploy my dashboards to cloud', 'connect this repo to dbtcharts.com', or 'get my boards live'. Do NOT use for authoring boards (use {{ s_skill_name_build }}) or for deleting/removing an org, project, or connection — this skill never rudbt-labs/dbt-charts546
- Data ExplorationExplore available sources, schemas, tables, columns, relationships, and data shape before writing dashboard YAML or answering analyst questions. Use when the user asks what data exists, where to find a metric/dimension, how tables relate, or which columns are available. Do NOT use for dashboard design decisions (use {{ s_skill_name_design_board }}) or error diagnosis after a failed render (use {{ s_skill_name_troubleshooting }}).dbt-labs/dbt-charts546
- Drill Down LinkPattern for cross-board navigation: a chart or table whose elements link to a detail board, passing a row value as a URL path segment or query parameter. Use when users need to click from a summary view into a per-item detail board. Triggers on: 'drill down', 'click through', 'detail page', 'per-item board', 'link to detail', 'cross-board navigation'. Do NOT use for filtering within the same board (use filter-bar-with-variables). Do NOT use for tabs within a single board (use the tabs layout).dbt-labs/dbt-charts546
- Faceted Small MultiplesPattern for showing the same metric sliced by a categorical dimension — either as one multi-series chart (color encoding) or as N side-by-side charts (manual small multiples). Use when comparing a trend or distribution across segments. Triggers on: 'by segment', 'by region', 'by category', 'small multiples', 'faceted', 'breakdown', 'compare across groups', 'stacked area'. Use color encoding for ≤5 segments in one chart; use manual multiples when segments need separate y-scales or spatial separatdbt-labs/dbt-charts546
- Filter Bar With VariablesPattern for interactive dashboards with dropdown/date/numeric filter controls wired into queries via Jinja variable substitution. Use when users need to slice data by dimension, date range, or threshold without editing YAML. Triggers on: 'filter', 'dropdown', 'date range', 'interactive', 'variable', 'select', 'picker', 'parameterized'. Variables render as UI controls above the charts. Do NOT use for drill-through navigation between boards (use drill-down-link). Do NOT use when all data fits on odbt-labs/dbt-charts546
- IntroStart here. What dbt Charts is, how to set up a project, and everything needed to write a typical board: its shape, its fields, the format names, and how to check a render without pictures. Use when asked to 'make charts of this with dbt charts' or 'use dbt charts', before any other skill. Do NOT use once you know the tool.dbt-labs/dbt-charts546
- Kpi RowPattern for a row of 3–5 KPI cards at the top of a board. Use when showing summary metrics (revenue, orders, conversion rate, avg order value) from a single aggregated query. Triggers on: 'KPI row', 'summary metrics', 'top metrics', 'hero numbers', 'scorecard'. Each KPI needs a separate single-row query OR one query with multiple columns. Do NOT use for time-series trends (use time-series-trend). Do NOT use for a single hero metric (use single-metric-bignum). Do NOT use if the data has more thandbt-labs/dbt-charts546
- Mcp SetupSet up the dbt charts MCP server for AI assistant integration. Use when running 'dct init mcp', installing dbt charts, configuring MCP for Cursor, Claude Desktop, VS Code, Codex, Copilot, or any MCP-compatible client, or troubleshooting MCP connection issues like 'server not starting', 'tools not appearing', 'MCP requires additional dependencies'. Do NOT use for building dashboards (use {{ s_skill_name_build }}). Do NOT use for dashboard errors (use {{ s_skill_name_troubleshooting }}).dbt-labs/dbt-charts546
- Report DesignDesign principles for dbt charts narrative reports — data-driven documents that answer specific questions. Use when creating analyses, investigations, periodic reports, or when the user says 'write a report', 'analyze this data', 'create an analysis', 'narrative report'. Covers narrative structure, chart selection for reports, content writing, and the executive-summary-first pattern. Do NOT use for at-a-glance monitoring dashboards (use {{ s_skill_name_design_board }}). Do NOT use for the build-dbt-labs/dbt-charts546
- Single Metric BignumPattern for a single hero KPI displayed at large scale with a prior-period delta in the support row. Use when one metric is the primary signal of the board and should visually dominate. Triggers on: 'hero metric', 'big number', 'single KPI', 'headline metric', 'north star', 'key metric', 'monthly recurring revenue', 'MRR'. Optionally add a sparkline for trend context. Do NOT use for three or more metrics (use kpi-row). Do NOT use when the chart type is more important than the number (use time-sedbt-labs/dbt-charts546
- Table Heavy Ops DashboardPattern for operational dashboards dominated by sortable tables with per-column formatting, labels, and conditional formatting. Use when users need to monitor status, triage incidents, or review row-level data with currency/percent/date formatting and visual severity cues. Triggers on: 'ops dashboard', 'incident table', 'ticket queue', 'status monitor', 'formatted table', 'sortable list', 'operational view'. Do NOT use when a chart communicates the pattern better (use top-n-with-detail for rankidbt-labs/dbt-charts546
- Time Series TrendPattern for a line (or area) chart tracking one or more numeric metrics over time. Use when the question is "how has X changed over time?" with a date dimension on x. Triggers on: 'trend', 'over time', 'time series', 'daily', 'weekly', 'monthly', 'historical'. Add a date-range variable to make it interactive. Do NOT use for category comparisons without a time axis (use top-n-with-detail or before-after-comparison). Do NOT use for composition over time (use faceted-small-multiples with area type)dbt-labs/dbt-charts546
- Top N With DetailPattern pairing a top-N bar chart with a detail table on the same query. Use when the question is "which are the top performers?" and the user also needs row-level detail. Triggers on: 'top N', 'top products', 'best customers', 'ranked list', 'leaderboard', 'ranked + detail'. The bar chart gives the ranking at a glance; the table provides drill-in context. Do NOT use when there is no natural ranking (use two-by-two-grid-overview). Do NOT use when detail is not needed (a plain bar chart suffices)dbt-labs/dbt-charts546
- TroubleshootingDiagnose and fix dbt charts dashboard errors. Use when validation, query execution, query inspection, or dashboard rendering returns an error, when a dashboard renders but looks wrong, when SQL fails, when YAML won't validate, or when the user says 'fix this error', 'debug this dashboard', 'why is this broken', 'chart shows no data'. Covers YAML validation failures, SQL execution errors, rendering issues, and variable misconfiguration. Do NOT use for building new dashboards from scratch (use {{ dbt-labs/dbt-charts546
- Two By Two Grid OverviewPattern for a 2×2 (or 2×3) grid of equally-weighted summary charts giving a balanced multi-metric overview. Use when four to six metrics are equally important and no single chart dominates. Triggers on: '2x2', 'grid overview', 'equal weight', 'four charts', 'overview dashboard', 'balanced layout', 'summary grid'. Each cell carries the same visual weight — no chart is emphasized over another. Do NOT use when one chart is the hero (use single-metric-bignum or put it in a wider column). Do NOT use dbt-labs/dbt-charts546
- Add Availability BadgeAdd or resolve an `availability` frontmatter field for a docs.getdbt.com page, so the page renders the correct applicability badge (where a feature runs, what plan/access it needs, which dbt engine version). Use when asked to add an availability badge, mark a page as platform/local/Enterprise-only, or figure out what availability value a feature needs.dbt-labs/docs.getdbt.com218
- CavecrewDecision guide for delegating to caveman-style subagents. Tells the main thread WHEN to spawn `cavecrew-investigator` (locate code), `cavecrew-builder` (1-2 file edit), or `cavecrew-reviewer` (diff review) instead of doing the work inline or using vanilla `Explore`. Subagent output is caveman-compressed so the tool-result injected back into main context is ~60% smaller — main context lasts longer across long sessions. Trigger: "delegate to subagent", "use cavecrew", "spawn investigator/builder/rdbt-labs/docs.getdbt.com218
- CavemanUltra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.dbt-labs/docs.getdbt.com218
- Caveman CommitUltra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit. Auto-triggers when staging changes.dbt-labs/docs.getdbt.com218
- Caveman CompressCompress natural language memory files (CLAUDE.md, todos, preferences) into caveman format to save input tokens. Preserves all technical substance, code, URLs, and structure. Compressed version overwrites the original file. Human-readable backup saved as FILE.original.md. Trigger: /caveman-compress FILEPATH or "compress memory file"dbt-labs/docs.getdbt.com218
- Caveman HelpQuick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".dbt-labs/docs.getdbt.com218
- Caveman ReviewUltra-compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix. Use when user says "review this PR", "code review", "review the diff", "/review", or invokes /caveman-review. Auto-triggers when reviewing pull requests.dbt-labs/docs.getdbt.com218
- Caveman StatsShow real token usage and estimated savings for the current session. Reads directly from the Claude Code session log — no AI estimation. Triggers on /caveman-stats. Output is injected by the mode-tracker hook; the model itself does not compute the numbers.dbt-labs/docs.getdbt.com218
- Converting Notion To Docusaurus BlogUse when converting a Notion markdown export to a Docusaurus blog post for the dbt docs site, or when given a path to a Notion export folder/file.dbt-labs/docs.getdbt.com218
- Create Docs SkeletonScaffold a new skeleton markdown doc for docs.getdbt.com — standard guide, reference page, feature/product page, or release note entry. Use when asked to create a new doc page, scaffold a doc, start a new page, or add a page to the sidebar.dbt-labs/docs.getdbt.com218
- Docs Issue TriageUse this skill to triage, score, and label GitHub issues in the docs.getdbt.com repo. Triggers when the user asks to triage issues, rank issues by priority or size, label GitHub issues, review the issue backlog, or score open docs issues. Also use this skill when the user says things like "what should we work on next", "rank our issues", "apply priority labels", "apply size labels", or "what are our highest priority issues". Always use this skill for any request involving prioritizing or sizing dbt-labs/docs.getdbt.com218
- Docs Issue TriageUse this skill to triage, score, and label GitHub issues in the docs.getdbt.com repo. Triggers when the user asks to triage issues, rank issues by priority or size, label GitHub issues, review the issue backlog, or score open docs issues. Also use this skill when the user says things like "what should we work on next", "rank our issues", "apply priority labels", "apply size labels", or "what are our highest priority issues". Always use this skill for any request involving prioritizing or sizing dbt-labs/docs.getdbt.com218
- Product Term RenameRename dbt product terms across docs.getdbt.com per the finalized naming convention — Fusion/dbt Fusion engine to "dbt v2", dbt Core to "dbt v1", and genuinely product-agnostic uses to "dbt". Use when asked to run the product rename, flip Fusion terminology, apply the v1/v2 naming, or execute the Product Rename Strategy. Handles the constants flip, specific-vs-generic audit, grammar repair, scoped prose edits, raw-string sweep, and verification gates; excludes blogs and release notes, includes udbt-labs/docs.getdbt.com218
- Ade Bench Cross Db TasksUse when authoring or debugging ade-bench tasks that must run on both DuckDB and Snowflake, including shared project migrations, setup patches, and solution patchesdbt-labs/ade-bench125
- Bug FixerSpecialized skill for diagnosing and fixing software defects in the repository.dbt-labs/terraform-provider-dbtcloud117