agentleFS
matyasstochmatyasstoch/david-skills/skills/delegating-to-agents/SKILL.md

delegating-to-agents

Skill59 starsChanged 5 months agoNo licenceView on GitHub

MUST be read ANY time another AI agent is involved — sending a prompt to or polling a Pi/Codex/Claude Code/Hermes/OpenCode agent, driving an agent running in another cmux pane/surface/terminal/tmux window, delegating or relaying ANYTHING to an agent in the same cmux workspace, spawning a sub-agent, or orchestrating agent-to-agent work. Read it BEFORE the first message you send to another agent. Covers the critical rule that prompts sent to a TUI agent must be ONE single line (newlines = Enter = fragmented/cut-off prompts), short polling cadence, which agent to pick, and per-agent characteristics. If you are about to type `cmux send`/`tmux send-keys` to any agent, this skill applies.

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.