SkillAgentSearch skills...

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 recommend…

Install / Use

npx skills add actionbook/rust-skills --skill m11-ecosystem

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

87/100

Supported Platforms

Universal

Our assessment of m11-ecosystem

m11-ecosystem scores 87/100 on our quality scale, 2175th of 4,700 Development & Engineering skills we index (top 47%).

Its SKILL.md is 4.3 KB long, well organised into 14 sections with 2 code examples: a solid amount of guidance for an agent.

With 1,479 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
18/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 3 months ago, so m11-ecosystem is actively maintained.
  • Our last check on 2026-11-02 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-03. Automated pattern scan on 2026-10-03. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

m11-ecosystem compared with similar skills

All 4 of these similar skills score higher than m11-ecosystem; compare them before choosing.

SkillScoreStarsUpdatedFormat
m11-ecosystem (this skill)by actionbook871.5k3mo agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
Agent-Reachby Panniantong100112.3k9d agoCLAUDE.md
headroomby headroomlabs-ai10079.8ktodayCLAUDE.md
ai-job-searchby ai-job-search-dev10072.1ktodayCLAUDE.md

Frequently asked questions

How do I install m11-ecosystem?
Run npx skills add actionbook/rust-skills --skill m11-ecosystem. The install tabs above show the steps for each supported agent.
Which AI agents does m11-ecosystem work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is m11-ecosystem safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is m11-ecosystem still maintained?
The repository was last updated about 3 months ago, so m11-ecosystem is actively maintained.

name: m11-ecosystem description: "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 绑定" user-invocable: false

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

View on GitHub
GitHub Stars1.5k
CategoryDevelopment
Updated2mo ago
Forks114

Languages

Shell

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium
m11-ecosystem — Universal Skill: Install & Safety Check | SkillAgent