new-terraform-provider
Use this when scaffolding a new Terraform provider.
76
43%
Does it follow best practices?
Impact
98%
1.06xAverage score across 6 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./terraform/provider-development/skills/new-terraform-provider/SKILL.mdQuality
Discovery
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 severely underdeveloped. While it correctly uses a 'Use when' clause and targets a specific domain (Terraform providers), it completely fails to explain what the skill actually does. The lack of concrete actions makes it nearly impossible for Claude to understand the skill's capabilities.
Suggestions
Add specific actions the skill performs, e.g., 'Generates provider boilerplate, creates resource and data source schemas, sets up acceptance testing framework, configures provider SDK structure'
Expand trigger terms to include variations like 'new provider', 'provider boilerplate', 'terraform plugin framework', 'provider SDK', 'custom terraform provider'
Restructure to clearly separate what from when: 'Scaffolds Terraform providers by generating boilerplate code, resource schemas, and test frameworks. Use when creating a new Terraform provider or setting up provider SDK structure.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - it only says 'scaffolding' without specifying what that entails (e.g., generating boilerplate, creating resource schemas, setting up provider configuration). | 1 / 3 |
Completeness | While it has a 'Use when' clause addressing when to use it, the 'what does this do' portion is essentially absent - 'scaffolding' alone doesn't explain what actions or outputs the skill provides. | 1 / 3 |
Trigger Term Quality | Contains 'Terraform provider' and 'scaffolding' which are relevant keywords, but misses common variations like 'new provider', 'provider boilerplate', 'terraform plugin', 'provider SDK', or 'tf provider'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Terraform provider' is fairly specific to a niche domain, but 'scaffolding' is generic enough that it could conflict with other scaffolding/boilerplate skills without more specific triggers. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is concise and well-structured for scaffolding a Terraform provider, with a clear step sequence. However, it relies on an external example file without showing its content, and some steps lack specific commands (e.g., 'Initialize a new Go module' should be 'go mod init <module-path>'). The workflow would benefit from explicit error handling guidance.
Suggestions
Replace 'Initialize a new Go module.' with the specific command: `go mod init github.com/org/terraform-provider-name`
Either inline the essential parts of assets/main.go or describe what customizations are needed in the example
Add error handling guidance: 'If go build fails, check for missing dependencies and run go mod tidy again'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only the necessary steps without explaining what Terraform or Go modules are. Every line serves a purpose. | 3 / 3 |
Actionability | Steps are concrete but incomplete - references an example file (assets/main.go) without showing its content, and 'Initialize a new Go module' lacks the specific command (go mod init). | 2 / 3 |
Workflow Clarity | Steps are clearly sequenced with build and test validation at the end, but lacks explicit error handling/feedback loops for when go build or go test fails. | 2 / 3 |
Progressive Disclosure | References an external asset file appropriately, but the reference format '[the example](assets/main.go)' is unclear about what the example contains or when to deviate from it. | 2 / 3 |
Total | 9 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- hashicorp/agent-skills
- Commit
9f2ede9
- 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.