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.
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill bats-testing-patternsOverall
score
75%
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/skillValidation 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 solid skill description with excellent completeness and distinctiveness. It clearly identifies the Bats testing framework niche and provides explicit 'Use when' guidance. The main weakness is the lack of specific concrete actions - it describes the domain well but doesn't enumerate what specific testing operations the skill enables.
Suggestions
Add specific concrete actions like 'write @test functions', 'use setup/teardown hooks', 'mock external commands', or 'validate exit codes and output' to improve specificity.
| 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 | Good coverage of natural terms: 'Bats', 'shell script testing', 'tests', 'shell scripts', 'CI/CD pipelines', 'test-driven development', 'shell utilities' - these are terms users would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on Bats testing framework for shell scripts - unlikely to conflict with general shell scripting skills or other testing frameworks due to the specific 'Bats' mention and shell-specific context. | 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 content is well-structured and concise with appropriate progressive disclosure to detailed resources. However, it critically lacks actionability - the instructions are too abstract and provide no concrete code examples, commands, or copy-paste ready content. The skill essentially serves as a pointer to another file rather than providing immediately useful guidance.
Suggestions
Add at least one concrete, executable Bats test example showing basic test structure (e.g., @test block with assertions)
Include specific commands for running Bats tests (e.g., 'bats test/*.bats' or 'bats --tap test/')
Provide a minimal example of test file structure showing setup/teardown functions
Add a concrete example of testing exit codes and output capture using Bats assertions
| 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 (confirm dialects → set up structure → write tests → add setup/teardown → run in CI), but there are no validation checkpoints, no feedback loops for error recovery, and the steps lack specificity. | 2 / 3 |
Progressive Disclosure | Clear overview structure with well-signaled one-level-deep reference to the implementation playbook. The skill appropriately keeps the main file concise while pointing to detailed resources. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 13 / 16 Passed | |
- 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.