CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

regenerate-all-tfgen-resources

Use when changing tools/iac-codegen behavior or its version. Regenerate every listed Terraform resource and verify committed output.

Quality

87%

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

86%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.

An exceptionally lean, well-structured skill body: every line is skill-specific, both commands are executable, and an explicit post-commit verification step covers this batch operation, with the CI context in 'Why' justifying the process. The remaining gaps are minor — the location of version.Current, what 'review' concretely means for generated packages, and no feedback loop for a failed verification.

Suggestions

Name the file where `version.Current` is defined so the 'Bump `version.Current`' step is copy-paste executable.

Add an explicit feedback loop, e.g. 'If check-generated-resources.sh reports differences, fix the generator input, re-run go generate, and re-commit' — this would raise both actionability and workflow clarity.

Make the review step concrete: specify what 'Review every generated package, versions.yaml, registry, example' means (e.g., diff regenerated output against committed files) and what 'the registry' refers to.

DimensionReasoningScore

Conciseness

Every sentence carries skill-specific information Claude could not infer — trigger conditions ('version.Current, the pinned SDK, or a resource override or acceptance file'), exact commands, and CI rationale ('CI checks each package version and compares regenerated output with committed files on every PR'). There is no padding and no explanation of concepts Claude already knows; even the 'Why' section earns its tokens by justifying the verification requirement. Nothing needs trimming, so anchor 4 does not apply.

5 / 5

Actionability

Provides two fully executable commands — 'Run `go generate ./internal/provider/` from the provider root' and 'Run `bash tools/iac-codegen/scripts/check-generated-resources.sh`' — plus concrete file targets ('versions.yaml', 'internal/provider/codegen.go'), matching anchor 4 ('mostly executable guidance with minor gaps'). It falls short of anchor 5's copy-paste-ready coverage because the file containing 'version.Current' is never named, and 'Review every generated package, versions.yaml, registry, example, and affected documentation page' does not say what review entails or what 'the registry' is.

4 / 5

Workflow Clarity

The 'Fix' section lays out a discernible sequence (bump version → generate → review outputs → add codegen.go entries → include output in the change → verify) with an explicit validation step ('Run bash tools/iac-codegen/scripts/check-generated-resources.sh after the change is committed to verify the full result'), so the batch-operation cap at 3 does not apply — validation is present. It falls short of anchor 5 because there is no error-recovery feedback loop (nothing says what to do when the check fails) and the sequence is prose rather than an explicitly ordered or checklist form; it is above anchor 3 because a clear checkpoint is explicitly stated.

4 / 5

Progressive Disclosure

The skill is under 50 lines, self-contained, and needs no external references, and the body is organized into clearly labeled sections ('Trigger', 'Fix', 'Why') — per the rubric guideline, short skills with no need for external references score 5 with just well-organized sections. No bundle files exist, so there are no buried or nested references to penalize; this is not anchor 4, which requires 'minor organization gaps' that are absent here.

5 / 5

Total

18

/

20

Passed

Description

82%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 description with an explicit 'Use when' trigger naming the specific tool and change types, plus a clear, concrete statement of what the skill does. Its only weakness is moderate action coverage — two concrete actions where a fuller enumeration (version bump, codegen.go entries, verification script) would improve specificity.

DimensionReasoningScore

Specificity

Names the domain ('tools/iac-codegen', 'Terraform resource') and exactly two concrete actions — 'Regenerate every listed Terraform resource and verify committed output' — which matches anchor 3 ('1-2 concrete actions, but not comprehensive'). It falls short of anchor 4's 'several specific actions' because steps the skill actually performs (bumping version.Current, adding codegen.go entries, running the check script) are absent.

3 / 5

Completeness

Both parts are explicit: what — 'Regenerate every listed Terraform resource and verify committed output'; when — 'Use when changing tools/iac-codegen behavior or its version', a concrete trigger phrase naming the exact tool and change types. This mirrors the anchor-5 example's 'Use when X. Do Y and Z.' structure; anchor 4's complaint ('when could be more explicit or specific') does not apply since the when-clause is maximally explicit for the triggers it names.

5 / 5

Trigger Term Quality

'changing tools/iac-codegen behavior or its version', 'Regenerate', and 'Terraform resource' give good keyword coverage of what a user in this repo would naturally say, matching anchor 4 ('good keyword coverage; a few natural terms missing'). It is not anchor 5 because common variations such as 'generated resources', 'SDK', or 'provider' are missing, and not anchor 3 because multiple relevant, natural keywords are present rather than just one generic term.

4 / 5

Distinctiveness Conflict Risk

'tools/iac-codegen' and 'Regenerate every listed Terraform resource' carve out a clear niche with distinct, tool-specific triggers; virtually no other skill would match this regeneration workflow, so conflict risk is minimal — a direct match to anchor 5. It is well above anchor 4's 'minor overlap risk with closely related skills' since no closely related skill domain is named.

5 / 5

Total

17

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

coralogix/terraform-provider-coralogix

Path

.claude/skills/regenerate-all-tfgen-resources/SKILL.md

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.