CtrlK
BlogDocsLog inGet started
Tessl Logo

provider-docs

Create, update, and review Terraform provider documentation for Terraform Registry using HashiCorp-recommended patterns, tfplugindocs templates, and schema descriptions. Use when adding or changing provider configuration, resources, data sources, ephemeral resources, list resources, functions, actions, or guides; when validating generated docs; and when troubleshooting missing or incorrect Registry documentation.

70

Quality

86%

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

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

A well-structured, actionable workflow that delegates detail to a clearly signaled reference. Tightening the duplicated path list and making the validation step's error-recovery loop explicit would raise the conciseness and workflow-clarity scores.

Suggestions

Remove the full template-path enumeration from Step 3 and reference the 'Template Paths' section of references/hashicorp-provider-docs.md instead, to avoid duplicating the reference and improve conciseness.

Add an explicit validate->fix->retry branch in Step 5 (e.g., 'If a check fails, fix the schema/template and re-run generation before re-validating') to turn the validation step into a clear feedback loop.

Give Step 5 a concrete verification command (e.g., running tfplugindocs generate again or a markdown lint/format check) so the validation step is executable rather than descriptive.

DimensionReasoningScore

Conciseness

A lean, directive workflow that assumes Claude's competence and mostly earns its tokens; the only mild redundancy is the full template-path list duplicated verbatim in the reference file, which could be left to the reference.

4 / 5

Actionability

Provides concrete, executable commands ('go generate ./...' and the explicit 'go run ... tfplugindocs generate --provider-name <provider_name>'), concrete template paths, and example-file conventions; the verification step (Step 5) states what to check but gives no command to run.

4 / 5

Workflow Clarity

A clearly sequenced 7-step workflow with a dedicated validation step (Step 5 with three verify bullets) and a re-run loop ('Re-run generation after every schema or template edit'); it lacks an explicit validate->fix->retry recovery branch, keeping it just below a 5.

4 / 5

Progressive Disclosure

The body is a focused overview that points to a single real, one-level-deep reference (references/hashicorp-provider-docs.md) with specific section pointers ('Example File Conventions', 'Action Pages section') and explicit on-demand loading guidance.

5 / 5

Total

17

/

20

Passed

Description

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

A strong, third-person description that clearly states capabilities and provides explicit, concrete use-when triggers across the full provider-documentation lifecycle. Minor additional concrete actions could push specificity to a perfect score.

DimensionReasoningScore

Specificity

Names the domain and three concrete lifecycle actions ('Create, update, and review Terraform provider documentation') plus mechanisms (tfplugindocs templates, schema descriptions), but stops short of the multi-action breadth of the score-5 anchor.

4 / 5

Completeness

Explicitly answers both 'what' (create/update/review provider documentation for the Registry) and 'when' with concrete trigger phrases ('Use when adding or changing...; when validating generated docs; and when troubleshooting missing or incorrect Registry documentation').

5 / 5

Trigger Term Quality

Comprehensive natural terms a Terraform provider developer would say — 'resources, data sources, ephemeral resources, list resources, functions, actions, or guides', 'validating generated docs', 'troubleshooting ... Registry documentation' — covering synonyms and object types.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (Terraform Registry provider documentation) with distinct, domain-specific triggers and minimal overlap risk with other skills.

5 / 5

Total

19

/

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

metadata_version

'metadata.version' is missing

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.