bats-testing-patterns
Master Bash Automated Testing System (Bats) for comprehensive shell script testing. Use when writing tests for shell scripts, CI/CD pipelines, or requiring test-driven development of shell utilities.
80
Quality
73%
Does it follow best practices?
Impact
90%
1.04xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/bats-testing-patterns/SKILL.mdQuality
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 skill description with excellent trigger terms and completeness. The explicit 'Use when...' clause provides clear guidance for skill selection. The main weakness is the lack of specific concrete actions - it describes the domain well but doesn't enumerate what specific testing capabilities it provides.
Suggestions
Add specific concrete actions like 'write test cases, mock commands, validate exit codes, generate test output' to improve specificity
Consider adding file extensions or patterns like '.bats files' as additional trigger terms
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Bats, shell script testing) and mentions some contexts (CI/CD pipelines, test-driven development), but lacks specific concrete actions like 'write test cases', 'mock commands', 'generate test reports', or 'validate exit codes'. | 2 / 3 |
Completeness | Clearly answers both what ('Master Bash Automated Testing System for comprehensive shell script testing') and when ('Use when writing tests for shell scripts, CI/CD pipelines, or requiring test-driven development of shell utilities') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Bats', 'shell script testing', 'tests', 'CI/CD pipelines', 'test-driven development', 'shell utilities'. These cover common variations of how users would request this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Bats framework specifically for shell script testing. The combination of 'Bats', 'shell script testing', and 'shell utilities' creates a distinct trigger profile unlikely to conflict with general testing or scripting skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is well-structured and concise, with appropriate progressive disclosure to a detailed playbook. However, it critically lacks actionability - the instructions are abstract directives without any concrete code examples, Bats syntax, or executable commands that would allow Claude to immediately write tests.
Suggestions
Add at least one complete, executable Bats test example showing basic syntax (e.g., @test block, assertions, setup/teardown)
Include specific Bats commands for running tests (e.g., 'bats test/*.bats' or 'bats --tap test/')
Provide concrete examples of common assertions like 'assert_success', 'assert_output', or bracket syntax for exit code checking
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding unnecessary explanations of what Bats is or how testing works. Every section serves a purpose and assumes Claude's competence with shell scripting and testing concepts. | 3 / 3 |
Actionability | The instructions are vague and abstract ('Set up a test structure', 'Write tests for exit codes') with no concrete code examples, commands, or executable guidance. It describes what to do rather than showing how. | 1 / 3 |
Workflow Clarity | Steps are listed in a logical sequence (confirm dialects → set up structure → write tests → add setup/teardown → run in CI), but there are no validation checkpoints, no specific commands, and no feedback loops for error recovery. | 2 / 3 |
Progressive Disclosure | Clear structure with a concise overview and well-signaled one-level-deep reference to the implementation playbook for detailed patterns. The separation between overview and detailed content is appropriate. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
9c177eb
- 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.