mvschwarz/openrig

Agent skills in the GitHub repository mvschwarz/openrig, each with its code score out of 100.

Build your own network of agents from Claude Code, Codex and Pi: persistent teams with roles, shared context and owned work.

Repository score

67 / 100 C

Skills

56

Verified

0

Average skill score

63

GitHub stars

8,830

License

Apache-2.0

Open mvschwarz/openrig on GitHub

56 skills in this repository

1. openrig-architect

   Use when designing multi-agent topologies that run ON OpenRig — authoring RigSpec and AgentSpec files for new rigs, creating agent startup content (guidance / skills / culture), o…

   76B
2. requirements-writer

   Use when converting PM intake into a slice SPEC.md with observable acceptance outcomes, explicit scope, and advisory sibling build dependencies.

   75B
3. dogfood

   Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "t…

   74B
4. orienting-to-an-inherited-seat

   Use 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 wo…

   74B
5. session-source-fork

   Use when authoring a rig spec member or `rig expand` payload that needs to start a new managed seat from a prior runtime conversation source — `session_source: { mode: fork, ref:…

   74B
6. openrig-operating-model

   Use 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…

   72B
7. retiring-and-inheriting-a-seat

   Use 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…

   72B
8. seat-continuity-and-handover

   Use 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/…

   71B
9. context-builder

   Gather and distill context from meetings, competitors, regulatory sources, and internal discussions. Produces background.md for a feature and updates shared context docs when new…

   69C
10. openrig-upgrade

    Use when an agent is preparing or performing an OpenRig CLI/daemon upgrade and must preserve live seats, verify each mutation, or reconcile managed plugin and skill files without…

    68C
11. test-driven-development

    Use when implementing any feature or bugfix, before writing implementation code

    68C
12. context-engineering

    Use when designing, reviewing, or debugging how an agent's context window gets filled, pruned, or shared — choosing what loads at boot versus on demand, sizing an install or an al…

    67C
13. openrig-user

    Use 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…

    67C
14. watchdog

    Use when configuring `rig watchdog` policies, authoring wake/refocus/alignment-checkpoint messages, or choosing the right intervention level for a stale-owner situation. The 3-lev…

    67C
15. agent-starters

    Use when creating, refreshing, packaging, inspecting, promoting, or deprecating a named per-seat starting point — Agent Starter manifest authoring, the 6-state lifecycle (captured…

    66C
16. openrig-software-factory

    Use when a user wants a continuing software team for a real repository, or has a first OpenRig team and needs a repeatable path for reviewed work and later tasks.

    66C
17. rig-bundles-and-shareable-artifacts

    Use when authoring or installing a rig bundle (packaged, shareable artifact that instantiates an opinionated OpenRig topology + workflow), reasoning about the bundle vs extension…

    66C
18. working-with-an-openrig-team

    Use when you are a person's coding agent in an app such as Claude Code, Codex, Cursor or VS Code, connected through the OpenRig MCP server, and the person wants their OpenRig team…

    66C
19. agent-browser

    Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extractin…

    65C
20. agent-operated-software

    Use when designing, building, operating, or diagnosing an ongoing application whose live backend or control loop includes OpenRig agents, including applications with a Markdown, Y…

    65C
21. topology-mutation-and-seat-management

    Use when changing a rig while it is alive — `rig grow` / `rig expand` / `rig shrink` / `rig launch` / `rig remove` / `rig discover` / `rig bind` / `rig adopt` / `rig attach`. Cove…

    65C
22. agent-startup-and-context-ingestion

    Use when designing or auditing how an agent becomes useful after launch — AGENTS.md overlays, role files, skills, rig specs, workflow specs, startup checklists, refocus messages,…

    64C
23. forming-an-openrig-mental-model

    Use 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…

    64C
24. oversight-team

    Use when you are a seat on the oversight pod (a standing monitor-mode rig that keeps OTHER rigs healthy), configuring or running the drift detectors, or choosing whether to interv…

    64C
25. review-team

    Use when assigned a review or when an authored review boundary is reached.

    64C
26. rig-lifecycle

    Use when reasoning about the rig lifecycle operations family (create / start / stop / resume / restore / snapshot / release / unclaim / destroy), reading or trusting `rig ps` / li…

    64C
27. systematic-debugging

    Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

    64C
28. applying-a-permission-policy

    Use 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 r…

    63C
29. cross-host-rig-commands

    Use when addressing a registered remote OpenRig host, choosing its transport, or interpreting a cross-host result.

    63C
30. openrig-skills

    Use 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…

    63C
31. specification-system

    Use when authoring rig specs, agent specs, workflow specs, startup/context fragments, operating-mode declarations, or designing the user spec library. Covers the 4 failure modes (…

    63C
32. verification-before-completion

    Use when about to claim work is complete, fixed, or passing, or before committing or creating PRs

    63C
33. delegating-work

    Use 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 yo…

    62C
34. exec-summary

    Generate a 1-2 page executive summary for a feature — orients sales, leadership, and engineering from a single document.

    62C
35. loading-addressable-markdown

    Use 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.

    62C
36. mission-slice-sop

    Use when starting, building, handing off, restoring, or closing a mission or slice under the default lightweight SDLC.

    62C
37. rigs

    Use when a person in their own Claude Code or Codex session mentions OpenRig, rigs or the rig command, or wants a team of coding agents (Claude Code, Codex) on their project. That…

    62C
38. orchestration-team

    Use when coordinating assignments, selected review boundaries, or blocked work across a rig.

    61C
39. developing-openrig

    Use when changing OpenRig's own source in a clone of the openrig repository: finding which package or file owns a behaviour, choosing which tests to run, testing a change without…

    60C
40. human-in-the-loop

    Use when classifying a slice closeout (auto-continue / human gate / park), routing a real decision to a human, or designing a human queue/dashboard surface. Treats humans as durab…

    60C
41. plan-review

    Multi-perspective review of a feature plan or requirements doc before development begins. Evaluates from strategy, design/UX, and engineering angles to catch gaps early.

    60C
42. claude-compaction-restore

    Use 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 se…

    59C
43. session-compaction-and-restore

    Use 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 a…

    59C
44. ui-mockup

    Create UI mockups at three fidelity levels — ASCII wireframes for quick iteration, standalone HTML mockups for delivery with requirements, and live prototypes for interaction test…

    59C
45. agent-operated-workflows

    Use 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;…

    58C
46. queue-handoff

    Use 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 compa…

    57C
47. refocusing

    Use 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 bef…

    56C
48. frontend-design

    Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applica…

    54D
49. messaging-the-human

    Use 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.

    54D
50. backlog-capture

    Quickly capture product ideas, feature requests, or insights from meetings and conversations. Rapid documentation with smart categorization and deduplication.

    53D
51. openrig-cmux

    Use when opening OpenRig fleet terminals into cmux — turning a rig, pod, mission, slice, or saved view into live agent tiles via `rig terminal --provider cmux`, or driving cmux on…

    53D
52. vault-user

    Use when checking the health of this rig's HashiCorp Vault or writing, reading, listing, deleting or explaining its secrets.

    52D
53. development-team

    Use when a development pod begins or hands off implementation, QA, or design work.

    51D
54. office-hours

    YC-style product validation using six forcing questions. Pressure-tests a feature idea before it becomes a requirement — ensuring real demand, a clear wedge, and evidence behind a…

    51D
55. openrig-herdr

    Use when opening OpenRig fleet terminals as a herdr wall — turning a rig, pod, mission, slice, or saved view into live interactive agent tiles via `rig terminal`, watching another…

    51D
56. software-for-agents

    Use when older OpenRig instructions name software-for-agents or describe agent-in-the-middle or studio software under the former skill name.

    49D

Scores come from a snapshot of 300 public GitHub repositories taken on 12 November 2026. Every score is the result of fixed checks run by code; no AI is involved. How scoring works.