agentenv-cli

Validate required environment variables with JSON or YAML output.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/SebastianBoehler/agent-cli-utils --skill agentenv-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agentenv-cli
Source: https://github.com/SebastianBoehler/agent-cli-utils/tree/main/skills/agentenv-cli
Command: npx skills add https://github.com/SebastianBoehler/agent-cli-utils --skill agentenv-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate environment prerequisites before running a model, sync task, or automation step, ensuring required variables are present and not leaking values unintentionally.

Core Features & Use Cases

  • Environment validation: Check that specified environment variables exist and, if needed, are non-empty.
  • Flexible input: Accepts variable names as positional arguments or from a file via -file required-env.txt.
  • Output formats: Produce machine-readable JSON or YAML for automation, or human-readable text for quick reviews.
  • Safe defaults: Use -strict by default for CI startup checks and preflight validations; -show-values and -allow-empty can be toggled with explicit intent.

Quick Start

Run agentenv OPENAI_API_KEY HOME to verify required variables are present.

Frequently Asked Questions about agentenv-cli

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

FAQPage Schema
How do I validate required environment variables before starting an automation?

Yes, you can load required environment variable names from a file using the `-file` flag, such as `-file required-env.txt`. This allows you to validate environment prerequisites from a predefined list rather than passing arguments individually.

How does environment variable validation work in CI pipelines?

You can output validation results in machine-readable JSON or YAML formats using the `-format` flag. This allows automation systems and CI pipelines to programmatically parse environment validation outcomes.

Can I check environment variables from a file for preflight checks?

Yes, you can load required environment variable names from a file using the `-file` flag, such as `-file required-env.txt`. This allows you to validate environment prerequisites from a predefined list rather than passing arguments individually.

How do I prevent leaking sensitive values during environment variable validation?

Environment variable validation uses safe defaults by omitting values during checks. You must explicitly toggle `-show-values` to display them, and `-allow-empty` to permit empty variables, preventing unintentional value leaks.

Does environment validation support machine-readable output for automation?

Yes, environment validation supports machine-readable output via the `-format` flag, producing JSON or YAML. This allows CI pipelines and automation tools to programmatically parse validation results.