什么是 Atlassian Template & Files Creator？

Atlassian Template & Files Creator 旨在简化组织处理文档和问题跟踪的方式。通过利用 Openclaw Skills，这个由智能体主导的工具管理模板的整个生命周期——从利益相关者发现到技术实施和全球部署。它弥补了手动内容创建与自动化的、宏驱动的文档之间的差距，确保项目章程、PRD 和会议记录在所有部门中保持一致。

对于希望在不增加行政开销的情况下强制执行高质量文档标准的团队来说，这项技能特别有价值。无论您是在构建自定义蓝图还是在 Jira 中更新字段配置，Openclaw Skills 都能提供必要的 MCP 集成，以大规模且精确地执行这些任务。

下载入口:https://github.com/openclaw/skills/tree/main/skills/alirezarezvani/atlassian-templates

安装与下载

1. ClawHub CLI

从源直接安装技能的最快方式。

2. 手动安装

将技能文件夹复制到以下位置之一

优先级：工作区 > 本地 > 内置

3. 提示词安装

将此提示词复制到 OpenClaw 即可自动安装。

Atlassian Template & Files Creator 应用场景

• 为新计划自动创建标准化的项目章程和 PRD。
• 在多个敏捷团队中扩展 Sprint 回顾格式，以确保一致的数据收集。
• 标准化用户故事和错误报告的 Jira 问题描述模板，以提高开发人员的清晰度。
• 使用 Openclaw Skills 通过批量模板部署实施组织范围的文档标准。

1. 分析利益相关者需求，以定义特定模板类型所需的结构、占位符和宏。
2. 使用 Confluence 存储格式 (Wiki Markup) 或 Jira 兼容的 Markdown/ADF 生成模板内容。
3. 执行 MCP 操作以在目标空间中创建或更新页面，并应用相关的标签和父级 ID。
4. 进行验证检查，以确保 {jira}、{tasks} 和 {status} 等宏在实时环境中正确渲染。
5. 通过更新现有模板并带有适当警告地存档过时版本来管理版本控制生命周期。

Atlassian Template & Files Creator 配置指南

要在您的环境中部署此技能，请确保您的 AI 智能体配置了 Atlassian MCP 服务器。在使用 Openclaw Skills 时，请使用以下环境变量对您的 Atlassian 实例进行身份验证。

# Set your Atlassian credentials
export CONFLUENCE_URL="https://your-domain.atlassian.net"
export JIRA_URL="https://your-domain.atlassian.net"
export ATLASSIAN_API_TOKEN="your-api-token-here"

配置完成后，智能体可以调用 confluence_create_page 或 jira_update_field_configuration 等工具来管理您的模板。

Atlassian Template & Files Creator 数据架构与分类体系

该技能使用特定的存储格式和元数据分类来管理内容，以确保与 Atlassian API 的兼容性。

name: "atlassian-templates"
description: 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.

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.

Workflows

Template Creation Process

1. Discover: Interview stakeholders to understand needs
2. Analyze: Review existing content patterns
3. Design: Create template structure and placeholders
4. Implement: Build template with macros and formatting
5. Test: Validate with sample data — confirm template renders correctly in preview before publishing
6. Document: Create usage instructions
7. Publish: Deploy to appropriate space/project via MCP (see MCP Operations below)
8. Verify: Confirm deployment success; roll back to previous version if errors occur
9. Train: Educate users on template usage
10. Monitor: Track adoption and gather feedback
11. Iterate: Refine based on usage

Template Modification Process

1. Assess: Review change request and impact
2. Version: Create new version, keep old available
3. Modify: Update template structure/content
4. Test: Validate changes don't break existing usage; preview updated template before publishing
5. Migrate: Provide migration path for existing content
6. Communicate: Announce changes to users
7. Support: Assist users with migration
8. Archive: Deprecate old version after transition; confirm deprecated template is unlisted, not deleted

Blueprint Development

1. Define blueprint scope and purpose
2. Design multi-page structure
3. Create page templates for each section
4. Configure page creation rules
5. Add dynamic content (Jira queries, user data)
6. Test blueprint creation flow end-to-end with a sample space
7. Verify all macro references resolve correctly before deployment
8. HANDOFF TO: Atlassian Admin for global deployment

Confluence Templates Library

See TEMPLATES.md for full reference tables and copy-paste-ready template structures. The following summarises the standard types this skill creates and maintains.

Confluence Template Types

Standard Sections included across all Confluence templates:

• Header panel with metadata (owner, date, status)
• Clearly labelled content sections with inline placeholder instructions
• Action items block using {tasks} macro
• Related links and references

Complete Example: Meeting Notes Template

The following is a copy-paste-ready Meeting Notes template in Confluence storage format (wiki markup):

{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}

Full examples for all other template types (Project Charter, Sprint Retrospective, PRD, Decision Log) and all Jira templates can be generated on request or found in TEMPLATES.md.

Jira Templates Library

Jira Template Types

Standard Sections included across all Jira templates:

• Clear summary line
• Acceptance or success criteria as checkboxes
• Related issues and dependencies block
• Definition of Done (for stories)

Macro Usage Guidelines

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

Atlassian MCP Integration

Primary Tools: Confluence MCP, Jira MCP

Template Operations via MCP

All MCP calls below use the exact parameter names expected by the Atlassian MCP server. Replace angle-bracket placeholders with real values before executing.

Create a Confluence page template:

{
  "tool": "confluence_create_page",
  "parameters": {
    "space_key": "PROJ",
    "title": "Template: Meeting Notes",
    "body": "",
    "labels": ["template", "meeting-notes"],
    "parent_id": ""
  }
}

Update an existing template:

{
  "tool": "confluence_update_page",
  "parameters": {
    "page_id": "",
    "version": "",
    "title": "Template: Meeting Notes",
    "body": "",
    "version_comment": "v2 — added status macro to header"
  }
}

Create a Jira issue description template (via field configuration):

{
  "tool": "jira_update_field_configuration",
  "parameters": {
    "project_key": "PROJ",
    "field_id": "description",
    "default_value": "