Advanced~18 minHazelJS
Multi-Agent and Skillgate
Journey C: ops-router, fraud path, Skillgate report/tools, and MCP export.
- Authors
- editorial-team
- Published
- Last reviewed
- Use the router door and a specialist path
- Read Skillgate include/deny report
- Say when Skillgate beats registering every CRUD route
On this page
Journey C — Multi-agent and Skillgate
Router door (F12)
curl -s localhost:3060/api/chat \
-H 'content-type: application/json' \
-d '{"message":"Track ORD-1001"}' | jq '{agent, steps, response}'
ops-router delegates to specialists (@Delegate / graph patterns). Why multiple DNA? Independent versioning + role separation.
Fraud path (partial in tour):
curl -s localhost:3060/api/fraud/chat \
-H 'content-type: application/json' \
-d '{"message":"Freeze ACC-RISK — high fraud risk"}' | jq .
Skillgate curation (F13)
REST controllers + @AgentSkill → OpenAPI → Skillgate.fromOpenApi → tools on api-concierge (src/skillgate/*). Include tags, deny /internal/, gate destructive/admin behind env flags.
curl -s 'localhost:3060/api/skillgate/report?json=1' | jq '{included: .included|length, denied: .denied|length}'
curl -s localhost:3060/api/ops/chat \
-H 'content-type: application/json' \
-d '{"message":"List recent orders"}' | jq .
Guide: /guides/skillgate-from-openapi-to-tool-registry. Comparison: /compare/mcp-vs-skillgate-vs-direct-api.
MCP export (F14)
# API must be up
npm run mcp
Same curated skills for IDE agents — transport, not a substitute for Agent OS governance.
Checkpoint G
When does Skillgate beat “register every CRUD route as a tool”? (Hint: curation, deny lists, write approval, reportability.)
Artifact: Checkpoint G: Skillgate curation rationale
Sources
- Meridian Ops README — hazeljs-meridian-ops/README.md — mental model + quick start
- Meridian TOUR.md — F1–F22 curl walkthrough
- Flagship project plan (21) — docs/agent-os/21-flagship-project-plan.md
- HazelJS Agent OS guide
- HazelJS Agent package