Catalog
Every x402, MPP, MCP, and skill listing we've indexed, normalized, and enriched.
domain-glossary
Extract a DDD-style ubiquitous language glossary from the current conversation.
deep-codebase-audit
Find deepening opportunities in a codebase, surfacing architectural friction and proposing refactors that turn shallow modules into deep ones. Use when the user wants to improve architecture, make a codebase more testable, consolidate tightly-coupled modules, or make it safer for
code-review
Performs a thorough code review of the current changes or a specified file / pull request. Covers correctness, security, performance, readability, and adherence to project conventions. Outputs prioritised, actionable feedback. TRIGGER when the user writes /code-review or asks for
ultra-orchestrator
Primary Ultra Orchestration entry point for strict Codex-controlled engineering runs. Use this single skill for development, bug fixes, OpenSpec work, multi-file implementation, review/QA-heavy tasks, risk-gated work, or any run that needs automatic mode selection, OpenSpec boots
ultra-orchestrator-legacy
Legacy compatibility entry point for the original Ultra Orchestrator flow. Use only when you need the older lightweight stage-based orchestration behavior without the new strict OpenSpec-first control plane.
spec-review
Review plans and work packages for specification completeness, hidden assumptions, dependency gaps, interface risks, and acceptance-check quality. Use after planning and before substantial implementation.
safety-guard
Apply careful, freeze, and guard behaviors to dangerous commands, broad edit scope, and high-impact operations. Use when execution needs command warnings, path restrictions, or combined safety guardrails.
risk-vetter
Classify tools, skills, commands, and external actions by risk level and define required approvals or guardrails before execution. Use whenever a run may invoke unfamiliar tooling, destructive actions, broad write scope, or external systems.
qa-verify
Run scenario-based verification and regression checks for changed behavior, user flows, and bug fixes before delivery. Use after implementation or review whenever behavior changed or user-visible quality matters.
openspec-ultra-bridge
Bridge OpenSpec change artifacts into Ultra-Orchestrator execution artifacts. Use when a repo follows OpenSpec for proposal, design, tasks, and archive, but execution should remain controlled by Ultra-Orchestrator through TaskManifest, WorkPackage, review, QA, risk gates, and led
dispatch-and-track
Assign work packages by role, enforce owned-path boundaries, manage execution state, track retries, blockers, review readiness, and host-driven ledger updates. Use when work is being handed off across phases or subagents.
deliver-and-retro
Assemble the final deliverable, orchestration log, vetter report, and concise retrospective for a completed orchestrated run. Use when implementation and review are complete and results need to be packaged clearly.
decision-complete-planner
Turn a structured intake artifact into a decision-complete plan, task graph, dependency map, owned paths, acceptance checks, expected outputs, and retry assumptions. Use when work spans multiple steps, files, or roles and needs explicit orchestration.
code-review
Review implementation results for production bugs, regressions, risk, evidence quality, and missing tests before integration. Use after code changes or when validating a worker result against acceptance criteria.
clarify-and-intake
Normalize ambiguous user requests into a structured intake artifact with task description, context, success criteria, constraints, and task type. Use before planning or implementation whenever requirements are incomplete, mixed, or implicit.
autoplan
Automatically chain intake, planning, spec review, and plan refinement into one orchestrated planning pass, surfacing only decisions that need explicit user approval. Use when the user wants a fast but disciplined planning workflow.
zvec
Zvec vector database development assistant. Use this skill when users need to develop vector search applications based on zvec, build RAG systems, implement semantic search, or handle vector data storage and querying. Suitable for Python and Node.js development environments, prov
maintaining-core-documentation
Creates, maintains, and synchronizes core project documentation (README, TODO, DESIGN, Architecture, Testing, Deployment). Use when the user needs to write, update, or structure project documentation based on codebase changes, or whenever the user asks to perform any documentatio
go-development
Use when developing Go applications, implementing job schedulers or cron, Docker API integrations, LDAP/AD clients, building resilient services with retry logic, setting up Go test suites (unit/integration/fuzz/mutation), running golangci-lint, or optimizing Go performance.
typo3-extension-upgrade
Use when upgrading TYPO3 extensions to newer LTS versions (v11->v12, v12->v13, v13->v14 - v14.3 LTS is the current target), running Extension Scanner, Rector, Fractor, PHPStan, fixing deprecated APIs, or resolving compatibility issues. Also triggers on: migration, version upgrade
academic-reviser
Self-review, audit, or verify CS/AI/ML paper drafts as a critical peer reviewer. Three-round review (evidence→argument→style) with Verification Status and debt tracking. Use when: reviewing a paper draft before submission, checking evidence compliance of claims, simulating peer r