CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/cargo-test

Configures and runs Rust's built-in `cargo test` - `#[test]` + `#[should_panic]` + `Result<(), E>` returns; integration tests in `tests/`; doc-tests embedded in `///` comments; `--lib` / `--bins` / `--all-targets` / `--workspace` selection; `cargo bench` (nightly) + Criterion (stable); `cargo test -- --test-threads=1` for serial; `cargo test -- --nocapture` to see println output. Use for any Rust project - testing is built into Cargo, no install needed.

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

100%

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

A well-structured, executable skill body: lean code-first content, a clearly sequenced multi-step workflow with a verification-bearing worked example, and clean one-level-deep progressive disclosure to a real reference file. No significant weaknesses.

DimensionReasoningScore

Conciseness

The body is lean: tables and copy-paste code/blocks with no padding explaining what Rust or testing is. Explanatory lines that exist ('Each file in tests/ compiles to its own binary', 'Avoids unwrap() boilerplate; allows ?') are practical guidance that earns their tokens, not generic concept re-explanation.

3 / 3

Actionability

Every section provides complete, executable Rust/bash/YAML examples with exact commands (`cargo test --all-targets --workspace`, `cargo test -- --nocapture`), concrete assertion macros, and a CI YAML block — copy-paste ready with no pseudocode.

3 / 3

Workflow Clarity

A 7-step 'How to use' sequence cross-references each numbered Step, and the 'Worked example' walks a full flow with expected verification output ('test result: ok. 2 passed', coverage gate exit 0). Testing is not a destructive/batch operation, so the feedback-loop cap does not apply.

3 / 3

Progressive Disclosure

SKILL.md is an overview that cleanly offloads coverage/benchmark detail to the single one-level-deep reference `references/coverage-and-benchmarks.md` (verified to exist), signaled consistently via inline links; the main test patterns stay inline.

3 / 3

Total

12

/

12

Passed

Description

85%

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 dense, specific description that answers both what and when with an explicit use clause and a clear Rust/cargo-test niche. Its main weakness is trigger-term quality: the description leans on technical syntax rather than natural user phrasings.

Suggestions

Lead with or foreground natural trigger phrasings like 'test a Rust project', 'run Rust tests', or 'write cargo tests' before the syntax detail, so users' natural language is matched.

Trim some of the inline syntax tokens (e.g. the full `--lib`/`--bins`/`--all-targets`/`--workspace` flag list) from the description and leave them for the body, reducing jargon density.

DimensionReasoningScore

Specificity

Lists many concrete actions such as `#[test]`, `#[should_panic]`, `Result<(), E>` returns, `tests/` integration tests, doc-tests, and `--lib`/`--bins`/`--all-targets`/`--workspace` selection — clearly multiple specific actions, not vague.

3 / 3

Completeness

It explicitly answers what ('Configures and runs Rust's built-in `cargo test`...') and when with an explicit trigger clause ('Use for any Rust project - testing is built into Cargo, no install needed'), satisfying the 'Use when...' requirement that would otherwise cap at 2.

3 / 3

Trigger Term Quality

Natural terms like 'cargo test', 'Rust project', and 'testing is built into Cargo' are present, but the description is dominated by technical syntax tokens (`#[should_panic]`, `Result<(), E>`, flag lists) rather than the common phrasings a user would naturally say; some relevant keywords but missing common variations.

2 / 3

Distinctiveness Conflict Risk

Scoped narrowly to Rust's `cargo test` ecosystem with distinct triggers (cargo test, Rust project, Cargo), making it unlikely to fire for non-Rust testing skills.

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.

Reviewed

Table of Contents