Atlassian Admin
Design and document Jira/Atlassian project permission schemes, roles, and browse/transition permissions for a growing solo or small-team product org.
Overview
Atlassian Admin is an agent skill for the Operate phase that helps define Jira project permission schemes, roles, and permission grants for small teams.
Install
npx skills add https://github.com/alirezarezvani/claude-skills --skill atlassian-adminWhat is this skill?
- Structured permissionScheme JSON with name, description, version, and owner fields
- Four role tiers: projectAdmin, developer, user, and viewer with typical group mappings
- Granular project permissions including ADMINISTER_PROJECTS, BROWSE_PROJECTS, and VIEW_DEV_TOOLS
- Templates for standard vs read-only stakeholder and contractor access patterns
- Four defined project roles: projectAdmin, developer, user, viewer
Adoption & trust: 624 installs on skills.sh; 17.5k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your Jira project permissions are ad hoc and you need a clear scheme for admins, developers, users, and read-only stakeholders.
Who is it for?
Indie founders who run engineering in Jira and need consistent RBAC templates when adding contractors or cross-functional viewers.
Skip if: Teams not using Atlassian Cloud/Server, or builders who only need issue creation without permission governance.
When should I use this skill?
When configuring or revising Atlassian/Jira project permission schemes, role-to-group mappings, or standard vs stakeholder access policies.
What do I get? / Deliverables
You produce a documented permission scheme with roles, typical groups, and permission keys ready to apply or review in Atlassian administration.
- Permission scheme document with roles and grants
- Role-to-group mapping recommendations
- Read-only vs developer access policy outline
Recommended Skills
Journey fit
Atlassian administration is ongoing product operations after you are shipping, not initial product discovery. Iterate covers tuning project roles, permission schemes, and stakeholder access as the team and contractors change.
How it compares
Use as a permission-scheme template and policy reference skill, not as an automated Jira REST admin integration.
Common Questions / FAQ
Who is atlassian-admin for?
Solo builders and small teams operating Jira for engineering PM who need structured permission schemes and role definitions.
When should I use atlassian-admin?
During Operate when iterating on project access—new hires, contractors, or separating admin vs developer vs viewer capabilities.
Is atlassian-admin safe to install?
The skill provides configuration guidance; review the Security Audits panel on this page and never paste production admin tokens into agent chats.
SKILL.md
READMESKILL.md - Atlassian Admin
{ "permissionScheme": { "name": "Standard Project Permission Scheme", "description": "Default permission scheme for standard projects. Assigns permissions based on project roles.", "version": "1.0", "lastUpdated": "YYYY-MM-DD", "owner": "IT Admin Team" }, "roles": { "projectAdmin": { "description": "Full project administration including configuration and user management", "typicalGroups": ["project-leads", "engineering-managers"] }, "developer": { "description": "Create and manage issues, transitions, and attachments", "typicalGroups": ["dept-engineering", "dept-product"] }, "user": { "description": "View issues, add comments, and create basic issues", "typicalGroups": ["org-all-employees"] }, "viewer": { "description": "Read-only access to project issues and boards", "typicalGroups": ["stakeholders", "external-contractors"] } }, "permissions": { "project": { "ADMINISTER_PROJECTS": { "description": "Manage project settings, roles, and permissions", "grantedTo": ["projectAdmin"] }, "BROWSE_PROJECTS": { "description": "View the project and its issues", "grantedTo": ["projectAdmin", "developer", "user", "viewer"] }, "VIEW_DEV_TOOLS": { "description": "View development panel (commits, branches, PRs)", "grantedTo": ["projectAdmin", "developer"] }, "VIEW_READONLY_WORKFLOW": { "description": "View read-only workflow", "grantedTo": ["projectAdmin", "developer", "user", "viewer"] } }, "issues": { "CREATE_ISSUES": { "description": "Create new issues in the project", "grantedTo": ["projectAdmin", "developer", "user"] }, "EDIT_ISSUES": { "description": "Edit issue fields", "grantedTo": ["projectAdmin", "developer"] }, "DELETE_ISSUES": { "description": "Delete issues permanently", "grantedTo": ["projectAdmin"] }, "ASSIGN_ISSUES": { "description": "Assign issues to team members", "grantedTo": ["projectAdmin", "developer"] }, "ASSIGNABLE_USER": { "description": "Be assigned to issues", "grantedTo": ["projectAdmin", "developer"] }, "CLOSE_ISSUES": { "description": "Close/resolve issues", "grantedTo": ["projectAdmin", "developer"] }, "RESOLVE_ISSUES": { "description": "Set issue resolution", "grantedTo": ["projectAdmin", "developer"] }, "TRANSITION_ISSUES": { "description": "Transition issues through workflow", "grantedTo": ["projectAdmin", "developer", "user"] }, "LINK_ISSUES": { "description": "Create and remove issue links", "grantedTo": ["projectAdmin", "developer"] }, "MOVE_ISSUES": { "description": "Move issues between projects", "grantedTo": ["projectAdmin"] }, "SCHEDULE_ISSUES": { "description": "Set due dates on issues", "grantedTo": ["projectAdmin", "developer"] }, "SET_ISSUE_SECURITY": { "description": "Set security level on issues", "grantedTo": ["projectAdmin"] } }, "comments": { "ADD_COMMENTS": { "description": "Add comments to issues", "grantedTo": ["projectAdmin", "developer", "user"] }, "EDIT_ALL_COMMENTS": { "description": "Edit any comment", "grantedTo": ["projectAdmin"] }, "EDIT_OWN_COMMENTS": { "description": "Edit own comments", "grantedTo": ["projectAdmin", "developer", "user"] }, "DELETE_ALL_COMMENTS": { "description": "Delete any comment", "grantedTo": ["projectAdmin"] }, "DELETE_OWN_COMMENTS": { "description": "Delete own comments", "grantedTo": ["projectAdmin", "developer", "user"] } }, "attachments": {