new-terraform-provider

Use this when scaffolding a new Terraform provider.

1.07x

Quality

43%

Does it follow best practices?

Impact

98%

1.07x

Average score across 6 eval scenarios

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./terraform/provider-development/skills/new-terraform-provider/SKILL.md

Quality

Content

64%

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

This is a reasonably concise and well-structured scaffolding skill with a clear step sequence. Its main weaknesses are the missing bundle asset (`assets/main.go`) which is critical to the workflow, the vague 'Initialize a new Go module' step lacking a concrete command, and the absence of error recovery guidance after build/test steps.

Suggestions

Provide the `assets/main.go` file in the bundle, or inline the essential main.go template directly in the skill if it's short enough.

Replace 'Initialize a new Go module' with the specific command, e.g., `go mod init github.com/org/terraform-provider-<name>`.

Add a feedback loop after `go build` and `go test` steps: e.g., 'If build fails, review errors, fix, and re-run. If tests fail, check test output and correct before proceeding.'

Dimension	Reasoning	Score
Conciseness	The skill is lean and efficient. It doesn't explain what Terraform is, what a provider is, or how Go modules work. Every step earns its place and assumes Claude's competence.	3 / 3
Actionability	The steps include specific commands (`go get`, `go mod tidy`, `go build`, `go test`), but the reference to `assets/main.go` is unresolvable since no bundle files are provided. The Go module initialization step ('Initialize a new Go module') lacks the specific command (`go mod init`). Key details like the module path are missing.	2 / 3
Workflow Clarity	Steps are clearly sequenced and include a conditional check at the start, plus build and test validation at the end. However, there's no explicit error recovery or feedback loop — if `go build` or `go test` fails, there's no guidance on what to do next, which matters for a scaffolding workflow.	2 / 3
Progressive Disclosure	The skill references `assets/main.go` as an example file, which is good progressive disclosure in principle, but the bundle file is not provided, making the reference broken. The content is appropriately concise for the SKILL.md level, but the missing asset undermines the structure.	2 / 3
	Total	9 / 12 Passed

Description

22%

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 description is extremely minimal — it provides a trigger condition but fails to describe what the skill actually does in any concrete detail. It lacks specific actions, file types generated, or tooling involved. The Terraform provider domain gives it some distinctiveness, but the description needs substantial expansion to be useful for skill selection.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Generates provider scaffolding including resource/data source skeletons, provider configuration, acceptance test templates, and Makefile for terraform-plugin-framework based providers.'

Expand trigger terms to include natural variations like 'terraform plugin', 'provider boilerplate', 'new terraform provider project', 'terraform-plugin-sdk', 'terraform-plugin-framework'.

Rewrite in third person voice (e.g., 'Scaffolds a new Terraform provider project...') and add an explicit 'Use when...' clause with richer trigger guidance.

Dimension	Reasoning	Score
Specificity	The description says 'scaffolding a new Terraform provider' but does not list any concrete actions (e.g., generating resource schemas, creating provider configuration, setting up acceptance tests). It's a single vague action.	1 / 3
Completeness	It has a 'when' clause ('Use this when scaffolding a new Terraform provider') but the 'what' is essentially missing — it doesn't describe what the skill actually does or produces. The 'what' is extremely weak, effectively just restating the trigger.	1 / 3
Trigger Term Quality	It includes 'Terraform provider' and 'scaffolding' which are relevant keywords a user might use, but misses common variations like 'terraform plugin', 'provider boilerplate', 'new provider project', 'terraform-plugin-sdk', 'terraform-plugin-framework'.	2 / 3
Distinctiveness Conflict Risk	'Terraform provider' is a fairly specific domain, which helps with distinctiveness, but 'scaffolding' is vague enough that it could overlap with general code scaffolding or project generation skills.	2 / 3
	Total	6 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: hashicorp/agent-skills
Commit: 339a113

Reviewed: 26 days ago

Table of Contents

Discovery Implementation Validation

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.