multi-agent-orchestration
Skill94 starsChanged 6 months agoNo licenceArchived repositoryView on GitHub
Invariants, lifecycle documentation, and error recovery strategies for PolyPilot's multi-agent orchestration system. Use when: (1) Modifying dispatch logic in SendViaOrchestratorAsync or SendViaOrchestratorReflectAsync, (2) Touching worker execution, result collection, or synthesis phases, (3) Modifying PendingOrchestration persistence or resume logic, (4) Debugging orchestrator-worker communication failures, (5) Adding error handling around worker dispatch or completion, (6) Modifying OnSessionComplete coordination or TCS ordering, (7) Working with reflection loop concurrency (semaphores, queued prompts), (8) Modifying SessionIdleEvent handling or IDLE-DEFER logic (BackgroundTasks check). Covers: 5-phase dispatch lifecycle, IDLE-DEFER background task guard, restart recovery via PendingOrchestration, worker failure patterns, and connection error handling.
We split this skill into the rules it gives an agent
32 rules. 0 are common, 15 are distinctive, and 17 are very specific to this project.
0
Common
Most of the 15 edited versions we read keep these.
15
Distinctive
This author's own choices. Worth a look.
17
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 measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Other versions18 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 18
- mizchi/skills★ 369same name
- DevelopersGlobal/ai-agent-skills★ 216same name
- roedyrustam/vibes-plug★ 75same name
- VoDaiLocz/kilo-kit-mcp★ 28same name
- composio-community/opencode-skills★ 14same name
- DavidTeju/shared-skills★ 9same name
- mnzralee/claude-multi-agent-architecture★ 8same name
- uvwt/agentdock-skills★ 6same name
- javalenciacai/QASkills★ 5same name
- thejordanleopold/claude-code-skills-distilled★ 4same name
8 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use refactoring, observability and 5 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
pproencaSkillrefactoring
Code refactoring best practices based on Martin Fowler's catalog and Clean Code principles. This skill should be used when refactoring existing code, improving code structure, reducing complexity, eliminating code smells, or reviewing code for maintainability. Triggers on tasks involving extract method, rename, decompose conditional, reduce coupling, or improve readability.
Also in 3 projects that use this
OpenAISkillobservability
Vercel Observability expert guidance — Drains (logs, traces, speed insights, web analytics), Web Analytics, Speed Insights, runtime logs, custom events, OpenTelemetry integration, and monitoring dashboards. Use when instrumenting, debugging, or optimizing application performance and user experience on Vercel.
Also in 3 projects that use this
kongyo2Skillprompt-engineering
Comprehensive prompt engineering framework for designing, optimizing, and iterating LLM prompts. This skill should be used when users request prompt creation, optimization, or improvement for any LLM task, or when users need help translating vague requirements into effective prompts through collaborative dialogue and iterative refinement.
Also in 3 projects that use this
MicrosoftSkillapi-design
Guide for designing and documenting RESTful APIs. Use when asked to design an API, create endpoints, or document an API.
Also in 4 projects that use this
Microsoft AzureSkillgit-workflow
Squad branching model: dev-first workflow with insiders preview channel
Also in 3 projects that use this
SentrySkillsecurity-review
Finds exploitable application security vulnerabilities in code changes. Use for Warden security scans, appsec review, OWASP-style checks, authentication or authorization bugs, injection, XSS, SSRF, path traversal, secrets, unsafe crypto, webhook verification, open redirects, or sensitive data exposure.
Also in 3 projects that use this
In this repository11 other files it gives its agents.
- .github/copilot-instructions.mdCopilot instructions
- android-wifi-deploySkill
- auth-token-safetySkill
- copilot-sdk-referenceSkill
- gh-aw-guideSkill
- health-monitoringSkill
- instruction-driftSkill
- maui-ai-debuggingSkill
- performance-optimizationSkill
- processing-state-safetySkill
- release-notesSkill
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.