env-vars Skill
Vercel environment variable expert guidance. Use when working with .env files, vercel env commands, OIDC tokens, or managing environment-specific configuration. Published by openai in plugins.
Decision snapshot
Is this a fit?
Testing, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
18 days ago
No specific cautions were detected. Review the source and requested permissions before installing.
What is env-vars Skill?
Vercel environment variable expert guidance. Use when working with .env files, vercel env commands, OIDC tokens, or managing environment-specific configuration. Published by openai in plugins. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Testing
- Testing use cases
Declared skill metadata
- Source file: plugins/vercel/skills/env-vars/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use env-vars Skill
- Use it for testing.
Built with
Editorial notes
Source
- Creator: openai
- Repository: openai/plugins
- Skill file: plugins/vercel/skills/env-vars/SKILL.md
What it does
Vercel environment variable expert guidance. Use when working with .env files, vercel env commands, OIDC tokens, or managing environment-specific configuration.
Skill instructions
Vercel Environment Variables You are an expert in Vercel environment variable management — .env file conventions, the vercel env CLI, OIDC token lifecycle, and environment-specific configuration. .env File Hierarchy Vercel and Next.js load environment variables in a specific order. Later files override earlier ones: | File | Purpose | Git-tracked? | |------|---------|-------------| | .env | Default values for all environments | Yes | | .env.local | Local overrides and secrets | No (gitignored) | | .env.development | Development-specific defaults | Yes | | .env.development.local | Local dev overrides | No | | .env.production | Production-specific defaults | Yes | | .env.production.local | Local prod overrides | No | | .env.test | Test-specific defaults | Yes | | .env.test.local | Local test overrides | No | Load Order (Next.js) 1. .env (lowest priority) 2. .env.[environment] (development, production, or test) 3. .env.local (skipped in test environment) 4. .env.[environment].local (highe
Verified compatibility and discovery
Frequently asked questions
What is env-vars?
env-vars is a open-source AI agent skill with Copy skill directory. Vercel environment variable expert guidance. Use when working with .env files, vercel env commands, OIDC tokens, or managing environment-specific configuration.
Who is env-vars best for?
env-vars is best for reusing agent instructions, scripts, and references, testing workflows.
How do I install env-vars?
Install or run env-vars using Copy skill directory. Check env-vars for the latest setup command.
Is env-vars actively maintained?
env-vars may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
