using-zuvo

Routes user requests to the matching Zuvo skill based on intent and priority.

6|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/greglas75/zuvo --skill using-zuvo-greglas75
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-zuvo
Source: https://github.com/greglas75/zuvo/tree/main/skills/using-zuvo
Command: npx skills add https://github.com/greglas75/zuvo --skill using-zuvo-greglas75

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working with a large skill ecosystem, it is hard to know which skill applies to a given request, and agents often skip quality gates by writing code directly. This Skill acts as an always-loaded router that inspects each user message and dispatches it to the correct Zuvo skill, enforcing pipeline order and quality gates. ## Core Features & Use Cases - Intent-based routing table: Maps user intents across five priority levels (Pipeline, Task, Audit, Utility, Release) to one of 58 skills such as zuvo:build, zuvo:debug, or zuvo:security-audit. - Pipeline enforcement: Ensures substantial production changes (3+ files or 150+ lines) flow through zuvo:brainstormzuvo:planzuvo:execute instead of ad-hoc edits. - Quality gates: Applies mandatory rules like tests for new code, CQ1-CQ40 self-evaluation, and review-before-push on all coding work. - Use Case: A user says "fix this login bug" — the router matches the intent to zuvo:debug and invokes it, rather than letting the agent patch the code without tests or review. ## Quick Start Ask the assistant to build a feature or fix a bug and let the router automatically invoke the matching Zuvo skill for the task.

Frequently Asked Questions about using-zuvo

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does the Zuvo skill router decide which skill to invoke?

It matches the user's message intent against a routing table organized into five priority levels: Pipeline, Task, Audit, Utility, and Release. When multiple skills match, the highest priority and most specific match wins.

When should I use zuvo:build versus the brainstorm-plan-execute pipeline?

Use zuvo:build for scoped work touching 1-5 files with clear requirements. Use the pipeline starting with zuvo:brainstorm for features touching 5 or more files or requiring design decisions.

Which platforms does the Zuvo skill ecosystem support?

Zuvo installs on Claude Code, Codex, Cursor, Antigravity, and Kimi Code using a single install script. Each platform gets an adapted distribution with the appropriate agent and skill formats.

When should requests not be routed to a skill?

Simple questions, one-line fixes, git operations, file reading, and general conversation should be handled directly. Skills are reserved for tasks requiring code analysis, non-trivial changes, or structured output.

What quality gates apply to code written without a skill?

New production files require tests, changes touching 3 or more files must go through zuvo:build, and all production code must pass the CQ1-CQ40 self-evaluation checklist before pushing.