Execute and diagnose Go acceptance tests for Terraform providers with structured troubleshooting.
Automate repetitive workflows and reduce manual effort
Example: Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example: Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example: Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add hashicorp/agent-skills --skill run-acceptance-testsCompatible with
Supported agents
Run focused acceptance tests using go test -run=TestAccFeatureHappyPath with TF_ACC=1 environment variable
Diagnose failures progressively: retry with -count=1 , enable verbose output with -v , activate debug logging via TF_LOG=debug , and persist Terraform workspace with TF_ACC_WORKING_DIR_PERSIST=1
Validate test reliability by intentionally breaking a TestCheckFunc, re-running the test
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionrun-acceptance-testsExecute the skills CLI command in your project's root directory to begin installation:
epx add hashicorp/agent-skills --skill run-acceptance-testsFetches run-acceptance-tests from hashicorp/agent-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/run-acceptance-tests
Restart Cursor to activate run-acceptance-tests. Access via /run-acceptance-testsin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
gcp-cloud-run
sickn33/antigravity-awesome-skills · Cloud · tag: run
playwright-cli
microsoft/playwright-cli · Testing · same category
accessibility-testing
aj-geddes/useful-ai-prompts · Testing · same category
qa-testing-playwright
vasilyu1983/ai-agents-public · Testing · same category
webapp-testing
skillcreatorai/ai-agent-skills · Testing · same category
idor-vulnerability-testing
davila7/claude-code-templates · Testing · same category
run-acceptance-tests reduced setup friction for our internal harness; good balance of opinion and flexibility.
We added run-acceptance-tests from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
I recommend run-acceptance-tests for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in run-acceptance-tests — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
run-acceptance-tests has been reliable in day-to-day use. Documentation quality is above average for community skills.
run-acceptance-tests fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
run-acceptance-tests has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in run-acceptance-tests — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
run-acceptance-tests is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Registry listing for run-acceptance-tests matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 53