- name
Atlassian Template and Files Creator/Modifier expert for creating, modifying, and managing Jira and Confluence templates, blueprints, custom layouts, reusable components, and standardized content stru
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add alirezarezvani/claude-skills --skill atlassian-templates -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add alirezarezvani/claude-skills --skill atlassian-templates -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add alirezarezvani/claude-skills --skill atlassian-templates -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add alirezarezvani/claude-skills --skill atlassian-templates -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/alirezarezvani/claude-skills/tree/HEAD/.gemini/skills/atlassian-templatesFrom the publisher
Specialist in creating, modifying, and managing reusable templates and files for Jira and Confluence. Ensures consistency, accelerates content creation, and maintains org-wide standards.
See references/template-design-patterns.md for template design patterns and references/governance-framework.md for the governance model. For deployment-ready storage-format markup, use the bundled scaffolder (see Template scaffolder below). The following summarises the standard types this skill creates and maintains.
Standard Sections included across all Confluence templates:
{tasks} macroFormat warning: The example below is legacy wiki markup (
{panel},h2.,{tasks}), shown for human readability. Wiki markup is NOT Confluence storage format and will be rejected bymcp__atlassian__createConfluencePage/updateConfluencePage, which expect storage format (XHTML,<ac:structured-macro>elements) or ADF. To get the deployment-ready storage-format equivalent, run the scaffolder:python3 scripts/template_scaffolder.py meeting-notes(see Template scaffolder).
{panel:title=Meeting Metadata|borderColor=#0052CC|titleBGColor=#0052CC|titleColor=#FFFFFF}
*Date:* {date}
*Owner / Facilitator:* @[facilitator name]
*Attendees:* @[name], @[name]
*Status:* {status:colour=Yellow|title=In Progress}
{panel}
h2. Agenda
# [Agenda item 1]
# [Agenda item 2]
# [Agenda item 3]
h2. Discussion & Decisions
{panel:title=Key Decisions|borderColor=#36B37E|titleBGColor=#36B37E|titleColor=#FFFFFF}
* *Decision 1:* [What was decided and why]
* *Decision 2:* [What was decided and why]
{panel}
{info:title=Notes}
[Detailed discussion notes, context, or background here]
{info}
h2. Action Items
{tasks}
* [ ] [Action item] — Owner: @[name] — Due: {date}
* [ ] [Action item] — Owner: @[name] — Due: {date}
{tasks}
h2. Next Steps & Related Links
* Next meeting: {date}
* Related pages: [link]
* Related Jira issues: {jira:key=PROJ-123}
Storage-format examples for the other built-in types (decision-log, runbook, project-kickoff) come from
python3 scripts/template_scaffolder.py --list; design patterns for the remaining types (Project Charter, Sprint Retrospective, PRD) are inreferences/template-design-patterns.md.
Standard Sections included across all Jira templates:
Dynamic Content: Use macros for auto-updating content (dates, user mentions, Jira queries)
Visual Hierarchy: Use {panel}, {info}, and {note} to create visual distinction
Interactivity: Use {expand} for collapsible sections in long templates
Integration: Embed Jira charts and tables via {jira} macro for live data
The bundled scaffolder emits Confluence storage-format XHTML — the exact body format createConfluencePage/updateConfluencePage accept. It is the canonical deployment path for this skill:
# List available template types (meeting-notes, decision-log, runbook, project-kickoff, custom)
python3 scripts/template_scaffolder.py --list
# Generate a template body (storage-format XHTML)
python3 scripts/template_scaffolder.py meeting-notes
# Custom template with chosen sections and macros, JSON output for programmatic use
python3 scripts/template_scaffolder.py custom --sections "Overview,Goals,Action Items" --macros "toc,status,info" --format json
Consume the output: take the CONFLUENCE STORAGE FORMAT MARKUP block (text mode) or the markup field (JSON mode) and pass it verbatim as the body of mcp__atlassian__createConfluencePage. Apply the suggested labels via the Confluence UI afterwards (label tools are not on the MCP).
Primary Tool: Atlassian Remote MCP server (bundled .mcp.json, server key atlassian). Tools surface as mcp__atlassian__<toolName> (camelCase). Canonical tool list: project-management/references/atlassian-mcp-tools.md. Never invent tool names — if a capability isn't in that list, it is not available via MCP; route to the web UI or REST API.
Obtain cloudId once via mcp__atlassian__getAccessibleAtlassianResources. Replace angle-bracket placeholders with real values; discover exact parameter names from each tool's schema at call time.
Create a Confluence template page (body from the scaffolder above):
mcp__atlassian__createConfluencePage (cloudId, space, title="Template: Meeting Notes",
body=<storage-format XHTML from template_scaffolder.py>, parent page id optional)
Labels (template, meeting-notes) must be applied in the Confluence UI — there is no MCP label tool.
Update an existing template page (read first to get the current version):
mcp__atlassian__getConfluencePage (cloudId, pageId=<existing page id>)
mcp__atlassian__updateConfluencePage (cloudId, pageId=<id>, version=<current + 1>,
body=<updated storage-format content>)
Jira issue description templates: there is no MCP tool for field configuration (default_value on the description field, screens, field contexts). Configure description defaults in the Jira admin UI (Settings > Issues > Field configurations) or via REST (/rest/api/3/fieldconfiguration). What MCP CAN do: create issues pre-filled with template text via mcp__atlassian__createJiraIssue (pass the template body as the description), and inspect required fields per issue type with mcp__atlassian__getJiraIssueTypeMetaWithFields.
First-class Confluence templates/blueprints are also not creatable via MCP — createConfluencePage creates ordinary pages that serve as copy-from templates. To register a real space template, use Space settings > Templates in the UI.
Deploy a template page to multiple spaces (batch):
# Repeat per target space:
mcp__atlassian__createConfluencePage (cloudId, space=<target>, title="Template: Meeting Notes", body=<storage-format content>)
# Verify each create before proceeding:
mcp__atlassian__getConfluencePage (cloudId, pageId=<id returned by create>)
# Assert the returned body is non-empty and contains the expected <ac:structured-macro> elements
Validation checkpoint after deployment:
mcp__atlassian__getConfluencePage and assert it renders without macro errorsmcp__atlassian__updateConfluencePage with version: <current + 1> and the previous version bodyOrg-Specific Standards:
{warning} banner before archiving; archive (do not delete)Quality Gates (apply before every deployment):
Governance Process:
Handoff summary (governance context in references/governance-framework.md):
© 2026 Skills Rack.
---name: atlassian-templatesdescription: Atlassian Template and Files Creator/Modifier expert for creating, modifying, and managing Jira and Confluence…---# .gemini/skills/atlassian-templates/SKILL.mdOverview
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.
FAQ
Download .gemini/skills/atlassian-templates/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/alirezarezvani/claude-skills.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.