Name: rust-testing
Rating: 67.2 (1 reviews)
Author: affaan-m

rust-testing

Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

The canonical home for this skill is rust-testing in affaan-m/ECC

Quality

Content

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

The body is highly actionable with executable examples and a clear TDD workflow containing validation feedback loops. Its main weakness is that all content lives in a single long file with no progressive disclosure into reference files.

Suggestions

Split advanced reference material (e.g. custom proptest strategies, full mockall API, criterion configuration) into one-level-deep reference files linked from the main sections.

Trim minor padding such as redundant inline labels ('// Equality') and the closing 'Remember' line to tighten token efficiency.

Consider a short 'Quick start' section at the top so the most common case (write + run a unit test) is reachable before the detailed sections.

Dimension	Reasoning	Score
Conciseness	Lean prose with executable code blocks and minimal concept explanation, though the ~500-line single file has minor padding (inline '// Equality' labels, the closing 'Remember' line) that could be trimmed.	4 / 5
Actionability	Fully executable, copy-paste-ready Rust code and exact cargo commands covering unit, integration, async, rstest, proptest, mockall, criterion, coverage, and CI — the common cases are well covered.	5 / 5
Workflow Clarity	The RED-GREEN-REFACTOR cycle is a clear sequenced workflow with explicit validation checkpoints (verify test fails, then passes) and a built-in feedback loop; coverage gating (--fail-under-lines 80) adds a further checkpoint.	5 / 5
Progressive Disclosure	Well-organized into clearly headed sections with no nested references, but everything is inlined in one ~500-line file with no bundle files; some advanced topics (custom proptest strategies, full mockall API) could be split into one-level-deep references.	4 / 5
	Total	18 / 20 Passed

Description

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

The description is specific, third-person, and well-scoped to Rust testing, but it omits an explicit 'Use when...' trigger clause, which caps completeness. Adding a trigger phrase would raise the completeness and trigger_term_quality scores.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when writing or running Rust tests, adding coverage, or following TDD in a Rust project.'

Mention 'cargo test' and 'benchmarks'/'doc tests' to broaden natural trigger terms users actually say.

Lead with a verb-driven action phrase ('Write, run, and organize Rust tests...') to make capabilities read as concrete actions rather than noun categories.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete capabilities — 'unit tests, integration tests, async testing, property-based testing, mocking, and coverage' — giving comprehensive coverage of the testing domain.	5 / 5
Completeness	Has a clear 'what' (Rust testing patterns including...) but no explicit 'when'/'Use when...' trigger clause, so per the rubric guideline completeness is capped at 3.	3 / 5
Trigger Term Quality	Strong natural keywords ('Rust testing', 'unit tests', 'integration tests', 'mocking', 'coverage', 'TDD') that users would say, though a few natural terms present in the body (benchmarks, doc tests, cargo test) are omitted from the description.	4 / 5
Distinctiveness Conflict Risk	Clearly scoped to Rust testing with a distinct niche and specific trigger terms, presenting minimal conflict risk with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (501 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: affaan-m/ECC
Path: .kiro/skills/rust-testing/SKILL.md
Commit: d8409a4

Reviewed: 1 day 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.