ericrisco/rsc-harness / skills/rust
rust
VerifiedUse when writing, reviewing, testing, or shipping Rust — ownership and the borrow checker (move/borrow/clone, Arc/RefCell, lifetimes), errors with Result/`?`/thiserror/anyhow, async on tokio, axum 0.8 services, cargo test, and sqlx + cargo-audit hardening. NOT the same service in Go (that is `go`), NOT a desktop webview shell (that is `tauri`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 14.3 KB |
| evals/README.md | markdown | 1.0 KB |
| evals/cases.yaml | config | 3.7 KB |
| references/async-tokio.md | markdown | 4.6 KB |
| references/axum-service.md | markdown | 4.0 KB |
| references/ownership.md | markdown | 4.6 KB |
| references/testing.md | markdown | 2.9 KB |
| scripts/verify.shexecutable | script | 2.8 KB |
evals/README.md
View on GitHub# Eval harness — `rust` skill
`cases.yaml` is a human/CI-readable trigger-and-capability spec, not an automated runner. To exercise
it, load the full skill catalog descriptions into a routing agent and, for each `should_trigger` prompt,
check that the `rust` skill fires; for each `should_not_trigger` prompt, check that it stays silent and
that any skill that does fire matches the stated `route_to` sibling (security-audit, deployment,
postgresdb, tauri, go). Because LLM routing is non-deterministic, run a few trials per prompt and take
the majority. For the `capability` scenario, run it once with the skill body unavailable and once with
`rust/SKILL.md` (plus references) loaded, then eyeball each output against the `must_include` rubric —
the with-skill answer should cover the rubric and clearly beat the baseline (a `thiserror` enum mapped
via `IntoResponse`, a `$1` bind parameter, `?` propagation with no `.unwrap()` on the request path).
Keep `cases.yaml` faithful to SKILL.md's "When to use / When NOT to use" whenever scope changes.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |