Skip to content
Skills Library
DevOps & cloud · Review & audit

preflight

/preflight

Use when checking whether the current execution environment is ready for a project's development work, including missing tools, incompatible versions, and setup blockers.

Repository
skills ↗
Licence
MIT
Last repository change
12.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when checking whether the current execution environment is ready for a project's development work, including missing tools, incompatible versions, and setup blockers.

Original author description

Use when checking whether the current execution environment is ready for a project's development work, including missing tools, incompatible versions, and setup blockers.

How it works

  1. Identify what the project needs
  2. Inspect and compare
  3. Resolve blockers with the human
Original SKILL.md headings · 26 lines, 571 words
SKILL.md preview
---
name: preflight
description: "Use when checking whether the current execution environment is ready for a project's development work, including missing tools, incompatible versions, and setup blockers."
---

# Preflight

Determine whether the environment where the agent will actually work can support the requested project work. Base the assessment on the project's requirements and observed environment; do not change the environment during inspection.

## Identify what the project needs

1. Identify the project, the requested work, and where commands will run: the local device, a container, remote machine, or another available execution environment. State when the agent cannot inspect the relevant environment.
2. Read the relevant setup documentation, project instructions, manifests, lockfiles, version pins, configuration, and existing development or CI commands. Identify the tools, runtimes, versions and services required for the requested work, as well as optional components. Respect the project's existing setup and conventions. If a requirement is unclear or sources conflict, report the uncertainty instead of inventing a requirement.

## Inspect and compare

3. Use focused, read-only checks appropriate to the operating system and execution environment. Identify the active executable or service, its version and availability, and compare them with the project's stated requirements. Check the capabilities relevant to this work rather than collecting an unrelated inventory. Avoid exposing credentials, secrets, or unnecessary personal data.
4. Classify each material requirement as **ready**, **missing**, **incompatible**, or **unknown**, and distinguish required components from optional ones. A command that cannot be inspected or executed is not necessarily absent; describe the observed failure and limits. Report the project evidence and actual observations supporting each blocker. Do not claim readiness when a required capability remains unknown.

## Resolve blockers with the human

Return environment evidence to [Deploy](../deploy/SKILL.md) for rollout, [Migrate](../migrate/SKILL.md) for state changes, or [Operate](../operate/SKILL.md) for service health. Readiness is a prerequisite; it does not prove deployment, migration, capture or recovery succeeded.

5. For a missing required component, propose a specific installation that fits the project and current platform. For a breaking mismatch, explain the expected and observed setup, its impact, and a concrete project-compatible fix. Describe the relevant command or changes, scope and meaningful effects so the human can review the proposal. If more than one valid approach exists, show the tradeoff and recommendation. Ask for confirmation before any installation or environment change, unless the human has already explicitly authorized that specific action.
6. When a required component is missing, incompatible or cannot be verified, stop work that depends on it. Present the proposed fix before proceeding with the affected project work. Continue independent read-only investigation where useful, and do not call a proposed fix complete until it has actually been applied and checked.
7. If a preferred or project-required tool is unavailable, do not silently substitute an inferior method. An alternative is inferior when it reduces required capability, correctness, reliability, security, project fidelity or verification coverage for the task. Explain what the alternative would change and ask for explicit confirmation before using it. If its quality relative to the required method is unclear, explain that uncertainty and ask before substituting. Earlier explicit authorization for that specific alternative remains valid.
8. After an approved change, recheck the affected requirement and report the actual result. Return readiness evidence and blockers to the person or workflow responsible for the affected work. A proposal does not authorize an environment change.

**Done:** Report a concise readiness assessment, evidence for material findings, the effects and approval needed for each proposed fix or inferior fallback, and any remaining unknowns. The affected work remains blocked until its requirements are met or the human explicitly accepts an identified alternative.
Files in this package (2)
  • SKILL.md 4 KB
  • agents/openai.yaml 1 KB

Versions

RepositoryScoreLicence
This page · nazmirket/skills90MIT
andreibesleaga/gabbe100CC-BY-4.0
pathmodeio/claude-plugin100MIT
aradmanamnaoon/agent-guardrails100MIT
mo-cmyk/mazarbul100Apache-2.0
thilak15/preflight100MIT
manpreet171/slopguard100MIT
rune-kit/rune100MIT
pandysp/claude-plugins90MIT

Database snapshot: 13.11.2026 · package version d79a3d9676e8 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 95cdf-orchestration-preflight
    Set up missing Linux prerequisites and audit whether a Cosmos Data Factory (CDF) Orchestration checkout and its Kubernetes or OSMO environment are ready to install the controller and run every packaged DAG. Use for prerequisite, pre-setup, Kubernetes, GPU, RWX/NFS, credential,…
  • 86environment-intelligence
    Discover and reuse the current machine’s tools, runtime, hardware, network capabilities and dependencies; acquire missing trusted tools when needed rather than compromising the technical route. Use when environmental constraints, setup, downloads or tool selection affect a task.
  • 100setup
    Set up New Relic Preflight observability for Kiro — verify the preflight/preflight-collector binaries are installed, wire up hook-based tool-call capture, and choose local vs. cloud mode. Use right after this power connects for the first time, or whenever the user asks to set…
  • 100platform-environment-validate
    Validate and configure the local Salesforce development environment. Runs a prerequisite scan across required tools with per-tool status and offers to install or update missing items. Use when the user asks to 'check my setup', 'validate tools', 'verify prerequisites', 'am I set…
  • 100sentinel-env
    Environment-aware pre-flight check. Use when starting work in a new environment, switching machines, or when 'works on my machine' bugs surface. Validates OS, runtime versions, installed tools, port availability, env vars, and disk space BEFORE coding starts. Like sentinel but…
  • 100i4h-workflow-setup
    Preflight and set up the root-level workflow runtime. Use for installation, missing component environments, or third-party failures; do not use for rollout validation.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.