From Harness Data
dbt-core conventions — contract-first models with contract.enforced true, mandatory unit tests, a semantic layer as the single metric source of truth, the dbt remote MCP as the governed agent surface, and auto-activating dbt-agent-skills. Use when building dbt models, contracts, unit tests, or semantic-layer metrics, or wiring the dbt MCP.
How this skill is triggered — by the user, by Claude, or both
Slash command
/harness-data:addon-dbt-coreThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- **Contract-first.** Every staging+ model declares
contract.enforced: true with explicit column types. The
contract-author agent writes the contract before the model body.dbt-build-model skill scaffolds them.semantic-modeler agent owns the manifest; no metric defined twice.This addon's dbt Cloud MCP carries a secret token, so it is not
auto-started by the plugin. Add it to your project's .mcp.json only when
you want governed dbt project access, then set DBT_CLOUD_TOKEN in your
environment (via env injection — never embed the token in the config):
{
"mcpServers": {
"dbt": {
"type": "http",
"url": "https://cloud.getdbt.com/mcp",
"headers": { "Authorization": "Bearer ${DBT_CLOUD_TOKEN}" }
}
}
}
npx claudepluginhub camilool8/harness-engineering-templates --plugin harness-dataGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
Dispatches multiple subagents concurrently for independent tasks without shared state. Use when facing 2+ unrelated failures or subsystems that can be investigated in parallel.