CtrlK
BlogDocsLog inGet started
Tessl Logo

pulumi-upgrade-provider

Automate Pulumi provider repo upgrades with the `upgrade-provider` tool. Use when upgrading a pulumi provider repository to a new upstream version, running `upgrade-provider`, and addressing its common failure modes like patch conflicts or missing module mappings.

74

Quality

91%

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

88%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 high-quality, executable runbook with strong workflow sequencing, validation checkpoints, and a real offloaded error reference. The main opportunity is tightening a few verbose policy explanations to improve token efficiency.

Suggestions

Condense the release-label and --major rationale in the Submit section to a short rule with one example; the current multi-clause explanation is repeated across sections.

Move the enumerated error-routing detail currently inline in Run Loop step 6 entirely into references/upgrade-provider-errors.md, keeping only a pointer in the body.

Trim the duplicated baseline_file assignment and rationale, which appears in both Preflight and Review, by referencing the preflight value once.

DimensionReasoningScore

Conciseness

Largely lean and command-driven with executable bash blocks, but some passages restate policy at length (e.g., the release-label and major-version rationale in the Submit section) that could be trimmed without losing clarity.

4 / 5

Actionability

Provides fully executable, copy-paste-ready bash and gh commands covering preflight, the run loop, error scanning, review, replacements audit, and submission, with concrete fallbacks (rg vs grep).

5 / 5

Workflow Clarity

Clear sequenced phases (Preflight → Run Loop → Stop/Report → Review → Submit) with explicit validation checkpoints (error scan, 'No actions needed' check, replacements.json TODO audit, clean working tree requirement) and a feedback loop (fix → rerun --no-submit).

5 / 5

Progressive Disclosure

SKILL.md is a well-organized overview with a single one-level-deep reference (references/upgrade-provider-errors.md, confirmed present) signaled clearly in both Run Loop and References; the bulk of error-detail content is appropriately offloaded, though the error taxonomy is summarized inline rather than fully deferred.

4 / 5

Total

18

/

20

Passed

Description

95%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, third-person description that clearly states the capability and provides an explicit 'Use when' trigger with concrete failure-mode examples. It is specific, distinct, and free of fluff.

DimensionReasoningScore

Specificity

Lists concrete actions — 'upgrading a pulumi provider repository to a new upstream version, running upgrade-provider, and addressing its common failure modes' — naming specific failure modes (patch conflicts, missing module mappings), though coverage of actions is solid rather than exhaustive.

4 / 5

Completeness

Explicitly answers both what ('Automate Pulumi provider repo upgrades with the upgrade-provider tool') and when ('Use when upgrading a pulumi provider repository...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural user phrasing is well covered: 'upgrading a pulumi provider repository', 'new upstream version', 'running upgrade-provider', plus concrete failure synonyms like 'patch conflicts' and 'missing module mappings'.

5 / 5

Distinctiveness Conflict Risk

Clear niche — Pulumi provider upgrades via the specific upgrade-provider tool — with distinct triggers and minimal overlap risk against other skills.

5 / 5

Total

19

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.