Env Health Check

Inspect environment variables, critical directories, and write permissions, then produce a health report. Use when validating deployment readiness, local run...

Security Scan

The skill's code and runtime instructions match its stated purpose (checking for presence of env vars, directory existence, and write permissions); it performs only local filesystem checks and writes a report, with no network calls or unexpected credential requests.

Purpose & Capability

Name/description, SKILL.md, README, skill.yaml, and index.js are consistent: the tool accepts --env and --dir flags, checks presence of those env vars and directory writeability, and emits a report. No unrelated binaries, credentials, or config paths are requested.

Instruction Scope

Instructions stay within the stated purpose, but note that the tool will (a) create and remove a temporary file in each checked directory to test writability, and (b) write a report file containing the checked env variable NAMES and directory paths (it does NOT include env VALUES). This means the report can reveal which secret-named environment variables exist on the system — avoid writing the report to a shared location if that metadata is sensitive.

Install Mechanism

No install spec is provided and there are no external downloads — the skill is shipped with a small JS script (index.js) and runs with Node.js. This is low-risk from an install perspective; no code is pulled from arbitrary URLs.

Credentials

The skill requests no environment variables by default; it only checks for the presence of env names you explicitly pass via --env. It does not read or write env values into the report (only presence is tested). The README example lists common API key names (e.g., OPENAI_API_KEY) which is reasonable sample usage but could encourage checking real secrets — remember the report will record the names you check.

Persistence & Privilege

The skill does not request elevated or persistent privileges and does not modify other skills or global agent configs. It will create an output file (default ./out/env_health_report.md or user-provided --out) and temporary files in checked directories to test writeability.

Assessment

This skill appears to do exactly what it says: local checks for env variable presence and directory existence/writeability and then writes a health report. Before running: (1) decide where the report file should be written — it will contain the NAMES of any env vars you check (but not their values), so avoid saving the report in a shared location if that metadata is sensitive; (2) be aware it will create and delete a small temp file in each directory you supply to test write permissions; (3) do not pass env names you don't want persisted on disk (the report lists the names). If those points are acceptable, the skill is coherent and suitable to use.

Inspect runtime prerequisites and emit a compact health report.

Workflow

1. Pass required env var names with --env flags.
2. Pass critical directories with --dir flags.
3. Run index.js and review OK/WARN/FAIL output.
4. Treat missing write access as a blocker unless the path is intentionally read-only.