autonomy--env-auditor

Name: autonomy--env-auditor
Availability: InStock
Author: Pattern

Audit repositories for cold-start environment variable loading blockers.

57|3|Updated Mar 30, 2026

Search Tags:#devops #security #audit #secrets #dotenv #agent-readiness #env-loading

Ready to run

npx skills add https://github.com/patterninc/code-mint --skill autonomy-env-auditor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: autonomy--env-auditor
Source: https://github.com/patterninc/code-mint/tree/main/.agents/skills/autonomy--env-auditor
Command: npx skills add https://github.com/patterninc/code-mint --skill autonomy-env-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit whether a repository's environment variable configuration allows an agent to load all required .env variables from scratch. Use when evaluating a new repository's agent-readiness, when environment loading fails during agent setup, or as part of an initial harness assessment. Do not use when .env files already load correctly and the goal is to add a single new variable, or when creating env loading capability (use autonomy--env-creator).

Core Features & Use Cases

Discover environment variable references across codebase and config files.
Evaluate the environment loading mechanism and secret source documentation.
Perform a cold-start test to identify blockers and required steps.

Quick Start

Run a cold-start env-loading assessment on a target repository and summarize findings in an audit report.

Frequently Asked Questions about autonomy--env-auditor

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

FAQPage Schema

How do I audit environment variable loading readiness for an AI agent in a new repository?▼

Audit environment variable loading readiness by inventorying env var references across code and config, evaluating loading mechanisms and secret sources, then performing a cold-start test to identify blockers and document remediation steps.

Why does my agent setup fail when trying to load required .env variables from scratch?▼

Agent setup fails loading .env variables from scratch when the repository lacks proper loading mechanisms or secret source documentation. Run an env-loading assessment to discover missing references, identify blockers, and generate required remediation steps.

What is a cold-start environment loading assessment for DevOps security?▼

A cold-start environment loading assessment evaluates whether a repository can load all required environment variables without pre-existing .env files, inventorying references and recording blockers to ensure AI agent readiness during onboarding harness checks.

When should I not use an env-loading readiness audit for my repository?▼

You should not use an env-loading readiness audit when .env files already load correctly and the goal is adding a single new variable, or when creating env loading capability, which requires a different env-creator approach instead.

Can I check if a repository's secret sources and dotenv configuration are ready for automated onboarding?▼

Yes, you can check secret sources and dotenv configuration readiness by evaluating the environment loading mechanism and documenting whether all required variables can load from a cold start, recording any blockers found during the harness assessment.

What's the best way to document environment setup blockers for AI agent onboarding?▼

The best way to document environment setup blockers is running a cold-start env-loading assessment that inventories variable references, evaluates loading mechanisms, and records all blockers with explicit remediation steps in an audit report.