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).
97
76%
Does it follow best practices?
Impact
99%
6.18xAverage score across 15 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./terraform/provider-development/skills/provider-actions/SKILL.mdQuality
Discovery
75%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 description effectively targets a specific technical niche (Terraform Provider Plugin Framework development) with clear 'what' and 'when' guidance. However, it could benefit from more concrete action verbs describing specific capabilities and additional natural trigger terms that developers might use when seeking this skill.
Suggestions
Add specific concrete actions like 'create custom resources', 'implement CRUD operations', 'handle provider configuration', or 'manage resource state'
Include additional natural trigger terms users might say such as 'terraform plugin', 'provider development', 'custom provider', 'resource hooks'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Terraform Provider, Plugin Framework) and mentions 'imperative operations' and 'lifecycle events', but doesn't list specific concrete actions like 'create resources', 'validate configurations', or 'handle state management'. | 2 / 3 |
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') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes relevant technical terms like 'Terraform Provider', 'Plugin Framework', 'lifecycle events', 'create, update, destroy', but these are somewhat technical. Missing natural variations users might say like 'terraform plugin', 'provider development', 'resource lifecycle hooks'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Terraform Provider Plugin Framework development with lifecycle events. Unlikely to conflict with general Terraform usage skills or other infrastructure-as-code tools due to the specific 'Plugin Framework' and 'imperative operations' focus. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill for Terraform provider action implementation with excellent executable code examples and clear validation workflows. The main weaknesses are moderate verbosity (some explanatory content Claude doesn't need) and the monolithic structure that could benefit from splitting into focused reference files. The checklists and error handling patterns are particularly valuable.
Suggestions
Split into multiple files: move Testing section to TESTING.md, Common Action Patterns to PATTERNS.md, and reference them from the main skill
Remove the Overview section's explanation of what actions are - Claude understands this from context; jump directly to file structure and implementation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some verbose explanations and redundant sections. The overview explains what actions are (which Claude likely knows), and some sections like 'Common Action Patterns' are somewhat abstract rather than providing concrete implementations. | 2 / 3 |
Actionability | Provides fully executable Go code examples throughout, including schema definitions, invoke methods, error handling patterns, polling implementations, and test patterns. Code is copy-paste ready with proper imports and complete function signatures. | 3 / 3 |
Workflow Clarity | Excellent workflow structure with explicit validation checklists, pre-submission checklist, and clear sequencing. The 'Schema Validation Checklist' and 'Pre-Submission Checklist' provide explicit verification steps. Testing workflow includes compile checks before running tests. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's a monolithic document (~400 lines) that could benefit from splitting into separate files (e.g., TESTING.md, SCHEMA.md, PATTERNS.md). References to external docs exist but internal content organization could be improved. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- hashicorp/agent-skills
- Commit
9f2ede9
- 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.