rust-testing

Patrones de pruebas en Rust incluyendo pruebas unitarias, de integración, async, basadas en propiedades, mocking y cobertura. Sigue la metodología TDD.

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./docs/es/skills/rust-testing/SKILL.md

Quality

Content

78%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 dense, highly actionable reference whose code examples and commands are uniformly executable and cover the Rust testing landscape well. Its weaknesses are structural: everything lives inline in one long file with no reference split, and a few sections re-teach basics Claude already knows.

Suggestions

Split advanced or peripheral sections (Benchmarks con Criterion, Integración con CI, proptest/mockall deep-dives) into reference files linked from a shorter SKILL.md overview.

Drop or compress the 'Macros de Aserción' table and TDD concept narration — Claude already knows assert_eq! and the red-green-refactor idea; keep only the Rust-specific mechanics.

Add an explicit feedback loop for TDD failure states (RED test unexpectedly passes, coverage below 80%) to reach a fully validated workflow.

Dimension	Reasoning	Score
Conciseness	The body is efficient — short headers leading directly into executable code, assuming Rust competence. Minor trimmable over-explanation remains (the 'Macros de Aserción' table and TDD cycle narration teach concepts Claude already knows), keeping it below the lean 5-anchor but above the 3-anchor's 'unnecessary explanation' level.	4 / 5
Actionability	Guidance is fully executable and copy-paste ready: complete #[cfg(test)] modules, rstest/proptest/mockall/criterion examples, a cargo test command table, and a GitHub Actions CI yaml covering the common cases. Only trivial placeholders (e.g. parse_config's todo!()) appear, and those are intentional TDD demonstrations.	5 / 5
Workflow Clarity	The 'Cómo Funciona' section gives a clear 7-step TDD sequence with explicit checkpoints (verify the test fails in ROJO, coverage gate at 80%), matching the 4-anchor. It falls short of 5 because there is no error-recovery feedback loop (e.g. what to do when the RED test unexpectedly passes or coverage falls below target).	4 / 5
Progressive Disclosure	The skill is a single ~500-line monolithic file: benchmarking, proptest, mocking, and CI content that clearly belong in separate reference files are all inlined, and no bundle files or reference pointers exist. Section headers give it structure (above the 2-anchor), but the absent split places it at the 3-anchor ('content that should be separate is inline').	3 / 5
	Total	16 / 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.

A specific, well-scoped description that clearly names what the skill covers across the Rust testing domain, but it entirely lacks a 'when to use' clause, which limits its discoverability and leaves completeness capped. Keyword coverage is solid though missing a few natural synonyms.

Suggestions

Append an explicit trigger clause, e.g. 'Usar cuando se escriban o corrijan pruebas en Rust, al aplicar TDD, o cuando el usuario mencione tests, cobertura o benchmarks.'

Add natural trigger variations users would actually say — 'tests'/'testing' in English, 'cargo test', 'benchmarks' — alongside the existing Spanish terms.

State the concrete actions in verb form ('Escribe... prueba, genera... benchmarks') rather than only naming the pattern categories.

Dimension	Reasoning	Score
Specificity	The description enumerates six concrete capability areas — 'pruebas unitarias, de integración, async, basadas en propiedades, mocking y cobertura' — plus the TDD methodology, matching the comprehensive multi-action anchor; unlike the 4-anchor, there are no notable gaps in coverage of the domain.	5 / 5
Completeness	The 'what' is clear and concrete, but there is no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3. It is not 2 because the 'what' half is specific and multi-faceted, not vague.	3 / 5
Trigger Term Quality	Good natural keyword coverage ('pruebas unitarias', 'mocking', 'cobertura', 'TDD', 'Rust') but missing common variations users would actually say — English 'tests'/'testing', 'cargo test', 'benchmarks'. It sits between the 3-anchor (missing common variations) and the 5-anchor (comprehensive synonyms), closer to 4.	4 / 5
Distinctiveness Conflict Risk	'Rust' combined with specific test-type triggers (property-based, mocking, coverage) carves a clear niche with distinct triggers and minimal conflict risk against generic testing or other-language 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: docs/es/skills/rust-testing/SKILL.md
Commit: c70874f

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.