pulumi-component
Guide for authoring Pulumi ComponentResource classes. Use when creating reusable infrastructure components, designing component interfaces, setting up multi-language support, or distributing component packages.
Install with Tessl CLI
npx tessl i github:pulumi/agent-skills --skill pulumi-component77
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
75%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 solid description with clear 'what' and 'when' clauses and good distinctiveness for its niche. The main weaknesses are moderate specificity in describing concrete actions and trigger terms that could be expanded to include more natural user language variations.
Suggestions
Add more specific concrete actions like 'define input/output properties, implement resource registration, configure child resources, set up resource options'
Expand trigger terms to include variations users might say: 'custom Pulumi resource', 'resource abstraction', 'Pulumi SDK component', 'infrastructure module'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Pulumi ComponentResource classes) and mentions some actions like 'creating reusable infrastructure components' and 'designing component interfaces', but lacks specific concrete actions like 'define input/output properties, implement resource registration, configure providers'. | 2 / 3 |
Completeness | Clearly answers both what ('Guide for authoring Pulumi ComponentResource classes') and when ('Use when creating reusable infrastructure components, designing component interfaces, setting up multi-language support, or distributing component packages') with explicit trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'Pulumi', 'ComponentResource', 'infrastructure components', 'multi-language support', but misses common variations users might say like 'custom resource', 'IaC component', 'Pulumi package', or 'resource abstraction'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Pulumi ComponentResource classes specifically, unlikely to conflict with general infrastructure or other IaC tool skills due to the explicit Pulumi and ComponentResource terminology. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill with excellent code examples covering the full component authoring lifecycle. The main weaknesses are moderate verbosity (explaining concepts Claude knows) and missing validation checkpoints in the distribution workflow. The structure and progressive disclosure are well-executed.
Suggestions
Remove explanatory rationale sections (e.g., 'Why' explanations under each pattern) - Claude understands these concepts; keep only the pattern and code
Add validation steps to the distribution workflow: how to verify a published component works, how to test consumer installation succeeds
Condense the 'When to Use This Skill' section into the opening paragraph or remove it entirely
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some explanatory content Claude already knows (e.g., explaining what a ComponentResource is, why versioning matters). Some sections like 'When to Use This Skill' add marginal value. The content could be tightened by removing rationale explanations and focusing purely on patterns. | 2 / 3 |
Actionability | Excellent executable code examples throughout in TypeScript and Python. Every pattern includes copy-paste ready code with complete imports, class definitions, and usage examples. The anti-patterns table provides clear wrong/right comparisons. | 3 / 3 |
Workflow Clarity | The component anatomy section provides a clear 4-step sequence, but the multi-language distribution workflow lacks explicit validation checkpoints. No verification steps for confirming successful publishing or testing that consumers can actually import the component after distribution. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from basics to advanced topics. References to related skills (pulumi-best-practices, pulumi-automation-api) are clearly signaled. External documentation links are provided at the end without deep nesting. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (831 lines); consider splitting into references/ and linking | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- 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.