CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/bats-testing

Configures Bats-core (Bash Automated Testing System) for testing CLI tools, shell scripts, and Unix programs - `.bats` test files with `@test` blocks, `run` to capture command exit + output, `[ "$status" -eq 0 ]` and `[ "$output" = ... ]` assertions, `setup`/`teardown` hooks, `load` for shared helpers, parallel execution via `--jobs N`, TAP-compliant output for CI integration. Use whenever the unit-under-test is a shell script, CLI binary, or anything invokable from Bash.

75

Quality

94%

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

Overview
Quality
Evals
Security
Files

Quality

Content

85%

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

A strong, highly actionable skill body: executable code throughout, a clear stepped workflow, and clean progressive disclosure via a single real reference file. The only weakness is mild redundancy in the Overview and Worked example.

Suggestions

Trim the two Overview block-quotes that define what Bats is — Claude already knows this; keep only the load/assertion mechanics.

Shorten or fold the Worked example, since its --help and no-args assertions duplicate the Step 3 and Step 6 examples.

DimensionReasoningScore

Conciseness

Mostly efficient with executable code in every section, but the Overview block-quotes define what Bats is (concepts Claude largely knows) and the Worked example re-covers the --help / no-args paths already shown in Steps 3 and 6 — material that could be tightened without losing clarity.

2 / 3

Actionability

Every section ships copy-paste-ready, executable code: install one-liners, verbatim .bats files, run/assertion patterns, setup/teardown, load helpers, bats-assert, skip, --jobs, and a CI reference — fully concrete with no pseudocode.

3 / 3

Workflow Clarity

A clearly sequenced 7-step "How to use" list maps to numbered Step 1–9 sections with cross-references, and the Worked example shows expected run output; testing CLI tools is not a destructive/batch context, so the missing explicit validate->fix->retry loop does not cap the score.

3 / 3

Progressive Disclosure

SKILL.md is a well-organized overview that splits CI detail into one clearly-signaled, one-level-deep reference (references/ci-integration.md, which exists and is linked from Steps 7/9 and the Worked example), giving easy navigation.

3 / 3

Total

11

/

12

Passed

Description

100%

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 high-quality description: third-person voice, concrete mechanism list, and an explicit trigger clause covering both what and when. It is specific, distinctive, and free of fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: ".bats test files with @test blocks", "run to capture command exit + output", "[ $status -eq 0 ] / [ $output = ... ] assertions", "setup/teardown hooks", "load for shared helpers", "parallel execution via --jobs N", "TAP-compliant output" — matching the score-3 anchor of multiple specific concrete actions.

3 / 3

Completeness

Clearly answers both what ("Configures Bats-core ... for testing CLI tools, shell scripts, and Unix programs" plus the mechanism list) and when (the explicit "Use whenever the unit-under-test is a shell script, CLI binary, or anything invokable from Bash" trigger clause), satisfying the score-3 anchor.

3 / 3

Trigger Term Quality

Uses natural terms users would say — "shell script", "CLI binary", "Bash", "testing CLI tools", "CI integration" — and an explicit trigger ("Use whenever the unit-under-test is a shell script, CLI binary, or anything invokable from Bash"), giving good coverage of natural language.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (Bats-core / Bash-basd test harness) with distinct triggers unlikely to overlap with other skills; the combination of ".bats", "@test blocks", and "TAP-compliant" makes it unambiguous.

3 / 3

Total

12

/

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.

Reviewed

Table of Contents