Freshness Check

When to Use

Use this skill when data is stale, a scheduled run is missing, or freshness checks fail.

Inputs

• Affected pipeline, asset, or freshness check.
• Expected schedule or freshness threshold.
• Last successful run time, if known.

Operating Context

• These starter skills can be used by Bruin Cloud agents, local agents, and external assistants connected to Bruin Cloud.
• In Bruin Cloud, use Cloud CLI access when the agent has it enabled. Use the bruin cloud CLI when the assistant has shell access and a configured API key or .bruin.yml; use Bruin Cloud MCP only when the assistant is configured for MCP tool calls or does not have direct CLI access. If using the CLI, list recent runs with bruin cloud runs list --project-id <project-id> --pipeline <pipeline-name>, diagnose the latest run with bruin cloud runs diagnose --project-id <project-id> --pipeline <pipeline-name> --latest, and inspect failed logs with bruin cloud instances failed-logs --project-id <project-id> --run-id <run-id>.
• In local development, inspect terminal output and the local logs/ folder, especially logs/runs, query logs, and export logs when they exist. Create local runs with bruin run <path> and explicit dates when needed.
• If investigation or fix verification requires running an asset or pipeline, prefer a dev or shadow environment. If none exists, ask whether to run in production or create temporary copies of the affected tables to reproduce and test the issue.
• For other agent runtimes or orchestrators, customize this skill with the correct scheduler, log source, and run trigger mechanism before using it.