openrig
claudecodexWork with your OpenRig team from your coding agent: hand it work, follow that work, answer its questions and read what it returns.
1 skill · 1 MCP server
OpenRig canonical skills and hooks for cross-runtime agent topology coordination, continuity, and operating discipline.
Not in a marketplace yet, so it loads for one session with --plugin-dir.
Plugin openrig-core in mvschwarz/openrig. Commands read from the repo's manifest — today.
agent-operated-softwareUse when designing, building, operating, or diagnosing an ongoing application whose live backend or control loop includes OpenRig agents, including applications with a Markdown, YAML, or JSON agent control plane or a thin surface over specialist agent roles. openrig: stage: provisional audience: any
agent-operated-workflowsUse when a bounded real-world procedure has a deterministic happy path but brownfield, variable, or partially knowable state; when an operation must resume from verified evidence; or when deciding whether agent judgment or ordinary code should own a procedure's control loop. openrig: stage: provisio
applying-a-permission-policyUse before launching a team during agent-guided setup, or when a user asks to configure OpenRig command permissions, reduce repeated native approval prompts, or apply a selected rig/seat permission policy. openrig: stage: established docs_checked: "2026-09-29" verification_status: "Verify the instal
claude-compaction-restoreUse when a Claude Code session is about to compact, has just compacted, reached its context limit, resumed after /compact, or must rebuild its working picture of a long-running seat from its own restore map, its JSONL transcript and the files it touched.
delegating-workUse when you have a task and must decide WHO does it — yourself, a spawned subagent, or another agent in the topology that already holds the context — or how to brief the agent you hand it to, which depends on the model it runs. The rule: how much would a blank slate have to read in to do this corre
forming-an-openrig-mental-modelUse when the system around you does not make sense yet: you just booted into a seat and do not know how the pieces fit; someone said rig, pod, seat, fleet, topology, or slice and you are not certain what they mean here; you are unsure what kind of rig you are in or what it is for; you do not know ho
loading-addressable-markdownUse when a mission, slice, dashboard, or task references Markdown as path#h2-slug or path#h2-slug/h3-slug outside the OpenRig context-pack library.
messaging-the-humanUse when project policy calls for a human decision or update, a human delivery is pending or failed, or a reply must resume the right work.
mission-slice-sopUse when starting, building, handing off, restoring, or closing a mission or slice under the default lightweight SDLC. openrig: stage: shipped sibling_skills: - queue-handoff - seat-continuity-and-handover - claude-compaction-restore
openrig-operating-modelUse when you do not know WHERE something belongs: you learned a lesson and are unsure which file takes it; you are about to create a new doc, folder, or convention; you are asking "should this be a skill, a note, or a chain file?"; you inherited a seat and want to know what SHOULD exist; or you are
openrig-skillsUse when an agent running inside OpenRig needs the right skill or context for fleet recovery, seat handover, new-seat orientation, a watchdog wake, cross-host reach to an agent on another machine, rig packaging, an OpenRig upgrade, systematic debugging, queue triage, or implementation planning; also
openrig-userUse when a specific `rig` command, subcommand, or flag is already known and you need its exact syntax, JSON shape, defaults, or error meaning. NOT for natural capability discovery, open-ended how-do-I questions, or choosing which OpenRig move applies.
orienting-to-an-inherited-seatUse when you have just been primed into an EXISTING seat through a planned handover — a different agent retired and handed you the seat plus its earned context — and you need a world model of what just happened to you. Covers how a handover differs from compaction and from a fresh launch, the inheri
queue-handoffUse when ending a turn, finishing a slice, blocked on another agent's work, or escalating to a human — durable work handoff via queue items so the system keeps moving across compactions, missed messages, and interruptions. Covers the hot-potato terminal-turn-rule (active work ends by passing the bal
refocusingUse when a long-running agent may have lost the product outcome, when context was compacted, when work has crossed a major boundary, or when a fresh path-based trace is needed before the next consequential action. Not for fresh-session orientation, waking an idle seat, or checkpoints. openrig: stage
retiring-and-inheriting-a-seatUse when you are a sitting agent near your context threshold (~85%) and a PLANNED seat transition is due — retire deliberately and hand your seat to a fresh successor primed from a packet, rather than let compaction degrade you. Covers the handover packet, the append-only lineage ledger (one row per
seat-continuity-and-handoverUse when replacing a seat's occupant (rebuild/handover/swap), reasoning about stable-seat-identity vs fluid-occupant-identity, choosing an old-occupant disposition (retire/advise/shadow), or recording provenance for an occupant change. Two independent outcomes (continuityOutcome + seatBindingOutcome
session-compaction-and-restoreUse when reasoning about what survives compaction/context-loss/restart/seat-refresh, designing a high-fidelity restore packet, or distinguishing native runtime resume vs fork vs artifact-backed mental-model rebuild. Covers the 4 failure modes that prevent honest restore (compacted seat drops hot pot
software-for-agentsUse when older OpenRig instructions name software-for-agents or describe agent-in-the-middle or studio software under the former skill name. openrig: stage: deprecated successor: agent-operated-software remove_in: 0.6.0
Work with your OpenRig team from your coding agent: hand it work, follow that work, answer its questions and read what it returns.
1 skill · 1 MCP server
Matt Pocock's agent skills for real engineering (grilling, spec/ticket flows, TDD, code review, domain modelling and more).
39 skills
Persistent memory for Claude Code: the next session starts where the last one left off.
29 skills · 1 MCP server · hooks
Cross-session memory and token savings for coding agents.
6 skills · 1 agent · 1 MCP server · hooks
Up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your coding agent's context.
1 MCP server
Automates browser interactions for web testing, form filling, screenshots, and data extraction
12 skills
Orchestrate multi-agent teams for parallel code review, hypothesis-driven debugging, and coordinated feature development using Claude Code's Agent Teams
6 skills · 7 commands · 4 agents
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.