How do I install the Emissary skill?

Run npx skillmds@latest add egregore-labs/emissary 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 Emissary 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 Emissary?

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 Emissary free to use?

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

Who published Emissary?

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

Emissary by egregore-labs — Agent Skill

Name: Emissary
Author: egregore-labs

Emissary

Compose, send, or run an Egregore emissary — portable handoff v1 artifacts with server-rendered HTML at egregore.xyz. Use for `/emissary`, "make/send/run an emissary", or when a user pastes an `egregore.xyz/emissary/e/<id>` link.

File contents

Egregore emissary Adapter

This is fallback coverage for a long-tail Egregore workflow that has not been ported to a hand-written Codex-native skill yet.

Use the project shell and filesystem directly. Do not invoke Claude Code commands. Translate interactive choices to structured Codex question tooling when it is available; otherwise render compact numbered choices with an Other: option and wait for the user.

Structured UX parity

This workflow has a Claude skill with user-visible structured output. After reading .claude/skills/emissary/SKILL.md, reproduce the same visible UX in Codex:

Preserve TUI boxes, markdown tables, rich cards, browser artifact rendering, exact confirmation blocks, and "no preamble" rules from the source skill.
Use the source skill's frame width, section order, labels, status footer, and examples as the contract for the final response.
Never replace a required box/table/card/artifact view with a prose summary unless the user explicitly asks for a summary.
When the source says to output a TUI box directly, paste that box as the visible response, preferably in a text fenced block.
Never show raw JSON, raw command output, or unformatted script output when the source skill requires formatted status or rendered output.

Read .claude/skills/emissary/SKILL.md for the workflow details.
Run the referenced bin/ scripts directly from Codex.
Treat graph and publish steps as best-effort unless that workflow explicitly says they are required.
For every external notification, follow .claude/context/notification-consent.md: plan without sending, then show a separate exact Send / Edit / Cancel checkpoint. Never infer notification consent from the workflow request or a batch approval.
Keep local-mode behavior filesystem-first and avoid graph or notification calls when egregore.json declares "mode": "local".
Never call the deprecated egregore-handoff CLI for Egregore project handoffs.

---name: emissarydescription: Compose, send, or run an Egregore emissary — portable handoff v1 artifacts with server-rendered HTML at egregore.xyz. Use for `/emissary`, "make/send/run an emissary", or when a user pastes an `egregore.xyz/emissary/e/<id>` link.---# Egregore emissary AdapterThis is fallback coverage for a long-tail Egregore workflow that has not beenported to a hand-written Codex-native skill yet.Use the project shell and filesystem directly. Do not invoke Claude Codecommands. Translate interactive choices to structured Codex question toolingwhen it is available; otherwise render compact numbered choices with an`Other:` option and wait for the user.## Structured UX parityThis workflow has a Claude skill with user-visible structured output. Afterreading `.claude/skills/emissary/SKILL.md`, reproduce the same visible UX in Codex:- Preserve TUI boxes, markdown tables, rich cards, browser artifact rendering, exact confirmation blocks, and "no preamble" rules from the source skill.- Use the source skill's frame width, section order, labels, status footer, and examples as the contract for the final response.- Never replace a required box/table/card/artifact view with a prose summary unless the user explicitly asks for a summary.- When the source says to output a TUI box directly, paste that box as the visible response, preferably in a `text` fenced block.- Never show raw JSON, raw command output, or unformatted script output when the source skill requires formatted status or rendered output.1. Read `.claude/skills/emissary/SKILL.md` for the workflow details.2. Run the referenced `bin/` scripts directly from Codex.3. Treat graph and publish steps as best-effort unless that workflow explicitly says they are required.4. For every external notification, follow `.claude/context/notification-consent.md`: plan without sending, then show a separate exact Send / Edit / Cancel checkpoint. Never infer notification consent from the workflow request or a batch approval.5. Keep local-mode behavior filesystem-first and avoid graph or notification calls when `egregore.json` declares `"mode": "local"`.6. Never call the deprecated `egregore-handoff` CLI for Egregore project handoffs.

Frequently asked questions