M11 Ecosystem

This handles Rust dependency and ecosystem questions, from picking the right crate to debugging integration errors like E0433 and E0603. It includes opinionated tables for common needs (serde for serialization, tokio for async, clap for CLI) and covers FFI scenarios with bindgen, PyO3, and wasm-bindgen. The skill auto-injects your current Cargo.toml dependencies for context and pushes you to think about maintenance status and feature flags before adding dependencies. Most useful when you're weighing framework choices or troubleshooting cross-language integration. The anti-patterns section calling out extern crate and wildcard versions is a nice touch that saves you from cargo hell.

skills.sh installs: 3.5K
GitHub stars: 1.6K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add actionbook/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?