Agent skill

M11 Ecosystem

by fjrevoredo in fjrevoredo/mini-diarium

A skill your agent uses when integrating crates or ecosystem questions.

MITAuto-check passed

Install M11 Ecosystem

skills CLI

$ npx skills add fjrevoredo/mini-diarium --skill m11-ecosystem -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install fjrevoredo/mini-diarium m11-ecosystem --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/fjrevoredo/mini-diarium.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/m11-ecosystem .claude/skills/m11-ecosystem && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "m11-ecosystem" agent skill from https://github.com/fjrevoredo/mini-diarium/tree/master/.agents/skills/m11-ecosystem into .claude/skills/m11-ecosystem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "m11-ecosystem", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/fjrevoredo/mini-diarium/tree/master/.agents/skills/m11-ecosystem

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add fjrevoredo/mini-diarium --skill m11-ecosystem -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install fjrevoredo/mini-diarium m11-ecosystem --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/fjrevoredo/mini-diarium.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/m11-ecosystem .agents/skills/m11-ecosystem && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "m11-ecosystem" agent skill from https://github.com/fjrevoredo/mini-diarium/tree/master/.agents/skills/m11-ecosystem into .agents/skills/m11-ecosystem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "m11-ecosystem", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add fjrevoredo/mini-diarium --skill m11-ecosystem -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install fjrevoredo/mini-diarium m11-ecosystem --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/fjrevoredo/mini-diarium.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/m11-ecosystem .cursor/skills/m11-ecosystem && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "m11-ecosystem" agent skill from https://github.com/fjrevoredo/mini-diarium/tree/master/.agents/skills/m11-ecosystem into .cursor/skills/m11-ecosystem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "m11-ecosystem", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/fjrevoredo/mini-diarium.git --path .agents/skills/m11-ecosystem

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add fjrevoredo/mini-diarium --skill m11-ecosystem -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install fjrevoredo/mini-diarium m11-ecosystem --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/fjrevoredo/mini-diarium.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/m11-ecosystem .gemini/skills/m11-ecosystem && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "m11-ecosystem" agent skill from https://github.com/fjrevoredo/mini-diarium/tree/master/.agents/skills/m11-ecosystem into .gemini/skills/m11-ecosystem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "m11-ecosystem", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install fjrevoredo/mini-diarium m11-ecosystem

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add fjrevoredo/mini-diarium --skill m11-ecosystem -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/fjrevoredo/mini-diarium.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/m11-ecosystem .github/skills/m11-ecosystem && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "m11-ecosystem" agent skill from https://github.com/fjrevoredo/mini-diarium/tree/master/.agents/skills/m11-ecosystem into .github/skills/m11-ecosystem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "m11-ecosystem", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add fjrevoredo/mini-diarium --skill m11-ecosystem -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install fjrevoredo/mini-diarium m11-ecosystem --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/fjrevoredo/mini-diarium.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/m11-ecosystem .opencode/skills/m11-ecosystem && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "m11-ecosystem" agent skill from https://github.com/fjrevoredo/mini-diarium/tree/master/.agents/skills/m11-ecosystem into .opencode/skills/m11-ecosystem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "m11-ecosystem", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: m11-ecosystem
GitHub stars: 308
Used in: 1 other repo
Token cost: ~1.1k tokens
SKILL.md length: 369 words
Files: 1
Skills in repo: 41
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

A skill your agent uses when integrating crates or ecosystem questions.

Works in 3 steps: Is it well-maintained? → What's the scope? → How does it integrate?
Integrating crates
SKILL.md covers Current Dependencies…, Core Question, Integration Decision →… and Thinking Prompt, plus 7 more sections
Calls cargo

What it does

M11 Ecosystem is an agent skill from fjrevoredo/mini-diarium. 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 绑定

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with WebAssembly, Rust and Python. The repository describes itself as: A local-only journal with serious encryption. Free, open source, and never touches the internet. The licence is MIT.

When your agent uses it

Integrating crates
Ecosystem questions

Example prompts

“/m11-ecosystem”

Requirements

Python 3
Node.js

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

Is it well-maintained?
What's the scope?
How does it integrate?

What it can do on your machine

Read from SKILL.md and the folder at commit eed457f. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- cargo
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

M11 Ecosystem loads about 1.1k tokens when it runs. Until then it costs about 99 tokens; SKILL.md has 369 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~99
When it runs · the whole SKILL.md, loaded when a task matches: ~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from fjrevoredo/mini-diarium at commit eed457f, republished under its MIT licence (© fjrevoredo). 369 words, ~1,111 tokens.

