Name: atlassian-templates
Rating: 55.2 (1 reviews)
Author: alirezarezvani

atlassian-templates

Atlassian Template and Files Creator/Modifier expert for creating, modifying, and managing Jira and Confluence templates, blueprints, custom layouts, reusable components, and standardized content structures. Use when building org-wide templates, custom blueprints, page layouts, and automated content generation.

Quality

63%

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

Fix and improve this skill with Tessl

tessl review fix ./.gemini/skills/atlassian-templates/SKILL.md

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

Quality

Content

62%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.

The content is well-organized, action-oriented, and rich in Atlassian-specific operational detail with strong validation checkpoints in its deployment workflows. Its main weakness is progressive disclosure: the body points to multiple bundled reference/script files that are not present, leaving the navigation structure unverifiable and incomplete.

Suggestions

Bundle the referenced files (`references/template-design-patterns.md`, `references/governance-framework.md`, `scripts/template_scaffolder.py`, `project-management/references/atlassian-mcp-tools.md`) or remove the references so navigation is real and verifiable.

Consider moving the legacy wiki-markup Meeting Notes example into `references/template-design-patterns.md` and keeping only the scaffolder-based storage-format path inline to reduce token weight.

Add explicit link syntax (e.g., `[Template design patterns](references/template-design-patterns.md)`) so the references are clearly signaled rather than backtick-mentioned in prose.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and focused on Atlassian-specific details Claude would not already know (storage format vs wiki markup, MCP tool constraints), but the Meeting Notes legacy-markup example and some process lists add length that could be trimmed without losing value.	3 / 5
Actionability	It provides concrete, executable guidance — real scaffolder commands (`python3 scripts/template_scaffolder.py meeting-notes`), explicit MCP tool calls with parameters, and clear gotchas about non-MCP capabilities — with only minor gaps around exact parameter names.	4 / 5
Workflow Clarity	Multi-step processes are clearly sequenced with validation checkpoints ('preview before publishing', 'Verify each create before proceeding', a dedicated validation checkpoint with rollback), though a few checklist steps remain implicit.	4 / 5
Progressive Disclosure	The body references external files (`references/template-design-patterns.md`, `references/governance-framework.md`, `scripts/template_scaffolder.py`, `project-management/references/atlassian-mcp-tools.md`), but no referenced bundle files actually exist in the skill directory, so the signaling cannot be verified and the structure is incomplete.	3 / 5
	Total	14 / 20 Passed

Description

63%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.

The description is clear and trigger-driven with concrete capability nouns and an explicit 'Use when' clause, placing it above the midpoint. It is held below a 5 by generic verbs and limited synonym/extension coverage in the trigger terms.

Suggestions

Add natural trigger synonyms users would actually say (e.g., 'meeting notes template', 'retro template', 'PRD template', 'issue templates') to broaden trigger coverage.

Replace generic verbs ('creating, modifying, managing') with more specific actions like 'generate storage-format templates', 'scaffold', or 'deploy' to raise specificity.

Tighten the 'when' clause to reference concrete user requests (e.g., 'Use when the user asks to set up reusable Jira/Confluence page or issue templates').

Dimension	Reasoning	Score
Specificity	Names concrete actions ('creating, modifying, and managing' templates, blueprints, custom layouts, reusable components, standardized content structures) across several distinct objects, though the verbs are somewhat generic across the listed nouns.	4 / 5
Completeness	It clearly states the 'what' and includes an explicit 'Use when building org-wide templates, custom blueprints, page layouts, and automated content generation' clause, though the 'when' could be slightly more specific to user requests.	4 / 5
Trigger Term Quality	It includes relevant terms ('Jira and Confluence templates', 'blueprints', 'page layouts') but omits common user-facing synonyms and file/extension variations a user would naturally say.	3 / 5
Distinctiveness Conflict Risk	The Atlassian/Jira/Confluence template niche is fairly distinct with specific triggers, with only minor overlap risk against general Confluence or Jira admin skills.	4 / 5
	Total	15 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 9 missing	Warning

	Total	15 / 16 Passed

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

Reviewed: ~3 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.