The body is lean and assumes Claude's Rust competence — it never explains what a test or crate is, and each section (install, parametrize, fixtures, matrix, async) earns its tokens with concrete code rather than prose.

Every step ships executable, copy-paste-ready Rust snippets plus a concrete `Cargo.toml` dev-dependency and a CI YAML line, fully matching the 'fully executable code/commands' anchor.

Steps 1–9 are clearly sequenced from install through CI integration, and the operations are non-destructive (running tests) where `cargo test` itself supplies the validation feedback loop, so the missing-checkpoint cap does not apply.

Content is well-organized into discrete titled sections with a clearly signaled References block; with no bundle files present and a self-contained single-file scope, the well-organized-structure anchor for simple skills is met.

Lists multiple specific concrete actions: parametrize via `#[case(...)]`, reusable setup via `#[fixture]`, matrix tests (cartesian product), async support via `#[async_std::test]`/`#[tokio::test]`, and `#[future]` for async fixtures — matching the 'lists multiple specific concrete actions' anchor.

Explicitly answers 'what' (the capabilities enumerated) and 'when' via 'Use when working with Rust and needing parametrize/fixture patterns beyond stdlib `#[test]`', satisfying the explicit-trigger anchor.

Covers the natural terms a Rust user would say — 'rstest', 'parametrize', 'fixture', 'Rust', 'stdlib `#[test]`' — with good coverage rather than generic jargon.

Narrowly niched to the rstest crate and Rust parametrize/fixture patterns with distinct triggers, making it unlikely to fire for an unrelated skill.