agentleFS
beecode-rsbeecode-rs/claude-skills/skills/orchestrating-ts-agents/SKILL.md

orchestrating-ts-agents

Skill0 starsChanged 3 months agoNo licenceView on GitHub

Plan and then actually run multi-agent work in a TypeScript / pnpm monorepo - decide which specialist does each piece (ts-implementer, ts-tester, ts-reviewer, code-explorer, Explore, Plan, general-purpose), pick a sequential or parallel shape, write each agent's prompt, spawn them, and stitch the results back together. Use this skill whenever a TypeScript task needs more than one pass: a feature or endpoint to implement then test then review, a refactor spanning several packages, a migration or codemod, an audit or analysis document, or any request phrased as "plan this", "break this down", "orchestrate this", "which agent should do this", "use the ts agents", or "implement it and add tests". Reach for it before hand-rolling a large TS task in the main thread, because routing to the specialists keeps the main context lean and guarantees the clean-code and contract-testing skills actually get applied.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.

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.