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

3.19x

Quality

83%

Does it follow best practices?

Impact

83%

3.19x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

77%

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

The body is highly actionable with executable examples, clear sequencing, and explicit validation checklists. Its main weaknesses are verbosity/redundancy and a lack of progressive disclosure — a ~530-line monolith with no offloading to reference files.

Suggestions

Split the testing patterns, documentation standards, and schema-issues detail into reference files under references/ and link to them one level deep to improve progressive disclosure and reduce inline bulk.

Consolidate the three overlapping schema sections (schema definition example, common schema issues, schema validation checklist) to remove redundancy and tighten conciseness.

Trim generic 'Common Action Patterns' bullets that restate obvious steps, keeping only guidance that adds non-obvious domain knowledge.

Dimension	Reasoning	Score
Conciseness	The body is ~530 lines and mostly domain-specific rather than explaining basics Claude knows, but it carries redundancy (schema example + common schema issues + schema validation checklist) and somewhat generic sections like 'Common Action Patterns', so it could be tightened rather than earning the top 'lean and efficient' anchor.	2 / 3
Actionability	It provides concrete, copy-paste-ready Go and HCL examples (Schema, Invoke, error handling, wait.WaitForStatus polling, acceptance tests, sweep functions, doc frontmatter) with explicitly justified placeholders for service-specific parts.	3 / 3
Workflow Clarity	Multi-step work is clearly sequenced (First Action Setup, testing flow) with explicit validation checkpoints and feedback loops ('go build' to catch type mismatches, 'terrafmt fmt/diff', Schema Validation and Pre-Submission checklists).	3 / 3
Progressive Disclosure	No bundle files exist and the skill is far over 50 lines, yet all detail (testing patterns, documentation standards, schema issues) is inline in one monolithic SKILL.md rather than split into one-level-deep reference files; sections are well-organized but content that should be separate is inline.	2 / 3
	Total	10 / 12 Passed

Description

90%

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 clear, distinct, and answers both what and when with an explicit 'Use when' trigger. Its only weakness is that it frames one capability rather than enumerating several concrete actions, which keeps specificity at the middle level.

Dimension	Reasoning	Score
Specificity	It names the domain ('Terraform Provider actions', 'Plugin Framework') and lifecycle events (before/after create, update, destroy), but describes essentially a single capability rather than listing multiple distinct concrete actions, matching the 'names domain and some actions, but not comprehensive' anchor.	2 / 3
Completeness	It explicitly answers both 'what' ('Implement Terraform Provider actions using the Plugin Framework') and 'when' via an explicit 'Use when...' trigger clause, matching the top anchor.	3 / 3
Trigger Term Quality	Terms a user would naturally say when needing this skill are well covered: 'Terraform Provider actions', 'Plugin Framework', 'lifecycle events', and 'before/after create, update, destroy'.	3 / 3
Distinctiveness Conflict Risk	The niche is narrow and specific (Terraform Provider actions via the Plugin Framework) with distinct triggers, making it unlikely to fire for an unrelated skill.	3 / 3
	Total	11 / 12 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 (530 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: hashicorp/agent-skills
Path: terraform/provider-development/skills/provider-actions/SKILL.md
Commit: 8c6573a

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.