CtrlK
BlogDocsLog inGet started
Tessl Logo

new-terraform-provider

Use this when scaffolding a new Terraform provider with the Plugin Framework: workspace layout, go module setup, provider server main.go, and a provider.go with schema and Configure. Also use when a user wants to start building a provider for a new API or asks how to begin a terraform-provider-* project.

75

Quality

93%

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

93%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 efficient, highly actionable scaffolding workflow with concrete commands and well-structured one-level-deep references to real example files. The only gap is the absence of an explicit error-recovery feedback loop after the build/test validation steps, which caps workflow_clarity at 4.

Suggestions

Add an explicit feedback loop after the validation steps, e.g. 'If `go build` or `go test` fails, fix the reported errors and re-run until both pass' to lift workflow_clarity toward 5.

Consider a short note on what to check when `go test ./...` fails (e.g. unrenamed DEMO_* references) so error recovery is guided rather than implicit.

DimensionReasoningScore

Conciseness

Lean numbered steps with specific commands and no padding or explanation of concepts Claude already knows; every token earns its place, matching the level-5 anchor.

5 / 5

Actionability

Fully executable guidance — concrete commands ('go get -u ...@latest', 'go mod tidy', 'go build -o /dev/null', 'go test ./...') plus complete copy-paste-ready example files (assets/main.go, assets/provider.go) and specific rename instructions — matching the level-5 anchor.

5 / 5

Workflow Clarity

Clear sequenced steps with explicit validation checkpoints (go build, go test) and a conditional confirm checkpoint at step 1, but it lacks an explicit error-recovery feedback loop, fitting level-4 rather than the level-5 'feedback loops for error recovery' anchor.

4 / 5

Progressive Disclosure

A concise overview pointing to one-level-deep real asset files (assets/main.go, assets/provider.go) with the bulk Go code split out and clearly signaled references, matching the level-5 anchor.

5 / 5

Total

19

/

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, specific description that explicitly covers both what the skill does and when to invoke it, with natural trigger phrasings and a clearly distinct niche. The only mild gap is keyword synonym breadth, which keeps trigger_term_quality at 4 rather than 5.

DimensionReasoningScore

Specificity

Lists multiple concrete scaffolding components — 'workspace layout, go module setup, provider server main.go, and a provider.go with schema and Configure' — giving comprehensive coverage of the concrete actions, matching the level-5 anchor rather than the level-4 'minor gaps' anchor.

5 / 5

Completeness

Explicitly answers both 'what' (the listed scaffolding deliverables) and 'when' ('Use this when...', 'Also use when a user wants to start building...') with concrete trigger phrases, matching the level-5 anchor.

5 / 5

Trigger Term Quality

Includes natural phrasings users would say ('scaffolding a new Terraform provider', 'start building a provider for a new API', 'asks how to begin a terraform-provider-* project') with good coverage, but stops short of the level-5 comprehensive-synonyms bar.

4 / 5

Distinctiveness Conflict Risk

Clear niche — a new Terraform provider using the Plugin Framework — with distinct triggers ('terraform-provider-* project', 'Plugin Framework') and minimal overlap risk, fitting the level-5 anchor.

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
hashicorp/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.