agency-roster
Skill286 starsChanged 5 months agoMITView on GitHub
Use when a round references agency-agents catalogs, role-family routing, multi-agent identity prompts, or English/Chinese specialist role catalogs.
In this repository18 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- arcgenticSkill
- audit-roundSkill
- claude-code-session-brokerSkill
- close-roundSkill
- codex-thread-orchestrationSkill
- codify-lessonSkill
- cross-session-handoffSkill
- execute-roundSkill
- orchestrate-roundSkill
- plan-roundSkill
- pre-round-scanSkill
- session-modeSkill
- source-intakeSkill
- spec-governanceSkill
- track-refsSkill
- using-arcgenticSkill
- verify-gatesSkill
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
- Distinctive: line 21
Use selected role families to improve identity handoff prompts.
- Distinctive: line 26
Do not vendor upstream role files.
- Very specific: line 27
Do not replace planner/developer/auditor state identities with agency roles.
≈ “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.
Files
agency-roster
Parses agency-agents-style catalogs as role-family references for arcgentic identity handoffs.
Workflow
Inspect the catalog locally:
arcgentic agency-roster inspect <catalog-path>- Select role families for the round, such as minimal-change engineer, software architect, security engineer, code reviewer, or auditor.
- Use selected role families to improve identity handoff prompts.
Boundaries
- Role catalogs are references, not imported arcgentic agents.
- Do not vendor upstream role files.
- Do not replace planner/developer/auditor state identities with agency roles.
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
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.