Menu

Individual skill

agents

0upvotes

Run a goal as a project: you coordinate. Use for "agents <task>", "take this to done", "work on this in parallel", "what are my threads doing", "pick up <slug>", "resume <slug>", "keep going until it is merged". Under `/agents` you do the work yourself unless it needs several lanes or a long wait — you judge; the plan line says why. No target you could verify (a file, API, number or measure) → the grill interview first, not threads. Read this skill before proposing anything for `/agents`: without it a proposal is in-session subagents.

Meta/muse-code/skills/agents/SKILL.md

Read pinned source

Source commit a2d33761e49b98f6ec1b48f12143264eb9b4ff4f

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Network or broad shell
Last checked
Nov 10, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
71,110
Repository last updated
Nov 9, 2026
License
CC0-1.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# agents

1. **Decide**: yourself unless several lanes or a long wait (§ 1); an
   irreversible step → § 2's question, then act.
2. **Clarify**: no target you could verify → `read_skill grill`, its interview
   until settled, no plan before; one decision to confirm → one grill-shaped
   question before the act; `remember --decision` as each settles.
3. **Init**: the message on stdin, `init - --slug … --done-means … --goal …
   --repo …`; `--engine codex|claude` when the user names the workers' engine.
4. **Propose** (only when § 1 says threads; else do it now): the threads as
   JSON → `propose`.
5. **Open or ask**: a plain split → `go`, arm the wake, tell the plan; else
   the texts to choose between, or § 2's question.
6. **Each wake**: `context` once; inbox, oldest first; propose ready threads;
Back to top