CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

rust-sop

Standard operating procedures for writing Rust in joelclaw. Covers idiomatic patterns, async/tokio, error handling, project structure, testing, and clawnode-specific conventions. Use when writing Rust code, reviewing Rust PRs, scaffolding Rust projects, debugging ownership/lifetime errors, or working on clawnode. Triggers on: 'rust', 'cargo', 'tokio', 'axum', 'clawnode', 'ownership', 'lifetimes', 'borrow checker', 'rust error', or any Rust development task.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

67%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 well-structured, highly actionable SOP whose org-specific conventions (stack choices, project layout, naming, validation commands, pdf-brain workflow) are excellent. Its main weakness is token efficiency: generic Rust idioms Claude already knows are re-taught inline, rules are repeated between the pattern sections and the anti-patterns table, and async/axum content is duplicated between the body and the reference files.

Suggestions

Trim the Ownership & Borrowing and Error Handling sections to the org-specific rules only (e.g., the <Module>Error naming convention, boundary-layer error mapping) and move generic Rust idiom examples into references/ownership.md, trusting Claude's existing Rust knowledge.

Remove duplication between the body's async/axum sections and references/async.md / references/axum.md — keep one canonical compact pattern per topic in the body and defer the rest to the references, and collapse the Anti-Patterns table entries that restate rules already stated inline.

Add an explicit feedback loop to the Validation Checklist (e.g., 'If clippy or fmt fails: fix all warnings, then re-run until clean before proceeding') to upgrade the workflow from a checklist to a validate-fix-retry loop.

DimensionReasoningScore

Conciseness

The org-specific sections (stack table, project structure, naming, validation commands) are tight and valuable, but the Core Patterns sections re-teach generic Rust knowledge Claude already has ('Use &str not String', Cow, basic thiserror/anyhow setup, #[tokio::main]) and duplicate content — 'Never unwrap()' and the lock-across-await rule each appear twice, and the body's async/axum sections overlap substantially with references/async.md and references/axum.md. Mostly efficient, but noticeably could be tightened.

3 / 5

Actionability

Guidance is largely executable: exact commands ('joelclaw docs search "tokio graceful shutdown signal"', 'cargo clippy --all-targets --all-features') and complete copy-paste code for the key patterns (PdsError enum, graceful shutdown, tracing subscriber, libsql init, axum routes). Minor gaps remain in signature-only snippets like 'fn process_record(record: &PdsRecord) -> Result<()> { ... }' and undefined helpers (compute_embedding, Daemon::new), so it sits just below fully copy-paste ready.

4 / 5

Workflow Clarity

The Validation Checklist provides explicit checkpoint commands with context-sensitive guidance ('Documentation-only edits need document validation, not an unrelated release build') and the Library-First section mandates a pre-work search step, giving a clear sequence for most work. It lacks an explicit fix-and-rerun feedback loop after validation failures, keeping it below the top anchor.

4 / 5

Progressive Disclosure

The References table is well-signaled with per-file content descriptions, and all five referenced files exist as one-level-deep bundle files with no nested references. The minor gap is that substantial async and axum content is inlined in the body while also living in the dedicated reference files, so content is not split as cleanly as it could be.

4 / 5

Total

15

/

20

Passed

Description

88%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 strong description that explicitly states both what the skill covers and when to use it, with a well-chosen set of natural trigger terms spanning the language, toolchain, frameworks, and org-specific components. Its only weaknesses are the absence of file-extension/artifact triggers and a broad catch-all trigger that slightly raises conflict risk with other Rust skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'writing Rust code, reviewing Rust PRs, scaffolding Rust projects, debugging ownership/lifetime errors, or working on clawnode' — and enumerates topic coverage (idiomatic patterns, async/tokio, error handling, project structure, testing), giving comprehensive coverage of the skill's capabilities. This matches the anchor for multiple specific concrete actions rather than the 'minor gaps' level below.

5 / 5

Completeness

It clearly answers 'what' ('Standard operating procedures for writing Rust in joelclaw. Covers idiomatic patterns, async/tokio, error handling, project structure, testing, and clawnode-specific conventions') and 'when' with an explicit 'Use when' clause listing concrete trigger scenarios, matching the top anchor exactly.

5 / 5

Trigger Term Quality

Trigger terms 'rust', 'cargo', 'tokio', 'axum', 'clawnode', 'ownership', 'lifetimes', 'borrow checker', 'rust error' are natural phrases a user would say, with good synonym coverage around ownership/borrowing. It falls short of a 5 because no file extensions or artifact names appear (.rs, Cargo.toml) and terms like 'crate' or 'rustc' are missing.

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche (joelclaw/clawnode Rust SOP) with ecosystem-specific triggers, making it mostly distinct. The catch-all 'or any Rust development task' and generic 'rust'/'cargo' triggers create minor overlap risk with any other Rust-related skill, keeping it just below the minimal-conflict top anchor.

4 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

joelhooks/joelclaw

Path

skills/rust-sop/SKILL.md

Reviewed

Table of Contents

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.