govern-agentic-os
Skill4 starsChanged 13 days agoMITView on GitHub
Audit, plan, execute, check, and hand off governance work for this Agentic OS/Claudesidian repository. Use when reconciling the repository with Linear Documents, auditing documentation or architecture, validating phase structure or historical-issue absorption, fixing cross-session drift, deciding where documentation belongs, or preparing an Agentic OS handoff.
- Reads credentials
In this repository131 other files it gives its agents.
- agent-contractSkill
- brand-chrome-loginSkill
- contexto-aristasSkill
- crear-bot-nicoSkill
- daily-standupSkill
- design-a-grok-botSkill
- drift-hunt-rosterSkill
- explain-grokbotSkill
- exportar-botSkill
- grok-bot-project-opsSkill
- hallazgoSkill
- handoff-local-hermesSkill
- identity-pipelineSkill
- loop-corpSkill
- no-devSkill
- orca-handoffSkill
- panorama-de-flujoSkill
- reporte-gmSkill
- routine-healthcheckSkill
- sprint-parallelSkill
- transcript-healthcheckSkill
- getting-started-brandySkill
- getting-started-calendario-contenidoSkill
- getting-started-cazador-de-canalesSkill
- getting-started-cazador-de-vuelosSkill
- getting-started-cazador-gangasSkill
- getting-started-cazador-inmobiliarioSkill
- getting-started-cazador-programasSkill
- getting-started-cazador-sponsorsSkill
- getting-started-cazador-viviendaSkill
- getting-started-content-drafterSkill
- getting-started-data-scienceSkill
- getting-started-demand-hunterSkill
- getting-started-digital-storesSkill
- getting-started-directory-builderSkill
- getting-started-enrichment-deskSkill
- getting-started-event-hunterSkill
- getting-started-expense-managerSkill
- getting-started-gm-operacionesSkill
- getting-started-inbox-managerSkill
- getting-started-intake-intelSkill
- getting-started-intelligence-gmSkill
- getting-started-join-a-startupSkill
- getting-started-last30daysSkill
- getting-started-life-opsSkill
- getting-started-luma-taggingSkill
- getting-started-market-watcherSkill
- getting-started-meta-vaultSkill
- getting-started-musa-designerSkill
- getting-started-plantillas-notionSkill
- getting-started-product-hunterSkill
- getting-started-publisherSkill
- getting-started-pulso-brandSkill
- getting-started-pulso-diaSkill
- getting-started-renewals-hunterSkill
- getting-started-saves-archivistSkill
- getting-started-scraping-deskSkill
- getting-started-seo-deskSkill
- getting-started-sliderSkill
- getting-started-swe-outer-loopSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. About 0 are common, 9 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
If the user does not select a mode, infer it from the request.
- Distinctive: line 24
Read governance-contract.md for every mode.
- Very specific: line 25
Read audit-protocol.md for audit, plan, or repo-wide execute work.
- Very specific: line 26
Read .config/agentic-os-governance.json when it exists.
- Distinctive: line 27
Read the relevant Linear Document or issue before judging its local projection.
- Very specific: line 28
Use memory/Graphify/OpenWiki only to discover pointers.
- Distinctive: line 35
Read source files semantically and generated/vendor artifacts mechanically.
- Very specific: line 40
Never read 01_Journal/, 03_Areas/, 04_Resources/, secret-like paths, credentials, tokens, or local environment files during this workflow.
- Distinctive: line 44
Start from audit evidence, not memory summaries.
- Distinctive: line 55
Keep Linear Documents canonical, issues as change records, and local mirrors generated or explicitly code-adjacent.
- Very specific: line 56
Run proportional tests and check before closing work.
- Distinctive: line 61
Run the single repository checker:
- Distinctive: line 77
Put the handoff in the operating system's temporary directory, not the repository.
- Distinctive: line 81
Update Linear only with explicit authorization.
- Very specific: line 89
After any change to .claude/commands/, .claude/skills/, or .agents/skills/, follow the repository's ADK sync instructions.
- Distinctive: line 93
Write current project narrative in Spanish.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Govern Agentic OS
Govern the repository without creating a second source of truth. Treat Linear Documents as durable project canon, repository files as executable or offline artifacts, and memory systems as pointer/derived-index layers.
Select one mode
| Mode | Default authority | Purpose |
audit | Read-only | Collect evidence and classify drift. |
plan | Read-only | Propose a gated remediation plan. |
execute | Mutating, explicitly authorized | Apply only an approved plan. |
check | Read-only | Run deterministic coherence checks. |
handoff | Read-only by default | Compact state into links, evidence, and next actions. |
If the user does not select a mode, infer it from the request. Never infer authorization for execute from an audit, diagnosis, review, or plan request.
Load only the needed context
- Read governance-contract.md for every mode.
- Read audit-protocol.md for
audit,plan, or repo-wideexecutework. - Read
.config/agentic-os-governance.jsonwhen it exists. Treat it as the machine-readable map of Linear IDs, permitted mirrors, exclusions, and phase invariants; do not hard-code those IDs elsewhere. - Read the relevant Linear Document or issue before judging its local projection.
- Use memory/Graphify/OpenWiki only to discover pointers. Verify every material claim at its source.
Apply the safe workflow
Audit
- State the scope and exclusions before reading files.
- Read source files semantically and generated/vendor artifacts mechanically.
- Inspect nested repositories for architecture, documentation, integration, and repository health; deep-review code only when evidence reveals drift or risk.
- Record each finding with severity, source, observed state, expected authority, evidence, and proposed disposition.
- Correct nothing. Publish findings to Linear only when the user explicitly authorizes the write.
Never read 01_Journal/, 03_Areas/, 04_Resources/, secret-like paths, credentials, tokens, or local environment files during this workflow.
Plan
- Start from audit evidence, not memory summaries.
- Preserve the authority split in the governance contract.
- Group work into small phases with one verifiable gate per phase.
- Correct P0/P1 findings in execution; route P2/P3 findings to prioritized Linear backlog.
- Show exact Linear and filesystem mutation targets. Do not apply the plan.
Execute
- Require an approved plan and resolve its exact targets.
- Re-read each target immediately before mutation.
- Apply the smallest coherent change; never auto-pull or auto-fix unrelated drift.
- Keep Linear Documents canonical, issues as change records, and local mirrors generated or explicitly code-adjacent.
- Run proportional tests and
checkbefore closing work. - Consolidate factual evidence in the relevant issue body only after verification. Do not create a parallel implementation log in comments.
Check
Run the single repository checker:
npm run agentic-os:check
npm run agentic-os:check -- --live
npm run agentic-os:check -- --jsonLocal mode is the offline default. It validates the governance config, generated-projection checksums, phase metadata, package/script safety, intention invariants, and ADK mirrors without reading secrets or making network calls. --live adds read-only Linear Document reachability and requires LINEAR_API_KEY; runtime tooling remains an explicit npm run tooling:check because it crosses into user-home runtime configuration. Neither mode writes or pulls. Interpret exit codes as:
0: checks passed; warnings may remain.1: coherence drift.2: invalid invocation or missing live precondition.
Handoff
- Put the handoff in the operating system's temporary directory, not the repository.
- Reference Linear Documents, issues, commits, diffs, and files instead of copying them.
- Include scope, verified state, remaining gates, exact next command, and suggested skills.
- Redact secrets and personal information.
- Update Linear only with explicit authorization.
Enforce the session contract
At session start, run local check and report drift without correcting it. Open the applicable Linear Document before planning or editing.
At session close, run local and live checks when authentication is available, update the relevant Linear issue body with implementation evidence, then prepare a pointer-based handoff. Comments are for exceptional human discussion, not canonical status or evidence. Never mark an issue Done while a required live check fails.
After any change to .claude/commands/, .claude/skills/, or .agents/skills/, follow the repository's ADK sync instructions. Do not run sync merely by invoking this skill.
Keep outputs English-ready
Write current project narrative in Spanish. Use English for filenames, command names, JSON keys, stable identifiers, and contract headings. Do not maintain parallel translations. Defer full English migration, privacy review, link review, and licensing to the explicit open-source publication gate.
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.

