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
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 explicit 'Use when' guidance. The main weakness is the opening phrase 'Guidance for working with' which is passive rather than action-oriented. The description would be slightly stronger if it listed concrete actions (e.g., 'Configure OIDC, manage secrets, integrate with secret stores').
Suggestions
Replace 'Guidance for working with' with specific action verbs like 'Configures OIDC, manages secrets and environments, integrates with secret stores for Pulumi ESC'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Pulumi ESC) and mentions several areas like 'managing secrets, configuration, environments, short-term credentials, configuring OIDC' but uses 'Guidance for working with' which is somewhat vague rather than listing concrete actions like 'configure', 'create', 'integrate'. | 2 / 3 |
Completeness | Clearly answers both what ('Guidance for working with Pulumi ESC') and when ('Use when users ask about managing secrets, configuration, environments...') with an explicit 'Use when' clause containing multiple specific trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'secrets', 'configuration', 'environments', 'OIDC', 'AWS', 'Azure', 'GCP', 'AWS Secrets Manager', 'Azure Key Vault', 'HashiCorp Vault', '1Password', 'Pulumi stacks'. These are all terms users would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche around Pulumi ESC specifically. The combination of 'Pulumi ESC', specific cloud providers, and named secret stores creates a unique fingerprint unlikely to conflict with generic secrets or configuration 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, clear workflows, and appropriate progressive disclosure to external documentation. The main weakness is some unnecessary introductory content explaining what ESC does, which Claude could infer. The troubleshooting section and best practices add genuine value.
Suggestions
Remove or significantly trim the 'What is ESC?' bullet list - Claude doesn't need marketing-style capability descriptions to use the tool effectively
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary explanation in the 'What is ESC?' section that Claude likely already knows. The bullet list of capabilities could be trimmed, though the CLI commands and examples are appropriately concise. | 2 / 3 |
Actionability | Provides fully executable CLI commands with clear syntax, concrete YAML examples, and copy-paste ready code blocks. The commands include proper argument placeholders and the examples are complete and runnable. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced with numbered steps, validation checkpoints (e.g., 'Verify with pulumi config'), and explicit guidance on when to use different commands. The AWS OIDC setup example shows a clear workflow with decision points. | 3 / 3 |
Progressive Disclosure | Excellent structure with clear sections, well-signaled external documentation links for detailed topics (AWS, Azure, GCP, syntax), and appropriate use of web-fetch tool references. Content is appropriately split between quick reference and pointers to deeper docs. | 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.
- 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.