preset-roles-permissions
Review Preset role, workspace membership, permission, access-control, DAR/RLS-adjacent, and effective-access changes through direct API calls. Use only for direct API workflows; Do not use for MCP-only work.
Install
npx skills add https://github.com/preset-io/agent-skills/tree/master/plugins/preset-api-skills/skills/preset-roles-permissions
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install preset-io-agent-skills@llmmart
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-roles-permissions
Use as the approval and access-review gate for permission-sensitive workflows.
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. - Use this skill alongside
preset-adminrole identifier and membership references for Management API role work. - Use
preset-supersetfor workspace current-user roles, permissions, and OpenAPI availability. - Treat role and permission changes as
permission_write. - Do not guess role IDs or custom role identifiers.
- Do not use internal
/api-internal/*, billing, SCIM, broad Superset security manager, or unsupported permission APIs from this skill; defer toreferences/role-permission-changes.md. - Require confirmation of target principal, current access, new access, seat impact, and rollback path.
Decision Rules
- Classify role and permission changes as access mutations.
- Resolve role identifiers before effect summary.
- Require approval with target and effect.
- Avoid applying role or permission changes until approval is explicit.
Workflow Order
- Inspect membership roles and permissions.
- Resolve target and role identifiers.
- Summarize access effect, seat impact, and rollback path.
- Stop before role or permission change.
Retrieve
- Role/permission mutation guidance and approval checks: references/role-permission-changes.md
- Approval policy: load
preset-apiand thenreferences/safety-policy.md.
Files (agent-skills)
-
references
-
role-permission-changes.md 1.7 KB
Loading…
-
-
SKILL.md 1.8 KB
--- name: preset-roles-permissions description: Review Preset role, workspace membership, permission, access-control, DAR/RLS-adjacent, and effective-access changes through direct API calls. Use only for direct API workflows; Do not use for MCP-only work. --- # preset-roles-permissions Use as the approval and access-review gate for permission-sensitive workflows. ## 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. - Use this skill alongside `preset-admin` role identifier and membership references for Management API role work. - Use `preset-superset` for workspace current-user roles, permissions, and OpenAPI availability. - Treat role and permission changes as `permission_write`. - Do not guess role IDs or custom role identifiers. - Do not use internal `/api-internal/*`, billing, SCIM, broad Superset security manager, or unsupported permission APIs from this skill; defer to `references/role-permission-changes.md`. - Require confirmation of target principal, current access, new access, seat impact, and rollback path. ## Decision Rules - Classify role and permission changes as access mutations. - Resolve role identifiers before effect summary. - Require approval with target and effect. - Avoid applying role or permission changes until approval is explicit. ## Workflow Order 1. Inspect membership roles and permissions. 2. Resolve target and role identifiers. 3. Summarize access effect, seat impact, and rollback path. 4. Stop before role or permission change. ## Retrieve - Role/permission mutation guidance and approval checks: [references/role-permission-changes.md](references/role-permission-changes.md) - Approval policy: load `preset-api` and then `references/safety-policy.md`.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.