dbt
Use when you need to run dbt commands against Snowflake -- build, test, compile, or full-refresh.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-15
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- dbt
- requires
- [ { "cli": "dbt", "reason": "dbt CLI for model builds, tests, and compilation" } ]
- description
- Use when you need to run dbt commands against Snowflake -- build, test, compile, or full-refresh.
- argument-hint
- [dbt command or model name]
- user-invocable
- true
03 SKILL.md 正文
dbt Command Runner
Codex: Read
../_shared/codex-tools.mdbefore following this skill. Apply its tool, root and dispatch mappings throughout.
Quick dbt operations.
Authentication
dbt typically needs Snowflake credentials available in the shell before any command runs. Most projects use one of:
- A
.envfile: never source it. Hand the variables to the one dbt command that needs them:python3 -B "<claudna-root>/scripts/env_from_file.py" .env SNOWFLAKE_ACCOUNT SNOWFLAKE_USER SNOWFLAKE_PASSWORD -- dbt <verb> ...(<claudna-root>per../_shared/claudna-root.md). Use whichever names the project'sprofiles.ymlreads withenv_var(). - A project-specific auth helper that exports
SNOWFLAKE_*vars: ask the user to run it in the shell the session starts from; do not source it yourself. - Direct env vars exported in
~/.zshrc/~/.bashrc
If the project's CLAUDE.md documents an auth helper, use that. Otherwise ask the user how their dbt profile expects to authenticate.
Quick Commands
Build a model:
dbt build --select model_name
Run with upstream deps:
dbt build --select +model_name
Test only:
dbt test --select model_name
Compile (no run):
dbt compile --select model_name
Full refresh (for incremental):
dbt run --select model_name --full-refresh
Instructions
When user asks about dbt:
- Confirm they're in the dbt project directory
- Confirm Snowflake auth is loaded (check the project's auth helper or
.env); see "Authentication" above - Run the appropriate command
- Report results and any test failures
04 同仓库更多 Skills
example-review
Use when you want to review pull requests with detailed, actionable feedback on code quality, correctness, and maintainability.
bad-skill
Too short
worktree
Use when starting feature work that needs isolation from the current workspace, or when running multiple Claude sessions in parallel on different branches — creates and manages git worktrees. For fetching latest main into every existing worktree and branch across your sibling repos, use /claudna:sync-branches instead.
weigh-development-paths
Use when at a development junction with multiple viable approaches — architecture choices, refactoring strategies, where to put new code, or which pattern to follow. Triggers on 'which approach', 'how should I', 'Option A vs B', or any point where the next step isn't obvious and the wrong choice creates rework.
verify-completion
Use when about to claim work is complete, fixed, or passing -- requires running verification commands and confirming output before making any success claims.
vercel
Use for Vercel operations — deploy to production or preview (or roll back), view, filter, or debug deployment logs, or check project status (deployments, domains, env vars, config). Replaces /vercel-deploy, /vercel-logs, /vercel-status.