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 tests) and provides explicit trigger conditions including the 'TestAcc' prefix. Its main weakness is that the 'what' portion is somewhat thin — it says 'guide for running' but doesn't enumerate specific capabilities like configuring environment variables, filtering tests, or interpreting output.
Suggestions
Add more specific concrete actions beyond just 'running', e.g., 'Runs acceptance tests for a Terraform provider, including configuring required environment variables, filtering specific test cases, and interpreting test output.'
| 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, filtering, interpreting results, or setting environment variables. | 2 / 3 |
Completeness | Clearly answers both what ('Guide for running acceptance tests for a Terraform provider') and when ('Use this 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', and the specific prefix 'TestAcc' which is exactly what users would type when asking about this task. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche — Terraform provider acceptance tests with the 'TestAcc' prefix is highly specific and unlikely to conflict with general testing skills or other Terraform-related 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 clearly covers three workflows for acceptance testing in Terraform providers. Its main strength is the clear sequencing of diagnostic escalation steps and the flip-test procedure. The only notable weakness is that it could be slightly more actionable with a complete copy-paste-ready command example combining the env vars and go test invocation.
Suggestions
Add a complete, copy-paste-ready command example, e.g., `TF_ACC=1 go test -run=TestAccFeatureHappyPath ./...` to improve actionability.
Consider adding a brief concrete example of editing a TestCheckFunc value for the flip procedure to make that workflow fully actionable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It assumes Claude knows Go testing, Terraform, and environment variables. Every line provides actionable information without unnecessary explanation. | 3 / 3 |
Actionability | Provides specific commands, environment variables, and flags, but lacks a complete executable example (e.g., the full `go test` command with env vars inline). The 'flip' procedure describes editing TestCheckFuncs but doesn't give 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 well-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 simple, focused skill under 50 lines with no need for external references, the content is well-organized into three clear sections (running, diagnosing, flipping) with logical grouping. No bundle files are needed. | 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.
339a113
Table of Contents
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.