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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

35%

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

The body is reasonably organized and concise, but it is light on actionable detail — abstract bullet directives with no concrete Bats examples — and its single external reference points to a missing file.

Suggestions

Add at least one concrete, executable Bats test example (e.g., a `@test` block with `run`/`assert`/`[ "$status" -eq 0 ]`) so guidance is copy-paste ready.

Add a validation checkpoint to the workflow, e.g., 'Run `bats tests/` and only proceed when all tests pass' as an explicit feedback loop.

Create the referenced `resources/implementation-playbook.md` or remove the broken reference, since progressive disclosure relies on that file existing.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and well-sectioned, but the opening line repeats scope already in the frontmatter and uses 'comprehensive' twice, so it could be tightened.	2 / 3
Actionability	Instructions are abstract directives ('Set up a test structure with helpers and fixtures', 'Write tests for exit codes, output, and side effects') with no concrete Bats syntax, commands, or executable examples; it describes rather than instructs.	1 / 3
Workflow Clarity	Steps are listed in a sensible sequence but lack validation checkpoints or feedback loops for the CI/run-tests step, which a testing workflow warrants.	2 / 3
Progressive Disclosure	It signals a one-level-deep reference to `resources/implementation-playbook.md` and sections the body well, but that referenced file does not exist in the bundle, so navigation is broken.	2 / 3
	Total	7 / 12 Passed

Description

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.

The description clearly states what the skill does and when to use it, with natural trigger terms and a distinct niche. Specificity is slightly held back because the actions are broad activity categories rather than a sharp list of concrete operations.

Suggestions

Tighten specificity by listing distinct concrete operations (e.g., 'write and run unit tests, mock commands, parametrize test cases') instead of broad activity categories.

Dimension	Reasoning	Score
Specificity	Names the Bats tool and domain plus several actions ('writing tests for shell scripts', 'CI/CD pipelines', 'test-driven development of shell utilities'), but these are high-level activity categories rather than a list of distinct concrete operations.	2 / 3
Completeness	Explicitly answers both what ('Master Bash Automated Testing System (Bats) 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').	3 / 3
Trigger Term Quality	Includes natural terms users would say — 'writing tests for shell scripts', 'CI/CD pipelines', 'test-driven development', 'shell utilities' — with good coverage of common phrasings.	3 / 3
Distinctiveness Conflict Risk	Scoped to a clear niche (Bats shell testing) with distinct triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Commit: 615669b

Reviewed: about 10 hours 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.