Loading...
Loading...
Found 10,137 Skills
Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.
Example project-specific skill template. Use as a starting point when creating guidelines for your own projects.
Two-layer autonomous conductor — design loop produces decision packets, dispatch loop routes to bounded issues with dedupe/cooldown/archive controls. Replaces v1's single-agent persistence with a durable control loop that stops only at real blockers.
Drive the Duvo public API from the terminal via the `duvo` CLI (`@duvoai/cli`). Use when the user wants to script Duvo — managing agents, runs, cases, queues, files, skills, connections, Clarity processes, or hitting an arbitrary endpoint via `duvo api` — instead of clicking through the Duvo web UI or hand-crafting `curl` calls.
Use at the start of any conversation—establishes how to find and use skills, requiring the Skill tool to be called before any response (including clarifying questions)
Applicable when you need to resolve ongoing git merge/rebase conflicts.
handoff the session, compact the conversation into a document a fresh agent can resume from, or restore context from a saved handoff. Triggers: /handoff, save session context, hand off to a new agent, resume from a handoff file. Flags: --resume <path>, --path <path>, and a positional focus argument.
Opens a pull request for a small jackin❯ change with the correct body shape and auto-selected verify-locally blocks.
Ingest raw context the user pastes or points at — a ticket, a design doc, meeting notes, a spec, a URL, referenced files/paths — and have an agent READ and UNDERSTAND all of it, then synthesize a well-formed feature brief (goal, scope, constraints, and load-bearing unknowns) that feeds sdd-clarify and the sdd-feature-flow harness. Use at the very start of a feature when you have source material instead of a one-line goal, or whenever the user says "here's the context" / "read this" / dumps a ticket or doc.
Audit a repo against the canonical repo-standard (STANDARD.md) and report what is done, drifted, missing, or N/A, with a fix for each gap. Verifies that startup was run and its outputs have not drifted, and generates the per-repo docs/repo-standard.md checklist when missing. Use when the user invokes /repo-standard, says "audit this repo against the standard", "is this repo to standard", "check repo standard", "bring this repo to standard", or when a review or engineer run enters a repo.
Runs a doer -> verifier-panel -> consensus loop to verify a deliverable before it ships. An orchestrator freezes acceptance criteria before implementation, dispatches a doer, then convenes a context-walled panel of independent verifiers - including an adversary with an explicit must-oppose mandate - for evidence-anchored review adjudicated to a SHIP / SHIP_WITH_CAVEATS / ITERATE / BLOCK / ESCALATE verdict logged to a ledger. Use for multi-agent verification of any artifact - code slices, plans, documents, audits - whenever asked to verify a deliverable, vet a plan, run a consensus review or independent review, set up a doer-verifier loop, or gate a ship decision. Works on any platform with parallel subagents; degrades to sequential fresh-context sessions without them. Not for trivial single-file edits or ordinary code review.
Gate a pitch against one journalist at a time. Runs the pair through proven media-relations checks (last-10-bylines audit, 90-day topic sweep, beat-vs-angle-vs-one-off, the 5 forms of journalism, source-mirror, stated-preferences, database triangulation) and returns fit, soft-fit, no-fit, or unknown with a real recent anchor and specific edits.