Layerkit Multi Agent
Coordinate specialist agents for integrate or contract heal; brownfield production code.
Install
$ agentstack add skill-hariharapanigrahy-layerkit-layerkit-multi-agent ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-hariharapanigrahy-layerkit-layerkit-multi-agent) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
layerkit-multi-agent
Team of agents on the same integration pipeline. The lead agent coordinates specialists directly; Layerkit does not generate a deterministic multi-agent plan.
Start
Contract heal (map already exists — human supplies OpenAPI/docs)
- Discover task omitted
- Researcher = evidence-backed semantic rename decisions when needed
- If only docs are supplied, researcher/AI must read/cite docs before source edits
- AI agents edit production source/test files directly
- Record rename decisions in the handoff note only when docs/code evidence supports a removed-to-added field rename
First-time / multi-vendor
Use the lead agent to assign vendors/files explicitly. Keep one writer per production file and use handoff notes for state.
Roles
| Role | Skill | Heal note | |------|-------|-----------| | orchestrator | orchestrate-integration | status shows mode=heal\|full | | discoverer | discover-data-layer | not in heal plan | | stylist | align-client-style | topology for existing adapters | | researcher | research-vendor | contract pin + drift | | designer / author | design / processor | surgical on drift | | privacy | privacy-review | human if new PII | | integrator | source-edit-client | direct production source edits | | verifier | doctor + project tests | quality | | checker | checker-assist | read-only |
Concurrency
- Parallel research/integrate per vendor when files do not overlap
- Single writer:
integrator:registry - Human: privacy, checker approval, breaking drift
Forbidden
- Two agents on the same registry file
- Re-running full discover on heal when domain is known
- Invented fields or guessed renames; self-approve
- Treating generated plans as production source code
- Relying on Layerkit runtime/route/strategy code instead of editing the client package
Success
- [ ] Agent assignments match intent (heal vs full)
- [ ] Specialists have explicit files/responsibilities
- [ ] Production adapters updated
- [ ] Project tests + quality green
- [ ] Human checker handoff complete
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: hariharapanigrahy
- Source: hariharapanigrahy/layerkit
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.