agentleFS
lautioliverlautioliver/barrilete-kit/.claude/skills/remove-member/SKILL.md

remove-member

Skill6 starsChanged 7 days agoMITView on GitHub

Removes or pauses a team member so they stop getting issues assigned automatically. Use with "/remove-member @user", "take X off the team", "X is going on vacation".

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Remove or pause?: If it is temporary (vacation, another priority), pause: they stay on the team but get no new issues.

    line 8

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Remove a member

  1. Remove or pause? If it is temporary (vacation, another priority), pause: they stay on the team but get no new issues.
    python3 scripts/agents/team.py pause <login>    # or: activate <login>
    python3 scripts/agents/team.py remove <login>
  2. Their open issues stay assigned. List them (gh issue list --assignee <login> --state open) and ask whether to reassign them. To reassign each one to whoever fits according to the team:
    new=$(python3 scripts/agents/team.py suggest --labels "<the issue's labels, comma-separated>")
    gh issue edit <n> --remove-assignee <login> --add-assignee "$new"
    Show the list of reassignments and wait for a "yes" before applying it.
  3. Commit .github/team.json on a branch and open a PR.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.