pre-flight

Validate pipeline readiness before tar_make() with pre-flight checks.

1|1|Updated Nov 20, 2025
One-click install
npx skills add https://github.com/estebandegetau/Fiscal-shocks --skill pre-flight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pre-flight
Source: https://github.com/estebandegetau/Fiscal-shocks/tree/main/.claude/skills/pre-flight
Command: npx skills add https://github.com/estebandegetau/Fiscal-shocks --skill pre-flight

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates pipeline readiness by performing a pre-flight validation before tar_make(), preventing wasted runs and API usage.

Core Features & Use Cases

  • Readiness checks that catch configuration errors, dirty git state, and stale dependencies before a pipeline run.
  • Upfront validation for targets, manifests, and credentials to avoid costly failures.
  • Clear pass/fail guidance with actionable remediation steps to keep the project healthy.

Quick Start

Invoke the pre-flight checks before tar_make() to verify readiness without executing the pipeline.

Frequently Asked Questions about pre-flight

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

FAQPage Schema
How do I validate pipeline readiness before running tar_make()?

To validate pipeline readiness before running tar_make(), invoke pre-flight checks to catch configuration errors, dirty git state, and stale dependencies without modifying files. It provides clear pass or fail guidance with actionable remediation steps to keep your project healthy.

What is pre-flight validation for API-calling pipeline targets?

Pre-flight validation is a read-only readiness check for API-calling targets across C1–C4 pipelines. It verifies target existence in the manifest, upstream dependency freshness, codebook validity, and provider credentials to prevent wasted runs and API usage before execution.

How do I check for missing API keys and stale dependencies before a pipeline run?

Checking for missing API keys and stale dependencies before a pipeline run requires upfront validation of environment variables and repository state. Pre-flight checks scan provider credentials and upstream dependencies, delivering actionable remediation steps for any detected configuration issues.

Does the pre-flight validation modify repository files during checks?

Pre-flight validation does not modify repository files during checks. It requires only read-only access to the repository state and environment variables to assess manifest targets, dirty git state, codebook validity, and provider credentials without altering your project.

Why does my pipeline fail due to configuration issues before execution?

Pipeline execution fails due to configuration issues when dirty git state, missing codebooks, or missing API keys go unchecked. Running a pre-flight readiness check catches these errors upfront, providing actionable remediation steps to resolve them before you run tar_make().