egregore-labs
- 96 skills
- 0 followers
- 5 hours ago last updated
- ▌ Me 2 · egregore-labsView or change your member identity — display name, email — shared across Claude Code, Codex, and Pi. Say 'who am I', 'call me <name>', 'change my name to X', or run '/me'.
- ▌ Pr 2 · egregore-labsUse for /pr, or 'create a PR' / 'open a pull request' — creates a pull request for the current branch against the repo's base branch with a formatted title and body. Not for reviewing an existing PR (review-pr).
- ▌ Note 2 · egregore-labsUse when the user says 'jot this down', 'note to self', 'just thinking out loud', or 'park this thought' — saves a private personal note, never shared or pushed until explicitly promoted.
- ▌ Pull 2 · egregore-labsUse for /pull when you need to sync the current branch and shared memory without also viewing activity (/activity auto-syncs already).
- ▌ Push 2 · egregore-labsUse for /push, or 'push my branch' — pushes the current branch to origin, setting upstream on first push, before opening a PR with /pr.
- ▌ Save 2 · egregore-labsUse when the user says 'push my work', 'save everything', or 'commit and push' — pushes the working branch and opens a PR to develop. Not when the user is leaving/done (/handoff, which auto-saves).
- ▌ Test 2 · egregore-labsValidate changes before /save — static analysis plus live Cypher validation against the graph, rendered as a pass/fail gate. Use for /test or 'test my changes'.
- ▌ View 2 · egregore-labs bundleGenerate a branded HTML artifact from Egregore data (quest, handoff, activity, board, network, or any document) and open it in the browser. Use for /view, 'render this', or 'show me visually'.
- ▌ Wrap 2 · egregore-labsClose your session with a personal summary — enriches the auto-captured Session node with topic, summary, and connections. Auto-saves. Use for /wrap or 'I'm done for now'.
- ▌ Issue 2 · egregore-labsReport an issue — captures context and routes it to the right place. Say 'this is broken', 'bug in', 'file an issue', 'report a problem'. Not a personal task (/todo) or team exploration (/quest).
- ▌ Quest 2 · egregore-labsUse when the user says 'let's explore', 'start a quest', or 'what quests are open' — manages open-ended explorations anyone can contribute to. Not a personal task (/todo) or something broken (/issue).
- ▌ Branch 2 · egregore-labsCreate a working branch from what you are about to work on. Use for /branch, or any request to start a new branch before making changes.
- ▌ Commit 2 · egregore-labsStage changes and create a commit with a properly formatted message. Use for /commit, or saving work locally — not sharing it (/push) or opening a pull request (/pr).
- ▌ Ingest 2 · egregore-labsUnified ingestion entry point — brings files, meetings, Google Workspace, Notion, or bulk corpora into intake, then promotes useful material into curated memory. Say 'ingest', 'bring this into Egregore'.
- ▌ Invite 2 · egregore-labsInvite someone to this Egregore — GitHub org invitation plus setup link. Say '/invite <username>' or 'invite <username> to the org'. Not removing a member (/delete-user).
- ▌ Summon 2 · egregore-labsDesign and launch a persistent agent (a spirit) that runs on a schedule or watches for conditions, via adaptive questioning that produces a reviewable spec before launch.
- ▌ Update 2 · egregore-labsUpdate local Egregore environment — sync the framework from upstream, run post-update migrations, and pull repos. Use for /update or when framework behavior seems broken or missing.
- ▌ Archive 2 · egregore-labsCapture an effective prompting technique or steering pattern as reusable knowledge. Use for /archive, or when a prompt worked especially well and is worth reusing — not insight about the work itself (/reflect).
- ▌ Checkup 2 · egregore-labsRun diagnostics on your Egregore environment and render a health report, auto-fixing what it can. Use for /checkup, a health check, or when something is broken and the root cause is unclear.
- ▌ Handoff 2 · egregore-labsAddress the current session context to a teammate or future you — pure capture, auto-saved. Say 'leave a handoff', 'pass this to <name>'. Not personal closure (/wrap), pending triage (/activity), or plain push (/save).
- ▌ Harvest 2 · egregore-labs bundleRun an adaptive harvest — directed elicitation that extracts, deepens, and synthesizes what people think about a topic. Say 'harvest', 'run a harvest', 'align the team on'. Not a casual question or unstructured chat.
- ▌ Meeting 2 · egregore-labsUse for /meeting, /meeting sync, /meeting backfill, or a search term — adaptively analyzes a Granola meeting into decisions, findings, actions, and continuity in shared memory.
- ▌ Reflect 2 · egregore-labsUse when the user says 'we decided', 'I realized', or 'that's a pattern' — captures decisions, findings, or patterns in shared memory. Not a private half-baked thought (/note) or cross-referencing (/deep-reflect).
- ▌ Activity 2 · egregore-labsSee what is happening across the team — recent sessions, handoffs, quests, and open PRs. Use for /activity, catching up after time away, or checking team-wide status at a glance.
- ▌ Announce 2 · egregore-labsSend an announcement to the Telegram group with a draft-then-approve flow. Use for /announce, telling the team something, or notifying everyone at once — not messaging one person or a structured handoff.
- ▌ Emissary 2 · egregore-labsCompose, 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.
- ▌ Tutorial 2 · egregore-labsInteractive walkthrough of Egregore's core loop — /activity, /reflect, and /quest or /add — with adaptive questions and real artifacts. Use for /tutorial or 'walk me through Egregore'.
- ▌ Dark Mode 2 · egregore-labsUse when generating or modifying any visual output that renders in a browser or artifact viewer: HTML pages, CSS, React SSR components, Egregore artifacts, markdown renderers, web components, design-system tokens, Tailwind themes, or standalone demos. Triggers on requests involving dark mode, theme toggles, color systems, card surfaces, browser rendering, or visual polish. The load-bearing lesson: if React SSR emits an inline hex color through `style={}`, CSS dark-mode overrides cannot reach it, so every theme-sensitive color must be emitted as `var(--token)` rather than a resolved hex. Do not use for TUI output, plain markdown files, or non-visual code.
- ▌ Dashboard 2 · egregore-labsSee your recent sessions, open handoffs, and current work at a glance. Use for /dashboard, checking your personal status — not the team-wide view (/activity).
- ▌ Review Pr 2 · egregore-labsUse when the user says 'review PR', 'is this PR safe to merge', or 'audit PR' — runs a CTO-level 10-point review checklist on one or more pull requests. Not creating a PR (/pr) or validating local changes (/test).
- ▌ Telemetry 2 · egregore-labsManage your own telemetry settings — check status, opt in/out, view or clear the buffered events. Use for /telemetry, 'turn off telemetry', or 'what data do you collect'.
- ▌ Contribute 2 · egregore-labsContribute an improvement back to the upstream Egregore framework as a cross-fork pull request. Use for /contribute, or submitting a framework fix upstream — not saving org work (/save) or filing a bug (/issue).
- ▌ Onboarding 2 · egregore-labsUse for /onboarding, or when a new member's onboarding is not yet complete — runs the deterministic VERIFY, ORIENT, INVITE, FIRST_HANDOFF welcome flow.
- ▌ Sync Repos 2 · egregore-labsSmart sync of all Egregore repos (memory + managed repos + current repo) — fetches first, only pulls if behind. Use for /sync-repos or 'sync all repos'.
- ▌ The Spiral 2 · egregore-labsA generative epistemology engine that transforms intuitions into rigorous, communicable output through structured Socratic dialogue. Use this skill whenever someone needs to develop, pressure-test, and articulate a complex thesis — fundraising materials, book proposals, product strategy, research agendas, organizational philosophy, policy design, or any context requiring deep structured thinking. Triggers on: 'let's think through', 'help me articulate', 'pressure test this', 'develop this thesis', 'spiral', 'deep exploration', 'Socratic', or any request to go from intuition to rigorous output. Also triggers when a user has a strong conviction but can't yet articulate it clearly, or when they need to prepare materials that require deep domain understanding (pitch decks, memos, strategy docs, proposals).
- ▌ Tui Design 2 · egregore-labsTUI Design System for Egregore slash commands. Use when designing or modifying any command's terminal output to ensure visual consistency. Triggers on: TUI, terminal output, box drawing, command output formatting, sigils, section markers. Do NOT use for browser rendering (use dark-mode) or external prose (use egregore-voice).
- ▌ Delete User 2 · egregore-labsRemove a member from this Egregore, revoking access across GitHub, Supabase, and Neo4j. Use for /delete-user, removing or kicking someone — not inviting (/invite) or viewing members (/dashboard).
- ▌ Create Skill 2 · egregore-labsCreate a skill your org owns — scaffolded in this Egregore, protected from framework updates, shared with teammates via /save.
- ▌ Deep Reflect 2 · egregore-labs bundleRun deep, multi-hop research over org memory to answer a question or cross-reference an insight, with a cited synthesis. Use for /deep-reflect — not one-shot recall (/search) or capturing an insight (/reflect).
- ▌ Ingest Corpus 2 · egregore-labsTurn a large folder of documents into a Connect-only knowledge base that answers questions with sources. Say 'build a knowledge base'. Not a few files (/ingest) or a meeting/Notion/Google source.
- ▌ Ingest Notion 2 · egregore-labsBring selected Notion pages into shared Egregore memory via Notion's official MCP. Routed from /ingest when the source is Notion — say '/ingest notion'. Selected pages only, not a full-workspace sync.
- ▌ Slack Connect 2 · egregore-labsSet up Slack as a notification channel for your Egregore — creates the workspace app, invites the bot, and binds a channel. Use for /slack-connect, 'connect slack', or 'set up slack notifications'.
- ▌ Teams Connect 2 · egregore-labsSet up Microsoft Teams as a notification channel for your Egregore — registers an Azure bot, uploads the app, and binds a channel. Use for /teams-connect, 'connect teams', or 'set up teams notifications'.
- ▌ Notion Connect 2 · egregore-labsUse for 'connect notion', 'notion status', or 'disconnect notion' — connects the current agent runtime directly to Notion's official hosted MCP for search and fetch, or checks/revokes that connection.
- ▌ Visual Explain 2 · egregore-labsExplain concepts visually using ASCII diagrams, flow charts, tables, and structural maps. Use when asked to explain, compare, or show how something works.
- ▌ Telegram Connect 2 · egregore-labsSet up Telegram as a notification center for your Egregore — creates the group, links the bot, and stores the chat ID. Use for /telegram-connect, 'connect telegram', or 'set up telegram notifications'.
- ▌ Ingest User Interview 2 · egregore-labsAnalyze user interview transcripts (Granola, pasted text, or a file) through a 3-analyst-agent plus Opus-synthesis pipeline. Say 'process the interview', 'onboarding interview', 'research call'.
- ▌ Me · egregore-labsView or change your member identity — display name, email — shared across Claude Code, Codex, and Pi. Say 'who am I', 'call me <name>', 'change my name to X', or run '/me'.
- ▌ Pr · egregore-labsUse for /pr, or 'create a PR' / 'open a pull request' — creates a pull request for the current branch against the repo's base branch with a formatted title and body. Not for reviewing an existing PR (review-pr).
- ▌ Note · egregore-labsUse when the user says 'jot this down', 'note to self', 'just thinking out loud', or 'park this thought' — saves a private personal note, never shared or pushed until explicitly promoted.
- ▌ Pull · egregore-labsUse for /pull when you need to sync the current branch and shared memory without also viewing activity (/activity auto-syncs already).
- ▌ Push · egregore-labsUse for /push, or 'push my branch' — pushes the current branch to origin, setting upstream on first push, before opening a PR with /pr.
- ▌ Save · egregore-labsSave Egregore work when the user invokes /save or $save, or asks to commit, push, sync, or save current changes from a Codex Egregore session.
- ▌ Test · egregore-labsValidate changes before /save — static analysis plus live Cypher validation against the graph, rendered as a pass/fail gate. Use for /test or 'test my changes'.
- ▌ View · egregore-labs bundleRender Egregore data and documents as branded browser artifacts. Use when the user invokes /view or $view, asks to show something visually, open it in a browser, make a document readable or presentable, render a quest/handoff/activity/board/network, or synthesize a visual artifact from a topic.
- ▌ Wrap · egregore-labsWrap an Egregore session when the user invokes /wrap or $wrap, or says they are done, wrapping up, or at a stopping point in Codex.
- ▌ Issue · egregore-labsReport an issue — captures context and routes it to the right place. Say 'this is broken', 'bug in', 'file an issue', 'report a problem'. Not a personal task (/todo) or team exploration (/quest).
- ▌ Quest · egregore-labsManage Egregore quests from Codex when the user invokes /quest or $quest, or asks to manage quests, using memory-first files and optional connected-mode graph updates.
- ▌ Branch · egregore-labsCreate a working branch from what you are about to work on. Use for /branch, or any request to start a new branch before making changes.
- ▌ Commit · egregore-labsStage changes and create a commit with a properly formatted message. Use for /commit, or saving work locally — not sharing it (/push) or opening a pull request (/pr).
- ▌ Ingest · egregore-labsUnified ingestion entry point — brings files, meetings, Google Workspace, Notion, or bulk corpora into intake, then promotes useful material into curated memory. Say 'ingest', 'bring this into Egregore'.
- ▌ Invite · egregore-labsInvite a GitHub user into this Egregore instance from Codex when the user invokes /invite or $invite, or asks to invite someone without exposing credentials.
- ▌ Summon · egregore-labsDesign and launch a persistent agent (a spirit) that runs on a schedule or watches for conditions, via adaptive questioning that produces a reviewable spec before launch.
- ▌ Update · egregore-labsUpdate local Egregore environment — sync the framework from upstream, run post-update migrations, and pull repos. Use for /update or when framework behavior seems broken or missing.
- ▌ Archive · egregore-labsCapture an effective prompting technique or steering pattern as reusable knowledge. Use for /archive, or when a prompt worked especially well and is worth reusing — not insight about the work itself (/reflect).
- ▌ Checkup · egregore-labsRun diagnostics on your Egregore environment and render a health report, auto-fixing what it can. Use for /checkup, a health check, or when something is broken and the root cause is unclear.
- ▌ Handoff · egregore-labsCreate an internal Egregore team handoff when the user invokes /handoff or $handoff, asks to hand off work, or wants to pass context to a teammate or future self.
- ▌ Harvest · egregore-labs bundleRun an adaptive Egregore harvest from Codex when the user invokes /harvest or $harvest to elicit tacit context, preferences, positions, and team judgment.
- ▌ Meeting · egregore-labsUse for /meeting, /meeting sync, /meeting backfill, or a search term — adaptively analyzes a Granola meeting into decisions, findings, actions, and continuity in shared memory.
- ▌ Reflect · egregore-labsUse when the user says 'we decided', 'I realized', or 'that's a pattern' — captures decisions, findings, or patterns in shared memory. Not a private half-baked thought (/note) or cross-referencing (/deep-reflect).
- ▌ Preview Design · egregore-labs bundleRender a real artifact through this branch's local MERIDIAN design code (not the published npm package) so the team can test the new Design Convention on the document / handoff / platform surfaces before it ships. Use for `/preview-design`, "preview the design convention", "render this with the new design", or Design Convention round-1 testing.
- ▌ Activity · egregore-labsShow Egregore team activity, pending handoffs, and open questions when the user invokes /activity or $activity, or asks what is happening in an Egregore checkout.
- ▌ Announce · egregore-labsDraft, confirm, and send an Egregore group announcement from Codex when the user invokes /announce or $announce.
- ▌ Emissary · egregore-labsCompose, 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.
- ▌ Tutorial · egregore-labsInteractive walkthrough of Egregore's core loop — /activity, /reflect, and /quest or /add — with adaptive questions and real artifacts. Use for /tutorial or 'walk me through Egregore'.
- ▌ Dark Mode · egregore-labsUse when generating or modifying any visual output that renders in a browser or artifact viewer: HTML pages, CSS, React SSR components, Egregore artifacts, markdown renderers, web components, design-system tokens, Tailwind themes, or standalone demos. Triggers on requests involving dark mode, theme toggles, color systems, card surfaces, browser rendering, or visual polish. The load-bearing lesson: if React SSR emits an inline hex color through `style={}`, CSS dark-mode overrides cannot reach it, so every theme-sensitive color must be emitted as `var(--token)` rather than a resolved hex. Do not use for TUI output, plain markdown files, or non-visual code.
- ▌ Dashboard · egregore-labsShow the current user's Egregore dashboard, recent sessions, open threads, and current work from Codex when the user invokes /dashboard or $dashboard, or asks for their dashboard.
- ▌ Review Pr · egregore-labsUse when the user says 'review PR', 'is this PR safe to merge', or 'audit PR' — runs a CTO-level 10-point review checklist on one or more pull requests. Not creating a PR (/pr) or validating local changes (/test).
- ▌ Telemetry · egregore-labsManage your own telemetry settings — check status, opt in/out, view or clear the buffered events. Use for /telemetry, 'turn off telemetry', or 'what data do you collect'.
- ▌ Contribute · egregore-labsContribute an improvement back to the upstream Egregore framework as a cross-fork pull request. Use for /contribute, or submitting a framework fix upstream — not saving org work (/save) or filing a bug (/issue).
- ▌ Onboarding · egregore-labsUse for /onboarding, or when a new member's onboarding is not yet complete — runs the deterministic VERIFY, ORIENT, INVITE, FIRST_HANDOFF welcome flow.
- ▌ Sync Repos · egregore-labsSmart sync of all Egregore repos (memory + managed repos + current repo) — fetches first, only pulls if behind. Use for /sync-repos or 'sync all repos'.
- ▌ The Spiral · egregore-labsRun a Codex-native structured Socratic dialogue when the user invokes /the-spiral or $the-spiral to turn an intuition into rigorous, communicable output.
- ▌ Tui Design · egregore-labsTUI Design System for Egregore slash commands. Use when designing or modifying any command's terminal output to ensure visual consistency. Triggers on: TUI, terminal output, box drawing, command output formatting, sigils, section markers. Do NOT use for browser rendering (use dark-mode) or external prose (use egregore-voice).
- ▌ Delete User · egregore-labsRemove a member from this Egregore, revoking access across GitHub, Supabase, and Neo4j. Use for /delete-user, removing or kicking someone — not inviting (/invite) or viewing members (/dashboard).
- ▌ Create Skill · egregore-labsCreate a skill your org owns — scaffolded in this Egregore, protected from framework updates, shared with teammates via /save.
- ▌ Deep Reflect · egregore-labsDeep research over the Egregore org memory — multi-hop, evidence-verified synthesis of what the org collectively knows — when the user invokes /deep-reflect or $deep-reflect.
- ▌ Ingest Corpus · egregore-labsTurn a large folder of documents into a Connect-only knowledge base that answers questions with sources. Say 'build a knowledge base'. Not a few files (/ingest) or a meeting/Notion/Google source.
- ▌ Ingest Notion · egregore-labsBring selected Notion pages into shared Egregore memory via Notion's official MCP. Routed from /ingest when the source is Notion — say '/ingest notion'. Selected pages only, not a full-workspace sync.
- ▌ Slack Connect · egregore-labsSet up Slack as a notification channel for your Egregore — creates the workspace app, invites the bot, and binds a channel. Use for /slack-connect, 'connect slack', or 'set up slack notifications'.
- ▌ Teams Connect · egregore-labsSet up Microsoft Teams as a notification channel for your Egregore — registers an Azure bot, uploads the app, and binds a channel. Use for /teams-connect, 'connect teams', or 'set up teams notifications'.
- ▌ Notion Connect · egregore-labsUse for 'connect notion', 'notion status', or 'disconnect notion' — connects the current agent runtime directly to Notion's official hosted MCP for search and fetch, or checks/revokes that connection.
- ▌ Visual Explain · egregore-labsExplain concepts visually using ASCII diagrams, flow charts, tables, and structural maps. Use when asked to explain, compare, or show how something works.
- ▌ Egregore · egregore-labs bundleEgregore mechanics as kernel functions — search shared memory, read team activity, create handoffs, save work, branch, and prepare notification plans without re-deriving bin/ CLI usage. Import and call directly; every function wraps the same runtime-neutral bin/ scripts the other harnesses use.
- ▌ Telegram Connect · egregore-labsSet up Telegram as a notification center for your Egregore — creates the group, links the bot, and stores the chat ID. Use for /telegram-connect, 'connect telegram', or 'set up telegram notifications'.
- ▌ Ingest User Interview · egregore-labsAnalyze user interview transcripts (Granola, pasted text, or a file) through a 3-analyst-agent plus Opus-synthesis pipeline. Say 'process the interview', 'onboarding interview', 'research call'.