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.

1.04x

Quality

62%

Does it follow best practices?

Impact

90%

1.04x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/bats-testing-patterns/SKILL.md

The canonical home for this skill is bats-testing-patterns in rmyndharis/antigravity-skills

Quality

Content

35%Scale 1-3

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

This skill content is essentially a table of contents with no actionable substance. It lacks any concrete code examples, specific Bats syntax, or executable commands, deferring everything to an external playbook. The instructions read as high-level bullet points that describe what to do without showing how, making the skill nearly useless without the referenced resource file.

Suggestions

Add at least one concrete, executable Bats test example (e.g., a minimal .bats file with @test, setup, teardown) directly in the SKILL.md so it provides immediate value without requiring the external resource.

Replace vague instruction bullets like 'Write tests for exit codes, output, and side effects' with specific Bats commands and assertions (e.g., `run my_script.sh; [ "$status" -eq 0 ]`).

Remove or significantly trim the 'Use this skill when' / 'Do not use this skill when' sections—these consume tokens without adding actionable guidance.

Add a quick-start workflow with explicit steps including how to install Bats, run a test file, and interpret results, with validation checkpoints.

Dimension	Reasoning	Score
Conciseness	The 'Use this skill when' and 'Do not use this skill when' sections are somewhat unnecessary padding—Claude doesn't need to be told when not to use a skill in this level of detail. The introductory paragraph also restates the title. However, the instructions section itself is reasonably brief.	2 / 3
Actionability	The instructions are entirely vague and abstract ('Write tests for exit codes, output, and side effects', 'Set up a test structure with helpers and fixtures') with zero concrete code, commands, or examples. Everything actionable is deferred to an external resource file.	1 / 3
Workflow Clarity	There is a rough sequence implied (confirm environments → set up structure → write tests → add setup/teardown → run in CI), but steps lack specificity, have no validation checkpoints, and no feedback loops for error recovery.	2 / 3
Progressive Disclosure	There is a reference to a detailed resource file (resources/implementation-playbook.md), which is good progressive disclosure. However, the SKILL.md itself provides almost no useful quick-start content—it's essentially an empty shell pointing elsewhere, making the overview layer too thin to be useful on its own.	2 / 3
	Total	7 / 12 Passed

Description

89%Scale 1-3

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 description with clear 'what' and 'when' clauses, good trigger terms covering the Bats ecosystem, and strong distinctiveness. Its main weakness is that the specificity of concrete actions could be improved — it describes the domain well but doesn't enumerate the specific capabilities (e.g., writing @test blocks, using bats assertions, mocking commands, setting up test helpers).

Suggestions

Add specific concrete actions like 'write @test blocks, create setup/teardown functions, use bats-assert and bats-support libraries, mock shell commands' to improve specificity.

Dimension	Reasoning	Score
Specificity	Names the domain (Bats/shell script testing) and implies actions like 'writing tests' and 'test-driven development', but doesn't list specific concrete actions like 'create test files', 'write assertions', 'mock commands', 'generate test fixtures', etc.	2 / 3
Completeness	Clearly answers both 'what' (Master 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 users would refer to this domain, including the tool name and common use cases.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive — Bats is a specific testing framework for shell scripts, which is a clear niche. The mention of 'Bats', 'Bash Automated Testing System', and 'shell script testing' makes it very unlikely to conflict with other skills like general testing or general shell scripting 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/bats-testing-patterns/SKILL.md
Commit: 7520423

Reviewed: ~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.