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
95%
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 well-crafted description with clear 'what' and 'when' clauses and distinctive trigger terms specific to Terraform acceptance testing. The main weakness is limited specificity in describing the full range of capabilities beyond just 'running' tests. The 'TestAcc' prefix is an excellent distinctive trigger that reduces conflict risk.
Suggestions
Expand the capabilities to include additional concrete actions like 'configure test environment variables, debug failing tests, interpret test output'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Terraform provider acceptance tests) and one action (running tests), but doesn't list multiple concrete actions like debugging, analyzing results, or configuring test environments. | 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'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'acceptance test', 'run a test', 'TestAcc' prefix. These are specific terms a developer working with Terraform would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Terraform provider acceptance tests with the distinctive 'TestAcc' prefix trigger. Unlikely to conflict with general testing skills or other Terraform skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
100%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-crafted skill that efficiently teaches acceptance test execution for Terraform providers. It provides concrete commands, clear sequential workflows with cumulative debugging options, and a clever 'flip test' validation technique. The content respects Claude's intelligence while providing all necessary specifics.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, assuming Claude knows Go testing, Terraform, and environment variables. No unnecessary explanations of basic concepts; every instruction earns its place. | 3 / 3 |
Actionability | Provides specific, executable commands (`go test -run=TestAccFeatureHappyPath`), exact environment variable names (`TF_ACC=1`, `TF_LOG=debug`), and concrete flags (`-count=1`, `-v`). Instructions are copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear sequential workflows for running tests, diagnosing failures (cumulative options in order), and flipping tests. The diagnosis workflow explicitly builds on previous steps, and the flip workflow includes validation (expect failure, then undo). | 3 / 3 |
Progressive Disclosure | For a focused, single-purpose skill under 50 lines, the content is well-organized with clear sections (running, diagnosing, flipping). No need for external references given the scope; structure is appropriate. | 3 / 3 |
Total | 12 / 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.
9f2ede9
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.