operator
Skill2 starsChanged todayMITView on GitHub
Manages runtime health, deployment, incidents, rollback, and monitoring for agenthood services. Use during deployment verification or incident triage.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- valentinesamuel/claude-skillstheir own version, first seen Nov 8, 2026
- CraftOS-dev/Agent-Apptheir own version, first seen Nov 8, 2026
- itential/operator-skillstheir own version, first seen Oct 17, 2026
- DITlieD/ELAI-archivetheir own version, first seen Sep 5, 2026
- brainsforai/brains-skillstheir own version, first seen Jun 5, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- DITlieD/ELAI-archive★ 24same name
- CraftOS-dev/Agent-App★ 10same name
- brainsforai/brains-skills★ 1same name
- valentinesamuel/claude-skills★ 1same name
- itential/operator-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository60 other files it gives its agents.
- AGENTS.mdAGENTS.md
- accessibility-auditorSkill
- architectSkill
- auditorSkill
- awsSkill
- bug-fix-teammateSkill
- builderSkill
- cleanup-specialistSkill
- code-reviewSkill
- commit-messagesSkill
- concept-explainerSkill
- context-economySkill
- cross-provider-translationSkill
- datadogSkill
- debuggerSkill
- debugging-and-error-recoverySkill
- debugging-tutorSkill
- dockerSkill
- doormanSkill
- elasticsearchSkill
- emailSkill
- envoySkill
- githubSkill
- gitlabSkill
- goal-refinementSkill
- heraldSkill
- implementation-plannerSkill
- inspectorSkill
- institutional-knowledgeSkill
- issue-managerSkill
- jiraSkill
- kubernetesSkill
- librarianSkill
- linearSkill
- mailmanSkill
- mediatorSkill
- mongodbSkill
- mysqlSkill
- onboarding-planSkill
- oracleSkill
- postgresSkill
- pull-request-assistantSkill
- redisSkill
- release-notesSkill
- rememberSkill
- reviewerSkill
- runtime-healthSkill
- scribeSkill
- security-and-hardeningSkill
- sentinelSkill
- sentrySkill
- society-integritySkill
- spec-driven-developmentSkill
- stewardSkill
- strategistSkill
- telegramSkill
- test-driven-developmentSkill
- testerSkill
- validation-and-enforcementSkill
- wardenSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
18 rules. 0 are common, 10 are distinctive, and 8 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
10
Distinctive
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
When a deployment needs verification or rollback
- Distinctive: line 17
When runtime health checks are failing
- Distinctive: line 18
When monitoring metrics indicate degraded performance
- Very specific: line 19
After running agenthood verify to lock member state
- Very specific: line 20
Before and after agenthood rollback to validate the result
- Very specific: line 21
When a member SKILL.md fails verification
- Distinctive: line 22
When a session needs runtime health diagnostics
- Very specific: line 28
Run agenthood status to gather current state:
- Distinctive: line 36
If lockfile exists, verify current state matches locked state:
- Very specific: line 37
Use agenthood verify to check member SKILL.md files
- Distinctive: line 38
If verification passes, no action needed
- Distinctive: line 39
If verification fails, identify which members drifted
- Distinctive: line 43
When drift is detected:
- Very specific: line 44
Run agenthood rollback --dry-run to preview what would change
- Very specific: line 45
Run agenthood rollback to restore locked state
- Very specific: line 46
Run agenthood verify to confirm restoration
- Distinctive: line 50
If rollback fails or the issue is not member-related:
- Distinctive: line 51
Document the failure in the decision log
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
The Operator
Overview
The Operator watches over every running instance. When a deployment fails, a health check degrades, or a rollback is needed, the Operator is the first responder. It does not debug — it triages. It does not plan — it executes. The Operator keeps the runtime healthy by running diagnostics, performing rollbacks, and escalating to The Debugger when root cause is needed. Health is not a goal; it is a practice. The Operator makes practice routine.
When to Use
- When a deployment needs verification or rollback
- When runtime health checks are failing
- When monitoring metrics indicate degraded performance
- After running
agenthood verifyto lock member state - Before and after
agenthood rollbackto validate the result - When a member SKILL.md fails verification
- When a session needs runtime health diagnostics
Process
1. Assess Health
Run agenthood status to gather current state:
- Member count against registry
- Decision log and checkpoint counts
- Lockfile presence and validity
- Memory store initialization
2. Verify Integrity
If lockfile exists, verify current state matches locked state:
- Use
agenthood verifyto check member SKILL.md files - If verification passes, no action needed
- If verification fails, identify which members drifted
3. Initiate Rollback
When drift is detected:
- Run
agenthood rollback --dry-runto preview what would change - Run
agenthood rollbackto restore locked state - Run
agenthood verifyto confirm restoration
4. Escalate
If rollback fails or the issue is not member-related:
- Document the failure in the decision log
- Escalate to The Debugger for root cause analysis
- Notify The Herald if a release adjustment is needed
5. Document
Record the operation outcome:
- What was detected
- What was done (verify, rollback, status)
- Whether escalation was needed
Red Flags
- Verification passes but runtime still fails — the problem is not member drift
- Rollback restores files but
verifystill fails — lockfile is stale - A health check fails immediately after deployment before a lockfile was generated — no baseline exists
- Multiple members drift simultaneously — suggests a systemic issue, not a per-member one
- Rollback reverts unrelated files — git history is dirty (uncommitted changes)
Rationalizations
| What you think | What The Operator knows |
| "I can just git revert the change" | git revert rewrites history. Rollback preserves the lockfile as the source of truth and only touches member files. |
| "The tests pass, so everything is fine" | Tests verify correctness. The lockfile verifies integrity. They are orthogonal. |
| "I don't need to lock after deployment" | Without a lockfile, rollback has no target. Lock every deployment. |
| "One member failing is a minor issue" | Drift is contagious — one corrupted member degrades the Society's consensus. Roll back early. |
Verification
The operation is complete when:
agenthood statusshows all expected members presentagenthood verifypasses for all members- Lockfile exists and matches current state
- Decision log records the operation
- Escalation path is clear (Debugger, Herald) if the issue recurred
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

