Agent skill · writing content · borghei
atlassian-templates
Create, modify, and govern reusable Jira and Confluence templates, blueprints, and standardized content structures. Use for org-wide templates, custom blueprints, page layouts, and automated content generation.
Why this skill is useful
Provides domain-specific knowledge on creating and managing reusable Jira and Confluence templates that the AI wouldn't reliably generate on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-07-21. 462 stars on the source repository.
What this skill does
Atlassian Template & Files Creator Expert Specialist in creating, modifying, and managing reusable templates and files for Jira and Confluence. Ensures consistency, accelerates content creation, and maintains org-wide standards through canonical, parameterized templates rather than per-use-case sprawl. Core Capabilities Template design — Confluence page templates with dynamic content, Jira issue templates/descriptions, blueprints for multi-page structures, versioning Content standardization — org-wide standards, reusable components and macros, template libraries, documentation Automation — dynamic fields, Jira integration, self-updating structures, template-based workflows Governance — lifecycle management, version control, deprecation, usage/adoption tracking When to Use Building org-wide Confluence page templates or Jira issue templates Designing blueprints for complex, multi-page content structures Establishing content standards and a curated template library Migrating teams off ad-hoc, from-scratch pages toward standardized templates Diagnosing low template adoption, broken macros, or version confusion Clarify First Before building the template, confirm these inputs. If any is unknown or vague, ASK — do not assume: [ ] Target tool & artifact — Confluence page template, Jira issue template, or multi-page blueprint (sets which macros/fields are available and the structure) [ ] Template type — meeting notes, PRD, charter, bug report, decision log, etc. (selects the base structure and placeholders) [ ] Rollout scope — one team vs org-wide canonical template (drives parameterization, naming, and governance) [ ] Dynamic vs static content — which fields auto-populate via macros/Jira queries vs fixed placeholders (drives build complexity and adoption) Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact. Quick Start 1. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills borghei/atlassian-templates