Skip to content

dct skills

List packaged agent skills, or show one by name. Skills are the AI-facing knowledge packs that ship with dbt Charts, each one teaches an AI assistant a specific authoring task (for example, chart, styling, custom-chart-build).

dct skills [OPTIONS] [NAME]

Arguments

Argument Description
NAME Skill name to show. Omit to list all skills.

Options

Flag Description
--json Output as JSON.

Examples

dct skills                  # List every packaged skill
dct skills chart            # Show the chart skill body (markdown)
dct skills chart --json     # Same skill, JSON-shaped

A skill's name differs by surface: dbtcharts.com's chat invokes it bare (/chart), while a file-installed local skill reads dct-chart. The registry name (what dct skills <name> and MCP get_skill take) is always bare, on every surface; the dct- prefix exists only in the file-installed directory name and frontmatter, produced once by dct init skills.

How skills are used

  • Orientation. dct skills chart is the one to read first: the board and chart grammar and the build-render-fix loop. It is the skill the one-line agent hand-off on dbtcharts.com points at.
  • File install (recommended). dct init skills copies CLI-rendered skills to your agent skill directories, each one namespaced under a dct- prefix (dct-chart/, dct-styling/, ...) so they never collide with a skill your project or another tool already installed. Gitignore ours with .agents/skills/dct-*/, or the same dct-*/ pattern under the Claude Code skills directory, without touching anyone else's. dct init skills always overwrites an existing install, so after pip install -U dbt-charts, re-run it to pick up new or updated skills.
  • MCP server. dct mcp serve exposes skills as tools that AI agents can call.
  • Zero-install fallback. dct skills <name> prints a skill body without file install; useful in CI or when you only need to read the content.
  • Reading a pattern. A pattern skill's body includes its YAML, which dct skills <name> prints for you to copy.