orchestrating-agents — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited orchestrating-agents (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Renamed to orchestrating-chat-agents on 2026-10-11.
The old name sent requests to the wrong skill. Shown only skill names, Haiku, Sonnet and Opus 5.5 routed 10 of 45 parallel-dispatch requests here, work that belongs to dispatching-subagents. Of seven candidate names, orchestrating-chat-agents caught the most of this skill's own requests (19/21 against 15/21) without drawing more of the others' (oaustegard/experiments subagent-skill-choice). The content is the same: API fan-out from surfaces with no native subagents, and Gemini delegation.
| you want | go to |
|---|---|
parallel Claude calls over the API from claude.ai, ConversationThread, AgentPool | orchestrating-chat-agents |
fan-out in Claude Code: Agent tool vs Workflow vs headless claude -p | dispatching-subagents |
SendMessage / ListAgents between native subagents | dispatching-subagents/references/native-messaging.md |
| which model or effort a subagent gets | agent-routing |
scripts/ here holds shims, so sys.path.insert(0, '/mnt/skills/user/orchestrating-agents/scripts') followed by from claude_client import invoke_claude still works. Point new code at /mnt/skills/user/orchestrating-chat-agents/scripts.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.