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.
90
87%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Risky
Do not use without reviewing
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description with excellent trigger term coverage and a clear 'Use when' clause that makes it highly selectable. Its main weakness is the opening phrase 'Guidance for working with' which is vague rather than listing concrete actions the skill enables. The description excels at distinctiveness due to the specificity of the Pulumi ESC domain and the enumeration of specific integrations.
Suggestions
Replace the vague opener 'Guidance for working with' with specific concrete actions, e.g., 'Configures and manages Pulumi ESC environments, secrets, and configuration. Sets up OIDC providers, integrates secret stores, and manages short-term credentials.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Pulumi ESC) and mentions several areas like managing secrets, configuration, environments, OIDC, and integrations, but uses the vague framing 'Guidance for working with' rather than listing concrete actions (e.g., 'configure OIDC providers', 'rotate credentials', 'create environments'). | 2 / 3 |
Completeness | Clearly answers both 'what' (working with Pulumi ESC for secrets, configuration, environments, credentials, OIDC, integrations) and 'when' with an explicit 'Use when...' clause listing specific trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'secrets', 'configuration', 'environments', 'short-term credentials', 'OIDC', specific cloud providers (AWS, Azure, GCP), specific secret stores (AWS Secrets Manager, Azure Key Vault, HashiCorp Vault, 1Password), 'Pulumi stacks', and 'ESC'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific focus on Pulumi ESC, which is a niche product. The combination of Pulumi-specific terminology with specific integrations (OIDC for cloud providers, named secret stores) makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill that provides actionable CLI commands, concrete YAML examples, and clear workflows with validation steps. Its main weakness is some verbosity in the introductory 'What is ESC?' section and the meta-instructional 'Working with the User' section, which could be tightened. Overall it serves as an effective reference that balances overview content with pointers to detailed documentation.
Suggestions
Remove or significantly trim the 'What is ESC?' bullet list — Claude doesn't need a marketing overview of ESC's capabilities when the rest of the skill demonstrates them concretely.
Tighten the 'Working with the User' section by removing the 'For Simple Questions' subsection (Claude already knows to answer simple questions directly) and condensing the meta-instructions.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'What is ESC?' bullet list explains capabilities Claude could infer from context. The 'Working with the User' section includes meta-instructions about how to interact that add bulk. However, the CLI commands and examples are reasonably tight. | 2 / 3 |
Actionability | Provides fully executable CLI commands, concrete YAML examples, specific URLs for documentation fetching, and clear troubleshooting steps with exact commands. The AWS OIDC workflow example gives a concrete step-by-step process. | 3 / 3 |
Workflow Clarity | Multi-step processes (creating environments, linking to stacks, complex tasks) are clearly sequenced with numbered steps. Validation checkpoints are explicit (e.g., 'Verify with pulumi config', 'Help them test with pulumi env get'). The complex task workflow includes understanding goals, checking setup, fetching docs, providing guidance, and validating. | 3 / 3 |
Progressive Disclosure | The skill provides a clear overview with essential commands and concepts inline, then directs to specific external documentation URLs for detailed topics (OIDC providers, syntax reference, CLI reference). References are one level deep and well-signaled with descriptive labels. | 3 / 3 |
Total | 11 / 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
b6214ca
- 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.