pulumi-esc
Guidance for working with Pulumi ESC (Environments, Secrets, and Configuration). Use when users ask about managing secrets, configuration, environments, short-term credentials, configuring OIDC for AWS, Azure, GCP, integrating with secret stores (AWS Secrets Manager, Azure Key Vault, HashiCorp Vault, 1Password), or using ESC with Pulumi stacks.
65
77%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./authoring/skills/pulumi-esc/SKILL.mdQuality
Discovery
N/ABased on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
Something went wrong
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill that provides concrete CLI commands, clear YAML examples, and well-structured workflows with validation steps. Its main weakness is moderate verbosity—the 'What is ESC?' section and some concept explanations could be trimmed since Claude already understands these abstractions. The progressive disclosure strategy of using web-fetch for detailed docs is effective, though the main file itself is somewhat long.
Suggestions
Remove or significantly trim the 'What is ESC?' bullet list—Claude doesn't need a marketing overview of the product's capabilities.
Consider extracting the 'Working with the User' behavioral guidance and provider URLs into a separate reference file to keep the main skill leaner.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'What is ESC?' bullet list explains things Claude could infer, and some sections like 'Key Concepts' restate what's already shown in the CLI commands. However, the content is generally well-structured and not excessively padded. The 'Working with the User' section adds meta-instructions that are useful but somewhat verbose. | 2 / 3 |
Actionability | The skill provides concrete, copy-paste-ready CLI commands, a complete YAML example, specific URLs for web-fetch, and clear troubleshooting steps with exact commands. The guidance is specific and executable throughout. | 3 / 3 |
Workflow Clarity | Multi-step processes like AWS OIDC setup and environment creation are clearly sequenced with numbered steps. The 'For Complex Tasks' section includes validation checkpoints (step 5 with `pulumi env get` or `pulumi preview`), and troubleshooting provides a feedback loop for common errors. | 3 / 3 |
Progressive Disclosure | The skill appropriately defers detailed documentation to external URLs via web-fetch, which is a good pattern. However, with no bundle files, all content is in a single monolithic file that's quite long (~150 lines of substantive content). Some sections like the API reference or provider-specific URLs could be split into separate files for better organization. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- pulumi/agent-skills
- Commit
f810e50
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.