provider-resources
Implement Terraform Provider resources and data sources using the Plugin Framework. Use when developing CRUD operations, schema design, state management, and acceptance testing for provider resources.
94
71%
Does it follow best practices?
Impact
96%
1.33xAverage score across 16 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./terraform/provider-development/skills/provider-resources/SKILL.mdQuality
Discovery
100%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 is a strong skill description that clearly identifies a specific technical domain (Terraform Provider development with the Plugin Framework), lists concrete actions, and includes an explicit 'Use when' clause with relevant trigger terms. The description is concise, uses third-person voice, and would be easily distinguishable from other skills in a large skill library.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: implementing resources and data sources, CRUD operations, schema design, state management, and acceptance testing. These are all concrete, well-defined activities in the Terraform provider development domain. | 3 / 3 |
Completeness | Clearly answers both 'what' (implement Terraform Provider resources and data sources using the Plugin Framework) and 'when' (Use when developing CRUD operations, schema design, state management, and acceptance testing for provider resources). The 'Use when' clause is explicit. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords a developer would use: 'Terraform Provider', 'Plugin Framework', 'CRUD operations', 'schema design', 'state management', 'acceptance testing', 'resources', 'data sources'. These are terms developers naturally use when working on Terraform providers. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — 'Terraform Provider' and 'Plugin Framework' create a very specific niche. This is unlikely to conflict with general infrastructure-as-code skills, generic testing skills, or other development skills due to the precise domain targeting. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a comprehensive but excessively verbose reference document that tries to cover everything inline rather than using progressive disclosure. While the code examples are high-quality and executable, the sheer volume (~500+ lines) makes it a poor fit for a SKILL.md that should be a concise overview. It would benefit greatly from splitting into a brief overview with links to separate reference files for CRUD patterns, testing, and schema design.
Suggestions
Split into a concise SKILL.md overview (under 100 lines) with links to separate files like CRUD_PATTERNS.md, TESTING.md, SCHEMA_DESIGN.md, and ERROR_HANDLING.md
Remove the SDKv2 resource pattern section entirely since the skill description specifies Plugin Framework - including both doubles the content without clear justification
Add an explicit numbered workflow for creating a new resource from scratch (e.g., 1. Create model struct, 2. Implement Schema, 3. Compile check, 4. Implement CRUD, 5. Write tests, 6. Run tests, 7. Write docs)
Remove explanatory text like 'Resources represent infrastructure objects that Terraform manages through Create, Read, Update, and Delete (CRUD) operations' - Claude knows what CRUD is
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at 500+ lines. Includes both SDKv2 and Plugin Framework patterns (doubling content), explains basic concepts like CRUD operations, and provides exhaustive code examples that could be split into reference files. Much of this (error handling patterns, test helpers, documentation templates) is content Claude already knows or could be in separate files. | 1 / 3 |
Actionability | All code examples are complete, executable Go code with proper imports and patterns. The test commands are copy-paste ready, and the CRUD operations show full function signatures with realistic error handling. Every section provides concrete, usable code. | 3 / 3 |
Workflow Clarity | The pre-submission checklist at the end provides a good sequence, but the overall document lacks a clear workflow for developing a resource from start to finish. There are no explicit validation checkpoints between steps (e.g., compile after schema, test after CRUD). The content reads as a reference catalog rather than a guided process. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with all content inline. The file structure, CRUD operations, schema design, state management, testing, error handling, and documentation standards are all in one massive document. External references are only to HashiCorp docs, not to companion files that could hold the detailed code examples. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (600 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Repository
- hashicorp/agent-skills
- Commit
de4323a
- 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.