metraton
UserSecurity-first multi-agent orchestration plugin for Claude Code — classifies every command by risk, gates state-changing operations behind consent, injects project context, and routes work to specialist agents. One unified plugin.
Categories
Indexed Skills (38)
agent-approval-protocol
Use for approval_request, COMMAND_SET, approval identifiers, fingerprints, and progress data
agent-contract-handoff
Use for the exact input/output schema and validation rules of agent_contract_handoff
agent-creation
Use when creating a new specialist agent for Gaia, or reviewing whether an existing agent follows the correct structure, tone, and component inventory
agent-response
Use when the orchestrator must read, reconcile, route, and present an agent_contract_handoff
agentic-loop
Use when the orchestrator injects "Carga la skill agentic-loop" with a goal, eval_command, metric, and threshold
brief-spec
Use when the user wants to create a brief or spec for a feature before planning
gaia-patterns
Use when building or modifying Gaia components -- agents, skills, hooks, CLI tools, or routing config
gaia-planner
Use when planning features or decomposing work into tasks from a brief
gaia-release
Use when testing, validating, or publishing Gaia releases -- "install local", "pre-release", "dry-run", "release", RC, stable, plugin dry-run
gaia-verify
Use when the user wants to verify a Gaia installation -- "probemos", "verify", "test installation", "gaia-verify"
git-conventions
Use when committing, squashing, merging, rebasing, or preparing changes for a pull request
orchestrator-present-approval
Use when presenting a returned APPROVAL_REQUEST for informed user consent
pending-approvals
Use when the user asks to list, inspect, approve, reject, or revoke pending approvals
security-tiers
Use when classifying any operation before executing it, or deciding whether user approval is required
subagent-request-approval
Use when a T3 command was blocked or a predictable ordered T3 set must be requested before execution
coding-standards
Use when writing, editing, or reviewing code and its inline documentation — module headers, inline comments, docstrings, doc comments — in any language or stack
verification-oracle
Use when re-running a task_gates entry (or a proposed contract verification block) whose verification_type is `command` or `code`, to deterministically re-execute the declared check and compare the actual result against the gate's expected value -- not for `semantic` or `self_review` gates, which need judgment rather than re-execution.
verification-rubric
Use when judging a task_gates entry whose verification_type is semantic or self_review -- reading the gate's evidence_shape as an explicit rubric, assessing the produced work against each stated criterion, and emitting a justified pass/fail verdict. Loaded by the verifier role for judgment-based gates.
command-execution
Use when executing any bash command, CLI tool, or shell operation
diagram-builder
Use when the user wants to build or extend a diagram deck of nested sections and components authored in plain YAML — an architecture map, a timeline diagram, a planner board, a process-flow diagram, a slide-style presentation, a side-by-side comparison, or a mind-map. Not for charts, plots, or numeric/data visualization — route those to the dataviz skill. Triggers — "build a diagram", "architecture diagram", "diagram deck", "timeline diagram", "flow diagram", "planner board", "comparison diagram", "add a page/section/component to the diagram".
skill-creation
Use when creating a new skill, improving an existing skill, or deciding what a skill should contain and how it should be structured
gaia-compact
Use when the user asks to compact the current session, including “compacta”, “compactemos”, or “compact the session”
investigation
Use when starting an investigation, analyzing existing code or infrastructure, or building findings before proposing changes
readme-writing
Use when writing, rewriting, cleaning up, or updating a README -- the root README of a repository, the README of a folder that holds one kind of thing (modules, migrations, components, services, scripts, environments, workloads; Gaia's own agents/, skills/ and hooks/ are one instance of that same shape), or the README shipped inside a template or scaffold handed to someone else. Triggers -- "escribí el README", "actualizá el README", "limpiá el README", "el README de este repo está desactualizado", "falta el README de esta carpeta", "write the README", "the README is stale", or a drift report flagging a README as stale.
scheduled-task
Use when the user wants something to run routinely / on a schedule rather than once now -- "tarea programada", "rutinariamente", "cada mañana", "cada N horas", "todas las noches", "schedule", "cron". Covers mounting, structuring, and running an unattended headless task that reports back, plus consuming its reports. NOT for work that runs once now in this session.
code-standards
Use when writing, modifying, reviewing, or refactoring code — any language or stack, application, infrastructure, or configuration. Also when asked to apply, audit, or clean up the code standards of a file or module.
ticket-writing
Use when creating or drafting tickets or issues, or when standardizing ticket output for a project
gaia-audit
Use when the user asks to audit, check, or review a Gaia component (an agent or a skill) against its standard and its live implementation -- "audita este skill", "chequea este agente", "¿está bien esta skill con la implementación?", "¿cómo mejoro este agente?"
blog-writing
Use when writing, drafting, or publishing a blog article for metraton.github.io
gmail-policy
Use when managing Gmail messages, labels, or email workflows via gws CLI or Gmail MCP tools
gmail-triage
Use when the user wants to clean up, organize, or triage their Gmail inbox interactively
gws-setup
Use when installing or configuring the Google Workspace CLI (gws) for a Google account
jira-ticket-writing
Use when creating or drafting Jira/Atlassian tickets or issues, or when standardizing ticket output for a project
visual-verify
Use when about to declare done on any output with a visual surface -- an HTML page, a rendered UI, a diagram, a slide, a screenshot-able view -- to confirm by looking at the rendered result instead of asserting it. Also use when asked to screenshot or visually check a page or a local file.
agent-protocol
Use when producing any agent response
execution
Use in a fresh specialist dispatch after the user has granted a T3 operation or COMMAND_SET
fast-queries
Use when diagnosing an issue, checking system health, or validating state before deeper investigation
claude-code-consent-adapter
Use when identifying the native consent mechanism implemented by Gaia's Claude Code adapter
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.