CtrlK
BlogDocsLog inGet started
Tessl Logo

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

1.33x
Quality

75%

Does it follow best practices?

Impact

96%

1.33x

Average score across 16 eval scenarios

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./terraform/provider-development/skills/provider-resources/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Discovery

85%

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 well-crafted skill description that clearly defines its scope for Terraform Provider development using the Plugin Framework. It excels at specificity and completeness with explicit 'Use when' guidance. The main weakness is trigger term coverage, which could benefit from additional natural language variations users might employ.

Suggestions

Add common trigger term variations like 'terraform plugin', 'provider development', 'custom provider', or file extensions like '.tf' to improve discoverability

Consider including terms like 'HashiCorp' or 'terraform-plugin-framework' that users familiar with the ecosystem might use

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'CRUD operations, schema design, state management, and acceptance testing for provider resources' - these are distinct, actionable capabilities.

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') with explicit trigger guidance.

3 / 3

Trigger Term Quality

Includes relevant terms like 'Terraform Provider', 'Plugin Framework', 'CRUD operations', 'acceptance testing', but misses common variations users might say like 'terraform plugin', 'provider development', 'resource implementation', or 'data source'.

2 / 3

Distinctiveness Conflict Risk

Very specific niche targeting Terraform Provider Plugin Framework development - unlikely to conflict with general Terraform usage skills or other infrastructure-as-code tools due to the specific 'Plugin Framework' and 'provider resources' terminology.

3 / 3

Total

11

/

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 is a comprehensive and highly actionable skill with excellent code examples covering the full Terraform provider development lifecycle. However, it's verbose for a SKILL.md file, including explanatory content Claude already knows and lacking explicit workflow sequencing for the development process. The content would benefit from being split into a concise overview with links to detailed reference files.

Suggestions

Add an explicit numbered workflow at the top showing the sequence: 1) Create resource file, 2) Implement schema, 3) Implement CRUD, 4) Write tests, 5) Run tests, 6) Write docs - with validation checkpoints between steps

Move detailed sections (Testing, Error Handling, Documentation Standards) to separate reference files and link to them from a concise overview

Remove the SDKv2 pattern example if Plugin Framework is the recommended approach, or clearly mark SDKv2 as legacy/deprecated

Trim the overview section - Claude doesn't need explanation of what CRUD operations or resources are

DimensionReasoningScore

Conciseness

The content is comprehensive but includes some redundancy and could be tightened. The overview section explains what resources are (which Claude knows), and some patterns are shown in both SDKv2 and Plugin Framework when only one may be needed.

2 / 3

Actionability

Excellent executable code examples throughout - complete CRUD operations, test patterns, finder functions, and state management are all copy-paste ready with proper imports and error handling.

3 / 3

Workflow Clarity

While the pre-submission checklist provides validation steps, the main content lacks explicit workflow sequencing. There's no clear 'do this, then validate, then proceed' pattern for the resource development process itself.

2 / 3

Progressive Disclosure

Content is well-organized with clear sections, but it's a monolithic document with extensive inline content. The references at the end are good, but detailed sections like testing and error handling could be split into separate files with links.

2 / 3

Total

9

/

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

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
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.