check-env

Compare app environment variables against Railway deployment configuration to detect missing variables.

Updated May 11, 2026
One-click install
npx skills add https://github.com/mmnavarr/harness --skill check-env-mmnavarr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: check-env
Source: https://github.com/mmnavarr/harness/tree/main/skills/check-env
Command: npx skills add https://github.com/mmnavarr/harness --skill check-env-mmnavarr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires railway, jq, and includes scripts (resource) components.

What problem does it solve? Deployed apps fail at runtime when required environment variables are missing from the hosting platform. This Skill audits an app's env.ts definitions against the variables actually configured in Railway, surfacing gaps before they cause production errors. ## Core Features & Use Cases - Variable Extraction: Reads server and client variables from an app's env.ts, noting which have defaults. - Railway Comparison: Fetches configured variable names from Railway via a bundled script and the Railway CLI. - Status Report: Outputs a markdown table classifying each variable as OK, using a default, or missing. - Use Case: Before deploying the admin app, run the check to confirm DATABASE_URL and other required variables are set in Railway, catching a missing variable that would have crashed the service at startup. ## Quick Start Ask the AI to run /check-env for the admin app to verify all required environment variables are configured in Railway.

Frequently Asked Questions about check-env

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

FAQPage Schema
How do I check for missing environment variables in Railway?▼

Run the check-env workflow with an app name such as admin or webapp. It reads the app's env.ts for required variables, fetches configured variable names from Railway via the CLI, and reports which are missing or relying on defaults.

How to compare env.ts variables with Railway deployment config?▼

The skill parses server and client variables from env.ts, then calls the bundled get-railway-vars.sh script to list variables set in Railway. It outputs a markdown table showing each variable's status: OK, using default, or missing.

Does this require the Railway CLI to be installed?▼

Yes, the Railway CLI must be installed and authenticated. The bundled script runs railway variables with service and environment IDs, so railway whoami must succeed before the check can fetch configured variable names.

Which apps are supported by the Railway variable check?▼

The script supports four apps: admin, webapp, bullqueue, and website. Each maps to a hardcoded Railway service ID, and unknown app names cause the script to exit with an error listing valid options.

Why does the check only fetch variable names and not values?▼

Fetching only key names via jq keeps the output small and avoids exposing secret values in the AI context. The comparison only needs to know whether a variable is set, not its contents.