egregore-labs/egregore / .codex/skills/meeting
meeting
UnverifiedAnalyze a Granola meeting into an evidence-backed briefing, decisions, findings, patterns, actions, and continuity. Use for /meeting, /meeting sync, /meeting backfill, or requests to process a meeting.
Egregore meeting Adapter
This adapter runs the canonical Egregore workflow for meeting. Its one
maintained body is .claude/skills/meeting/SKILL.md; read that file completely and follow it here.
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/meeting/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
textfenced block. - If the canonical body says the command's stdout is the card and must not
be repeated, that rule assumes a host that displays command output in full;
in Codex, paste the card once as the visible response in a
textfenced block and do not print it a second time. - Never show raw JSON, raw command output, or unformatted script output when the source skill requires formatted status or rendered output.
- Read
.claude/skills/meeting/SKILL.mdfor 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.jsondeclares"mode": "local". - Never call the deprecated
egregore-handoffCLI for Egregore project handoffs.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |