CtrlK
BlogDocsLog inGet started
Tessl Logo

provider-resources

Implement Terraform Provider resources and data sources using the Plugin Framework: CRUD operations, schema design, plan modifiers and validators, not-found handling, waiters for eventually consistent APIs, import support, resource design principles, and required acceptance test coverage. Use when adding or changing a resource or data source, deciding whether an API concept should be a resource, wiring a resource to the provider's configured client, handling drift or resource-not-found, or reviewing a resource implementation before submission.

79

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-5

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

The content is a high-quality implementation guide: lean, executable, and well-sequenced with explicit validation checkpoints and a pre-submission checklist. Progressive disclosure is exemplary — the body is an overview that defers depth to two real, one-level-deep reference files signposted at the points where they apply.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence (no 'what is Terraform' padding), every section earns its tokens, and it defers deep material to references rather than restating it. It is lean and efficient throughout.

5 / 5

Actionability

It provides fully executable, copy-paste-ready Go code for every CRUD operation plus Schema, Finders, Waiters, and an acceptance test, with specific concrete examples (e.g. `resource.ImportStatePassthroughID(ctx, path.Root("id"), req, resp)`) covering the common cases.

5 / 5

Workflow Clarity

The implementation sequence is explicit (File Structure -> Resource Structure -> CRUD -> Testing) with an explicit Pre-Submission Checklist, validation feedback loops ('Read must handle out-of-band deletion by removing the resource from state', 'Delete tolerates already-deleted'), and per-step error-recovery guidance. The destructive/batch validation cap is satisfied by the not-found and _disappears test patterns.

5 / 5

Progressive Disclosure

SKILL.md is a clear overview with well-signaled, one-level-deep references — 'references/design-principles.md' and 'references/retries-and-waiters.md' are each described, exist as real files, and are referenced inline at the point of need (e.g. the waiter details). Content is appropriately split with easy navigation.

5 / 5

Total

20

/

20

Passed

Description

100%Weight 40%Scale 1-5

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 exemplary: concise yet comprehensive, third-person voice, with a clear 'what' and an explicit 'Use when ...' clause covering realistic trigger scenarios. It carves a distinct niche and routes edge cases to sibling skills, leaving little room for misfires.

DimensionReasoningScore

Specificity

The description lists multiple concrete capabilities — 'CRUD operations, schema design, plan modifiers and validators, not-found handling, waiters for eventually consistent APIs, import support' — providing comprehensive coverage of the skill's surface.

5 / 5

Completeness

It explicitly answers 'what' (the enumerated capabilities) and 'when' via a concrete 'Use when ...' clause with five trigger scenarios, matching the score-5 anchor.

5 / 5

Trigger Term Quality

Natural trigger phrases users would actually say are comprehensively enumerated: 'adding or changing a resource or data source', 'deciding whether an API concept should be a resource', 'handling drift or resource-not-found', 'reviewing a resource implementation before submission'.

5 / 5

Distinctiveness Conflict Risk

The niche is highly specific (Terraform Provider resources/data sources via the Plugin Framework) with distinct triggers and explicit referrals to sibling skills (provider-configuration, provider-framework-migration), minimizing conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (522 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

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.