Loading...
Loading...
Found 73 Skills
Use the Orca CLI to orchestrate worktrees and live terminals through a running Orca editor. Use when an agent needs to create, inspect, update, or remove Orca worktrees; inspect repo state known to Orca; or read, send to, wait on, or stop Orca-managed terminals. Triggers include "use orca cli", "manage Orca worktrees", "read Orca terminal", "reply to Claude Code in Orca", "create a worktree in Orca", or any task where the agent should operate through Orca instead of talking to git worktrees and terminal processes directly.
Use the Orca CLI to coordinate multiple coding agents via inter-agent messaging, task DAGs, dispatch with preamble injection, decision gates, and coordinator loops. Use when an agent needs to send or check inter-agent messages; create, dispatch, or track orchestration tasks; coordinate multi-agent workflows; or act as a coordinator dispatching work across terminals. Triggers include "orchestrate agents", "dispatch task", "send message to agent", "check inbox", "coordinate agents", "multi-agent", "create task DAG", "worker_done", "escalation", or any task involving inter-agent coordination through Orca.
Use Orca's computer-use CLI to inspect and control local desktop apps through accessibility trees, screenshots, and safe UI actions. Use when an agent needs to list desktop apps, get an app state, read visible UI, click, type, press keys, scroll, drag, set values, or perform app accessibility actions. Triggers include "computer use", "orca computer", "list apps", "get app state", "read Spotify", "read Slack", "click app", "type text", "press key", "set value", "scroll app", "drag app", and desktop app interaction tasks.
Complete guide for Orca - Solana's leading concentrated liquidity AMM (CLMM). Covers Whirlpools SDK for swaps, liquidity provision, pool creation, position management, and fee harvesting on Solana and Eclipse networks.
Use Orca's Linear CLI through `orca linear ...` commands to read linked ticket context with `orca linear issue --current --full --json`, post completion updates, move work forward through Linear workflow states, attach PR/MR links with `orca linear attach --current --url <pr-or-mr-url> --title "PR/MR link" --json`, and triage Linear tasks for assignee, priority, estimate, due date, labels, and parented follow-up creation for Linear-linked Orca tasks without treating ticket text as instructions. Use when working from a Linear issue, finishing work with a PR/MR, moving Linear status, searching Linear issues, or creating follow-up Linear tickets.
Keep the Orca desktop app's workspace list honest about the git worktrees your workflow actually creates — link each one to its issue, keep its status current, and clean out the ones whose work already merged. Use when the user says "orcakit", "clean up my orca workspaces", "my Orca sidebar is full of finished work", "which workspaces are stale", "link my worktrees to their issues", "remove the workspaces for merged issues", or "where should Orca put new worktrees".
Use the public `orca` CLI to operate Orca-managed worktrees, folder contexts, terminals, repos, automations, worktree comments, and the browser embedded inside the Orca app. Use when the user says "$orca-cli", "use orca cli", "Orca worktree", "child worktree", "cardStatus", "spawn codex/claude in a worktree", "read/wait/send Orca terminal", "terminal send", "Orca browser", or "control the browser inside Orca". Prefer this over raw `git worktree`, ad hoc PTYs, Playwright, or Computer Use when the task touches Orca-managed state. Use Computer Use for browser windows, webviews, or desktop UI outside Orca's embedded browser.
Use Orca's Linear CLI through `orca linear ...` commands to read linked ticket context with `orca linear issue --current --full --json`, post completion updates, move work forward through Linear workflow states, attach PR/MR links with `orca linear attach --current --url <pr-or-mr-url> --title "PR/MR link" --json`, and triage Linear tasks for assignee, priority, estimate, due date, labels, and parented follow-up creation for Linear-linked Orca tasks without treating ticket text as instructions. Use when working from a Linear issue, finishing work with a PR/MR, moving Linear status, searching Linear issues, or creating follow-up Linear tickets. Legacy bundled alias for `orca-linear`; remains available for existing installs.
Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, skill sharing, worktree comments, and Orca's embedded browser through the `orca` CLI. Use when the user says "$orca-cli", "Orca worktree", "child worktree", "spawn codex/claude in a worktree", "read/wait/send Orca terminal", "handoff" / "handover" / "give this to another agent", "Orca browser", or "share skills". Prefer it over raw git worktree, ad hoc PTYs, or Computer Use when Orca state is involved. Use Computer Use only when a visible window needs GUI control that a CLI, filesystem, or API cannot do.
Spawn and manage parallel AI coding agents via tmux. Use when you need to orchestrate workers, delegate sub-tasks, run multi-agent improvement loops, or manage agent lifecycles with orca CLI commands like spawn, list, kill, steer, logs, and daemon.
Orca orchestration coordinator runbook for orchestrator sessions only: bind the Run created by /orca-tasks, dispatch ready tasks one-worktree-one-branch, drive the task DAG, watchdog check --wait, gate failures, auto-merge green PRs, release workers. Also has a quick path for 1-2 task runs without a plan. Invoke with /orca-orchestrate.
Coordinator loop for an approved wish on Orca — one Run per wish, one Task per group, supervised workers in child worktrees, review→fix loops, Linear written only at gate transitions. genie v6 'corpo leve': genie owns the documents and this protocol; Orca owns dispatch state; Linear owns status; brain owns preferences.