Egregore delete-user Adapter
SkillDatabases & dataRemove 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).
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Egregore delete-user Adapter skill
What this skill tells your AI
The instructions your AI receives, as published by egregore-labs/egregore in .codex/skills/delete-user/SKILL.md and read by ahel’s review.
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.
- Read
.claude/skills/delete-user/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.
Signals
- GitHub stars
- 289
- Forks
- 21
- Last commit
- Sep 2026
ahel recommends instead
Advanced
- Catalog kind
- skill
- Gateway key
delete-user- Source
- github.com/egregore-labs/egregore