Skip to content
anyai.fyi

env-vars

Skill from vercel/vercel-plugin

Other Worth a look curated

Install

npx skills add vercel/vercel-plugin --skill env-vars

Runs the open skills CLI and installs the skill for your agent (Claude Code, Codex, Cursor …). Alternatively copy the skill folder into .claude/skills/ or upload it in Claude.ai under Settings → Skills.

As a Claude Code plugin

/plugin marketplace add anthropics/claude-plugins-official /plugin install vercel-plugin@vercel

This skill is part of the plugin “vercel-plugin”. In Claude Code the plugin installs it together with the plugin’s other skills, commands and hooks.

What does the env-vars skill do?

Vercel environment variable expert guidance. Use when working with .env files, vercel env commands, Secret or Config variable types, OIDC tokens, or managing environment-specific configuration.

Description from the SKILL.md in the source repository.

Works with Vercel

Questions about env-vars

What does the env-vars skill do?

Vercel environment variable expert guidance. Use when working with .env files, vercel env commands, Secret or Config variable types, OIDC tokens, or managing environment-specific configuration.

How do I install env-vars?

In a terminal: npx skills add vercel/vercel-plugin --skill env-vars. The skills CLI asks which agents to install it for. In Claude.ai you can upload the skill folder as a ZIP under Settings → Skills.

Which agents can use env-vars?

Skills use the open SKILL.md format, which Claude Code, Claude.ai, the Claude API, OpenAI Codex, Cursor, Gemini CLI and other agents support.

Is env-vars safe to use?

Our automatic check found patterns worth a look (see “Check”). That is not proof of anything bad – read the SKILL.md and scripts before installing.

Which tool is env-vars for?

env-vars comes from the makers of Vercel and helps your agent work with it.

More skills from vercel/vercel-plugin

queues
vercel/vercel-plugin

Vercel Queues guidance — durable topics with at-least-once delivery, independent consumer groups, retries, delays, and idempotency keys via @vercel/queue (JS) or vercel-queue (Python). Use when deferring background work, buffering traffic, fanning out events, or choosing between Queues and Workflows.

Development curated
No risky patterns found
vercel-cli
vercel/vercel-plugin

Vercel CLI expert guidance. Use when deploying, managing environment variables, linking projects, viewing logs, querying metrics, debugging a deployed app on Vercel (errors, 5xx responses, timeouts, slow routes, or a single failing request), managing domains, managing feature flags with vercel flags, or interacting with the Vercel platform from the command line. Use the vercel-tracing skill instead for `vercel traces` span search, trace inspection, and sampling rules, or for OpenTelemetry setup.

Research & Web curated
No risky patterns found
vercel-agent
vercel/vercel-plugin

Vercel Agent guidance — dashboard and Slack chat, code review, production investigation, approved actions, and product installation. Use when configuring or working with Vercel's AI assistant.

Development curated
No risky patterns found
runtime-cache
vercel/vercel-plugin

Vercel Runtime Cache API guidance — ephemeral per-region key-value cache with tag-based invalidation. Shared across Functions, Routing Middleware, and Builds. Use when implementing caching strategies beyond framework-level caching.

Development curated
No risky patterns found
routing-middleware
vercel/vercel-plugin

Vercel Routing Middleware guidance — request interception before cache, rewrites, redirects, personalization. Works with any framework. Supports Edge, Node.js, and Bun runtimes. Use when intercepting requests at the platform level.

Other curated
No risky patterns found
react-best-practices
vercel/vercel-plugin

Vercel's React and Next.js performance rules (70 rules in 8 categories ordered by impact - eliminating waterfalls, bundle size, server-side performance, client-side data fetching, re-renders, rendering performance, JavaScript performance, and advanced patterns). Use when writing, reviewing, or refactoring React components, Next.js pages, or data fetching for performance. Not an accessibility or TypeScript style guide.

Frontend & UI curated
No risky patterns found
microfrontends
vercel/vercel-plugin

Guide for building, configuring, and deploying microfrontends on Vercel. Use this skill when the user mentions microfrontends, multi-zones, splitting an app across teams, independent deployments, cross-app routing, incremental migration, composing multiple frontends under one domain, microfrontends.json, @vercel/microfrontends, the microfrontends local proxy, or path-based routing between Vercel projects. Also use when the user asks about shared layouts across projects, navigation between microfrontends, fallback environments, asset prefixes, or feature flag controlled routing.

Other curated
No risky patterns found
knowledge-update
vercel/vercel-plugin

Corrects outdated LLM knowledge about the Vercel platform and introduces new products. Injected at session start.

Other curated
No risky patterns found

Related skills in Other