Download SKILL.mdSave it as .claude/skills/m11-ecosystem/SKILL.md (or your agent's skills folder).

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:

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?
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

Show full SKILL.md (146 more words)Show less

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

When	See
Error type design	m06-error-handling
Trait integration	m04-zero-cost
FFI safety	unsafe-checker
Resource management	m12-lifecycle

Files

Just SKILL.md in .agents/skills/m11-ecosystem of fjrevoredo/mini-diarium.

Open the folder on GitHubat commit eed457f

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in fjrevoredo/mini-diarium, which our catalogue first saw on October 7, 2026.

NeverSight/learn-skills.devdata/skills-md/actionbook/rust-skills/m11-ecosystem

Compare with similar skills

M11 Ecosystem next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

M11 Ecosystem compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
M11 Ecosystem this skillfjrevoredo/mini-diarium	308	1 repos	~1.1k	Automated safety check: Pass	MIT	today
Edge Pythondylan-sutton-chavez/edge-python	273	—	~11k	Automated safety check: Pass	Custom licence	today
Test Runnernoumena-labs/Sipp	121	—	~854	Automated safety check: Pass	Apache-2.0	19 days ago
Daemon Devnteract/nteract	179	—	~3k	Automated safety check: Pass	BSD-3-Clause	today
Check Loanwordayutaz/piper-plus	230	—	~1.1k	Automated safety check: Pass	MIT	today
Check Runtime Parityayutaz/piper-plus	230	—	~972	Automated safety check: Pass	MIT	today

Similar skills

Edge Python
dylan-sutton-chavez/edge-python
Write, run, test and package Edge Python programs with the edge CLI.
273 GitHub stars~11k tokensUpdated today
SecurityAuto-check passed
Test Runner
noumena-labs/Sipp
Runs the narrowest relevant tests to validate changes. An agent skill from noumena-labs/Sipp.
121 GitHub stars~854 tokensUpdated 19 days ago
AI & LLM EngineeringAuto-check passed
Daemon Dev
nteract/nteract
Develop, debug, and manage the runtimed daemon, Python bindings, and build system.
179 GitHub stars~3k tokensUpdated today
DevelopmentAuto-check passed
Check Loanword
ayutaz/piper-plus
ZH-EN code-switching loanword の同期と forward-compat を 1 コマンドで検査。zhenloanword.json を編集したり 5 ランタイムのいずれかに新規エントリを追加する前後に呼ぶ。Python source を canonical とし、Rust×2 / Go / C / WASM / C++ の 6 mirror + Python…
230 GitHub stars~1.1k tokensUpdated today
DevelopmentAuto-check passed
Check Runtime Parity
ayutaz/piper-plus
推論パスの canonical Python (exportonnx.py / vits/models.py:VitsModel.infer) を変更した PR で、6 ランタイム (Python runtime / Rust / Go / C / C++ / WASM) の inference path が追随しているかを git diff で確認。PR
230 GitHub stars~972 tokensUpdated today
AI & LLM EngineeringAuto-check passed
Prepare Release
ayutaz/piper-plus
9 パッケージ × 5 レジストリの version bump と関連ファイル更新 (Cargo.lock / package-lock.json / Swift checksum / CHANGELOG 昇格) を 1 コマンドで適用案にする read-mostly skill。release-prep (確認用) の続きに呼び、実 bump 差分の markdown 提案 + 順序付き…
230 GitHub stars~2k tokensUpdated today
DevelopmentAuto-check passed

Questions about M11 Ecosystem

What does M11 Ecosystem do?

A skill your agent uses when integrating crates or ecosystem questions. M11 Ecosystem is an agent skill from fjrevoredo/mini-diarium. Use when integrating crates or ecosystem questions.

When should I use M11 Ecosystem?

M11 Ecosystem fits situations like: integrating crates; ecosystem questions.

How do I install M11 Ecosystem in Claude Code?

Run `npx skills add fjrevoredo/mini-diarium --skill m11-ecosystem -a claude-code`. Or copy the skill folder (.agents/skills/m11-ecosystem in fjrevoredo/mini-diarium) into .claude/skills/m11-ecosystem in your project. Claude Code loads it when a task matches its description.

How do I install M11 Ecosystem in Codex?

Run `npx skills add fjrevoredo/mini-diarium --skill m11-ecosystem -a codex`. Or copy the skill folder (.agents/skills/m11-ecosystem in fjrevoredo/mini-diarium) into .agents/skills/m11-ecosystem in your project. Codex loads it when a task matches its description.

Can I use M11 Ecosystem in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add fjrevoredo/mini-diarium --skill m11-ecosystem -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/m11-ecosystem, .gemini/skills/m11-ecosystem, .github/skills/m11-ecosystem and .opencode/skills/m11-ecosystem in your project.

What does M11 Ecosystem need to run?

Going by SKILL.md and its folder, M11 Ecosystem needs the command-line tools its instructions call (cargo). Our summary lists: Python 3; Node.js.

Does M11 Ecosystem access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is M11 Ecosystem safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does M11 Ecosystem use?

M11 Ecosystem is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does M11 Ecosystem use?

About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to M11 Ecosystem?

Skills that share tags, products or a category with M11 Ecosystem: Edge Python (dylan-sutton-chavez/edge-python, 273 stars), Test Runner (noumena-labs/Sipp, 121 stars), Daemon Dev (nteract/nteract, 179 stars) and Check Loanword (ayutaz/piper-plus, 230 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains M11 Ecosystem?

fjrevoredo (a GitHub user) maintains it in fjrevoredo/mini-diarium, which has 308 GitHub stars. The repository holds 41 skills in this directory. The repository was last updated on October 9, 2026.

Source: fjrevoredo/mini-diarium on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install M11 Ecosystem

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Current Dependencies (Auto-Injected)

Ecosystem Integration

Core Question

Integration Decision → Implementation

Thinking Prompt

Trace Up ↑

Trace Down ↓

Quick Reference

Language Interop

Cargo Features

Error Code Reference

Crate Selection Criteria

Anti-Patterns

Related Skills

Files

Used in 1 other repository

Compare with similar skills

Similar skills

More from fjrevoredo/mini-diarium

Related

Questions about M11 Ecosystem