provider-actions

Implement Terraform Provider actions using the Plugin Framework. Use when developing imperative operations that execute at lifecycle events (before/after create, update, destroy).

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/terraform/skills/provider-actions/SKILL.md

Quality

Content

71%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 comprehensive, executable guide with strong code examples, checklists, and validation steps for implementing Terraform Provider actions. Its main weakness is monolithic structure with no progressive disclosure via bundle files despite its length.

Suggestions

Move the detailed polling/timeout code, documentation standards, and changelog format into reference files under ./references/ and link to them from SKILL.md to improve progressive disclosure.

Tighten the 'Common Action Patterns' bullet lists into concrete code snippets or remove the generic guidance that does not add executable detail.

Replace the placeholder comments in the Invoke example ('// Implement action logic with error handling') with a minimal concrete call so the example is fully executable as written.

Dimension	Reasoning	Score
Conciseness	Mostly lean and technical, assuming Claude's competence without explaining what Terraform is; a few generic bullet lists ('Common Action Patterns') and inline comments could be trimmed, but not enough padding to drop to 3.	4 / 5
Actionability	Provides concrete, mostly copy-paste-ready Go and HCL examples plus exact commands ('go test -c', 'TF_ACC=1 go test ...'); minor gaps like placeholder comments ('// Implement action logic') in the Invoke example keep it just below 5.	4 / 5
Workflow Clarity	Clear sequenced setup steps, schema-validation and pre-submission checklists, and compile-then-test ordering with cleanup (sweepers); validation checkpoints are present, with only minor gaps preventing a 5.	4 / 5
Progressive Disclosure	Well-sectioned single file with clearly signaled cross-skill references ('use the provider-test-patterns skill, if available'), but no bundle files are used and ~500 lines of detail (polling code, documentation standards, changelog format) that could live in references is inlined.	3 / 5
	Total	15 / 20 Passed

Description

87%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 concretely states both capability and trigger conditions with specific lifecycle-event keywords. It is concise, distinct, and uses an explicit 'Use when...' clause with concrete triggers.

Dimension	Reasoning	Score
Specificity	Names the domain ('Terraform Provider actions', 'Plugin Framework') and concrete actions ('implement', 'imperative operations that execute at lifecycle events') with specific event enumeration, but stops short of the fully comprehensive multi-action coverage of a 5.	4 / 5
Completeness	Clearly answers both what ('Implement Terraform Provider actions using the Plugin Framework') and when ('Use when developing imperative operations that execute at lifecycle events (before/after create, update, destroy)') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural keyword coverage ('Terraform Provider actions', 'Plugin Framework', 'lifecycle events', 'create, update, destroy') that a developer would naturally say, with only minor variations/synonyms missing.	4 / 5
Distinctiveness Conflict Risk	A clear niche (Terraform Provider Plugin Framework actions at lifecycle events) with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (516 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: hashicorp/agent-skills
Path: plugins/terraform/skills/provider-actions/SKILL.md
Commit: 3268468

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.