orca-kit

Orient an agent inside an Orca multi-agent workspace: worktrees, per-person routing, the merge agent, CI runners, and the config file.

Skill by JAGUARAVI

IndexedMIT★ 2

Write a review

Chalk Labs

Need help deploying orca-kit?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/jaguaravi-orca-kit

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

Orient an agent inside an Orca multi-agent workspace: worktrees, per-person routing, the merge agent, CI runners, and the config file. Use when asked "how does this workspace work", "which worktree am I in", "who owns this", "how do I route to a person", "where are the keys/CI", or when the agent needs to know how work lands. Do not use for a specific task's steps (use `task-workflow`) or for merging (use `merge-agent`).

Use cases: devops, productivity, agent-building

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools: No tools found
Secrets: None asked for
Install scripts: None found

Network hosts it talks to 1

codeload.github.com · found in install command

Files it touches

~/.claude/skills/orca-kit

What's inside

Skill name: orca-kit
Description: Orient an agent inside an Orca multi-agent workspace: worktrees, per-person routing, the merge agent, CI runners, and the config file. Use when asked "how does this workspace work", "which worktree am I in", "who owns this", "how do I route to a person", "where are the keys/CI", or when the agent needs to know how work lands. Do not use for a specific task's steps (use `task-workflow`) or for merging (use `merge-agent`).
License: MIT
Instructions: 44 lines in SKILL.md · view on GitHub

Files (1)

SKILL.md

SKILL.md (first lines)

# Orca kit orientation

## Topology
- One host runs Orca + a fleet of agents (Claude Code, Codex, OpenCode v2, Cursor, Antigravity).
- Each task gets its own **git worktree** (`orca worktree create`); work lands via PRs.
- A background **merge agent** serializes merges, resolves safe conflicts, escalates hard ones.
- **Self-hosted CI runners** execute Actions on the VMs (no GitHub minutes).

## Where things live (all from one config)
Everything is resolved by `lib/orca-kit.sh` from `~/.orca-kit.env` (or defaults):
`KIT_HOME`, `MERGE_DIR`, `KEYS_DIR`, `PEOPLE_DIR`, `HACKATHON_DIR`, `MODEL`, `GH`, `RUNNER_*`.
Never hardcode paths — source the lib.

```bash
. /path/to/orca-kit/lib/orca-kit.sh   # then use $MERGE_DIR, $KEYS_DIR, $AGENT_BIN, ...
```

## Per-person routing
- The **worktree owner** is `<worktree>/.orca-owner`, else `$ORCA_PERSON`/`$ORCA_OWNER`, else the
  configured default owner.
- Owner → that person's env (`$KEYS_DIR/<Owner>.env`: keys, `GH_CONFIG_DIR`, git identity).
- Launch agents through `orca-route <agent>` (e.g. `orca-route-claude`) so the right keys/GitHub
  identity are used automatically.

## Worktrees
```bash
orca worktree ps                 # orchestration summary
orca worktree list               # all worktrees
orca-reap --repo <dir> --dry-run # remove merged/abandoned worktrees
```

## CI runners
```bash
systemd/orca-runner-bootstrap.sh <owner/repo>   # provision this box as a runner
systemd/orca-runner-health.sh                   # restart/free ports/self-heal (via timer)
```
A shared runner is never clean: free CI ports and assert tools before trusting a failure.

## Guardrails for agents
- Stay inside the worktree; don't switch branches of a shared checkout.
- Don't touch `main` directly; land through a PR labeled `merge-ready`.
- Don't paste secrets into logs; keys live in `$KEYS_DIR/<Owner>.env` (600).
- If a conflict is semantic (same logic/contract), don't guess — escalate.

From JAGUARAVI/orca-kit, MIT.

Signals

Stars: 2
Forks: 0
Open issues: 0
Last commit (this folder): Oct 13, 2026 (18 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License: MIT
Repository: github.com/JAGUARAVI/orca-kit
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql

More from JAGUARAVI

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped: 50+; launches shipped
media placements: 500+; media placements
founders on every account: 2; founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get orca-kit running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Need help deploying orca-kit?

Call Get help

Cite this page

orca-kit skill. Agent Mart. https://agentmart.dev/skills/jaguaravi-orca-kit (last updated 2026-10-24)

Need help deploying orca-kit?

Install

About

Reviews

Permissions

Network hosts it talks to 1

Files it touches

What's inside

More from JAGUARAVI/orca-kit

Signals

Details

More from JAGUARAVI

Rather not set it up yourself?

Get orca-kit running in your business