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 ./.agent/skills/bats-testing-patterns/SKILL.md

Quality

Content

22%

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

This skill is essentially a thin table of contents with no actionable content of its own. It defers all concrete guidance to a referenced playbook that isn't provided in the bundle, leaving the SKILL.md body without any executable examples, Bats syntax, or meaningful workflow steps. The content fails to serve as a useful quick-start reference and relies entirely on external files for substance.

Suggestions

Add a concrete quick-start example showing a minimal Bats test file with @test blocks, setup/teardown, and a run command so the skill is immediately actionable without opening referenced files.

Replace the abstract instruction bullets with specific, executable steps (e.g., 'mkdir -p test/fixtures && cat > test/example.bats <<EOF ... EOF && bats test/').

Add a validation checkpoint such as 'Run `bats --tap test/` and verify all tests pass before committing' to establish a feedback loop in the workflow.

Ensure referenced paths are consistent—the skill references both `resources/implementation-playbook.md` and `./sub-skills/implementation-playbook.md` which appear to be different paths for the same content.

Dimension	Reasoning	Score
Conciseness	The 'Use this skill when' and 'Do not use this skill when' sections add moderate bloat—Claude can infer applicability from context. The instructions section is brief but the overall content has unnecessary framing without adding much actionable value.	2 / 3
Actionability	The instructions are entirely abstract ('Confirm shell dialects', 'Set up a test structure', 'Write tests for exit codes'). There are zero concrete code examples, no Bats syntax, no executable commands, and no sample test files. Everything actionable is deferred to a referenced file.	1 / 3
Workflow Clarity	The five bullet points in Instructions loosely suggest a sequence but lack specificity, validation checkpoints, or any feedback loops. There is no clear multi-step workflow with concrete commands or verification steps.	1 / 3
Progressive Disclosure	The skill references `resources/implementation-playbook.md` and a sub-skill, which is appropriate progressive disclosure structure. However, no bundle files were provided to verify these references exist, the SKILL.md itself contains almost no substantive quick-start content, and the references are somewhat redundant (the same playbook is mentioned twice under different paths).	2 / 3
	Total	6 / 12 Passed

Description

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.

The description is well-structured with a clear 'Use when' clause and good trigger terms that cover the Bats testing niche effectively. Its main weakness is that it lacks specific concrete actions—it says 'comprehensive shell script testing' but doesn't enumerate what capabilities it actually provides (e.g., writing @test blocks, using setup/teardown, mocking commands, asserting outputs). The domain specificity naturally provides good distinctiveness.

Suggestions

Add specific concrete actions like 'write @test blocks, mock shell commands, assert exit codes and output, set up test fixtures with setup/teardown' to improve specificity.

Consider adding file extension triggers like '.bats files' or tool name variations to further strengthen trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (Bats/shell script testing) and mentions some contexts (CI/CD pipelines, TDD of shell utilities), but doesn't list specific concrete actions like 'write test cases', 'mock commands', 'generate test reports', or 'assert exit codes'.	2 / 3
Completeness	Clearly answers both 'what' (Bash Automated Testing System for shell script testing) and 'when' (explicit 'Use when' clause covering writing tests for shell scripts, CI/CD pipelines, or TDD of shell utilities).	3 / 3
Trigger Term Quality	Includes strong natural trigger terms: 'Bats', 'shell script testing', 'CI/CD pipelines', 'test-driven development', 'shell utilities'. These cover the main ways a user would phrase requests related to this skill.	3 / 3
Distinctiveness Conflict Risk	Bats is a very specific niche tool for shell script testing, making this highly distinctive. The mention of 'Bats', 'shell script', and 'shell utilities' creates clear boundaries that are unlikely to conflict with general testing or coding skills.	3 / 3
	Total	11 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Repository: Dokhacgiakhoa/antigravity-ide
Path: .agent/skills/bats-testing-patterns/SKILL.md
Commit: c4a059b

Reviewed: 2 days 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.