agentleFS
Sign inStart free
dadwadw233dadwadw233/team-collab-skills/skills/digest/SKILL.md

digest

Skill4 starsChanged 6 months agoApache-2.0View on GitHub

Use when the user invokes `$digest`, asks for a multi-agent wave digest or progress summary, or asks "what's the status of the wave" / "where are things".

  • Installs packages

36 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use aeon-update, auto-workflow and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • aaronjmarsSkill

    aeon-update

    Pull framework updates from the upstream Aeon repo into this instance - 3-way merges canon's new commits into a PR, never clobbering operator config.

    Also in 4 projects that use this

  • aaronjmarsSkill

    auto-workflow

    Two-mode aeon.yml workflow builder - analyze inspects URLs and emits a tiered, signal-verified skill-enablement plan plus an aeon.yml diff; enable flips slugs to enabled:true and opens a PR.

    Also in 4 projects that use this

  • +10 more from aaronjmars

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 1 is distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 32 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Follow the installed team-collab-protocol skill and its references/multi-agent.md flow.

    line 21
  2. Very specific:

    Before running any CLI command, check command -v team-collab.

    line 22
  3. Very specific:

    Treat the first token after $digest as the wave slug.

    line 23
  4. Very specific:

    If the user asked for a fresher view of code/docs state, add --refresh-truth-source.

    line 28
  5. Distinctive:

    If a decision or unblock is needed, tell the user what's blocking and let them direct the next step.

    line 31
  6. Very specific:

    If a future Codex version supports custom slash commands and /digest reaches the model as plain user text, handle it exactly the same way …

    line 35

“Common” is measured: kept by at least 6 in 10 of the 32 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.

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

Team Collab Digest

This is a Codex-friendly command wrapper for the multi-agent wave digest. Codex does not currently support arbitrary custom top-level slash commands like /digest, so the supported Codex entry point is:

$digest <slug>

What this does

The digest aggregates a whole wave into one view: what needs a decision, what's blocked, what's merge-ready, the merge order, truth-source/resource risks, and which agents have gone stale. $digest is the human→coordinator shortcut for "where are things right now".

Required behavior

  1. Follow the installed team-collab-protocol skill and its references/multi-agent.md flow. If the protocol skill is not available in the current session, read ~/.codex/skills/team-collab-protocol/SKILL.md; if that file is missing, stop and tell the user to run team-collab install-skills --agent codex --force.
  2. Before running any CLI command, check command -v team-collab. If missing, stop and tell the user to install the CLI with npm install -g @embodot/collab@latest, then refresh skills with team-collab install-skills --agent codex --force if needed.
  3. Treat the first token after $digest as the wave slug. If none is given, infer the wave from the current working directory (multi-agent/<slug>/ subtree). If still unknown, ask which wave.
  4. Run the digest:
    team-collab multi-agent digest --wave <slug>
    If the user asked for a fresher view of code/docs state, add --refresh-truth-source. If they asked about a specific time window, add --since <duration>.
  5. Present the digest output to the user. Call attention to anything in the Needs Decision, Blockers, or Stale Agents sections, since those are the items most likely to need the user's input.
  6. Be clear about write semantics: the CLI creates multi-agent/<slug>/digests/*.md and makes a local docs commit; --refresh-truth-source may also update agent status files. It does not auto-push, so cross-machine visibility requires an explicit docs repo push.
  7. If a decision or unblock is needed, tell the user what's blocking and let them direct the next step.

Compatibility note

If a future Codex version supports custom slash commands and /digest reaches the model as plain user text, handle it exactly the same way as $digest.

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