Claude Cursor GitHub Copilot Skill

preset-admin

Manage Preset teams, workspaces, memberships, invites, role identifiers, seat checks, and audit logs through direct Management API calls. Use only for direct API workflows; Do not use for MCP-only work.

LLM Mart · 0 points · 2 views 257 listing impressions 0 install-command copies
Download preset-io-agent-skills-plugins_preset-api-skills_skills_preset-admin-73d2674.zip · 13 KB

Install

skills CLI npx skills add https://github.com/preset-io/agent-skills/tree/master/plugins/preset-api-skills/skills/preset-admin
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install preset-io-agent-skills@llmmart
Git git clone https://github.com/preset-io/agent-skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole preset-io/agent-skills collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

preset-admin

Use for Preset Management API administration beyond read-only workspace discovery.

Always

  • Auth and conventions come from preset-api (JWT exchange, base URLs, Rison); resolve the workspace hostname through the Management API when it is not already known.
  • Default to read-only preflight and ID/role lookup.
  • Resolve team, workspace, user, invite, and role identifiers from API responses before mutations.
  • Get explicit confirmation before role changes, invites, member removals, workspace lifecycle actions, audit downloads, or any write.
  • Use preset-roles-permissions for permission-sensitive role/access changes.

Decision Rules

  • Classify membership role and invite changes as approval-gated mutations.
  • Use metadata reads for membership, role, invite, and audit inspection.
  • Require target and effect summary before any access change.
  • Avoid applying invite or member role changes until approval is explicit.

Workflow Order

  1. Identify team, workspace, user, invite, member, and role identifiers.
  2. Inspect membership, role, invite, and audit metadata.
  3. Prepare approval summary with target and expected effect.
  4. Stop before invite, member role, removal, or workspace change.

Retrieve

Do Not

  • Do not use internal /api-internal/*, billing/payment, SCIM, API key CRUD, permission/DAR/RLS, or database connection mutation routes from this skill.
Files (agent-skills)
  • examples
    • team_memberships.py 1.1 KB
      Loading…
  • references
    • audit-logs.md 5.1 KB
      Loading…
    • deferrals.md 2.2 KB
      Loading…
    • invites.md 4.9 KB
      Loading…
    • role-identifiers.md 3.5 KB
      Loading…
    • team-member-access-changes.md 1.3 KB
      Loading…
    • team-member-lookup.md 1.6 KB
      Loading…
    • team-memberships.md 1.1 KB
      Loading…
    • workspace-management.md 7.8 KB
      Loading…
  • SKILL.md 2.5 KB
    ---
    name: preset-admin
    description: Manage Preset teams, workspaces, memberships, invites, role identifiers, seat checks, and audit logs through direct Management API calls. Use only for direct API workflows; Do not use for MCP-only work.
    ---
    
    # preset-admin
    
    Use for Preset Management API administration beyond read-only workspace discovery.
    
    ## Always
    
    - Auth and conventions come from `preset-api` (JWT exchange, base URLs, Rison); resolve the workspace hostname through the Management API when it is not already known.
    - Default to read-only preflight and ID/role lookup.
    - Resolve team, workspace, user, invite, and role identifiers from API responses before mutations.
    - Get explicit confirmation before role changes, invites, member removals, workspace lifecycle actions, audit downloads, or any write.
    - Use `preset-roles-permissions` for permission-sensitive role/access changes.
    
    ## Decision Rules
    
    - Classify membership role and invite changes as approval-gated mutations.
    - Use metadata reads for membership, role, invite, and audit inspection.
    - Require target and effect summary before any access change.
    - Avoid applying invite or member role changes until approval is explicit.
    
    ## Workflow Order
    
    1. Identify team, workspace, user, invite, member, and role identifiers.
    2. Inspect membership, role, invite, and audit metadata.
    3. Prepare approval summary with target and expected effect.
    4. Stop before invite, member role, removal, or workspace change.
    
    ## Retrieve
    
    - Team membership routing: [references/team-memberships.md](references/team-memberships.md)
    - Team member lookup, seat checks, response fields: [references/team-member-lookup.md](references/team-member-lookup.md)
    - Team role changes and removals: [references/team-member-access-changes.md](references/team-member-access-changes.md)
    - Workspace create/update/delete/un-hibernate: [references/workspace-management.md](references/workspace-management.md)
    - Invites, cancellation, resend, bulk invite: [references/invites.md](references/invites.md)
    - Audit log lookup and downloads: [references/audit-logs.md](references/audit-logs.md)
    - Role identifiers: [references/role-identifiers.md](references/role-identifiers.md)
    - Unsupported or adjacent Manager endpoints: [references/deferrals.md](references/deferrals.md)
    - Approval policy before writes/downloads: load `preset-api` and then `references/safety-policy.md`.
    
    ## Do Not
    
    - Do not use internal `/api-internal/*`, billing/payment, SCIM, API key CRUD, permission/DAR/RLS, or database connection mutation routes from this skill.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.