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

announce

Skill293 starsChanged 11 days agoMITView on GitHub

Draft, preview, and explicitly send an Egregore group announcement. Use for /announce, telling the team something, or notifying everyone—not a direct message or structured handoff.

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

6 rules. 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Write the final draft to tmp/announce-message.md, then make the file private and prepare one actor-bound Runtime plan:

    line 18
  2. Distinctive:

    Read the plan's identifier and digest:

    line 29
  3. Very specific:

    Use the printed values as {plan_id} and {digest}, respectively.

    line 35
  4. Distinctive:

    Read the exact preview fields from the saved plan:

    line 39
  5. Distinctive:

    Only a fresh Send response for that exact checkpoint authorizes:

    line 53
  6. Very specific:

    Use {plan_id} from the saved plan.

    line 60

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

Egregore announce

Draft one concise group message. The request authorizes drafting, never dispatch or artifact publication. Reuse sufficient EGREGORE_ORG_CONTEXT_V1; do not repeat organizational retrieval merely to decorate the message.

Preserve quoted wording exactly. Otherwise use 2–5 lines: what changed, the relevant branch/artifact when already authorized, and the requested action. Notification consent and publication consent are separate. Never publish a referenced artifact automatically; publication is a separate SHARE workflow with its own source/destination approval.

Write the final draft to tmp/announce-message.md, then make the file private and prepare one actor-bound Runtime plan:

chmod 600 tmp/announce-message.md
bash bin/notification.sh plan --kind group --message-file tmp/announce-message.md > tmp/announce-plan.json

Read the plan's identifier and digest:

jq -r '.plan_id, .digest' tmp/announce-plan.json

Use the printed values as {plan_id} and {digest}, respectively; quote placeholders in single quotes when you use them in a command, and write any single quote inside a value as '\''.

Read the exact preview fields from the saved plan:

jq -r '.org, .recipient, .channels, .deliveries, .message' tmp/announce-plan.json

Show one dedicated Send / Edit / Cancel checkpoint containing the exact organization, group, every delivery/channel, and final message returned by the plan. Edit cancels the old plan before creating a new one. Cancel calls:

bash bin/notification.sh cancel '{plan_id}'

Only a fresh Send response for that exact checkpoint authorizes:

bash bin/notification.sh approve \
  '{plan_id}' '{digest}' APPROVE_EXACT_NOTIFICATION --out tmp/announce-approval.json

Use {plan_id} from the saved plan; the adapter reads the private approval receipt from tmp/announce-approval.json without exposing its credential:

bash bin/notification.sh dispatch '{plan_id}' --approval-file tmp/announce-approval.json

Report the returned delivery receipt. Never retry from old approval, change a destination, or fall back to another channel. Local instances without a notification capability stop after preview and return the text for manual use. The Runtime service owns ActorContext authorization, exact-plan binding, transport, and content-free telemetry.

When to invoke

Draft, preview, and explicitly send an Egregore group announcement. Use for /announce, telling the team something, or notifying everyone—not a direct message or structured handoff.

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.