manage-known-users
Skill18 starsChanged 3 months agoMITView on GitHub
Add, edit, or remove humans and agents from the team directory (shared and per-agent known-users.json). Use when the user says "add user", "add a teammate", "remove user", "edit user", "manage known users", "register a person", or describes someone new on the team.
- Sends data out
In this repository9 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- create-agentSkill
- doctorSkill
- logsSkill
- manage-routinesSkill
- manage-work-hoursSkill
- setupSkill
- setup-watcherSkill
- update-frameworkSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 4 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 40
If the user said "add", go to Add.
- Very specific: line 48
If the user can't find the ID and you have any agent's slack_bot_token available, you can search:
- Distinctive: line 54
Don't proceed without a confirmed Slack ID.
- Very specific: line 62
Only follow up if (b): "Which agents?" — list available agent names from the agents/ directory.
- Distinctive: line 70
Don't ask for everything in one big question.
- Very specific: line 78
Use jq to merge into existing files without losing other entries.
- Very specific: line 82
When writing to agents/<n>/known-users.json for the first time:
- Distinctive: line 114
Don't leak personal info (phone, address) into known-users — keep entries professional.
≈ “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
Manage Known Users
The team directory has two layers, merged at runtime:
shared/known-users.json— visible to all agents (the default)agents/<n>/known-users.json— visible only to that agent (selective visibility)
Same Slack ID in both → local entry wins for that key only. Otherwise union.
Schema
{
"users": {
"U0XXXXXXXXX": {
"kind": "human",
"name": "Full Name",
"short_name": "First",
"title": "Founder",
"role": "founder",
"email": "person@example.com",
"responsibilities": "One-line summary of what this person owns",
"authority": "What instructions from this person count as authoritative",
"tone": "How agents should address this person"
}
}
}For agents, kind: "agent" plus channel: "C0… (#name)" instead of email.
role is freeform but agents key off it. Common values: founder, support-engineer, partner, customer, agent, unknown, external, bot.
Step 1 — Decide: add, edit, or remove?
If the user said "add", go to Add. "Remove" / "delete" → Remove. "Edit" / "change" / "update" → Edit. If unclear, ask.
Step 2 — Resolve the Slack ID
The user almost never knows their teammate's Slack member ID. Help them find it:
- In Slack, click the person's profile → ⋮ menu → "Copy member ID" (starts with
U). - Paste it here.
If the user can't find the ID and you have any agent's slack_bot_token available, you can search:
curl -s -X POST https://slack.com/api/users.list \
-H "Authorization: Bearer $TOKEN" | jq -r '.members[] | select(.profile.real_name | test("<name>"; "i")) | "\(.id) \(.profile.real_name) \(.profile.email // "no email")"'Don't proceed without a confirmed Slack ID.
Step 3 (Add) — Visibility tree
ONE question, with three options:
Should this person be visible to (a) all agents, (b) specific agents only, or (c) no agents (you're just registering them in shared but they shouldn't appear in any team directory)?
Only follow up if (b): "Which agents?" — list available agent names from the agents/ directory.
Step 4 (Add) — Gather fields
For humans: name, short_name, title, role, email, responsibilities, authority, tone.
For other agents: name, short_name, title, role: "agent", channel, responsibilities, authority.
Don't ask for everything in one big question; offer reasonable defaults based on context. Confirm the assembled record before writing.
Step 5 (Add) — Write to the right file(s)
- Visibility (a) → write to
shared/known-users.json - Visibility (b) → write to each chosen
agents/<n>/known-users.json(create the file if missing). Do NOT also write to shared. - Visibility (c) → write to
shared/known-users.jsonbut tell the user nothing renders this until at least one agent's local file references it.
Use jq to merge into existing files without losing other entries. Pretty-print on save.
Step 6 (Add) — Create per-agent file if needed
When writing to agents/<n>/known-users.json for the first time:
{ "users": {} }Then merge in the new entry.
Step 7 (Edit) — Find the entry
Show all matches across shared/ and per-agent files. Ask which one to edit. Re-prompt for fields with current values as defaults.
Step 8 (Remove) — Find and confirm
grep -l "U0XXXXXXXXX" shared/known-users.json agents/*/known-users.jsonConfirm with the user before removing — multiple agents may reference this person.
Step 9 — Restart listener
shared/known-users.json is loaded at listener startup; per-agent files are read on demand and cached. To pick up changes immediately:
pm2 restart ginnie-agents-listener --update-envTell the user the change is live.
Notes
- The
kindfield drives whether the entry shows up under "Humans" or "Agents" in the rendered team directory. - Don't leak personal info (phone, address) into known-users — keep entries professional.
- For agents, the
bot_user_id(fromagents/<n>/slack.json) IS the Slack ID to use as the key.
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.

