Check the health of the HashiCorp Vault instance in an OpenRig environment and manage stored secrets. Use its API to write, read, list, or delete entries and explain how secret paths are organized.
- Checking whether the local Vault instance is healthy
- Storing or retrieving secret values
- Listing secret paths and explaining their contents
mvschwarz/openrig☆ 8KUpdated Oct 21, 2026
Plan agent replacements while keeping the same workspace identity. The skill separates creating a successor from assigning it to the existing role, records both outcomes, and prepares durable handover notes and traceable replacement history.
- Replace an agent while preserving its workspace identity
- Prepare recap notes for a successor
- Track successor creation and assignment separately
mvschwarz/openrig☆ 8KUpdated Oct 21, 2026
Helps older OpenRig instructions that reference software-for-agents lead to its maintained successor, agent-operated-software. This temporary compatibility redirect identifies where to find the current architecture and operating guidance.
- Following older OpenRig instructions
- Finding guidance under the successor skill name
- Checking the compatibility redirect's retirement schedule
mvschwarz/openrig☆ 8KUpdated Oct 21, 2026
Plan how agents retain active work across conversation compaction, context loss, and restarts. Organize restoration packets that preserve purpose, progress, ownership, and constraints, distinguish resume from fork or rebuild, and check whether work actually resumes correctly.
- Prepare restoration materials before conversation compaction
- Preserve task purpose and ownership across a restart
- Distinguish native resume, fork, and artifact-based rebuild
mvschwarz/openrig☆ 8KUpdated Oct 21, 2026
Plan an agent's handover to a fresh successor before its context fills up. Prepare transfer materials, preserve the role's address, record tenure history, and explicitly transfer recurring duties and authority while keeping a way to consult retained predecessors.
- Planning a handover before an agent's context fills up
- Transferring recurring duties and authority
- Recording an agent role's tenure history
mvschwarz/openrig☆ 8KUpdated Oct 21, 2026
Review assigned code changes against project conventions, architecture, and intended behavior. Verify findings with source code and tests, classify their severity, and record a merge readiness verdict, with an optional deeper process for independent reviews and resolving disagreements.
- Reviewing assigned code changes
- Checking duplication and inconsistent patterns
- Reviewing fixes that lack a written specification
mvschwarz/openrig☆ 8KUpdated Oct 21, 2026
Coordinate work across an OpenRig agent team with clear assignments, attached context, completion criteria, and selected review checkpoints. Track queue status, identify blocked or idle owners, and resolve handoff gaps while leaving implementation with the assigned agents.
- Assign agent tasks with context and completion criteria
- Identify blockers and missed handoffs from queue status
- Route reviews at the agreed milestones
mvschwarz/openrig☆ 8KUpdated Oct 21, 2026
Evaluate a feature idea before turning it into requirements using six sequential questions. Examine customer demand, current workarounds, a specific user's pain, and the smallest useful solution, then save an evidence-based assessment with a verdict and next steps.
- Validating customer demand before writing requirements
- Narrowing a feature to its smallest useful version
- Separating customer evidence from assumptions
mvschwarz/openrig☆ 8KUpdated Oct 21, 2026
Hand off OpenRig work through persistent queue items that record the next owner, blockers, and closure reasons. The skill covers notifying recipients, escalating to a human, and keeping supporting evidence accessible across interruptions and missed messages.
- Passing completed work to the next agent
- Recording work blocked by another task
- Escalating a decision to a human
mvschwarz/openrig☆ 8KUpdated Oct 21, 2026
Manage OpenRig development work from setup to completion using shared specification, progress, and evidence files. Record what was actually checked and pass work to the next owner so handoffs and conversation compaction preserve the context.
- Starting a development task with clear completion criteria
- Recording progress and verification evidence
- Handing work to another agent
mvschwarz/openrig☆ 8KUpdated Oct 21, 2026
Change a running OpenRig setup by adding or removing agent seats, connecting existing sessions, or attaching terminals. Guides checks for roles, startup context, permissions, and session identity so the setup reflects each change correctly.
- Add agent seats to a running rig
- Remove seats and clean up remaining references
- Connect an existing session to an OpenRig node
mvschwarz/openrig☆ 8KUpdated Oct 21, 2026
Look up exact syntax, options, JSON output, defaults, and error meanings for a known OpenRig command. Use the reference to check command behavior and diagnose runtime differences against the installed help and running daemon.
- Checking required flags for a known rig command
- Looking up queue commands and handoff syntax
- Investigating command errors and daemon compatibility
mvschwarz/openrig☆ 8KUpdated Oct 21, 2026
Plan and verify OpenRig startup, shutdown, and recovery. Compare reported status with actual running sessions, distinguish recovery outcomes, and define reboot tests that expose partial failures instead of hiding them behind a fresh launch.
- Checking rig status after a host reboot
- Designing recovery tests across runtimes
- Investigating partially restored agent sessions
mvschwarz/openrig☆ 8KUpdated Oct 21, 2026
Guide changes to OpenRig itself by locating relevant source files, choosing tests, assessing sensitive areas, and preparing pull requests. Use isolated test environments to check changes without disrupting the daemon running the current agent session.
- Locate the source files responsible for a behavior
- Choose tests for an OpenRig change
- Test without disrupting the current agent session
mvschwarz/openrig☆ 8KUpdated Oct 21, 2026
Create screen mockups at three levels: text wireframes, standalone HTML files, or working prototype pages. Use requirements, existing app styles, and real project data to show layouts and interactions for review or testing.
- Sketch screen layouts while writing requirements
- Deliver HTML mockups alongside requirements
- Test interactions with existing components
mvschwarz/openrig☆ 8KUpdated Oct 21, 2026
Coordinate with OpenRig agents on registered remote machines using SSH or HTTP connections. Select the intended host, inspect agent state, send messages, and interpret failures while checking whether remote actions actually took effect.
- Checking agents on a registered remote host
- Sending messages to agents on another machine
- Diagnosing connection and authentication failures
mvschwarz/openrig☆ 8KUpdated Oct 21, 2026
Guides the design and review of agent startup context, including role files and links to authoritative records. It helps identify stale guidance, missing updates, overloaded startup files, and instructions that lose the purpose of the work.
- Designing startup files for a new agent
- Reviewing stale guidance used by running agents
- Separating role information from reusable procedures
mvschwarz/openrig☆ 8KUpdated Oct 21, 2026
Develop features and fix bugs by writing a behavior test first, observing its expected failure, and adding the minimum code needed to pass. Then clean up the code while keeping tests passing, applying this process where regression risk warrants it.
- Developing a feature from a failing behavior test
- Reproducing a bug before implementing its fix
- Refactoring while keeping behavior tests passing
mvschwarz/openrig☆ 8KUpdated Oct 21, 2026
Classify agent work as ready to continue, needing human judgment, or intentionally paused. Structure decision requests with evidence, a recommended choice, and clear outcomes, then connect the recorded decision to the next responsible agent.
- Deciding whether agent work needs human review
- Preparing decision requests with evidence and recommended choices
- Designing a dashboard for pending human decisions
mvschwarz/openrig☆ 8KUpdated Oct 21, 2026
Guides agents through sending human decision requests and updates using registered recipients. It covers concise briefs, delivery checks, duplicate prevention, and linking replies to the correct work so that delivery receipts are kept distinct from human decisions.
- Sending a decision request with clear options
- Reporting an outcome that needs no action
- Investigating a failed or uncertain delivery
mvschwarz/openrig☆ 8KUpdated Oct 21, 2026
Open terminal views for OpenRig agents in cmux, grouped by rig, pod, mission, slice, or saved view. Inspect connection health and view agent sessions with read-only access where required, while keeping the underlying sessions running.
- View a rig's agent terminals together in cmux
- Monitor mission or slice terminals in read-only mode
- Reopen a saved terminal view
mvschwarz/openrig☆ 8KUpdated Oct 21, 2026
Guide OpenRig CLI and background service upgrades while protecting active sessions and local file changes. The skill provides staged checks, verified database backups, selective plugin refreshes, and migration helpers, with evidence checked after each change.
- Upgrading OpenRig while preserving active sessions
- Backing up and checking the database before an upgrade
- Refreshing managed plugins while preserving local edits
mvschwarz/openrig☆ 8KUpdated Oct 21, 2026
Create reusable starting configurations that combine an agent’s role, startup context, and source history. The skill guides registry entries, checks whether their sources are current, and manages their progression from initial capture to recommendation or retirement.
- Create reusable startup context for an agent role
- Refresh an agent workspace from an existing starter
- Check a starter’s source history and freshness
mvschwarz/openrig☆ 8KUpdated Oct 21, 2026
Investigate bugs, failed tests, and unexpected behavior through reproducible steps, evidence gathering, and comparison with working code. Test one hypothesis at a time, then implement a focused fix and verify it with tests.
- Investigating failed tests or builds
- Tracing production bugs across components
- Reassessing a problem after repeated failed fixes
mvschwarz/openrig☆ 8KUpdated Oct 21, 2026