run-acceptance-tests
Guide for running acceptance tests for a Terraform provider. Use this when asked to run an acceptance test or to run a test with the prefix `TestAcc`.
99
87%
Does it follow best practices?
Impact
100%
2.17xAverage score across 16 eval scenarios
Passed
No known issues
Quality
Discovery
89%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 is a solid, focused description that clearly identifies its niche (Terraform provider acceptance testing) and provides explicit trigger conditions including the TestAcc prefix convention. Its main weakness is that it only describes one action (running tests) rather than listing additional concrete capabilities like debugging test failures or configuring test environments.
Suggestions
Add more specific concrete actions beyond 'running' tests, such as 'configuring test environment variables, debugging test failures, interpreting test output' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (Terraform provider acceptance tests) and one action (running tests), but doesn't list multiple concrete actions like debugging failures, interpreting output, configuring test environments, etc. | 2 / 3 |
Completeness | Clearly answers both 'what' (guide for running acceptance tests for a Terraform provider) and 'when' (when asked to run an acceptance test or to run a test with the prefix TestAcc), with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'acceptance tests', 'Terraform provider', 'run a test', 'TestAcc' prefix. These are terms a user would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — the combination of 'Terraform provider', 'acceptance tests', and the 'TestAcc' prefix creates a very clear niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, concise skill that covers three distinct workflows for acceptance testing in Terraform providers. Its main strength is clear workflow sequencing with cumulative diagnostic steps and a feedback loop for the flip procedure. The primary weakness is that commands could be more copy-paste ready with full command-line examples including environment variables.
Suggestions
Provide a complete, copy-paste ready command example, e.g., `TF_ACC=1 go test -run=TestAccFeatureHappyPath ./path/to/package` to improve actionability
Add a brief concrete code example for the 'flip' procedure showing what a TestCheckFunc edit looks like (e.g., changing an expected value)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every sentence provides actionable, non-obvious information. No explanation of what Go tests are, what Terraform is, or other concepts Claude already knows. The content is lean and efficient. | 3 / 3 |
Actionability | Provides specific commands and environment variables, but lacks complete executable examples (e.g., full command lines with env vars inline like `TF_ACC=1 go test -run=TestAccFeatureHappyPath ./...`). The 'flip' procedure describes editing TestCheckFuncs but doesn't show a concrete code example of what to change. | 2 / 3 |
Workflow Clarity | Three distinct workflows (running, diagnosing, flipping) are clearly sequenced with explicit steps. The diagnosis workflow is cumulative and ordered, the flip workflow includes a validation/feedback loop (check if test fails, then undo or report). Missing env var handling is addressed with a conditional step. | 3 / 3 |
Progressive Disclosure | For a skill under 50 lines with a focused scope, the content is well-organized into three clear sections (running, diagnosing, flipping) without needing external references. The structure is easy to scan and navigate. | 3 / 3 |
Total | 11 / 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
b129bb5
- 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.