How to use
- Copy the installation command and review the source package before installing it in your own agent environment.
- Check the source document for required tools, credentials and supported hosts.
- Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/poorvith-mp/skills-agents --skill agent-architectureBefore you start
- Installation does not include a model subscription, API allowance or permission to access your files.
- Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
Agent Architecture
Design multi-agent systems where coordination does not become the failure mode.
Process
- Justify the second agent. Most tasks that look multi-agent are one agent with better tools. Split only when roles need genuinely different context or run concurrently.
- Decompose by context boundary, not by job title. An agent exists to hold a distinct working set, not to mirror an org chart.
- Define the contract between agents — the exact shape of what is passed, and what is guaranteed about it. Free-text handoff is where multi-agent systems lose information.
- Decide where state lives. Shared mutable state between agents needs the same care as between threads.
- Isolate failure. One agent failing or looping must not stall the others; set timeouts and a supervisor that can terminate.
- Make the trace reconstructable. When output is wrong, you need to see which agent decided what, with what input.
- Bound the total cost. Agents that can spawn agents need a hard ceiling.
Deliverables
- Role decomposition with the context boundary justifying each agent
- Message contracts between agents
- Failure isolation, timeouts and supervision model
- Trace format and cost ceiling
Verification & Quality Checklist
- [ ] Code compiles and all automated tests and typechecks pass without new warnings.
- [ ] Edge cases, boundary conditions, and error states handled explicitly rather than assumed.
- [ ] No hardcoded secrets, credentials, or insecure defaults introduced.
- [ ] Changes are covered by a test that fails without them.
Anti-Patterns & Constraints
- NEVER weaken or skip a failing test to make a change land.
- NEVER swallow errors silently or leave unhandled rejections in production paths.
- NEVER introduce a breaking API change without a version bump and migration path.