- Home
- Skills
- Agents & Orchestration
- Environment Contract Drift Fixer
More screenshots
Works with the AI Agents you already use
Environment Contract Drift Fixer
Fix environment variable contract drift in a repo using Cursor.
$1
Environment Contract Drift Fixer
Example session with this skill installed
Audit my repo for env var drift. I renamed STRIPE_SECRET to STRIPE_SECRET_KEY but I think the Docker config and README are still using the old name. Fix the docs and add a check.
- Read your context and instructions
- Compiled the environment contract drift
1. Environment Contract Decision
Decision: ENV CONTRACT DRIFT FOUND
Found legacy STRIPE_SECRET in docker-compose.yml and README.md, while src/config.ts expects STRIPE_SECRET_KEY.
4. Drift Findings
| Area | Finding | Risk |
|---|---|---|
| Stripe | STRIPE_SECRET vs STRIPE_SECRET_KEY | Runtime failure in Docker |
| Docs | README mismatch | Onboarding confusion |
6. Safe Patch Summary
- Updated
docker-compose.ymlplaceholders. - Aligned
README.mdsetup instructions. - Created
scripts/check-env-drift.mjsfor CI.
Connects securely to your tools. The creator never sees your data.
About this skill
The problem
Environment variables often drift between local development, Docker configs, CI workflows, and deployment documentation. This causes "works on my machine" failures, broken handoffs, and production outages when renamed or missing variables go unnoticed.
What it does
- Audits the entire repository to map environment variable usage across code, config loaders, schemas, and documentation.
- Identifies missing, unused, renamed, legacy, or ambiguous variables.
- Proposes a canonical environment contract to resolve naming conflicts.
- Generates safe patches for
.env.example, READMEs, and Docker files using only placeholders. - Adds guardrails like startup validation and CI drift checks to prevent future inconsistencies.
Frameworks & tools
Works with any stack including Node.js, Express, Prisma, Next.js, Docker, GitHub Actions, and platforms like Vercel or Render.
Why this beats prompting it yourself
Manual auditing is error-prone and often misses variables hidden in CI YAMLs or deployment notes. This skill enforces a structured workflow that creates a source register, ensuring no variable is overlooked while strictly protecting you from accidental secret exposure in logs or docs.
Use cases
- Standardize environment variable names before a major client handoff.
- Fix deployment failures caused by inconsistent naming between code and hosting providers.
- Clean up legacy variables after a refactor or platform migration.
- Add automated checks to ensure
.env.examplenever falls out of sync with the code.
Known limitations
Cannot access live hosting dashboards, cloud secret stores, or production logs. It does not handle real secret rotation or validate the values of secrets themselves.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Agents & Orchestration.
Cannot access cloud provider dashboards, read real secret values, or perform actual deployments. Limited to files available within the repository context.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 3 months ago
- Software
- prisma
Node.js
Permissions
Permissions are limited to the active local workspace and are used to inspect user-supplied or local workspace files; create or modify bounded local fixes, tests, documentation, or review artifacts; run repository-supported local tests, checks, builds, or parsing commands. The skill package does not require bundled credentials, unrestricted external network access, or automatic production changes.