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.
76
Quality
73%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./docs/v19.7/configuration/agent/skills_external/antigravity-awesome-skills-main/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 completeness and distinctiveness. It clearly identifies when to use the skill and targets a specific niche (Bats testing framework). The main weakness is the lack of specific concrete actions - it says 'comprehensive shell script testing' but doesn't enumerate what specific testing capabilities it provides.
Suggestions
Add specific concrete actions like 'write test cases, mock commands, assert exit codes and outputs, set up test fixtures' to improve specificity
Consider adding file extension triggers like '.bats files' or mentioning 'bats-core' for additional keyword coverage
| 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', 'assert outputs', or 'generate test reports'. | 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 good 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 good progressive disclosure to external resources. However, it critically lacks actionable content - the instructions are too abstract to be useful without opening the referenced playbook. The SKILL.md should include at least one concrete, executable example to be immediately useful.
Suggestions
Add a minimal executable Bats test example showing basic test structure (e.g., @test block with assertions)
Include concrete commands for running tests (e.g., 'bats test/*.bats' or 'bats --tap test/')
Provide a specific example of setup/teardown functions rather than just mentioning them
Add at least one concrete pattern for testing exit codes or output validation
| 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 clear purpose without padding. | 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 but lack specificity and validation checkpoints. No concrete commands or feedback loops for verifying test setup or catching failures. | 2 / 3 |
Progressive Disclosure | Clear overview structure with appropriate reference to detailed implementation in a separate file (resources/implementation-playbook.md). Navigation is one level deep and well-signaled. | 3 / 3 |
Total | 9 / 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.
- Repository
- duclm1x1/Dive-Ai
- Commit
20ba150
- 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.