pre-flight-check

Validate MCP configurations, API connectivity, and tool readiness before production.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/jlenrique/course-DEV-IDE-with-AGENTS --skill pre-flight-check-jlenrique
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pre-flight-check
Source: https://github.com/jlenrique/course-DEV-IDE-with-AGENTS/tree/main/skills/pre-flight-check
Command: npx skills add https://github.com/jlenrique/course-DEV-IDE-with-AGENTS --skill pre-flight-check-jlenrique

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Validates MCP configurations, API authentication, tool availability, and orchestrates a consolidated readiness report to ensure production runs start with a healthy tool ecosystem.

Core Features & Use Cases

  • Verifies MCP config presence across vertices and ensures API heartbeat connectivity before production.
  • Executes targeted checks (Notion, Box Drive, and blocker reporting) and aggregates results into a four-tier readiness classification with actionable guidance.
  • Supports optional smoke tests and static classifications for tools without programmatic access to maintain readiness posture in production pipelines.

Quick Start

Run the pre-flight check to generate a structured readiness report for all integrated tools.

Frequently Asked Questions about pre-flight-check

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

FAQPage Schema
How do I verify API connectivity and MCP configurations before a production run?

Pre-flight checks validate MCP configurations and API heartbeats before production by executing deterministic config checks and smoke tests, aggregating results into a four-tier readiness classification with actionable guidance for any detected blockers.

What is a pre-flight check for environment changes and tool readiness?

A pre-flight check for tool readiness validates MCP configurations, API authentication, and tool availability after environment changes, outputting a consolidated readiness report to ensure production runs start with a healthy tool ecosystem.

How do I run smoke tests and validate Notion and Box Drive integrations?

Pre-flight checks validate Notion and Box Drive integrations by executing targeted checks and smoke tests, aggregating results into a four-tier readiness classification with actionable resolution guidance for any detected blockers.

Can I automate tool readiness checks for tools without programmatic access?

Yes, you can automate readiness checks for tools without programmatic access by applying optional static classifications during the pre-flight check, maintaining a readiness posture within your production pipelines.

Does pre-flight check work without external dependencies?

Yes, the pre-flight check works without external dependencies, using internal scripts and references to perform deterministic MCP config checks, API heartbeats, and static classifications for a consolidated readiness report.