How do I install the Announce skill?

Run npx skillmds@latest add egregore-labs/announce in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Announce safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Announce?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Announce free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Announce?

egregore-labs (@egregore-labs) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Announce by egregore-labs — Agent Skill

Name: Announce
Author: egregore-labs

File contents

Egregore Announce

Native Codex Egregore skill. Use this to send concise team announcements through the existing Egregore notification path.

Flow

Draft a message from the user request and current context. Keep it under 500 characters unless the user provided exact text.
If the announcement references a memory artifact, publish it first and add the returned URL only when publication succeeds:

bash bin/publish-artifact.sh document "$FILE_PATH" --title "$TITLE" --author "$AUTHOR" --description "$DESCRIPTION"

Use handoff, quest, or document as the artifact type when appropriate. Never fabricate a URL.

Follow .claude/context/notification-consent.md. Create a plan without sending:

PLAN_JSON=$(bash bin/notify.sh plan group "$MESSAGE")

Preview the plan's exact organization, all deliveries/channels, and exact final message. Confirm in a separate checkpoint with structured Codex question tooling when available; otherwise render those fields followed by:

Send this announcement?
1. Send
2. Edit
3. Cancel

If the user edits, cancel the old plan, redraft, plan, and preview again. If they cancel, cancel the plan and stop. Only after they select Send for that exact preview, run:

APPROVAL_JSON=$(bash bin/notify.sh approve "$PLAN_ID" "$DIGEST" APPROVE_EXACT_NOTIFICATION)
APPROVAL_TOKEN=$(printf '%s' "$APPROVAL_JSON" | jq -r '.approval_token')
bash bin/notify.sh dispatch "$PLAN_ID" "$APPROVAL_TOKEN"

Emit telemetry in the background:

bash bin/telemetry.sh emit "command" '{"command":"announce"}' >/dev/null 2>&1 &

Confirm whether the exact approved group send succeeded.

Rules

The request to announce is not dispatch consent. Always use a dedicated exact-delivery checkpoint.
Do not expose notification credentials.
Use bin/notify.sh; do not call Telegram directly.
Do not use Claude Code commands.

---name: announcedescription: Draft, confirm, and send an Egregore group announcement from Codex when the user invokes /announce or $announce.---# Egregore AnnounceNative Codex Egregore skill. Use this to send concise team announcementsthrough the existing Egregore notification path.## Flow1. Draft a message from the user request and current context. Keep it under 500 characters unless the user provided exact text.2. If the announcement references a memory artifact, publish it first and add the returned URL only when publication succeeds:```bashbash bin/publish-artifact.sh document "$FILE_PATH" --title "$TITLE" --author "$AUTHOR" --description "$DESCRIPTION"```Use `handoff`, `quest`, or `document` as the artifact type when appropriate.Never fabricate a URL.3. Follow `.claude/context/notification-consent.md`. Create a plan without sending:```bashPLAN_JSON=$(bash bin/notify.sh plan group "$MESSAGE")```4. Preview the plan's exact organization, all deliveries/channels, and exact final message. Confirm in a separate checkpoint with structured Codex question tooling when available; otherwise render those fields followed by:```textSend this announcement?1. Send2. Edit3. Cancel```5. If the user edits, cancel the old plan, redraft, plan, and preview again. If they cancel, cancel the plan and stop. Only after they select Send for that exact preview, run:```bashAPPROVAL_JSON=$(bash bin/notify.sh approve "$PLAN_ID" "$DIGEST" APPROVE_EXACT_NOTIFICATION)APPROVAL_TOKEN=$(printf '%s' "$APPROVAL_JSON" | jq -r '.approval_token')bash bin/notify.sh dispatch "$PLAN_ID" "$APPROVAL_TOKEN"```6. Emit telemetry in the background:```bashbash bin/telemetry.sh emit "command" '{"command":"announce"}' >/dev/null 2>&1 &```7. Confirm whether the exact approved group send succeeded.## Rules- The request to announce is not dispatch consent. Always use a dedicated exact-delivery checkpoint.- Do not expose notification credentials.- Use `bin/notify.sh`; do not call Telegram directly.- Do not use Claude Code commands.

Frequently asked questions

Announce