agentleFS
egregore-labsegregore-labs/egregore/.claude/skills/activity/SKILL.md

activity

Skill293 starsChanged 10 days agoMITView on GitHub

Explicit Activity card only. Use when the user names /activity or directly asks to show, open, or render the Activity dashboard/card. Never use it to answer or synthesize what the team is focused on, busy with, prioritizing, or doing; analytical organizational questions use Search/Runtime QMD.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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 this bounded status card only when the user names Activity or directly asks to display its dashboard/card.

    line 8
  2. Distinctive:

    Do not sync repositories, query memory again, or call implementation infrastructure directly.

    line 36
  3. Distinctive:

    Run one typed transition:

    line 52
  4. Distinctive:

    Never print raw JSON or narrate routine commands.

    line 64
  5. Very specific:

    Use /activity quests to show the snapshot's full bounded quest list.

    line 68

≈ “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.

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

Activity

Use this bounded status card only when the user names Activity or directly asks to display its dashboard/card. "Explicit" means display intent, not merely a question about the team. Questions asking for explanation or synthesis of current focus, themes, priorities, or work use attached EGREGORE_ORG_CONTEXT_V1 evidence or exactly one Search workflow query when that evidence is absent. The same applies to returning to earlier work. Never use Activity as discovery or analysis fallback.

Render the team view immediately. The renderer's stdout IS the product card: fully visible the moment rendering finishes, appearing exactly once in the conversation. Never copy, regenerate, summarize, or repeat the card — or any of its rows — in your reply. The card's own closing question is the prompt for the next turn; after the command, add nothing beyond an answer to something the user separately asked.

When to invoke

Explicit Activity card only. Use when the user names /activity or directly asks to show, open, or render the Activity dashboard/card. Never use it to answer or synthesize what the team is focused on, busy with, prioritizing, or doing; analytical organizational questions use Search/Runtime QMD.

Read path

Fetch exactly one authorized Runtime snapshot and render it:

bash bin/activity-data.sh 2>/dev/null \
  | bash bin/node-run.sh bin/codex-skill-render.mjs activity-card -

Do not sync repositories, query memory again, or call implementation infrastructure directly. The snapshot already contains bounded canonical sessions, questions, quests, todos, and lifecycle-resolved handoffs. Canonical Markdown/Git wins over every projection.

Connected enrichment is a separate capability-authorized adapter. Use it only when the user explicitly asks for Connected/projected status by setting EGREGORE_STATUS_CONNECTED_ENRICH=1 for the same single data command. Never replace canonical lifecycle fields with the returned projection payload.

Handoff actions

For activity done N, activity expire N, or activity reopen N:

  1. Fetch one snapshot as above.
  2. Map N to handoffs_to_me[N-1].
  3. Run one typed transition:
bash bin/activity-action.sh <done|expire|reopen> "<sessionId>" \
  --expected-revision "<lifecycleRevision>"

Report the resulting canonical state. Never accept graph state as lifecycle authority, silently complete work by age, or record focus through graph calls.

Rendering rules

  • Never print raw JSON or narrate routine commands.
  • Preserve the shared 72-column activity card.
  • Show Local status without graph/setup messaging.
  • End the turn after the card; act on the user's reply next turn.
  • Use /activity quests to show the snapshot's full bounded quest list.

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.