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.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/bats-testing-patterns/SKILL.md

Quality

Content

53%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill is commendably concise and well-structured as an overview, but it sacrifices actionability by providing only abstract instructions and no executable examples, and its sole progressive-disclosure reference points to a missing file. Strengthening the inline guidance and fixing the dangling reference would materially improve it.

Suggestions

Add at least one concrete, copy-paste-ready Bats example (a basic @test block with assert_success/assert_output) so the skill is executable without opening the external file.

Fix or create the referenced 'resources/implementation-playbook.md' (note the skill uses 'resources/' while the bundle convention is 'references/') — a dangling reference breaks progressive disclosure.

Insert an explicit validation/checkpoint step in the workflow (e.g. run 'bats test/' and confirm all tests pass before committing to CI) to support the CI/CD multi-step process.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, listing only what to do without padding or explaining what Bats or shell testing is; every section earns its place and there is no over-explanation.	5 / 5
Actionability	Guidance is high-level and abstract ('Set up a test structure with helpers and fixtures', 'Write tests for exit codes, output, and side effects') with no concrete code, commands, or executable examples; it describes rather than instructs, and defers specifics entirely to an external file.	2 / 5
Workflow Clarity	Steps are roughly sequenced ('Confirm dialects', 'Set up structure', 'Write tests', 'Add setup/teardown and run in CI'), but there are no validation checkpoints, feedback loops, or concrete verification steps despite CI integration being a multi-step operation.	3 / 5
Progressive Disclosure	Structure is present but the single referenced file 'resources/implementation-playbook.md' does not exist in any bundle directory, making the reference a dangling pointer; with no actual detailed material available, navigation collapses and the overview cannot deliver on its promise of progressive disclosure.	2 / 5
	Total	12 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-targeted description that explicitly covers both capability and trigger conditions with natural phrasing and a distinct niche. The main gap is slightly generic action language and missing common synonyms/extensions, which keep it just below a perfect specificity and trigger-term score.

Dimension	Reasoning	Score
Specificity	Names the domain (Bats, shell script testing) and several concrete actions implied by the tool ('comprehensive shell script testing', 'test-driven development of shell utilities'), but the actions are slightly generic rather than enumerated like 'extract text', 'fill forms'; lists a few specific capabilities with minor coverage gaps.	4 / 5
Completeness	Explicitly answers both 'what' ('Master Bats for comprehensive shell script testing') and 'when' ('Use when writing tests for shell scripts, CI/CD pipelines, or requiring TDD of shell utilities') with concrete trigger phrases, matching the anchor for clearly and explicitly answering both.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ('writing tests for shell scripts', 'CI/CD pipelines', 'test-driven development') and the domain name 'Bats', but omits common synonyms or file extensions like 'bash tests', '.bats', or 'shell testing'.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (Bats specifically for shell scripts) with distinct triggers unlikely to fire for non-shell testing skills; minimal overlap risk with general test frameworks.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: rmyndharis/antigravity-skills
Path: skills/bats-testing-patterns/SKILL.md
Commit: 3eff4af

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.