Routes semantic collaboration requests to external AI providers through a bounded JSON coordinator.
npx skills add https://github.com/sumitake/agent-collab --skill route-sumitake
Please help me install this Agent Skill. Skill: route Source: https://github.com/sumitake/agent-collab/tree/main/plugins/agent-collab/skills/route Command: npx skills add https://github.com/sumitake/agent-collab --skill route-sumitake
coordinator.py using logical actions such as review.repository, codegen.repository, or context.documents.reason. - Targeted and independent review: Honor operator-named providers via explicit_target, or bind a caller-verified distinct reviewer for authorized independent review and governance tasks. - Planning vs live dispatch: Set dispatch_requested=false for provider-free planning of route eligibility, or true for a live request consuming at most one provider attempt per work unit. - Use Case: An operator says "ask Codex to review this repository." The caller resolves the plugin root, builds a routing request with the review.repository action, quality profile, effort class, and explicit_target, then sends it to the coordinator and interprets the returned content records. ## Quick Start Ask the agent to route a repository review to Codex by building one bounded JSON routing request and sending it to the plugin's coordinator.py over stdin.High-intent search queries and answers about installing and using this skill.
Build one bounded JSON routing request with the review.repository action, a quality profile, and an effort class, then send it on stdin to python3 coordinator.py at the plugin root. Use explicit_target when the operator names a specific provider.
Supported actions include architecture.conceptual, architecture.repository, review.repository, governance.repository, codegen.repository, frontend_codegen.repository, frontend_review.repository, and context extract/reason actions for documents and repositories.
The caller verifies the reviewer's provider family before dispatch and binds it with explicit_target, then checks the returned native lineage afterward. A route, receipt, or self-assertion alone never proves independence.
Yes, set dispatch_requested to false for a planning-only request. Planning reports route eligibility from known family evidence, not live availability or authentication state.
A consumed work unit is never replayed, retried, or failed over to another provider. Preserve any recovered partial content record and report the failure at the caller or client layer.
ReadyToGo-EducationPublish a local HTML page to Lovable via API and return a public URL.
dungnt97Identify security holes and failure modes in code changes via adversarial reasoning.
8DionysusConverts reviewed session evidence into a bounded multi-axis progression delta with verdicts and hints.
ClaudioCeppi83Control Spotify playback and search tracks from the terminal.