mvschwarz/openrig / packages/daemon/assets/plugins/openrig-core/skills/openrig-operating-model
openrig-operating-model
VerifiedUse 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 about to duplicate knowledge that already has a home. Also the trace-to-root: how a seat orients by reading one filename at each level from where it stands up to the fleet.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 24.4 KB |
| scripts/compose.pyexecutable | script | 28.7 KB |
| scripts/scaffold.shexecutable | script | 2.1 KB |
| scripts/trace-due.shexecutable | script | 1.5 KB |
| scripts/trace-stamp.shexecutable | script | 231 B |
| scripts/trunk-diff.shexecutable | script | 966 B |
| templates/LEARNED.md | markdown | 1.6 KB |
| templates/NOTES.md | markdown | 370 B |
| templates/PLAYBOOK.md | markdown | 184 B |
| templates/SOP.md | markdown | 676 B |
| templates/SPEC.md | markdown | 2.5 KB |
templates/LEARNED.md
View on GitHub---
seat: <pod>-<member>@<rig> # or rig/pod/fleet coords at higher altitudes
template: <path-or-name of SOP.md this refines> @ <version/sha>
owners: self (sole direct writer) · <orchestrator/PM> (by proposal) · hierarchy (boundaries only, marked)
updated: <YYYY-MM-DD from the clock command — never mental math>
status: UNSEEDED # the first real occupant replaces this line with: seeded-by-self <date>
---
# LEARNED — <instance coords>
<!-- Size is soft guidance: keep the file as small as honestly covers the job.
Before handover or clear, distill LESSONS into HOW I WORK and retain needed context. -->
## MY JOB HERE
<!-- This instance's actual function, in operational terms. If you cannot write
this section yourself, say so to your orchestrator — that discovery is the
audit working, not a failure. -->
## STANDING DUTIES
<!-- One per line: DUTY — cadence — surface. These survive handovers ONLY if
enumerated here. -->
-
## HOW I WORK
<!-- Learned SOP bullets. EVERY bullet carries its reason — a rule without its
why is scripture and will be misapplied. -->
-
## GATES & AUTHORITIES
<!-- What I hold (granted in writing, cite the grant). What I must never infer. -->
-
## KEY RELATIONSHIPS
<!-- who I hand to · who gates me · whose funnel I feed -->
-
## TRIGGER POINTERS
<!-- situation → read this. Attach pointers to MOMENTS, not to boot. -->
-
## LESSONS (dated, newest first)
<!-- Distill into HOW I WORK at deposit boundaries; preserve necessary reasons
and archive superseded material. Attention is the budget, not a hard line cap. -->
-
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 463k | Updated | Claude CodeCodex | Verified | Install |
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 463k | Updated | Claude CodeCodex | Verified | Install |
| discernment-nudgeanthropics/skillsAfter you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format. | Stars: 195k | Updated | Claude CodeCodex | Verified | Install |
| internal-commsanthropics/skillsA set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.). | Stars: 195k | Updated | Claude CodeCodex | Verified | Install |