Name: atlassian-admin
Rating: 71.2 (1 reviews)
Author: alirezarezvani

atlassian-admin

Atlassian Administrator for managing and organizing Atlassian products (Jira, Confluence, Bitbucket, Trello), users, permissions, security, integrations, system configuration, and org-wide governance. Use when asked to add users to Jira, change Confluence permissions, configure access control, update admin settings, manage Atlassian groups, set up SSO, install marketplace apps, review security policies, or handle any org-wide Atlassian administration task.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

The canonical home for this skill is atlassian-admin in alirezarezvani/claude-skills

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense, action-oriented reference skill with exemplary workflow sequencing and verification checkpoints; its main weakness is that broad governance and reference material is inlined in a single file rather than split into supporting reference files.

Suggestions

Move large reference blocks (Global Configuration, Governance & Policies, Disaster Recovery, Metrics & Reporting) into separate files under references/ and keep SKILL.md as an overview with one-level-deep links.

Tighten a few high-level workflow steps (e.g. 'Configure default permissions per group scheme') by citing the specific admin-console path or REST endpoint, as is done elsewhere.

Add the actual .mcp.json / references files referenced inline (e.g. project-management/references/atlassian-mcp-tools.md) so the signaled reference paths resolve to real bundle files.

Dimension	Reasoning	Score
Conciseness	Per-line content is lean and assumes Claude's competence — no concept explanations of what Jira/Confluence are — but the total inlined volume across governance, disaster recovery, and metrics sections is bulk that could partly live in reference files, pulling it just below the top anchor.	4 / 5
Actionability	Provides concrete UI navigation paths and real REST endpoints with payloads (e.g. 'POST /rest/api/3/user' with a JSON body) plus named MCP tools, though a few steps remain high-level ('Configure default permissions per group scheme').	4 / 5
Workflow Clarity	Every workflow is a numbered sequence with explicit verification checkpoints — 'VERIFY: Confirm ... active: false', 'CRITICAL: Audit user's owned content' — and destructive/batch operations (deprovisioning, permission schemes) include confirm-after steps, matching the top anchor.	5 / 5
Progressive Disclosure	Well-organized into clear sections with a single clearly-signaled one-level-deep reference ('project-management/references/atlassian-mcp-tools.md'), but no bundle files exist and substantial reference-grade material (global settings, disaster recovery, metrics) is inlined rather than split out.	4 / 5
	Total	17 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-scoped description that clearly answers both what the skill does and when to invoke it, with concrete trigger phrases and a distinct administrative niche. Slight room to broaden trigger synonyms, but otherwise exemplary.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete administrative actions — 'add users to Jira, change Confluence permissions, configure access control, update admin settings, manage Atlassian groups, set up SSO, install marketplace apps, review security policies' — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly states what the skill does ('managing and organizing Atlassian products... users, permissions, security, integrations, system configuration, and org-wide governance') and provides a concrete 'Use when asked to...' trigger clause enumerating real scenarios.	5 / 5
Trigger Term Quality	Includes natural user phrasings like 'add users to Jira', 'change Confluence permissions', 'set up SSO', and 'install marketplace apps'; coverage is strong but lacks some synonym/variation breadth that would reach the top anchor.	4 / 5
Distinctiveness Conflict Risk	Scoped to org-wide Atlassian administration with triggers (SSO, marketplace apps, admin settings, governance) that clearly distinguish it from per-product Jira/Confluence skills, minimizing conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: alirezarezvani/claude-skills
Path: .gemini/skills/atlassian-admin/SKILL.md
Commit: 19392f7

Reviewed: ~2 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.