CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

67

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense, code-rich, well-organized authoring guide whose core examples are executable and well-structured. Its main weakness is progressive disclosure: an 830-line monolith with no bundle files, plus minor redundancy and a few placeholder code blocks.

Suggestions

Move the Multi-Language Components and Distribution sections into separate reference files (e.g. references/multi-language.md, references/distribution.md) and keep SKILL.md as a concise overview pointing to them, one level deep.

Dedupe the SecureBucketArgs interface: it is defined in both 'Use Defaults for Optional Properties' and 'Sensible Defaults with Override' — define it once and reference it.

Fill or remove the placeholder ellipses in secondary examples (WebService ECS service, Database sg/cluster `{ /* ... */ }`, VpcNetwork VPC creation) so all code blocks are executable, or explicitly mark them as illustrative snippets.

DimensionReasoningScore

Conciseness

Mostly efficient and code-forward with tight "Why/Wrong/Right" framing, but the 830-line body has redundancy (e.g. SecureBucketArgs is defined twice across sections) and could be trimmed. Not a 5 because of that repetition; not a 3 because explanations are Pulumi-specific and earn their place rather than padding.

4 / 5

Actionability

Core examples (StaticSite in TS+Python, SecureBucket) are complete and copy-paste ready, but several secondary pattern examples use placeholders ("// ...service config...", "{ /* ... */ }") that are not executable. Not a 5 because of those gaps; not a 3 because the common cases are fully covered with real code.

4 / 5

Workflow Clarity

The four required elements form a clear sequenced anatomy, reinforced by an Anti-Patterns table and a Quick Reference that function as checklists. Not a 5 because there are no explicit validation/feedback-loop checkpoints, though this authoring skill is not a destructive or batch operation so the 3-cap does not apply.

4 / 5

Progressive Disclosure

Headers, tables, and a Quick Reference give real structure, but the skill is a monolithic 830-line file that inlines entire sections (Multi-Language Components, Distribution) which would be better offloaded to bundle files, and no references/scripts/assets bundle files exist. Not a 4 because for a skill this large the overview-into-details split is absent; not a 2 because section organization is genuinely clear, not minimal.

3 / 5

Total

15

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-structured description that clearly states what the skill does and when to invoke it, with concrete trigger phrases spanning the full component lifecycle. The only minor gap is keyword synonym coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across the lifecycle — "creating reusable infrastructure components, designing component interfaces, setting up multi-language support, or distributing component packages" — giving comprehensive coverage rather than a single generic verb.

5 / 5

Completeness

Explicitly answers both: the "what" ("Guide for authoring Pulumi ComponentResource classes") and the "when" ("Use when creating... designing... setting up... or distributing...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural keywords for the niche ("Pulumi ComponentResource", "reusable infrastructure components", "multi-language support", "distributing component packages"), but lacks synonyms or common variations a user might phrase differently. Not a 5 because coverage of alternative phrasings is incomplete.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (Pulumi ComponentResource authoring) with distinct triggers; the body even delineates boundaries against the sibling pulumi-best-practices skill, minimizing wrong-skill conflict.

5 / 5

Total

19

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

14

/

16

Passed

Repository
pulumi/agent-skills
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.