agentleFS
Sign inStart free
oliverweissloliverweissl/context-garden/skills/mycelium/SKILL.md

mycelium

Skill4 starsChanged 16 days agoMITView on GitHub

Decide whether to spawn subagents (one, or several in parallel) to search, investigate or edit, and brief them well; passes finding notes between agents so they don't redo the same exploration. Use before delegating to an agent and after an agent reports findings.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. tdimino/claude-code-minoan★ 41same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check shared notes: <this-skill-dir>/bin/mycelium brief "<task>".

    line 26
  2. Distinctive:

    Write the brief with these lines (the plugin's gate hook denies an Agent call that lacks them and tells you what's missing):

    line 27
  3. Very specific:

    Never spawn a second agent for the same investigation: reuse the first result or continue that agent.

    line 36

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

mycelium

!"${CLAUDE_SKILL_DIR}/bin/mycelium" mode --banner

Agents that do not expand the line above (e.g. Codex): run <this-skill-dir>/bin/mycelium mode --banner first and follow it.

Delegation costs a fresh context per agent. Default to doing the work yourself: a single file lookup, a small edit or one test command never needs an agent.

mycelium is not on PATH: always use the full <this-skill-dir>/bin/mycelium path. Notes live in <git root>/.mycelium/notes.json. From a folder of repos, name files as <repo>/<path>: each note goes to the repo that holds the file.

Before spawning an agent

  1. Delegate only a bounded task with a finish condition. Prefer one agent; run agents in parallel only for independent tasks.
  2. Check shared notes: <this-skill-dir>/bin/mycelium brief "<task>".
  3. Write the brief with these lines (the plugin's gate hook denies an Agent call that lacks them and tells you what's missing):
    Task: <one question or change, with a finish condition>
Why delegate: <why the main thread would be less efficient>
Known: <relevant notes from `brief`, or "none relevant">
Return: <findings with file:line, answer, unresolved questions>
Budget: <max searches/turns; on exhaustion return partial findings>
  4. Never spawn a second agent for the same investigation: reuse the first result or continue that agent. The gate denies near-duplicates unless a Not a duplicate: <how> line explains the difference.
  5. For code search use a read-only agent (scout, installed by bin/mycelium install-agents); use an editing agent only when it owns a distinct change.

After an agent returns

A reply's Notes: block (- <topic> | <finding> | <file>..., part of scout's format; add it to your Return: for other agents) is recorded by the plugin's SubagentStop hook. Record any other durable finding once, with the files it describes:

<this-skill-dir>/bin/mycelium note "<subsystem>" "<finding>" <file>...

Notes are hashed against their files; bin/mycelium list --stale shows notes whose files changed. Re-check, then bin/mycelium verify <id>, or bin/mycelium drop <id>. Keep task status out of notes (or use --kind status, which is never briefed).

Gate modes, hook setup, note format: references/protocol.md.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free