Centralized secrets, configuration, and dynamic credentials management for Pulumi infrastructure and applications.
Works with
Supports environment composition through imports and layering, with reserved keys for environmentVariables , pulumiConfig , and files
Generates short-term credentials via OIDC for AWS, Azure, and GCP; integrates with AWS Secrets Manager, Azure Key Vault, HashiCorp Vault, and 1Password
Core CLI commands include pulumi env init , pulumi env edit , pulumi env open (reveals
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionpulumi-escExecute the skills CLI command in your project's root directory to begin installation:
Fetches pulumi-esc from pulumi/agent-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate pulumi-esc. Access via /pulumi-esc in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
34
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
34
stars
Pulumi ESC is a centralized service for managing environments, secrets, and configuration across cloud infrastructure and applications.
ESC enables teams to:
# Create a new environment
pulumi env init <org>/<project-name>/<environment-name>
# Edit environment (opens in editor)
pulumi env edit <org>/<project-name>/<environment-name>
# Set values
pulumi env set <org>/<project-name>/<environment-name> <key> <value>
pulumi env set <org>/<project-name>/<environment-name> <key> <value> --secret
# View definition (secrets hidden)
pulumi env get <org>/<project-name>/<environment-name>
# Open and resolve (reveals secrets)
pulumi env open <org>/<project-name>/<environment-name>
# Run command with environment
pulumi env run <org>/<project-name>/<environment-name> -- <command>
# Link to Pulumi stack
pulumi config env add <project-name>/<environment-name>
pulumi env get: Shows static definition, secrets appear as [secret]pulumi env open: Resolves and reveals all values including secrets and dynamic credentialspulumi env run: Executes commands with environment variables loadedpulumi config env add: Only takes the / portionEnvironments are YAML documents with reserved top-level keys:
imports: Import and compose other environmentsvalues: Define configuration and secretsReserved sub-keys under values:
environmentVariables: Map values to shell environment variablespulumiConfig: Configure Pulumi stack settingsfiles: Generate files with environment dataimports:
- common/base-config
values:
environment: production
region: us-west-2
dbPassword:
fn::secret: super-secure-password
environmentVariables:
AWS_REGION: ${region}
DB_PASSWORD: ${dbPassword}
pulumiConfig:
aws:region: ${region}
app:dbPassword: ${dbPassword}
If the user asks basic questions like "How do I create an environment?" or "What's the difference between get and open?", answer directly using the information above.
When users need more information, use the web-fetch tool to get content from the official Pulumi ESC documentation:
pulumi env subcommands over esc CLI.Use the web-fetch tool with specific prompts to extract relevant information from these docs.
When helping users:
pulumi env commands to list environments or read definitionspulumi env get or pulumi preview
a. Only use pulumi env open when the full resolved values are needed, but use cautiously as it reveals secrets.User: "How do I set up AWS OIDC credentials in ESC?"
1. Use the web-fetch tool to get AWS OIDC documentation from "https://www.pulumi.com/docs/esc/integrations/dynamic-login-credentials/aws-login/"
2. Provide the user with the configuration
3. Ask the user if they have a pre-defined role or need one created for them
4. Set up as much of the environment as possible, then guide them through any steps that you can't do for them
5. Help them test with `pulumi env get` or `pulumi env open` if necessary
pulumi env init my-org/my-project/dev-config
# Edit environment (accepts new definition from a file, better for agents, more difficult for users)
pulumi env edit --file /tmp/example.yml my-org/my-project/dev-config
pulumi config env add my-project/dev-config
pulumi config # Verify environment values are accessible
Always prefer CLI commands. Only use the API when absolutely necessary (e.g., bulk operations, automation).
Available API endpoints include:
GET /api/esc/environments/{orgName} - List environmentsGET /api/esc/environments/{orgName}/{projectName}/{envName} - Read environment definitionGET /api/esc/providers?orgName={orgName} - List available providersUse call_pulumi_cloud_api() tool to make requests when needed.
fn::secret for sensitive values<org>/my-app/production-aws not <org>/app/prodpulumi config shows expected values after linking an environment to a stackpulumi env run for commands needing environment variablespulumi env open when absolutely necessary, as it reveals secretspulumi env ls -o <org>pulumi env open not pulumi env getpulumi config env ls to ensure the stack is listed.
pulumi env get <org>/<project-name>/<environment-name>.pulumiConfig key exists and is nested under the values key.Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
pulumi-esc is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: pulumi-esc is focused, and the summary matches what you get after install.
I recommend pulumi-esc for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Solid pick for teams standardizing on skills: pulumi-esc is focused, and the summary matches what you get after install.
pulumi-esc reduced setup friction for our internal harness; good balance of opinion and flexibility.
We added pulumi-esc from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
pulumi-esc is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
We added pulumi-esc from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: pulumi-esc is the kind of skill you can hand to a new teammate without a long onboarding doc.
pulumi-esc fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 50