Manage Project Members

VerifiedCaution

List, invite, remove, or update roles for Workbench project members and collaborators, with input validation and mandatory explicit confirmation before write actions.

Sby Skills Guide Bot
ProductivityIntermediate
10/30/2026
Claude CodeCodex
#project-management#access-control#team-collaboration#permissions#workbench

Recommended for

Automated summary

This skill manages Workbench project members and collaborators by listing, adding, removing, or changing roles through a Python script.

Strengths

  • Enforces a preview plus explicit user confirmation before any write action (add, remove, update_role), requiring a separate turn before execution.
  • Explicitly blocks assigning or simulating the OWNER role and routes ownership-transfer requests to support.
  • Validates required inputs and points to helper scripts for resolving unknown project_id and employee_id values.
  • Delegates read-only permission questions to the share_and_permissions documentation instead of altering membership.

Limitations

  • Relies on external Workbench scripts (manage_project_members.py, show_project_overview.py, search_employees.py) being available in the environment.
  • Only two roles are assignable (CONTRIBUTOR, VIEWER); there is no ownership or custom-role handling.
  • Resolving an unknown employee name or project depends entirely on other skills, adding prerequisite steps.
When to use it

Use it when you actually need to inspect or change who belongs to a Workbench project and with which role.

When not to use it

Avoid it for questions about permission rules or project ownership, or for ownership transfers, which belong to the dedicated permissions doc or support.

Security analysis

Caution
Quality score80/100

The SKILL.md itself contains no destructive, exfiltrating, or obfuscated instructions and includes sensible safety guardrails (mandatory user confirmation, no OWNER assignment, input validation). However, it delegates real work to a Python script that is not provided for inspection and performs membership write operations, so it warrants caution rather than a clean 'safe' rating.

Findings
  • •Skill instructs execution of an external Python script (skills/workbench/manage_project_members/scripts/manage_project_members.py) whose contents are not included, so the actual behavior cannot be verified.
  • •Performs write/mutating actions (add, remove, update_role) against project membership, though mitigated by a mandatory preview-and-confirm step and an explicit prohibition on assigning/transferring OWNER.
  • •No allowed-tools are declared even though the skill requires shell execution of Python scripts, creating a mismatch between declared capabilities and required privileges.
  • •Declares no allowed-tools, yet its Execution block requires shell/Python invocation of skills/workbench/manage_project_members/scripts/manage_project_members.py plus auxiliary scripts (show_project_overview, search_employees) — the actual script bodies are not included, so their behavior (network calls, auth, scope of write) cannot be verified.
  • •Skill performs privileged write actions (add/remove members, role changes) on project data; safety depends entirely on the referenced script honoring the documented confirmation gate, which is unverifiable from this file.
How this analysis is made

Examples

List project members
Show me all members and their roles in the Workbench project "Apollo".
Invite a colleague as viewer
Add Maria Chen to project 3f2a9c1e-8b4d-4a7e-9c2f-1d6e5b8a0c33 as a VIEWER.
Change a member's role
Change employee 7c1d9e2a-4f3b-4c8d-a1e2-9b0f6d3c5a78 from CONTRIBUTOR to VIEWER in the Apollo project.

name: manage-project-members description: List, invite/add, remove, or update roles for project members and collaborators in Workbench. side_effect: write

Manage Project Members

Intent: manage-project-members

User request patterns

  • add member to project
  • invite employee to project
  • list project members
  • remove member from project
  • change member role

Retrieval tags

  • workbench
  • project-members
  • collaborators
  • add-member
  • remove-member
  • share-project

Instructions

  • For questions about Owner being absent from the Share dropdown or who can create sprints, read skills/workbench/share_and_permissions/SKILL.md and answer without changing membership.
  • Owner may appear in existing member data, but it is not an assignable Share option. Do not execute add or update_role with OWNER, or remove/re-add an Owner to simulate an ownership transfer. The script accepting an enum is not evidence of a supported ownership-transfer workflow. Explain this limitation and direct ownership-delegation requests to support for confirmed options.
  • Input Verification Rule:
    • project_id is required and must be a valid UUID (if unknown, run python skills/workbench/show_project_overview/scripts/show_project_overview.py to resolve project_id).
    • action: list (default), add (invite employee), remove (remove from project), or update_role.
    • employee_id: Required for add, remove, and update_role (if only employee name is known, run python skills/employee/search_employees/scripts/search_employees.py --name "<name>" to resolve employee_id).
    • role: CONTRIBUTOR (default) or VIEWER for invitations and role updates.
  • Mandatory User Confirmation & Turn Boundary (for write actions):
    • Adding, removing, or updating roles for project members are write actions. Before executing manage_project_members.py with add, remove, or update_role, ALWAYS present a preview:
      • Project: <project name>
      • Employee: <employee name>
      • Action / Role: <add as CONTRIBUTOR / remove / update role to VIEWER>
    • Ask the user: "Do you confirm [Action] for [Employee Name] in project '[Project Name]'?".
    • STOP and wait for explicit user confirmation (e.g. "yes", "confirm", "đồng ý") in a subsequent turn before executing. DO NOT execute the script in the same turn as presenting the preview.

Required arguments

  • project_id: UUID of the project.

Optional arguments

  • action: list | add | remove | update_role.
  • employee_id: UUID of the employee.
  • role: Assignable collaborator role (CONTRIBUTOR, VIEWER).

Execution

python skills/workbench/manage_project_members/scripts/manage_project_members.py --project-id <UUID> [--action <list|add|remove|update_role>] [--employee-id <UUID>] [--role <CONTRIBUTOR|VIEWER>]

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/manage-project-members-mvda886y/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/manage-project-members-mvda886y' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/manage-project-members-mvda886y/download' --output '.skill-downloads/manage-project-members-mvda886y/SKILL.md.part' && mv '.skill-downloads/manage-project-members-mvda886y/SKILL.md.part' '.skill-downloads/manage-project-members-mvda886y/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/manage-project-members-mvda886y/SKILL.md' && test -s '.skill-downloads/manage-project-members-mvda886y/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/manage-project-members' && cp -R '.skill-downloads/manage-project-members-mvda886y' '.claude/skills/manage-project-members'

Codex
test -f '.skill-downloads/manage-project-members-mvda886y/SKILL.md' && test -s '.skill-downloads/manage-project-members-mvda886y/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/manage-project-members' && cp -R '.skill-downloads/manage-project-members-mvda886y' '.agents/skills/manage-project-members'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/manage-project-members-mvda886y'

openskills read 'manage-project-members-mvda886y'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/manage-project-members-mvda886y/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills