guardian-env

Validate local development environments for Node, Python, Rust, Go, and Docker projects.

1|Updated May 18, 2026

Search Tags:#debugging #onboarding #python #validation #docker #environment #node

Ready to run

npx skills add https://github.com/linenoize/topia --skill guardian-env

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: guardian-env
Source: https://github.com/linenoize/topia/tree/main/skills/guardian-env
Command: npx skills add https://github.com/linenoize/topia --skill guardian-env

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It catches environment mismatches before they turn into wasted debugging time, failed installs, or false “works on my machine” bugs.

Core Features & Use Cases

Runtime validation: Confirms Node, Python, Rust, Go, and Docker versions match project constraints.
Tool and dependency checks: Verifies package managers, Git, Docker, and hard external CLI dependencies the project relies on.
Project readiness signals: Checks ports, environment variables, disk space, and platform-specific requirements so you can start work with confidence.
Use case: Run it when moving to a new laptop, onboarding to a repository, or after install failures that suggest the machine is missing something.

Quick Start

Ask the assistant to run guardian-env against this project and report any environment blockers before you begin coding.

Frequently Asked Questions about guardian-env

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

FAQPage Schema

How do I validate my local development environment before coding starts?▼

Environment validation works by checking runtime versions, installed tools, port availability, environment variables, disk space, and hard CLI dependencies against project constraints. It then provides read-only remediation guidance to resolve setup issues before coding begins.

Does environment validation support Node, Python, Rust, Go, and Docker projects?▼

Environment validation supports Node, Python, Rust, Go, and Docker projects. It confirms installed runtime versions match project constraints and verifies required package managers and external CLI dependencies.

What's the best way to catch works-on-my-machine failures during project onboarding?▼

The best way to catch works-on-my-machine failures during project onboarding is to validate the environment before coding. Running guardian-env checks for mismatches in runtime versions, missing tools, and environment variables to prevent setup issues.

How do I check for missing environment variables and port availability before running a project?▼

To check for missing environment variables and port availability, run an environment validation check against your project. It scans for these project readiness signals along with runtime versions and disk space, then provides read-only remediation guidance.

Can I use environment validation to verify hard external CLI dependencies the project relies on?▼

Yes, you can use environment validation to verify hard external CLI dependencies the project relies on. It checks for required package managers, Git, Docker, and other tools to ensure your machine is ready for development.

Why does environment validation only provide read-only remediation guidance?▼

Environment validation provides read-only remediation guidance to safely identify setup issues without automatically modifying your system. This ensures you maintain control over changes to runtime versions, environment variables, and dependencies while resolving blockers.