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

60%

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

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

Quality

Content

42%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.

A compact, well-structured skill body that is undermined by a lack of executable Bats examples, missing test-run validation feedback in the workflow, and a broken external reference. It reads as an outline pointing to details that are not actually provided.

Suggestions

Add a concrete copy-paste Bats example (a `@test` block asserting exit codes and output) directly in SKILL.md so the skill is actionable without the missing playbook.

Insert an explicit validation loop in the Instructions: run `bats tests/`, and if any test fails, fix and re-run before proceeding.

Either create `resources/implementation-playbook.md` or remove the references to it, so progressive-disclosure navigation resolves to real content.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient short bullet lists, but the intro repeats "comprehensive" twice, adds "production-grade" fluff, re-explains the Bats acronym already present in the frontmatter, and the Use/Don't-use sections largely restate the description's triggers.	3 / 5
Actionability	Instructions are high-level hints ("Set up a test structure with helpers and fixtures", "Add setup/teardown and run tests in CI") with no executable Bats code or commands, and the only source of detailed examples points to a non-existent file.	2 / 5
Workflow Clarity	A rough sequence is present (confirm dialects -> set up structure -> write tests -> add setup/teardown and run in CI) but there is no validation/feedback checkpoint (run tests, check pass/fail, fix and re-run), which caps a testing workflow at 3.	3 / 5
Progressive Disclosure	Sections are well-organized and the playbook reference is clearly signaled one level deep, but the referenced `resources/implementation-playbook.md` does not exist in the bundle, so the promised navigation leads nowhere.	3 / 5
	Total	11 / 20 Passed

Description

78%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 description that clearly states both capability and explicit Use-when triggers with natural keywords. Its main weakness is mild fluff ("Master", "comprehensive") and a single core action elaborated into contexts rather than multiple distinct concrete actions.

Suggestions

Replace "Master ... for comprehensive shell script testing" with concrete actions such as "Write and run Bats unit tests, set up fixtures and helpers, and integrate tests into CI pipelines".

Add the "TDD" abbreviation alongside "test-driven development" to improve trigger synonym coverage.

Tighten "CI/CD pipelines" to "shell tests in CI/CD pipelines" to reduce overlap with general CI/CD skills.

Dimension	Reasoning	Score
Specificity	The core capability is essentially a single action — testing shell scripts with Bats — applied across contexts ("writing tests for shell scripts, CI/CD pipelines, or requiring test-driven development of shell utilities"), with "Master" and "comprehensive" adding fluff rather than distinct concrete actions.	3 / 5
Completeness	It 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 concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural keyword coverage ("tests", "shell scripts", "CI/CD pipelines", "test-driven development", "shell utilities", "Bash", "Bats") that users would plausibly say, though the "TDD" abbreviation synonym is not stated explicitly.	4 / 5
Distinctiveness Conflict Risk	The Bats/shell-testing niche is mostly distinct with specific triggers, but "CI/CD pipelines" and generic "writing tests" wording create minor overlap risk with general testing or CI/CD 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/bats-testing-patterns/SKILL.md
Commit: 57c135b

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