status

Check dbt manifest.json and run_results.json presence and age in target paths.

Updated Dec 29, 2025
One-click install
npx skills add https://github.com/yu-iskw/dbt-artifacts-parser-ts --skill status-yu-iskw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: status
Source: https://github.com/yu-iskw/dbt-artifacts-parser-ts/tree/main/plugins/dbt-tools-cli/skills/status
Command: npx skills add https://github.com/yu-iskw/dbt-artifacts-parser-ts --skill status-yu-iskw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Quickly determine whether dbt artifact files exist for a target directory and whether they are up to date, so you can decide if analysis can proceed.

Core Features & Use Cases

  • Check for the presence of manifest.json and run_results.json under a given target path.
  • Compute artifact age and freshness to determine readiness for analysis.
  • Provide a concise readiness signal to guide subsequent dbt tooling commands.

Quick Start

Run dbt-tools status --dbt-target ./target --json to receive a machine-readable snapshot of artifact presence and freshness.

Frequently Asked Questions about status

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if dbt artifact files like manifest.json are present and fresh?

To check dbt artifact freshness, the status command identifies whether manifest.json and run_results.json exist under a given target path and computes their age to signal readiness for analysis.

Can I check dbt artifacts readiness for remote storage prefixes like s3 or gs?

You can check dbt artifacts readiness for remote storage by applying the status command to s3:// or gs:// prefixes, evaluating the presence and age of manifest and run_results files without requiring a local directory.

Do I need dbt-tools installed to verify manifest and run_results freshness?

You need dbt-tools on your PATH to verify manifest and run_results freshness, along with a valid local target directory or remote storage prefix to evaluate artifact readiness successfully.

What is the best way to get a machine-readable snapshot of dbt artifact readiness?

The best way to get a machine-readable snapshot of dbt artifact readiness is running dbt-tools status with the --json flag, which outputs presence and freshness data for manifest and run_results files.

Why does my dbt analysis fail if target artifacts are outdated?

dbt analysis may fail or produce stale results if target artifacts are outdated, because downstream tooling relies on the current presence and freshness of manifest.json and run_results.json to process accurately.

When should I not use an automated status check for dbt artifacts?

You should not use an automated status check for dbt artifacts when dbt-tools is not on your PATH or when no valid local target directory or remote prefix exists, as the readiness evaluation requires these inputs.