agentleFS
Sign inStart free
metagit-aimetagit-ai/metagit-cli/skills/metagit-aos/SKILL.md

metagit-aos

Skill4 starsChanged 13 days agoMITView on GitHub

Compose ACL, task graph, scheduler, merge, and related coordination subsystems via metagit aos|coord status|doctor|next. Use when an operator or orchestrator needs one snapshot of coordination health or the next work envelope without launching models. Start with the day-1 quickstart for the canonical control loop.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use when you need a composed view of coordination state, or a preview of what should run next across ACL + task graph + optional 0009–0012.

    line 15
  2. Distinctive:

    Run ledger: docs/reference/run-ledger.md

    line 22
  3. Very specific:

    Prefer aos next preview before --commit when exploring.

    line 50

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Metagit Agent Operating System (AOS)

<!-- modality:aos_status --><!-- modality:run_ledger -->

Use when you need a composed view of coordination state, or a preview of what should run next across ACL + task graph + optional 0009–0012.

Day-1 control loop (start here): docs/agents-quickstart.md

Full reference: docs/reference/aos.md Run ledger: docs/reference/run-ledger.md

Minimal practice workspace: examples/agent-aos-loop/

Control loop

export METAGIT_AGENT_MODE=true

metagit context pack --tier 2 --json
metagit prompt workspace --kind session-start --text-only

metagit aos status --json
metagit aos doctor --json
metagit aos next --json                 # preview (no schedule record)
metagit aos next --commit --json        # record schedule decision
# then compile / ACL / work / complete / merge enqueue as separate steps
metagit context compile --project P --repo R --task-id NODE --json
metagit aos next --apply-hints --agent-id agent-1 --json   # ACL APIs only
metagit task complete --node-id NODE --json

Alias: metagit coord … is identical to metagit aos ….

Rules

  • Doctor --fix requires --yes and only runs lease expire-on-list + worktree gc.
  • next --apply-hints never launches models and never runs compile.
  • Prefer aos next preview before --commit when exploring.

Related

  • ACL primitives: skill metagit-agent-coordination
  • Scheduler alone: metagit schedule next
  • Quickstart: docs/agents-quickstart.md

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free