CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

56

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/bats-testing-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

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 well-organized and lean, but it lacks concrete, executable Bats guidance (no code or commands) and its single referenced resource file is missing. Adding real Bats syntax examples and either providing or removing the broken reference would most improve it.

Suggestions

Add at least one concrete, copy-paste Bats example using @test, run, and assertions (e.g. assert_success, [ "$status" -eq 0 ]) so the Instructions are executable rather than abstract.

Remove the fluff in the opener (drop the repeated 'comprehensive' and 'production-grade') to tighten the intro.

Either create resources/implementation-playbook.md with the detailed patterns or drop the reference to it, since the current pointer resolves to a non-existent file.

Add an explicit validation/verification checkpoint (e.g. 'Run bats tests/ and fix failures before committing') to the CI step.

DimensionReasoningScore

Conciseness

The body is mostly lean and does not explain concepts Claude already knows, but the opener repeats 'comprehensive...comprehensive' and adds 'production-grade' fluff that could be tightened; closest to 'mostly efficient but 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 executable Bats code or commands (e.g. @test, run, assert_success, [ "$status" -eq 0 ]); it describes rather than instructing concretely.

1 / 3

Workflow Clarity

A sequence is present (confirm dialects → set up structure → write tests → add setup/teardown and run in CI), but there are no explicit validation checkpoints or feedback loops, which caps clarity at 2.

2 / 3

Progressive Disclosure

The body is a clear, well-sectioned overview pointing one level deep to a signaled reference (resources/implementation-playbook.md), but that referenced bundle file does not exist, so the navigation is broken rather than cleanly wired.

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.

A strong, well-structured description that clearly scopes a niche (Bats shell testing) with explicit 'Use when' triggers. The main weakness is mild fluff ('comprehensive...comprehensive', 'production-grade') and a lack of multiple enumerated concrete actions.

DimensionReasoningScore

Specificity

Names the domain (Bats/shell testing) and the action 'writing tests', but uses 'comprehensive' fluff and does not enumerate multiple concrete actions like writing fixtures, mocking, or asserting; closest to 'names domain and some actions, but not comprehensive'.

2 / 3

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 an explicit trigger clause.

3 / 3

Trigger Term Quality

'tests for shell scripts', 'CI/CD pipelines', and 'test-driven development of shell utilities' are natural phrases a user would say when needing this skill, giving good coverage of likely triggers.

3 / 3

Distinctiveness Conflict Risk

Bats/shell-script unit testing is a clear niche with distinct triggers that are unlikely to fire for non-shell testing skills, making conflict risk low.

3 / 3

Total

11

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
rmyndharis/antigravity-skills
Reviewed

Table of Contents

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.