
M11 Ecosystem
- 1.4k installs
- 1.3k repo stars
- Updated May 24, 2026
- actionbook/rust-skills
m11-ecosystem is an agent skill for use when integrating crates or ecosystem questions. keywords: e0425, e0433, e0603, crate, cargo, dependency, feature flag, workspace, which crate to use, using external c.
About
The m11-ecosystem skill is designed for use when integrating crates or ecosystem questions. Keywords: E0425, E0433, E0603, crate, cargo, dependency, feature flag, workspace, which crate to use, using external C. Before adding dependencies: Is there a standard solution? --- Trace Up ↑ To domain constraints (Layer 3): | Question | Trace To | Ask | |----------|----------|-----| | Framework choice | domain-* | What constraints matter? Invoke when the user integrating crates or ecosystem questions.
- Is there a standard solution?.
- What's the maintenance status?.
- What's the API stability?.
M11 Ecosystem by the numbers
- 1,409 all-time installs (skills.sh)
- +51 installs in the week ending Jul 28, 2026 (Skillselion tracking)
- Ranked #264 of 1,896 Design & UI/UX skills by installs in the Skillselion catalog
- Security screen: HIGH risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
m11-ecosystem capabilities & compatibility
- Capabilities
- is there a standard solution? · what's the maintenance status? · what's the api stability?
- Use cases
- frontend
What m11-ecosystem says it does
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
Use when integrating crates or ecosystem questions. Keywords: E0425, E0433, E0603, crate, cargo, dependency, feature flag, workspace, which crate to use, using
npx skills add https://github.com/actionbook/rust-skills --skill m11-ecosystemAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1.4k |
|---|---|
| repo stars | ★ 1.3k |
| Security audit | 2 / 3 scanners passed |
| Last updated | May 24, 2026 |
| Repository | actionbook/rust-skills ↗ |
How do I use when integrating crates or ecosystem questions. keywords: e0425, e0433, e0603, crate, cargo, dependency, feature flag, workspace, which crate to use, using external c?
Use when integrating crates or ecosystem questions. Keywords: E0425, E0433, E0603, crate, cargo, dependency, feature flag, workspace, which crate to use, using external C.
Who is it for?
Developers using m11 ecosystem workflows documented in SKILL.md.
Skip if: Skip when the task falls outside m11-ecosystem scope or needs a different stack.
When should I use this skill?
User integrating crates or ecosystem questions.
What you get
Completed m11-ecosystem workflow with documented commands, files, and expected deliverables.
- Crate recommendation
- Cargo.toml dependency block
- Feature-flag configuration
By the numbers
- Targets Rust errors E0425, E0433, and E0603
- Auto-injects up to 30 lines from Cargo.toml dependencies
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:
1. Is it well-maintained?
- Recent commits?
- Active issue response?
- Breaking changes frequency?
2. What's the scope?
- Do you need the full crate or just a feature?
- Can feature flags reduce bloat?
3. How does it integrate?
- Trait-based or concrete types?
- Sync or async?
- What bounds does it require?
---
Trace Up ↑
To domain constraints (Layer 3):
"Which HTTP framework should I use?"
↑ Ask: What are the performance requirements?
↑ Check: domain-web (latency, throughput needs)
↑ Check: Team expertise (familiarity with framework)| Question | Trace To | Ask |
|---|---|---|
| Framework choice | domain-* | What constraints matter? |
| Library vs build | domain-* | What's the deployment model? |
| API design | domain-* | Who are the consumers? |
---
Trace Down ↓
To implementation (Layer 1):
"Integrate external crate"
↓ m04-zero-cost: Trait bounds and generics
↓ m06-error-handling: Error type compatibility
"FFI integration"
↓ unsafe-checker: Safety requirements
↓ m12-lifecycle: Resource cleanup---
Quick Reference
Language Interop
| Integration | Crate/Tool | Use Case |
|---|---|---|
| C/C++ → Rust | bindgen | Auto-generate bindings |
| Rust → C | cbindgen | Export C headers |
| Python ↔ Rust | pyo3 | Python extensions |
| Node.js ↔ Rust | napi-rs | Node addons |
| WebAssembly | wasm-bindgen | Browser/WASI |
Cargo Features
| Feature | Purpose |
|---|---|
[features] | Optional functionality |
default = [...] | Default features |
feature = "serde" | Conditional deps |
[workspace] | Multi-crate projects |
Error Code Reference
| Error | Cause | Fix |
|---|---|---|
| E0433 | Can't find crate | Add to Cargo.toml |
| E0603 | Private item | Check crate docs |
| Feature not enabled | Optional feature | Enable in features |
| Version conflict | Incompatible deps | cargo update or pin |
| Duplicate types | Different crate versions | Unify in workspace |
---
Crate Selection Criteria
| Criterion | Good Sign | Warning Sign |
|---|---|---|
| Maintenance | Recent commits | Years inactive |
| Community | Active issues/PRs | No response |
| Documentation | Examples, API docs | Minimal docs |
| Stability | Semantic versioning | Frequent breaking |
| Dependencies | Minimal, well-known | Heavy, obscure |
---
Anti-Patterns
| Anti-Pattern | Why Bad | Better |
|---|---|---|
extern crate | Outdated (2018+) | Just use |
#[macro_use] | Global pollution | Explicit import |
Wildcard deps * | Unpredictable | Specific versions |
| Too many deps | Supply chain risk | Evaluate necessity |
| Vendoring everything | Maintenance burden | Trust crates.io |
---
Related Skills
| When | See |
|---|---|
| Error type design | m06-error-handling |
| Trait integration | m04-zero-cost |
| FFI safety | unsafe-checker |
| Resource management | m12-lifecycle |
Related skills
Forks & variants (1)
M11 Ecosystem has 1 known copy in the catalog totaling 760 installs. They canonicalize to this original listing.
- zhanghandong - 760 installs
How it compares
Pick m11-ecosystem over general Rust syntax skills when the blocker is crate selection, Cargo.toml configuration, or cross-language binding setup.
FAQ
What does m11-ecosystem do?
Use when integrating crates or ecosystem questions. Keywords: E0425, E0433, E0603, crate, cargo, dependency, feature flag, workspace, which crate to use, using external C.
When should I use m11-ecosystem?
User integrating crates or ecosystem questions.
Is m11-ecosystem safe to install?
Review the Security Audits panel on this page before installing in production.