pulumi-automation-api
Load this skill when a user asks how to run Pulumi programmatically, embed Pulumi in an application, orchestrate multiple stacks in code, build a self-service infrastructure portal, replace pulumi CLI shell scripts with code, or use the Pulumi Automation API (LocalWorkspace, createOrSelectStack, inline programs). Also load for questions about multi-stack sequencing, parallel deployments, or passing outputs between stacks via code.
85
82%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%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 that clearly defines a specific niche (Pulumi Automation API and programmatic infrastructure orchestration), provides rich trigger terms that users would naturally use, and explicitly states when the skill should be loaded. The only minor note is that it lacks a concise 'what it does' summary sentence before the trigger guidance, but the trigger scenarios themselves implicitly convey the capabilities well.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: running Pulumi programmatically, embedding Pulumi in applications, orchestrating multiple stacks, building self-service infrastructure portals, replacing CLI shell scripts with code, and using specific API constructs (LocalWorkspace, createOrSelectStack, inline programs). | 3 / 3 |
Completeness | Clearly answers both 'what' (programmatic Pulumi usage, Automation API, multi-stack orchestration, etc.) and 'when' with explicit trigger guidance ('Load this skill when a user asks how to...' followed by detailed trigger scenarios). The 'Also load for' clause adds additional trigger conditions. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Pulumi Automation API', 'LocalWorkspace', 'createOrSelectStack', 'inline programs', 'multi-stack', 'parallel deployments', 'passing outputs between stacks', 'self-service infrastructure portal', 'replace pulumi CLI shell scripts'. These are highly natural phrases a user would use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — focuses specifically on the Pulumi Automation API and programmatic infrastructure orchestration, which is a clear niche distinct from general Pulumi usage, general IaC skills, or other cloud tooling skills. The specific API names (LocalWorkspace, createOrSelectStack) further reduce conflict risk. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%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 with excellent executable code examples covering the key Automation API patterns. Its main weaknesses are verbosity (explaining concepts Claude already knows, like what programmatic access means) and missing validation checkpoints in multi-step workflows. The content would benefit from trimming explanatory prose and integrating error handling directly into the orchestration workflows.
Suggestions
Remove or drastically shorten the 'What is Automation API' and 'When to Use' sections — Claude understands these concepts; focus on the how, not the why.
Integrate error handling and validation checkpoints directly into the multi-stack orchestration workflow (e.g., check result.summary.result after each stack.up() before proceeding to the next stack).
Consider splitting detailed patterns (parallel deployments, configuration passing, error handling) into a separate PATTERNS.md file, keeping SKILL.md as a concise overview with the core pattern and quick reference table.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanations Claude would already know (e.g., 'What is Automation API' section explaining what programmatic access means, the 'When NOT to Use' section with obvious points, and verbose descriptions of use cases like 'Applications that provision their own infrastructure'). The content could be tightened by ~30% without losing actionable information. | 2 / 3 |
Actionability | The skill provides fully executable TypeScript code examples throughout — createOrSelectStack, multi-stack orchestration, configuration setting, output reading, error handling, and parallel deployments are all copy-paste ready with real imports and proper async/await patterns. | 3 / 3 |
Workflow Clarity | The multi-stack orchestration pattern shows clear sequencing (deploy in order, destroy in reverse), but lacks explicit validation checkpoints between stack deployments. For multi-stack operations where a failed intermediate stack could leave infrastructure in a bad state, there should be validation/rollback steps between sequential deployments. The error handling section exists but is separate from the workflow rather than integrated into it. | 2 / 3 |
Progressive Disclosure | The skill references related skills and external documentation at the bottom, which is good. However, the content itself is quite long (~200+ lines) with detailed patterns that could be split into separate reference files (e.g., patterns.md, examples.md). The quick reference table at the end is helpful but the overall document is monolithic. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- pulumi/agent-skills
- Commit
3ec9d51
- 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.