CtrlK
BlogDocsLog inGet started
Tessl Logo

m11-ecosystem

Use when integrating crates or ecosystem questions. Keywords: E0425, E0433, E0603, crate, cargo, dependency, feature flag, workspace, which crate to use, using external C libraries, creating Python extensions, PyO3, wasm, WebAssembly, bindgen, cbindgen, napi-rs, cannot find, private, crate recommendation, best crate for, Cargo.toml, features, crate 推荐, 依赖管理, 特性标志, 工作空间, Python 绑定

62

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/m11-ecosystem/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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, table-driven reference skill that gives concrete crate and error-fix recommendations. Its weak spots are padding with concepts Claude already knows and the absence of any sequenced workflow with validation for a skill that advises on dependency decisions.

Suggestions

Cut the generic 'Thinking Prompt' questions and the basic Cargo-features table; replace with a one-line decision rule to tighten token use.

Add a short ordered workflow (evaluate maintenance → check scope/feature flags → verify trait/bounds compatibility → confirm via `cargo check`) with an explicit validation checkpoint.

Replace a couple of recommendation tables with a minimal executable snippet (e.g. a representative `[dependencies]` + `[features]` Cargo.toml excerpt) to lift actionability.

DimensionReasoningScore

Conciseness

Tables are information-dense, but the generic 'Thinking Prompt' questions and the basic Cargo-features table ([features], default, etc.) restate knowledge Claude already has, so it is mostly efficient with notable padding.

3 / 5

Actionability

Provides concrete, specific guidance — named crates (serde, tokio, reqwest, axum) and error→fix mappings (E0433 → 'Add to Cargo.toml') — with only minor gaps from the near-absence of executable code or commands.

4 / 5

Workflow Clarity

This is a decision/reference skill rather than a sequenced process; the loose three-question 'Thinking Prompt' gives a rough framework but there is no ordered workflow or validation checkpoints, matching the 3 anchor's 'sequence present but checkpoints missing'.

3 / 5

Progressive Disclosure

Well-organized into clearly headed sections (Integration Decision, Quick Reference, Error Code Reference, Anti-Patterns) with single-level 'Related Skills' cross-references; no bundle files exist, so structure is carried entirely by sectioning, with minor organization gaps.

4 / 5

Total

14

/

20

Passed

Description

86%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, keyword-rich description with an explicit trigger clause and a clear Rust-ecosystem niche. The only weakness is that the headline 'what' is somewhat generic, leaning on the keyword list to supply concreteness.

Suggestions

Lead with a concrete action clause before the keywords, e.g. 'Recommend and integrate Rust crates for a task. Use when …' to strengthen the 'what'.

Group the keyword sprawl into a short bulleted trigger list so the description reads as guidance rather than a raw tag dump.

DimensionReasoningScore

Specificity

Lists several concrete sub-capabilities ('using external C libraries', 'creating Python extensions', 'PyO3', 'wasm', 'feature flag', 'workspace') rather than a single vague action, with minor coverage gaps keeping it below a 5.

4 / 5

Completeness

Explicit 'Use when integrating crates or ecosystem questions' answers 'when' and the keyword list elaborates 'what', but the core 'what' statement ('integrating crates or ecosystem questions') is slightly less concrete than the 5 anchor's enumerated actions.

4 / 5

Trigger Term Quality

Comprehensive natural keyword coverage including synonyms (wasm/WebAssembly), tool names (bindgen, cbindgen, napi-rs), file names (Cargo.toml), error codes (E0425, E0433, E0603), and bilingual terms — matching the 5 anchor's inclusion of synonyms and extensions.

5 / 5

Distinctiveness Conflict Risk

Tightly scoped to the Rust crate ecosystem via cargo/Cargo.toml/PyO3/bindgen triggers, giving a clear niche with minimal overlap risk against other skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
actionbook/rust-skills
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.