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`.
Install with Tessl CLI
npx tessl i github:hashicorp/agent-skills --skill run-acceptance-testsOverall
score
89%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 100%
↑ 2.17xAgent success when using this skill
Validation for skill structure
Discovery
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.
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 actions the skill enables beyond just 'running' tests.
Suggestions
Expand the capabilities list to include additional concrete actions like 'configure test environment variables', 'debug failing tests', or 'analyze 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
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 skill that efficiently covers acceptance test workflows for Terraform providers. The diagnostic escalation path is particularly well-designed with cumulative options. The main weakness is the 'flip' test section which could benefit from a concrete code example showing what to edit in a TestCheckFunc.
Suggestions
Add a concrete code example showing how to edit a TestCheckFunc value to flip a test (e.g., changing an expected string value)
| 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 commands and environment variables, but lacks complete executable examples. The 'flip' test procedure describes editing TestCheckFuncs without showing concrete code for what to edit or how. | 2 / 3 |
Workflow Clarity | Clear sequential workflows for running tests, diagnosing failures (cumulative options in order), and flipping tests. The diagnostic escalation path is well-structured with explicit checkpoints. | 3 / 3 |
Progressive Disclosure | For a skill under 50 lines with a focused scope, the content is well-organized into distinct sections (running, diagnosing, flipping) without needing external references. Structure is appropriate for the content volume. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
94%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 |
|---|---|---|
body_examples | No examples detected (no code fences and no 'Example' wording) | Warning |
Total | 15 / 16 Passed | |
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.