agentleFS
Sign inStart free
docxologydocxology/codomyrmex/.agents/skills/agent-interop/SKILL.md

agent-interop

Skill10 starsChanged 38 days agoMITView on GitHub

Keep Codex, Claude Code, and Hermes workflows aligned through portable skills, explicit runtime adapters, and shared MCP contracts.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Treat .agents/skills/ as the portable, repository-scoped skill layer.

    line 8
  2. Distinctive:

    Keep tool names, schemas, approval expectations, and verification steps in the shared documentation.

    line 13
  3. Distinctive:

    When transferring work, pass objective, scope, assumptions, files changed, tool calls made, evidence, unresolved risks, and the next …

    line 15

≈ “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

Agent Interoperability

Treat .agents/skills/ as the portable, repository-scoped skill layer. Keep runtime-specific configuration in the runtime’s own file and link back to the portable skill instead of duplicating its logic.

  • Codex discovers project skills from .agents/skills/ and project MCP settings from .codex/config.toml.
  • Claude Code uses .claude/skills/ and project MCP settings from .mcp.json; when a portable skill is not mirrored there, read the corresponding .agents/skills/<name>/SKILL.md explicitly.
  • Hermes can discover the same tree through skills.external_dirs in ~/.hermes/config.yaml; external skill directories are read-only discovery sources.
  • Keep tool names, schemas, approval expectations, and verification steps in the shared documentation. Do not rely on one runtime’s permission model being honored by another.

When transferring work, pass objective, scope, assumptions, files changed, tool calls made, evidence, unresolved risks, and the next verification step. Prefer a small handoff record over copying hidden conversational state.

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