new-terraform-provider
tessl i github:hashicorp/agent-skills --skill new-terraform-providerUse this when scaffolding a new Terraform provider.
Validation
94%| Criteria | Description | Result |
|---|---|---|
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
Total | 15 / 16 Passed | |
Implementation
65%This is a reasonably well-structured scaffolding skill that is concise and follows a logical sequence. However, it has gaps in actionability (missing specific commands and inline example content) and lacks error recovery guidance for the build/test steps. The reference to an external asset file is good for progressive disclosure but could be better signaled.
Suggestions
Add the specific command for initializing a Go module: 'go mod init github.com/org/terraform-provider-name'
Include error recovery guidance after 'go build' and 'go test' steps (e.g., 'If build fails: check error output, fix issues, and re-run')
Either inline the essential parts of assets/main.go or add a brief description of what the example contains
| 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 at 'assets/main.go' without showing its contents, and 'Initialize a new Go module' lacks the specific command ('go mod init'). | 2 / 3 |
Workflow Clarity | Steps are clearly sequenced with a good confirmation checkpoint at step 1, but lacks validation feedback loops - if 'go build' or 'go test' fails, there's no guidance on how to fix and retry. | 2 / 3 |
Progressive Disclosure | References an external asset file appropriately, but the reference '[the example](assets/main.go)' is not clearly signaled as to what it contains or why it's important. The skill is simple enough that this is minor. | 2 / 3 |
Total | 9 / 12 Passed |
Activation
22%This description is too minimal to be effective. While it correctly uses a 'Use when' clause and mentions the specific domain (Terraform provider), it completely fails to explain what concrete actions the skill performs. A user or Claude cannot determine what capabilities this skill offers beyond the vague term 'scaffolding'.
Suggestions
Add specific concrete 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 plugin', 'terraform-plugin-sdk', 'provider development', '.tf provider'
Restructure to lead with capabilities: 'Scaffolds new Terraform providers by generating boilerplate code, resource schemas, and test frameworks. Use when creating a new Terraform provider or starting provider development.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - it only says 'scaffolding' without explaining what that entails (e.g., generating boilerplate, creating resource schemas, setting up provider configuration). | 1 / 3 |
Completeness | Has a 'Use when' clause addressing when to use it, but 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', or 'provider SDK'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Terraform provider' is fairly specific and unlikely to conflict with general coding skills, but 'scaffolding' is generic enough that it could overlap with other project scaffolding or Terraform-related skills. | 2 / 3 |
Total | 6 / 12 Passed |
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.