M11 Ecosystem

The m11-ecosystem skill helps developers select appropriate Rust crates and manage dependencies by providing decision matrices, evaluation criteria, and integration patterns for common use cases like serialization, async runtimes, HTTP frameworks, and language interoperability. It's designed for Rust developers and maintainers who need to make informed choices about adding external dependencies, assessing crate quality and maintenance status, and understanding how new crates integrate with existing code architecture. The skill solves the problem of decision paralysis when choosing between multiple crate options and ensures selections align with project constraints and team expertise.

skills.sh installs: 747
GitHub stars: 1.3K
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add zhanghandong/rust-skills --skill m11-ecosystem --agent claude-code

Installs into .claude/skills of the current project.

Files

Current Dependencies (Auto-Injected)

!grep -A 100 '^\[dependencies\]' Cargo.toml 2>/dev/null | head -30 || echo "No Cargo.toml found"

Ecosystem Integration

Layer 2: Design Choices

Core Question

What's the right crate for this job, and how should it integrate?

Before adding dependencies:

Is there a standard solution?
What's the maintenance status?
What's the API stability?

Integration Decision → Implementation

Need	Choice	Crates
Serialization	Derive-based	serde, serde_json
Async runtime	tokio or async-std	tokio (most popular)
HTTP client	Ergonomic	reqwest
HTTP server	Modern	axum, actix-web
Database	SQL or ORM	sqlx, diesel
CLI parsing	Derive-based	clap
Error handling	App vs lib	anyhow, thiserror
Logging	Facade	tracing, log

Thinking Prompt

Before adding a dependency:

Is it well-maintained?
- Recent commits?
- Active issue response?
- Breaking changes frequency?
What's the scope?
- Do you need the full crate or just a feature?
- Can feature flags reduce bloat?