rune-sentinel-env

Validates runtime versions, tools, ports, and environment variables before coding starts.

1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/dangvu008/VietTruyen --skill rune-sentinel-env-dangvu008
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rune-sentinel-env
Source: https://github.com/dangvu008/VietTruyen/tree/main/.agents/skills/rune-sentinel-env
Command: npx skills add https://github.com/dangvu008/VietTruyen --skill rune-sentinel-env-dangvu008

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Environment mismatches cause the classic "works on my machine" failures that waste hours of debugging time on issues that are not code bugs. This Skill catches missing runtimes, wrong versions, occupied ports, and missing configuration before any development work begins. ## Core Features & Use Cases - Runtime and Tool Validation: Detects project type from config files (package.json, pyproject.toml, Cargo.toml, go.mod) and verifies installed Node.js, Python, Rust, Go, and Docker versions against declared constraints, including a 9-tier binary detection lookup for hard CLI dependencies. - Port, Env Var, and Disk Checks: Verifies required ports are free, compares .env against .env.example by key presence only (never logging values), and checks disk space and platform-specific issues like Windows long paths or Linux file watcher limits. - Use Case: After cloning a new project, run an environment check to receive a structured READY / READY WITH WARNINGS / BLOCKED report where every finding includes a copy-paste remediation command, such as nvm install 18 for a wrong Node version. ## Quick Start Run an environment pre-flight check on this project and report any missing runtimes, tools, ports, or environment variables with fix commands.

Frequently Asked Questions about rune-sentinel-env

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

FAQPage Schema
How do I check if my machine can run a project before installing dependencies?

Run an environment pre-flight check that reads project config files like package.json or pyproject.toml, then verifies installed runtime versions, package managers, ports, and environment variables. It returns a READY, READY WITH WARNINGS, or BLOCKED verdict with fix commands.

How to fix 'works on my machine' bugs caused by environment differences?

These bugs usually come from version mismatches, stale PATH entries, or missing CLI tools. Validate runtime versions against config constraints and use multi-tier binary detection covering PATH, package manager globals, desktop app bundles, and common install directories.

Does the environment check work on Windows, macOS, and Linux?

Yes, the checks handle cross-platform differences including WSL detection, Windows long path support, macOS Xcode CLI tools for native modules, and Linux file watcher limits. Remediation commands are provided per operating system.

Is it safe to check .env files without exposing secrets?

Yes, the check only verifies key presence by comparing .env against .env.example and never reads or logs variable values. It also flags if .env is committed to git or still contains placeholder values.

What are the limitations of automated environment validation?

The check is read-only and never installs or modifies anything, so fixes must be applied manually. Version compatibility for wrapped external tools is logged for review rather than auto-judged, and checks only cover tools evidenced by project config files.