Install
$ agentstack add skill-ulises-jeremias-agent-toolkit-dbt-validation ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
dbt validation (HOW)
Use when the repository is a dbt project or the task requires dbt verification. Client workflows may delegate here.
Boundaries
- Follow repo
AGENTS.md,Makefile,README, and CI—not generic guesses. - Do not change Snowflake security settings, network rules, or warehouse admin from this skill.
- If
dbtor credentials are missing, say so and do not claim validation passed.
Discovery
Look for dbt_project.yml, packages.yml, models/, Makefile, pyproject.toml, or CI jobs that invoke dbt.
Typical commands (examples only—prefer repo docs)
| Intent | Often used (verify in repo) | | --- | --- | | Syntax / graph | dbt parse, dbt compile | | Dependencies | dbt deps when packages change | | Tests | dbt test or subset flags the repo documents | | Build | dbt run / dbt build when the user approves mutating runs |
Makefile wrappers (e.g. make parse) take precedence when documented.
Evidence
- Summarize which commands ran and high-level outcome (pass/fail/skipped) for tickets and PRs.
- On failure, capture actionable error lines; do not dump full logs unless the user asks.
Safety
- Prefer read-only checks (
parse,compile,test) when the task is review-only. - Production runs require explicit user approval per repo policy.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: ulises-jeremias
- Source: ulises-jeremias/agent-toolkit
- License: MIT
- Homepage: https://ulises-jeremias.github.io/agent-toolkit-archive/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.