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

56%

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

38%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 body is well-structured and lean, but its instructions are high-level rather than executable and the one detailed reference points to a missing file. This leaves the skill unable to deliver the concrete patterns it promises without the absent playbook.

Suggestions

Add a minimal executable Bats example (e.g. an `@test` block asserting an exit code and output) directly in the Instructions so the skill is actionable without the external file.

Create the referenced `resources/implementation-playbook.md` (or correct the path) so the progressive-disclosure reference resolves to real content.

Add an explicit validation checkpoint such as "run `bats tests/` and only proceed when all tests pass" to the workflow, including a fix-and-rerun loop for failures.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with no concept over-explanation, but the opening restates the description ("Comprehensive guidance for writing comprehensive unit tests") and the "Use this skill when / Do not use this skill when" lists re-expand triggers already present in the description.	3 / 5
Actionability	Instructions are high-level hints ("Set up a test structure with helpers and fixtures", "Write tests for exit codes, output, and side effects") with no executable Bats code, no `@test` syntax, and no concrete `bats` commands in the body.	2 / 5
Workflow Clarity	A rough sequence is present (confirm dialects → set up structure → write tests → setup/teardown + run in CI), but validation checkpoints are only implicit and there is no error-recovery guidance.	3 / 5
Progressive Disclosure	Structure is clean with a single one-level-deep reference ("resources/implementation-playbook.md"), but that referenced file does not exist in the bundle — the promised detailed content is a dead reference, so progressive disclosure is not actually delivered.	2 / 5
	Total	10 / 20 Passed

Description

75%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 clear, third-person description that conveys a distinct niche and explicit trigger guidance. It is concise and well-targeted, with only minor gaps in synonym coverage and trigger specificity.

Dimension	Reasoning	Score
Specificity	Names the domain ("Bash Automated Testing System (Bats)", "shell script testing") and several specific use contexts ("writing tests for shell scripts, CI/CD pipelines", "test-driven development of shell utilities"), with only minor coverage gaps.	4 / 5
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"), with the trigger guidance slightly general rather than maximally specific.	4 / 5
Trigger Term Quality	Includes natural phrases users would say ("writing tests for shell scripts", "CI/CD pipelines", "test-driven development"), though it omits common synonyms like "bash tests", "Bats", or ".bats files".	4 / 5
Distinctiveness Conflict Risk	The Bats/shell-testing niche with CI/CD and TDD triggers is mostly distinct, with only minor overlap risk against general testing or CI tooling skills.	4 / 5
	Total	16 / 20 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
Path: skills/bats-testing-patterns/SKILL.md
Commit: 1f67c44

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