delete-user
Skill293 starsChanged 10 days agoMITView on GitHub
Remove 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).
- Reads credentials
1 other project uses a version of this.
Adopted by
Most recently taken up by
- BerriAI/litellm-skillstheir own version, first seen Apr 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- BerriAI/litellm-skills★ 84same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository50 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- activitySkill
- announceSkill
- archiveSkill
- branchSkill
- checkupSkill
- commitSkill
- contributeSkill
- create-skillSkill
- dark-modeSkill
- dashboardSkill
- deep-reflectSkill
- emissarySkill
- envSkill
- handoffSkill
- harvestSkill
- ingest-corpusSkill
- ingest-notionSkill
- ingestSkill
- ingest-user-interviewSkill
- inviteSkill
- issueSkill
- meetingSkill
- meSkill
- noteSkill
- notion-connectSkill
- onboardingSkill
- prSkill
- pullSkill
- pushSkill
- questSkill
- recordsSkill
- reflectSkill
- review-prSkill
- saveSkill
- slack-connectSkill
- summonSkill
- sync-reposSkill
- telegram-connectSkill
- telemetrySkill
- testSkill
- the-spiralSkill
- tui-designSkill
- tutorialSkill
- updateSkill
- viewSkill
- visual-explainSkill
- wrapSkill
- preview-designSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 2 are distinctive, and 9 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 6
Remove a member from this Egregore.
- Very specific: line 11
Not this: invite someone → /invite · view members → /dashboard
- Very specific: line 19
CRITICAL: Never expose credentials in tool output: All credential handling happens inside bin/api-call.sh.
- Very specific: line 23
If $ARGUMENTS is empty, show usage and stop:
- Very specific: line 50
If "Cancel", stop with: Cancelled.
- Distinctive: line 56
Read the non-secret configuration first:
- Very specific: line 62
Use the printed value as {slug}.
- Very specific: line 68
Use that printed value as {slug} instead.
- Distinctive: line 70
Run with description "Removing {username} from org":
- Very specific: line 84
Treat .status == "removed" as success.
- Very specific: line 116
If errors array is non-empty, append:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Remove a member from this Egregore. Revokes access across GitHub, Supabase, and Neo4j.
When to invoke
User says: "remove user", "delete user", "kick", "revoke access", "remove member", "remove them", "delete member"
Not this: invite someone → /invite · view members → /dashboard
Arguments: $ARGUMENTS (Required: GitHub username of the person to remove)
Execution rules
CRITICAL: Suppress raw output. Save the API response to a file, read it with jq, and only show formatted status lines to the user.
CRITICAL: Never expose credentials in tool output. All credential handling happens inside bin/api-call.sh; never read a token into the conversation or substitute it into a command.
Step 1: Validate
If $ARGUMENTS is empty, show usage and stop:
Usage: /delete-user <github-username>
Example: /delete-user someuser
Modes (you'll be asked):
revoke — Remove access, keep their contributions
full — Remove access and erase their dataStep 2: Confirm
For confirmation, ask with a structured question when available and permitted in this session; otherwise ask in plain text:
question: "How should {username} be removed from this org?"
header: "Remove mode"
options:
- label: "Revoke access"
description: "Remove repository and hosted membership access. Keep their sessions, artifacts, and contributions in shared memory."
- label: "Full delete"
description: "Revoke access AND erase their sessions, profile, todos, and telemetry. Artifacts and quests are kept but orphaned."
- label: "Cancel"
description: "Don't remove anyone."If "Cancel", stop with: Cancelled.
Map "Revoke access" → mode=revoke, "Full delete" → mode=full.
Step 3: Remove (credentials stay inside the helper)
Read the non-secret configuration first:
bash bin/config-get.sh slugUse the printed value as {slug}. If slug is unset or empty, read the fallback:
bash bin/config-get.sh org_nameUse that printed value as {slug} instead. Use the supplied GitHub username as {username} and the confirmed mode (revoke or full) as {mode}. Quote substituted values in single quotes, writing any embedded single quote as '\''.
Run with description "Removing {username} from org":
bash bin/api-call.sh DELETE '/api/org/{slug}/members/{username}?mode={mode}' --auth github --out tmp/delete-user-response.jsonThe helper reads the configured API URL and GitHub token internally, falling back to gh auth token if the token is absent from .env. If it fails, report its error and stop; the helper leaves no response file after a failure.
Read the response:
jq '.' tmp/delete-user-response.jsonTreat .status == "removed" as success. Use .mode, .username, and .actions for the result, .errors for partial failures, and .detail for an API error.
Step 4: Display result
Interpret the response read in Step 3. Never show raw JSON to the user.
Success (status=removed, mode=revoke):
Removing {username} from {org_name}...
GitHub access: revoked
Membership: deactivated
Member record: marked as removed
{username} can no longer access this Egregore.
Their contributions are preserved in shared memory.Success (status=removed, mode=full):
Removing {username} from {org_name}...
GitHub access: revoked
Membership: deactivated
Sessions: deleted
Contributions: orphaned (artifacts kept)
Member profile: deleted
Telemetry: deleted
{username} has been fully removed from this Egregore.If errors array is non-empty, append:
Partial failures (non-fatal):
- {error1}
- {error2}API error (status is not removed):
Cannot remove {username}: {error}Common errors:
- "Only org admins or platform admins can remove members" → you need admin role
- "Cannot remove an admin. Change their role first." → target is an admin
- "No active membership found" → user isn't a member or already removed
Step 5: Telemetry (fire-and-forget)
bash bin/telemetry.sh emit "command" '{"command":"delete-user"}' 2>/dev/null &Rules
- Only org admins or platform admins can remove members — the API verifies this
- Cannot remove admins — they must be demoted first (future feature)
- Cannot remove yourself
- GitHub removal is best-effort — if the caller's token lacks repo admin scope, GitHub removal may fail but Supabase/Neo4j cleanup still proceeds
- Never expose tokens — all credential reads happen inside bash scripts
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

