new-terraform-provider

Use this when scaffolding a new Terraform provider.

1.44x

Quality

71%

Does it follow best practices?

Impact

85%

1.44x

Average score across 2 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Fix and improve this skill with Tessl

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

Quality

Content

85%

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

The body is token-efficient, well-structured, and uses a real referenced example file with explicit build/test verification. The main gap is the underspecified `go mod init` step, which is the only non-executable instruction in an otherwise copy-paste-ready workflow.

Suggestions

Replace "Initialize a new Go module.." with the concrete command, e.g. `go mod init example.org/terraform-provider-<name>`.

Add a brief note on what to do if `go build` or `go test` fails (fix errors and re-run) to close the error-recovery feedback loop.

Optionally state the expected TODO items in main.go so the "Remove TODO comments" step is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is a lean numbered list of commands with no concept explanation or padding; every line earns its place.	3 / 3
Actionability	Most steps are copy-paste commands and reference a real main.go example, but "Initialize a new Go module.." omits the concrete `go mod init <module-path>` command, leaving a key detail incomplete.	2 / 3
Workflow Clarity	A clear sequenced workflow with an upfront confirmation gate and explicit verification steps (`go build -o /dev/null`, `go test ./...`); appropriate for a simple single-purpose skill.	3 / 3
Progressive Disclosure	Short, well-organized content with a single clearly-signaled, one-level reference to a real bundle file (`assets/main.go`); no nested reference chains.	3 / 3
	Total	11 / 12 Passed

Description

57%

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

The description is concise and has an explicit trigger with a distinct niche, but it states only a single action and does not separately elaborate on what the skill actually does. Expanding the capability statement while keeping the trigger would raise specificity and completeness.

Suggestions

Add a brief capability clause distinct from the trigger, e.g. "Scaffolds a new Terraform provider using the Plugin Framework: initializes the Go module, writes main.go, and verifies build/tests."

Include a couple of natural trigger variations such as "create" or "build a Terraform provider" to broaden keyword coverage.

Keep the explicit "Use this when..." trigger since it already satisfies the trigger-guidance requirement.

Dimension	Reasoning	Score
Specificity	"scaffolding a new Terraform provider" names one concrete action and a clear domain, but does not list multiple specific capabilities as the top anchor requires.	2 / 3
Completeness	An explicit "Use this when" trigger is present, but the "what does this do" collapses into the trigger phrase with no distinct capability description, so it does not clearly answer both.	2 / 3
Trigger Term Quality	"scaffolding" and "Terraform provider" are natural terms a user would say, but coverage is thin with no common variations (e.g. "build" or "create a provider").	2 / 3
Distinctiveness Conflict Risk	"scaffolding a new Terraform provider" carves out a clear, narrow niche that is unlikely to trigger for unrelated skills.	3 / 3
	Total	9 / 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: hashicorp/agent-skills
Commit: 957d5f9

Reviewed: 4 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.