#800 by GitHub stars
atlassian/atlassian-mcp-server
Official remote MCP server for Atlassian. Securely connect Jira, Confluence, Jira Service Management, Bitbucket, and Compass to Claude, ChatGPT, Cursor, VS Code, and other AI tools using OAuth 2.1 or API tokens.
History
Review weekly changes to SKILL.md before updating. Dates mark the weeks in which we observed each version; checks apply to the recorded commits.
View weekly changes
skills/atlassian-mcp-code-search/SKILL.md
Week of Nov 2, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 37e57a78b193
No earlier version was observed for comparison.
skills/capture-tasks-from-meeting-notes/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Not checked yet → After Network or broad shell
b74220d41142 → 37e57a78b193
Diff text is unavailable under the recorded licenses. Line counts and the GitHub link remain available.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Not checked yet
First observation → b74220d41142
No earlier version was observed for comparison.
skills/generate-status-report/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Not checked yet → After Network or broad shell
b74220d41142 → 37e57a78b193
Diff text is unavailable under the recorded licenses. Line counts and the GitHub link remain available.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Not checked yet
First observation → b74220d41142
No earlier version was observed for comparison.
skills/jira-sprint-dashboard/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Not checked yet → After Network or broad shell
b74220d41142 → 37e57a78b193
Diff text is unavailable under the recorded licenses. Line counts and the GitHub link remain available.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Not checked yet
First observation → b74220d41142
No earlier version was observed for comparison.
skills/search-company-knowledge/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Not checked yet → After Network or broad shell
b74220d41142 → 37e57a78b193
Diff text is unavailable under the recorded licenses. Line counts and the GitHub link remain available.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Not checked yet
First observation → b74220d41142
No earlier version was observed for comparison.
skills/spec-to-backlog/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Not checked yet → After Network or broad shell
b74220d41142 → 37e57a78b193
Diff text is unavailable under the recorded licenses. Line counts and the GitHub link remain available.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Not checked yet
First observation → b74220d41142
No earlier version was observed for comparison.
skills/triage-issue/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Not checked yet → After Network or broad shell
b74220d41142 → 37e57a78b193
Diff text is unavailable under the recorded licenses. Line counts and the GitHub link remain available.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Not checked yet
First observation → b74220d41142
No earlier version was observed for comparison.
skills/v1/capture-tasks-from-meeting-notes/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Not checked yet → After Network or broad shell
b74220d41142 → 37e57a78b193
Diff text is unavailable under the recorded licenses. Line counts and the GitHub link remain available.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Not checked yet
First observation → b74220d41142
No earlier version was observed for comparison.
skills/v1/generate-status-report/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Not checked yet → After Network or broad shell
b74220d41142 → 37e57a78b193
Diff text is unavailable under the recorded licenses. Line counts and the GitHub link remain available.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Not checked yet
First observation → b74220d41142
No earlier version was observed for comparison.
skills/v1/jira-sprint-dashboard/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Not checked yet → After Network or broad shell
b74220d41142 → 37e57a78b193
Diff text is unavailable under the recorded licenses. Line counts and the GitHub link remain available.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Not checked yet
First observation → b74220d41142
No earlier version was observed for comparison.
skills/v1/search-company-knowledge/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Not checked yet → After Network or broad shell
b74220d41142 → 37e57a78b193
Diff text is unavailable under the recorded licenses. Line counts and the GitHub link remain available.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Not checked yet
First observation → b74220d41142
No earlier version was observed for comparison.
skills/v1/spec-to-backlog/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Not checked yet → After Network or broad shell
b74220d41142 → 37e57a78b193
Diff text is unavailable under the recorded licenses. Line counts and the GitHub link remain available.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Not checked yet
First observation → b74220d41142
No earlier version was observed for comparison.
skills/v1/triage-issue/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Not checked yet → After Network or broad shell
b74220d41142 → 37e57a78b193
Diff text is unavailable under the recorded licenses. Line counts and the GitHub link remain available.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Not checked yet
First observation → b74220d41142
No earlier version was observed for comparison.
View on GitHubAdd to my skills
Verified commit 37e57a78b1938a099d1dcffdfc5a61154068c15e
git clone --filter=blob:none --no-checkout https://github.com/atlassian/atlassian-mcp-server.git .hotskills/atlassian-atlassian-mcp-server && git -C .hotskills/atlassian-atlassian-mcp-server checkout --detach 37e57a78b1938a099d1dcffdfc5a61154068c15e
# Copy each selected skill directory from .hotskills/atlassian-atlassian-mcp-server into .claude/skills/<skill-name>/git clone --filter=blob:none --no-checkout https://github.com/atlassian/atlassian-mcp-server.git .hotskills/atlassian-atlassian-mcp-server && git -C .hotskills/atlassian-atlassian-mcp-server checkout --detach 37e57a78b1938a099d1dcffdfc5a61154068c15e
# Copy each selected skill directory from .hotskills/atlassian-atlassian-mcp-server into .gemini/skills/<skill-name>/1.1kGitHub stars
10stars in 7 days
13skills in this repository
4commits in 30 days
Heat
5.5- Star growth, last 7 daysAhead of 81% of tracked repositories
- Star growth, last 24 hoursAhead of 71% of tracked repositories
- Rank movement, last 7 daysAhead of 17% of tracked repositories
- Commits, last 30 daysAhead of 67% of tracked repositories
- Accounts asking about it through MCP, last 7 daysNot available
- Hot votes this weekAhead of 0% of tracked repositories
Heat never changes the order by stars, and sponsorship never touches it. How heat works
Stars over time
Individual skills in this repository
- atlassian-mcp-code-search
skills/atlassian-mcp-code-search - capture-tasks-from-meeting-notes
skills/capture-tasks-from-meeting-notes - generate-status-report
skills/generate-status-report - jira-sprint-dashboard
skills/jira-sprint-dashboard - search-company-knowledge
skills/search-company-knowledge - spec-to-backlog
skills/spec-to-backlog - triage-issue
skills/triage-issue - capture-tasks-from-meeting-notes
skills/v1/capture-tasks-from-meeting-notes - generate-status-report
skills/v1/generate-status-report - jira-sprint-dashboard
skills/v1/jira-sprint-dashboard - search-company-knowledge
skills/v1/search-company-knowledge - spec-to-backlog
skills/v1/spec-to-backlog - triage-issue
skills/v1/triage-issue
How it works
atlassian-mcp-code-search
When your agent uses it
Find source, callers, and API consumers outside the local workspace using the Atlassian MCP code search operations (searchCode, getCodeFile, scanCodeRepo, listCodeDirectory). Use whenever an answer needs code that is not checked out locally, even without an explicit search request or a known repository.
What it loads into context
Frontmatter
80 tokensAlways available to the agent
SKILL.md
1,264 tokensWhen the skill is activated
Reference documents
77,020 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- When To Use
- Operations
- Search And Navigate
- Reverse Dependencies
- Efficiency
- Reporting
Scripts executed separately
../generate-status-report/scripts/jql_builder.py../v1/generate-status-report/scripts/jql_builder.py
Files
../../.claude-plugin/marketplace.jsonasset818 bytes../../.claude-plugin/plugin.jsonasset382 bytes../../.mcp.jsonasset121 bytes../README.mddoc2,250 bytesSKILL.mdcore5,882 bytesSKILL.mdcore5,882 bytesSKILL.mdcore5,882 bytesSKILL.mdcore5,882 bytesSKILL.mdcore5,882 bytes../capture-tasks-from-meeting-notes/SKILL.mddoc17,609 bytes../capture-tasks-from-meeting-notes/references/action-item-patterns.mddoc7,358 bytes../generate-status-report/SKILL.mddoc16,527 bytes../generate-status-report/references/jql-patterns.mddoc1,780 bytes../generate-status-report/references/report-templates.mddoc2,556 bytes../generate-status-report/scripts/jql_builder.pyruns6,596 bytes../jira-sprint-dashboard/SKILL.mddoc16,236 bytes../search-company-knowledge/SKILL.mddoc17,905 bytes../spec-to-backlog/SKILL.mddoc20,094 bytes../spec-to-backlog/references/breakdown-examples.mddoc9,573 bytes../spec-to-backlog/references/epic-templates.mddoc12,106 bytes../spec-to-backlog/references/ticket-writing-guide.mddoc9,854 bytes../triage-issue/SKILL.mddoc21,427 bytes../triage-issue/references/bug-report-templates.mddoc9,960 bytes../triage-issue/references/search-patterns.mddoc6,211 bytes../v1/capture-tasks-from-meeting-notes/SKILL.mddoc15,039 bytes../v1/capture-tasks-from-meeting-notes/references/action-item-patterns.mddoc7,358 bytes../v1/generate-status-report/SKILL.mddoc11,312 bytes../v1/generate-status-report/references/jql-patterns.mddoc1,780 bytes../v1/generate-status-report/references/report-templates.mddoc2,556 bytes../v1/generate-status-report/scripts/jql_builder.pyruns6,596 bytes../v1/jira-sprint-dashboard/SKILL.mddoc15,469 bytes../v1/search-company-knowledge/SKILL.mddoc17,081 bytes../v1/spec-to-backlog/SKILL.mddoc17,432 bytes../v1/spec-to-backlog/references/breakdown-examples.mddoc9,573 bytes../v1/spec-to-backlog/references/epic-templates.mddoc12,106 bytes../v1/spec-to-backlog/references/ticket-writing-guide.mddoc9,854 bytes../v1/triage-issue/SKILL.mddoc19,379 bytes../v1/triage-issue/references/bug-report-templates.mddoc9,960 bytes../v1/triage-issue/references/search-patterns.mddoc6,211 bytes
Read SKILL.md
# Code Search And Navigation With The Atlassian MCP
Adapted from the TWG CLI `code-search.md` reference, for agents that reach code
search through the Atlassian MCP server instead of `twg search-code`.
## When To Use
Use this when an answer needs source unavailable locally, including follow-up
questions without an explicit search request. Start from the known service,
behavior, error, API, or symbol; discover the repository if unknown. Verify
implementation claims against source. Skip when local code, supplied context,
or general knowledge answers the question.
The Atlassian MCP covers code as well as Jira and Confluence. In the default v2capture-tasks-from-meeting-notes
When your agent uses it
Analyze meeting notes to find action items and create Jira tasks for assigned work. When an agent needs to: (1) Create Jira tasks or tickets from meeting notes, (2) Extract or find action items from notes or Confluence pages, (3) Parse meeting notes for assigned tasks, or (4) Analyze notes and generate tasks for team members. Identifies assignees, looks up account IDs, and creates tasks with proper context.
What it loads into context
Frontmatter
103 tokensAlways available to the agent
SKILL.md
4,404 tokensWhen the skill is activated
Reference documents
1,902 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Keywords
- Overview
- Workflow
- Action Item Pattern Examples
- Handling Edge Cases
- Tips for High-Quality Results
- When NOT to Use This Skill
- Examples
- Quick Reference
- Calling non-primary tools
Files
SKILL.mdcore17,609 bytesreferences/action-item-patterns.mddoc7,358 bytes
Read SKILL.md
# Capture Tasks from Meeting Notes
## Keywords
meeting notes, action items, create tasks, create tickets, extract tasks, parse notes, analyze notes, assigned work, assignees, from meeting, post-meeting, capture tasks, generate tasks, turn into tasks, convert to tasks, action item, to-do, task list, follow-up, assigned to, create Jira tasks, create Jira tickets, meeting action items, extract action items, find action items, analyze meeting
## Overview
Automatically extract action items from meeting notes and create Jira tasks with proper assignees. This skill parses unstructured meeting notes (from Confluence or pasted text), identifies action items with assignees, looks up Jira account IDs, and creates tasks—eliminating the tedious post-meeting ticket creation process.
**Use this skill when:** Users have meeting notes with action items that need to become Jira tasks.
---
## Workflowgenerate-status-report
When your agent uses it
Generate project status reports from Jira issues and publish to Confluence. When an agent needs to: (1) Create a status report for a project, (2) Summarize project progress or updates, (3) Generate weekly/daily reports from Jira, (4) Publish status summaries to Confluence, or (5) Analyze project blockers and completion. Queries Jira issues, categorizes by status/priority, and creates formatted reports for delivery managers and executives.
What it loads into context
Frontmatter
102 tokensAlways available to the agent
SKILL.md
3,867 tokensWhen the skill is activated
Reference documents
1,134 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Keywords
- Workflow
- Step 1: Identify Scope
- Step 2: Query Jira
- Step 3: Analyze Data
- Step 4: Format Report
- Step 5: Publish to Confluence
- Complete Example Workflow
- Tips for Quality Reports
- Resources
- Calling non-primary tools
Scripts executed separately
scripts/jql_builder.py
Files
SKILL.mdcore16,527 bytesSKILL.mdcore16,527 bytesSKILL.mdcore16,527 bytesreferences/jql-patterns.mddoc1,780 bytesreferences/report-templates.mddoc2,556 bytesscripts/jql_builder.pyruns6,596 bytes
Read SKILL.md
# Generate Status Report
## Keywords
status report, project status, weekly update, daily standup, Jira report, project summary, blockers, progress update, Confluence report, sprint report, project update, publish to Confluence, write to Confluence, post report
Automatically query Jira for project status, analyze issues, and generate formatted status reports published to Confluence.
**CRITICAL**: This skill should be **interactive**. Always clarify scope (time period, audience, Confluence destination) with the user before or after generating the report. Do not silently skip Confluence publishing—always offer it.
## Workflow
Generating a status report follows these steps:
1. **Identify scope** - Determine project, time period, and target audiencejira-sprint-dashboard
When your agent uses it
Create a visual Jira sprint dashboard from Jira project, space, sprint, board, filter, JQL, work item keys, or Jira URL data. Use when the user asks for a Jira sprint dashboard, standup dashboard, sprint review, delivery review, engineering manager dashboard, WIP review, planning view, closeout view, or a visual snapshot of Jira work that is more useful than a flat report. Use the richest dashboard format supported by the current agent, such as Cursor Canvas, an interactive artifact, HTML, or Markdown.
What it loads into context
Frontmatter
129 tokensAlways available to the agent
SKILL.md
3,533 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Output Mode
- Cursor Canvas Renderer
- Portable Renderers
- Get The Scope
- Query Jira
- Normalize
- Dashboard Model
- Dashboard Shape
- Content And Style
- Renderer-Specific Style
- Self-Check
Files
SKILL.mdcore16,236 bytesSKILL.mdcore16,236 bytesSKILL.mdcore16,236 bytesSKILL.mdcore16,236 bytesSKILL.mdcore16,236 bytesSKILL.mdcore16,236 bytesSKILL.mdcore16,236 bytesSKILL.mdcore16,236 bytesSKILL.mdcore16,236 bytes
Read SKILL.md
# Jira Sprint Dashboard
Build a focused dashboard that helps an engineering manager, tech lead, or
senior engineer see current Jira work quickly enough to decide what needs
attention. The output is a dashboard, not a prose report and not a generic
health score.
This skill is read-only by default. Do not create, update, transition, assign,
or comment on Jira work items unless the user explicitly asks for a write action
after reviewing the dashboard.
## Output Mode
Use the richest dashboard renderer supported by the current environment. Thesearch-company-knowledge
When your agent uses it
Search across company knowledge bases (Confluence, Jira, internal docs) to find and explain internal concepts, processes, and technical details. When an agent needs to: (1) Find or search for information about systems, terminology, processes, deployment, authentication, infrastructure, architecture, or technical concepts, (2) Search internal documentation, knowledge base, company docs, or our docs, (3) Explain what something is, how it works, or look up information, or (4) Synthesize information from multiple sources. Searches in parallel and provides cited answers.
What it loads into context
Frontmatter
123 tokensAlways available to the agent
SKILL.md
4,074 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Keywords
- Overview
- Workflow
- Search Best Practices
- Handling Common Scenarios
- Examples
- Tips for High-Quality Answers
- When NOT to Use This Skill
- Quick Reference
Files
SKILL.mdcore17,905 bytesSKILL.mdcore17,905 bytesSKILL.mdcore17,905 bytes
Read SKILL.md
# Search Company Knowledge
## Keywords
find information, search company knowledge, look up, what is, explain, company docs, internal documentation, Confluence search, Jira search, our documentation, internal knowledge, knowledge base, search for, tell me about, get information about, company systems, terminology, find everything about, what do we know about, deployment, authentication, infrastructure, processes, procedures, how to, how does, our systems, our processes, internal systems, company processes, technical documentation, engineering docs, architecture, configuration, search our docs, search internal docs, find in our docs
## Overview
Search across siloed company knowledge systems (Confluence, Jira, internal documentation) to find comprehensive answers to questions about internal concepts, systems, and terminology. This skill performs parallel searches across multiple sources and synthesizes results with proper citations.
**Use this skill when:** Users ask about internal company knowledge that might be documented in Confluence pages, Jira tickets, or internal documentation.
---
## Workflowspec-to-backlog
When your agent uses it
Automatically convert Confluence specification documents into structured Jira backlogs with Epics and implementation tickets. When an agent needs to: (1) Create Jira tickets from a Confluence page, (2) Generate a backlog from a specification, (3) Break down a spec into implementation tasks, or (4) Convert requirements into Jira issues. Handles reading Confluence pages, analyzing specifications, creating Epics with proper structure, and generating detailed implementation tickets linked to the Epic.
What it loads into context
Frontmatter
103 tokensAlways available to the agent
SKILL.md
4,724 tokensWhen the skill is activated
Reference documents
7,022 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Overview
- Core Workflow
- Step 1: Fetch Confluence Page
- Step 2: Ask for Project Key
- Step 3: Analyze Specification
- Step 4: Present Breakdown to User
- Step 5: Create Epic FIRST
- Step 6: Create Child Tickets
- Step 7: Provide Summary
- Edge Cases & Troubleshooting
- Tips for High-Quality Breakdowns
- Examples of Good Breakdowns
- Calling non-primary tools
Files
SKILL.mdcore20,094 bytesreferences/breakdown-examples.mddoc9,573 bytesreferences/epic-templates.mddoc12,106 bytesreferences/ticket-writing-guide.mddoc9,854 bytes
Read SKILL.md
# Spec to Backlog
## Overview
Transform Confluence specification documents into structured Jira backlogs automatically. This skill reads requirement documents from Confluence, intelligently breaks them down into logical implementation tasks, **creates an Epic first** to organize the work, then generates individual Jira tickets linked to that Epic—eliminating tedious manual copy-pasting.
## Core Workflow
**CRITICAL: Always follow this exact sequence:**
1. **Fetch Confluence Page** → Get the specification content
2. **Ask for Project Key** → Identify target Jira project
3. **Analyze Specification** → Break down into logical tasks (internally, don't create yet)
4. **Present Breakdown** → Show user the planned Epic and ticketstriage-issue
When your agent uses it
Intelligently triage bug reports and error messages by searching for duplicates in Jira and offering to create new issues or add comments to existing ones. When an agent needs to: (1) Triage a bug report or error message, (2) Check if an issue is a duplicate, (3) Find similar past issues, (4) Create a new bug ticket with proper context, or (5) Add information to an existing ticket. Searches Jira for similar issues, identifies duplicates, checks fix history, and helps create well-structured bug reports.
What it loads into context
Frontmatter
121 tokensAlways available to the agent
SKILL.md
5,193 tokensWhen the skill is activated
Reference documents
4,059 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Keywords
- Overview
- Workflow
- Edge Cases & Troubleshooting
- Tips for Effective Triage
- Examples
- When NOT to Use This Skill
- Quick Reference
- Calling non-primary tools
Files
SKILL.mdcore21,427 bytesreferences/bug-report-templates.mddoc9,960 bytesreferences/search-patterns.mddoc6,211 bytes
Read SKILL.md
# Triage Issue
## Keywords
triage bug, check duplicate, is this a duplicate, search for similar issues, create bug ticket, file a bug, report this error, triage this error, bug report, error message, similar issues, duplicate bug, who fixed this, has this been reported, search bugs, find similar bugs, create issue, file issue
## Overview
Automatically triage bug reports and error messages by searching Jira for duplicates, identifying similar past issues, and helping create well-structured bug tickets or add context to existing issues. This skill eliminates manual duplicate checking and ensures bugs are properly documented with relevant historical context.
**Use this skill when:** Users need to triage error messages, bug reports, or issues to determine if they're duplicates and take appropriate action.
---
## Workflowcapture-tasks-from-meeting-notes
When your agent uses it
Analyze meeting notes to find action items and create Jira tasks for assigned work. When an agent needs to: (1) Create Jira tasks or tickets from meeting notes, (2) Extract or find action items from notes or Confluence pages, (3) Parse meeting notes for assigned tasks, or (4) Analyze notes and generate tasks for team members. Identifies assignees, looks up account IDs, and creates tasks with proper context.
What it loads into context
Frontmatter
103 tokensAlways available to the agent
SKILL.md
3,792 tokensWhen the skill is activated
Reference documents
1,902 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Keywords
- Overview
- Workflow
- Action Item Pattern Examples
- Handling Edge Cases
- Tips for High-Quality Results
- When NOT to Use This Skill
- Examples
- Quick Reference
Files
SKILL.mdcore15,039 bytesreferences/action-item-patterns.mddoc7,358 bytes
Read SKILL.md
# Capture Tasks from Meeting Notes
## Keywords
meeting notes, action items, create tasks, create tickets, extract tasks, parse notes, analyze notes, assigned work, assignees, from meeting, post-meeting, capture tasks, generate tasks, turn into tasks, convert to tasks, action item, to-do, task list, follow-up, assigned to, create Jira tasks, create Jira tickets, meeting action items, extract action items, find action items, analyze meeting
## Overview
Automatically extract action items from meeting notes and create Jira tasks with proper assignees. This skill parses unstructured meeting notes (from Confluence or pasted text), identifies action items with assignees, looks up Jira account IDs, and creates tasks—eliminating the tedious post-meeting ticket creation process.
**Use this skill when:** Users have meeting notes with action items that need to become Jira tasks.
---
## Workflowgenerate-status-report
When your agent uses it
Generate project status reports from Jira issues and publish to Confluence. When an agent needs to: (1) Create a status report for a project, (2) Summarize project progress or updates, (3) Generate weekly/daily reports from Jira, (4) Publish status summaries to Confluence, or (5) Analyze project blockers and completion. Queries Jira issues, categorizes by status/priority, and creates formatted reports for delivery managers and executives.
What it loads into context
Frontmatter
102 tokensAlways available to the agent
SKILL.md
2,623 tokensWhen the skill is activated
Reference documents
1,134 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Keywords
- Workflow
- Step 1: Identify Scope
- Step 2: Query Jira
- Step 3: Analyze Data
- Step 4: Format Report
- Step 5: Publish to Confluence
- Complete Example Workflow
- Tips for Quality Reports
- Resources
Scripts executed separately
scripts/jql_builder.py
Files
SKILL.mdcore11,312 bytesSKILL.mdcore11,312 bytesSKILL.mdcore11,312 bytesreferences/jql-patterns.mddoc1,780 bytesreferences/report-templates.mddoc2,556 bytesscripts/jql_builder.pyruns6,596 bytes
Read SKILL.md
# Generate Status Report
## Keywords
status report, project status, weekly update, daily standup, Jira report, project summary, blockers, progress update, Confluence report, sprint report, project update, publish to Confluence, write to Confluence, post report
Automatically query Jira for project status, analyze issues, and generate formatted status reports published to Confluence.
**CRITICAL**: This skill should be **interactive**. Always clarify scope (time period, audience, Confluence destination) with the user before or after generating the report. Do not silently skip Confluence publishing—always offer it.
## Workflow
Generating a status report follows these steps:
1. **Identify scope** - Determine project, time period, and target audiencejira-sprint-dashboard
When your agent uses it
Create a visual Jira sprint dashboard from Jira project, space, sprint, board, filter, JQL, work item keys, or Jira URL data. Use when the user asks for a Jira sprint dashboard, standup dashboard, sprint review, delivery review, engineering manager dashboard, WIP review, planning view, closeout view, or a visual snapshot of Jira work that is more useful than a flat report. Use the richest dashboard format supported by the current agent, such as Cursor Canvas, an interactive artifact, HTML, or Markdown.
What it loads into context
Frontmatter
129 tokensAlways available to the agent
SKILL.md
3,352 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Output Mode
- Cursor Canvas Renderer
- Portable Renderers
- Get The Scope
- Query Jira
- Normalize
- Dashboard Model
- Dashboard Shape
- Content And Style
- Renderer-Specific Style
- Self-Check
Files
SKILL.mdcore15,469 bytesSKILL.mdcore15,469 bytesSKILL.mdcore15,469 bytesSKILL.mdcore15,469 bytesSKILL.mdcore15,469 bytesSKILL.mdcore15,469 bytesSKILL.mdcore15,469 bytesSKILL.mdcore15,469 bytesSKILL.mdcore15,469 bytes
Read SKILL.md
# Jira Sprint Dashboard
Build a focused dashboard that helps an engineering manager, tech lead, or
senior engineer see current Jira work quickly enough to decide what needs
attention. The output is a dashboard, not a prose report and not a generic
health score.
This skill is read-only by default. Do not create, update, transition, assign,
or comment on Jira work items unless the user explicitly asks for a write action
after reviewing the dashboard.
## Output Mode
Use the richest dashboard renderer supported by the current environment. Thesearch-company-knowledge
When your agent uses it
Search across company knowledge bases (Confluence, Jira, internal docs) to find and explain internal concepts, processes, and technical details. When an agent needs to: (1) Find or search for information about systems, terminology, processes, deployment, authentication, infrastructure, architecture, or technical concepts, (2) Search internal documentation, knowledge base, company docs, or our docs, (3) Explain what something is, how it works, or look up information, or (4) Synthesize information from multiple sources. Searches in parallel and provides cited answers.
What it loads into context
Frontmatter
123 tokensAlways available to the agent
SKILL.md
3,862 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Keywords
- Overview
- Workflow
- Search Best Practices
- Handling Common Scenarios
- Examples
- Tips for High-Quality Answers
- When NOT to Use This Skill
- Quick Reference
Files
SKILL.mdcore17,081 bytesSKILL.mdcore17,081 bytesSKILL.mdcore17,081 bytes
Read SKILL.md
# Search Company Knowledge
## Keywords
find information, search company knowledge, look up, what is, explain, company docs, internal documentation, Confluence search, Jira search, our documentation, internal knowledge, knowledge base, search for, tell me about, get information about, company systems, terminology, find everything about, what do we know about, deployment, authentication, infrastructure, processes, procedures, how to, how does, our systems, our processes, internal systems, company processes, technical documentation, engineering docs, architecture, configuration, search our docs, search internal docs, find in our docs
## Overview
Search across siloed company knowledge systems (Confluence, Jira, internal documentation) to find comprehensive answers to questions about internal concepts, systems, and terminology. This skill performs parallel searches across multiple sources and synthesizes results with proper citations.
**Use this skill when:** Users ask about internal company knowledge that might be documented in Confluence pages, Jira tickets, or internal documentation.
---
## Workflowspec-to-backlog
When your agent uses it
Automatically convert Confluence specification documents into structured Jira backlogs with Epics and implementation tickets. When an agent needs to: (1) Create Jira tickets from a Confluence page, (2) Generate a backlog from a specification, (3) Break down a spec into implementation tasks, or (4) Convert requirements into Jira issues. Handles reading Confluence pages, analyzing specifications, creating Epics with proper structure, and generating detailed implementation tickets linked to the Epic.
What it loads into context
Frontmatter
103 tokensAlways available to the agent
SKILL.md
4,087 tokensWhen the skill is activated
Reference documents
7,022 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Overview
- Core Workflow
- Step 1: Fetch Confluence Page
- Step 2: Ask for Project Key
- Step 3: Analyze Specification
- Step 4: Present Breakdown to User
- Step 5: Create Epic FIRST
- Step 6: Create Child Tickets
- Step 7: Provide Summary
- Edge Cases & Troubleshooting
- Tips for High-Quality Breakdowns
- Examples of Good Breakdowns
Files
SKILL.mdcore17,432 bytesreferences/breakdown-examples.mddoc9,573 bytesreferences/epic-templates.mddoc12,106 bytesreferences/ticket-writing-guide.mddoc9,854 bytes
Read SKILL.md
# Spec to Backlog
## Overview
Transform Confluence specification documents into structured Jira backlogs automatically. This skill reads requirement documents from Confluence, intelligently breaks them down into logical implementation tasks, **creates an Epic first** to organize the work, then generates individual Jira tickets linked to that Epic—eliminating tedious manual copy-pasting.
## Core Workflow
**CRITICAL: Always follow this exact sequence:**
1. **Fetch Confluence Page** → Get the specification content
2. **Ask for Project Key** → Identify target Jira project
3. **Analyze Specification** → Break down into logical tasks (internally, don't create yet)
4. **Present Breakdown** → Show user the planned Epic and ticketstriage-issue
When your agent uses it
Intelligently triage bug reports and error messages by searching for duplicates in Jira and offering to create new issues or add comments to existing ones. When an agent needs to: (1) Triage a bug report or error message, (2) Check if an issue is a duplicate, (3) Find similar past issues, (4) Create a new bug ticket with proper context, or (5) Add information to an existing ticket. Searches Jira for similar issues, identifies duplicates, checks fix history, and helps create well-structured bug reports.
What it loads into context
Frontmatter
121 tokensAlways available to the agent
SKILL.md
4,703 tokensWhen the skill is activated
Reference documents
4,059 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Keywords
- Overview
- Workflow
- Edge Cases & Troubleshooting
- Tips for Effective Triage
- Examples
- When NOT to Use This Skill
- Quick Reference
Files
SKILL.mdcore19,379 bytesreferences/bug-report-templates.mddoc9,960 bytesreferences/search-patterns.mddoc6,211 bytes
Read SKILL.md
# Triage Issue
## Keywords
triage bug, check duplicate, is this a duplicate, search for similar issues, create bug ticket, file a bug, report this error, triage this error, bug report, error message, similar issues, duplicate bug, who fixed this, has this been reported, search bugs, find similar bugs, create issue, file issue
## Overview
Automatically triage bug reports and error messages by searching Jira for duplicates, identifying similar past issues, and helping create well-structured bug tickets or add context to existing issues. This skill eliminates manual duplicate checking and ensures bugs are properly documented with relevant historical context.
**Use this skill when:** Users need to triage error messages, bug reports, or issues to determine if they're duplicates and take appropriate action.
---
## WorkflowSkills included
- atlassian-mcp-code-search
- capture-tasks-from-meeting-notes
- generate-status-report
- jira-sprint-dashboard
- search-company-knowledge
- spec-to-backlog
- triage-issue
- capture-tasks-from-meeting-notes
- generate-status-report
- jira-sprint-dashboard
- search-company-knowledge
- spec-to-backlog
- triage-issue
Repository facts
- License
- Apache-2.0
- Created
- Aug 1, 2025
- Last pushed
- Nov 5, 2026
- Forks
- 147
- Open issues
- 91
- Project activity
- Active
Rank over the last 12 weeks
Now #800 · best #569 · down 140 in 30 days
- #788 on Oct 31
- #789 on Nov 1
- #792 on Nov 2
- #797 on Nov 3
- #799 from Nov 4 to Nov 5
- #800 since Nov 6
72 earlier periods
- #566 on Aug 2
- #560 on Aug 7
- #557 on Aug 8
- #562 on Aug 9
- #585 on Aug 10
- #588 on Aug 11
- #581 on Aug 12
- #589 on Aug 13
- #586 on Aug 14
- #569 on Aug 15
- #586 from Aug 16 to Aug 17
- #601 on Aug 18
- #590 on Aug 19
- #588 on Aug 20
- #597 on Aug 21
- #606 on Aug 24
- #617 on Aug 25
- #602 on Aug 26
- #607 on Aug 27
- #620 on Aug 28
- #579 from Aug 29 to Aug 30
- #603 on Aug 31
- #618 on Sep 1
- #608 on Sep 2
- #611 on Sep 3
- #591 on Sep 4
- #589 on Sep 5
- #599 on Sep 6
- #610 on Sep 7
- #627 on Sep 8
- #614 on Sep 9
- #618 on Sep 10
- #612 on Sep 13
- #634 on Sep 14
- #627 on Sep 15
- #635 on Sep 16
- #634 on Sep 17
- #637 on Sep 18
- #628 on Sep 20
- #641 on Sep 21
- #650 on Sep 22
- #648 on Sep 23
- #621 on Sep 24
- #615 on Sep 25
- #613 on Sep 26
- #637 on Sep 27
- #643 on Sep 28
- #678 on Sep 29
- #657 on Sep 30
- #629 on Oct 1
- #641 on Oct 4
- #645 on Oct 5
- #652 on Oct 6
- #660 on Oct 7
- #694 on Oct 8
- #672 on Oct 9
- #678 on Oct 12
- #675 on Oct 13
- #684 on Oct 14
- #673 on Oct 15
- #689 on Oct 16
- #668 on Oct 17
- #659 on Oct 18
- #695 on Oct 19
- #703 on Oct 20
- #707 on Oct 21
- #690 on Oct 22
- #688 on Oct 23
- #772 on Oct 25
- #781 on Oct 28
- #782 on Oct 29
- #784 on Oct 30
Before you install
Network or broad shellAutomated signals, not a guarantee
Checked Nov 3, 2026
Not fully analyzed: some files were too long, unreadable or missing. This never lowers the level.
Show 28 notes
skills/atlassian-mcp-code-search/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/atlassian-mcp-code-search/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/atlassian-mcp-code-search/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/atlassian-mcp-code-search/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/generate-status-report/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/generate-status-report/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/jira-sprint-dashboard/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/jira-sprint-dashboard/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/jira-sprint-dashboard/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/jira-sprint-dashboard/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/jira-sprint-dashboard/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/jira-sprint-dashboard/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/jira-sprint-dashboard/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/jira-sprint-dashboard/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/search-company-knowledge/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/search-company-knowledge/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/v1/generate-status-report/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/v1/generate-status-report/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/v1/jira-sprint-dashboard/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/v1/jira-sprint-dashboard/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzed
- No broad tool permissions
- No dangerous shell commands
- 329 network referencesin 17 files: skills/spec-to-backlog/SKILL.md:34 skills/v1/spec-to-backlog/SKILL.md:34 skills/triage-issue/SKILL.md:170 and 14 more
- No hidden or obfuscated text
- No instruction overrides
- 4 executable scriptsin 2 files: skills/generate-status-report/scripts/jql_builder.py:1 skills/v1/generate-status-report/scripts/jql_builder.py:1
- No access to secrets
- No requests to vote in Hot
Show all 333 signals by file
.claude-plugin/marketplace.json
- Network accessline 1
{ "$schema": "https://anthropic.com/claude-code/marketplace.schema.json", - Network accessline 2
"$schema": "https://anthropic.com/claude-code/marketplace.schema.json", - Network accessline 19
"source": "./", "category": "productivity", "homepage": "https://github.com/atlassian/atlassian-mcp-server" - Network accessline 20
"category": "productivity", "homepage": "https://github.com/atlassian/atlassian-mcp-server" } - Network accessline 21
"homepage": "https://github.com/atlassian/atlassian-mcp-server"
.mcp.json
skills/README.md
- Network accessline 3
The skills in this directory target the **Atlassian Rovo MCP v2** endpoint, `https://mcp.atlassian.com/v2/mcp`. They are what every packaged plugin installs, and each one - Network accessline 4
`https://mcp.atlassian.com/v2/mcp`. They are what every packaged plugin installs, and each one - Network accessline 5
lives at `skills/<name>/SKILL.md` per the [Agent Skills](https://agent-plugins.org/) convention. - Network accessline 32
For the current tool reference, see [Supported tools](https://support.atlassian.com/atlassian-rovo-mcp-server/docs/supported-tools/). - Network accessline 33
[Supported tools](https://support.atlassian.com/atlassian-rovo-mcp-server/docs/supported-tools/).
skills/capture-tasks-from-meeting-notes/SKILL.md
- Network accessline 40
**URL patterns:** - `https://[site].atlassian.net/wiki/spaces/[SPACE]/pages/[PAGE_ID]/[title]` - Network accessline 40
**URL patterns:** - `https://[site].atlassian.net/wiki/spaces/[SPACE]/pages/[PAGE_ID]/[title]` - Network accessline 41
- `https://[site].atlassian.net/wiki/spaces/[SPACE]/pages/[PAGE_ID]/[title]` - Network accessline 41
- `https://[site].atlassian.net/wiki/spaces/[SPACE]/pages/[PAGE_ID]/[title]` - Network accessline 340
**Source:** https://yoursite.atlassian.net/wiki/spaces/TEAM/pages/12345 - Network accessline 340
**Source:** https://yoursite.atlassian.net/wiki/spaces/TEAM/pages/12345 - Network accessline 356
1. [PROJ-123] - [Task summary] Assigned to: [Name] https://yoursite.atlassian.net/browse/PROJ-123 - Network accessline 356
1. [PROJ-123] - [Task summary] Assigned to: [Name] https://yoursite.atlassian.net/browse/PROJ-123 - Network accessline 358
https://yoursite.atlassian.net/browse/PROJ-123 - Network accessline 358
https://yoursite.atlassian.net/browse/PROJ-123 - Network accessline 360
2. [PROJ-124] - [Task summary] Assigned to: [Name] https://yoursite.atlassian.net/browse/PROJ-124 - Network accessline 360
2. [PROJ-124] - [Task summary] Assigned to: [Name] https://yoursite.atlassian.net/browse/PROJ-124 - Network accessline 362
https://yoursite.atlassian.net/browse/PROJ-124 - Network accessline 362
https://yoursite.atlassian.net/browse/PROJ-124
skills/generate-status-report/SKILL.md
- Network accessline 233
- Bold (`**text**`) for emphasis - Tables for metrics if needed - Links to Jira issues: `[PROJ-123](https://yourinstance.atlassian.net/browse/PROJ-123)` - Network accessline 233
- Bold (`**text**`) for emphasis - Tables for metrics if needed - Links to Jira issues: `[PROJ-123](https://yourinstance.atlassian.net/browse/PROJ-123)` - Network accessline 235
- Links to Jira issues: `[PROJ-123](https://yourinstance.atlassian.net/browse/PROJ-123)` - Network accessline 235
- Links to Jira issues: `[PROJ-123](https://yourinstance.atlassian.net/browse/PROJ-123)`
skills/generate-status-report/scripts/jql_builder.py
skills/search-company-knowledge/SKILL.md
- Network accessline 284
**Source:** [Page Title](https://yoursite.atlassian.net/wiki/spaces/SPACE/pages/123456) - Network accessline 284
**Source:** [Page Title](https://yoursite.atlassian.net/wiki/spaces/SPACE/pages/123456) - Network accessline 289
**Related Tickets:** - [PROJ-123](https://yoursite.atlassian.net/browse/PROJ-123) - Brief description - Network accessline 289
**Related Tickets:** - [PROJ-123](https://yoursite.atlassian.net/browse/PROJ-123) - Brief description - Network accessline 290
- [PROJ-123](https://yoursite.atlassian.net/browse/PROJ-123) - Brief description - Network accessline 290
- [PROJ-123](https://yoursite.atlassian.net/browse/PROJ-123) - Brief description - Network accessline 291
- [PROJ-456](https://yoursite.atlassian.net/browse/PROJ-456) - Brief description - Network accessline 291
- [PROJ-456](https://yoursite.atlassian.net/browse/PROJ-456) - Brief description - Network accessline 298
**Confluence Documentation:** - [Stratus Architecture Guide](https://yoursite.atlassian.net/wiki/spaces/DOCS/pages/12345) - Network accessline 298
**Confluence Documentation:** - [Stratus Architecture Guide](https://yoursite.atlassian.net/wiki/spaces/DOCS/pages/12345) - Network accessline 299
- [Stratus Architecture Guide](https://yoursite.atlassian.net/wiki/spaces/DOCS/pages/12345) - Network accessline 299
- [Stratus Architecture Guide](https://yoursite.atlassian.net/wiki/spaces/DOCS/pages/12345) - Network accessline 300
- [Minion Configuration](https://yoursite.atlassian.net/wiki/spaces/DEVOPS/pages/67890) - Network accessline 300
- [Minion Configuration](https://yoursite.atlassian.net/wiki/spaces/DEVOPS/pages/67890) - Network accessline 302
**Jira Issues:** - [PROJ-145](https://yoursite.atlassian.net/browse/PROJ-145) - Minion scaling implementation - Network accessline 302
**Jira Issues:** - [PROJ-145](https://yoursite.atlassian.net/browse/PROJ-145) - Minion scaling implementation - Network accessline 303
- [PROJ-145](https://yoursite.atlassian.net/browse/PROJ-145) - Minion scaling implementation - Network accessline 303
- [PROJ-145](https://yoursite.atlassian.net/browse/PROJ-145) - Minion scaling implementation - Network accessline 304
- [PROJ-203](https://yoursite.atlassian.net/browse/PROJ-203) - Performance optimization - Network accessline 304
- [PROJ-203](https://yoursite.atlassian.net/browse/PROJ-203) - Performance optimization
skills/spec-to-backlog/SKILL.md
- Network accessline 34
Extract the cloud ID and page ID from the URL pattern: - Standard format: `https://[site].atlassian.net/wiki/spaces/[SPACE]/pages/[PAGE_ID]/[title]` - Network accessline 34
Extract the cloud ID and page ID from the URL pattern: - Standard format: `https://[site].atlassian.net/wiki/spaces/[SPACE]/pages/[PAGE_ID]/[title]` - Network accessline 35
- Standard format: `https://[site].atlassian.net/wiki/spaces/[SPACE]/pages/[PAGE_ID]/[title]` - Network accessline 35
- Standard format: `https://[site].atlassian.net/wiki/spaces/[SPACE]/pages/[PAGE_ID]/[title]` - Network accessline 276
"key": "PROJ-123", "id": "10001", "self": "https://yoursite.atlassian.net/rest/api/3/issue/10001" - Network accessline 276
"key": "PROJ-123", "id": "10001", "self": "https://yoursite.atlassian.net/rest/api/3/issue/10001" - Network accessline 277
"id": "10001", "self": "https://yoursite.atlassian.net/rest/api/3/issue/10001" } - Network accessline 277
"id": "10001", "self": "https://yoursite.atlassian.net/rest/api/3/issue/10001" } - Network accessline 278
"self": "https://yoursite.atlassian.net/rest/api/3/issue/10001" - Network accessline 278
"self": "https://yoursite.atlassian.net/rest/api/3/issue/10001" - Network accessline 376
**Epic:** PROJ-123 - User Authentication System https://yoursite.atlassian.net/browse/PROJ-123 - Network accessline 376
**Epic:** PROJ-123 - User Authentication System https://yoursite.atlassian.net/browse/PROJ-123 - Network accessline 377
https://yoursite.atlassian.net/browse/PROJ-123 - Network accessline 377
https://yoursite.atlassian.net/browse/PROJ-123 - Network accessline 381
1. PROJ-124 - Design authentication database schema https://yoursite.atlassian.net/browse/PROJ-124 - Network accessline 381
1. PROJ-124 - Design authentication database schema https://yoursite.atlassian.net/browse/PROJ-124 - Network accessline 382
https://yoursite.atlassian.net/browse/PROJ-124 - Network accessline 382
https://yoursite.atlassian.net/browse/PROJ-124 - Network accessline 384
2. PROJ-125 - Implement user registration API endpoint https://yoursite.atlassian.net/browse/PROJ-125 - Network accessline 384
2. PROJ-125 - Implement user registration API endpoint https://yoursite.atlassian.net/browse/PROJ-125 - Network accessline 385
https://yoursite.atlassian.net/browse/PROJ-125 - Network accessline 385
https://yoursite.atlassian.net/browse/PROJ-125 - Network accessline 387
3. PROJ-126 - Implement user login API endpoint https://yoursite.atlassian.net/browse/PROJ-126 - Network accessline 387
3. PROJ-126 - Implement user login API endpoint https://yoursite.atlassian.net/browse/PROJ-126 - Network accessline 388
https://yoursite.atlassian.net/browse/PROJ-126 - Network accessline 388
https://yoursite.atlassian.net/browse/PROJ-126 - Network accessline 390
4. PROJ-127 - Build login form UI components https://yoursite.atlassian.net/browse/PROJ-127 - Network accessline 390
4. PROJ-127 - Build login form UI components https://yoursite.atlassian.net/browse/PROJ-127 - Network accessline 391
https://yoursite.atlassian.net/browse/PROJ-127 - Network accessline 391
https://yoursite.atlassian.net/browse/PROJ-127 - Network accessline 393
5. PROJ-128 - Build registration form UI components https://yoursite.atlassian.net/browse/PROJ-128 - Network accessline 393
5. PROJ-128 - Build registration form UI components https://yoursite.atlassian.net/browse/PROJ-128 - Network accessline 394
https://yoursite.atlassian.net/browse/PROJ-128 - Network accessline 394
https://yoursite.atlassian.net/browse/PROJ-128 - Network accessline 396
6. PROJ-129 - Add authentication integration to existing features https://yoursite.atlassian.net/browse/PROJ-129 - Network accessline 396
6. PROJ-129 - Add authentication integration to existing features https://yoursite.atlassian.net/browse/PROJ-129 - Network accessline 397
https://yoursite.atlassian.net/browse/PROJ-129 - Network accessline 397
https://yoursite.atlassian.net/browse/PROJ-129 - Network accessline 399
7. PROJ-130 - Write authentication tests and documentation https://yoursite.atlassian.net/browse/PROJ-130 - Network accessline 399
7. PROJ-130 - Write authentication tests and documentation https://yoursite.atlassian.net/browse/PROJ-130 - Network accessline 400
https://yoursite.atlassian.net/browse/PROJ-130 - Network accessline 400
https://yoursite.atlassian.net/browse/PROJ-130 - Network accessline 402
**Source:** https://yoursite.atlassian.net/wiki/spaces/SPECS/pages/123456 - Network accessline 402
**Source:** https://yoursite.atlassian.net/wiki/spaces/SPECS/pages/123456
skills/spec-to-backlog/references/epic-templates.md
- Network accessline 45
## Source Specification https://company.atlassian.net/wiki/spaces/PRODUCT/pages/123456/Notifications-Spec - Network accessline 45
## Source Specification https://company.atlassian.net/wiki/spaces/PRODUCT/pages/123456/Notifications-Spec - Network accessline 46
https://company.atlassian.net/wiki/spaces/PRODUCT/pages/123456/Notifications-Spec - Network accessline 46
https://company.atlassian.net/wiki/spaces/PRODUCT/pages/123456/Notifications-Spec - Network accessline 115
## Source Documentation https://company.atlassian.net/wiki/spaces/ENG/pages/789012/Payment-Failure-Investigation - Network accessline 115
## Source Documentation https://company.atlassian.net/wiki/spaces/ENG/pages/789012/Payment-Failure-Investigation - Network accessline 116
https://company.atlassian.net/wiki/spaces/ENG/pages/789012/Payment-Failure-Investigation - Network accessline 116
https://company.atlassian.net/wiki/spaces/ENG/pages/789012/Payment-Failure-Investigation - Network accessline 185
## Source Documentation https://company.atlassian.net/wiki/spaces/ENG/pages/345678/PG15-Migration-RFC - Network accessline 185
## Source Documentation https://company.atlassian.net/wiki/spaces/ENG/pages/345678/PG15-Migration-RFC - Network accessline 186
https://company.atlassian.net/wiki/spaces/ENG/pages/345678/PG15-Migration-RFC - Network accessline 186
https://company.atlassian.net/wiki/spaces/ENG/pages/345678/PG15-Migration-RFC - Network accessline 262
## Source Specification https://company.atlassian.net/wiki/spaces/API/pages/456789/Public-API-v1-Spec - Network accessline 262
## Source Specification https://company.atlassian.net/wiki/spaces/API/pages/456789/Public-API-v1-Spec - Network accessline 263
https://company.atlassian.net/wiki/spaces/API/pages/456789/Public-API-v1-Spec - Network accessline 263
https://company.atlassian.net/wiki/spaces/API/pages/456789/Public-API-v1-Spec - Network accessline 273
- **Rate limiting**: 1,000 requests/hour per API key (higher tiers available) - **Versioning**: URI-based (/v1/, /v2/) - **Base URL**: https://api.company.com/v1 - Network accessline 273
- **Rate limiting**: 1,000 requests/hour per API key (higher tiers available) - **Versioning**: URI-based (/v1/, /v2/) - **Base URL**: https://api.company.com/v1 - Network accessline 275
- **Base URL**: https://api.company.com/v1 - Network accessline 275
- **Base URL**: https://api.company.com/v1 - Network accessline 343
## Source Documentation https://company.atlassian.net/wiki/spaces/DESIGN/pages/567890/Dashboard-Redesign - Network accessline 343
## Source Documentation https://company.atlassian.net/wiki/spaces/DESIGN/pages/567890/Dashboard-Redesign - Network accessline 344
https://company.atlassian.net/wiki/spaces/DESIGN/pages/567890/Dashboard-Redesign - Network accessline 344
https://company.atlassian.net/wiki/spaces/DESIGN/pages/567890/Dashboard-Redesign
skills/spec-to-backlog/references/ticket-writing-guide.md
- Network accessline 113
## Resources - API Spec: https://company.atlassian.net/wiki/API-Design - Network accessline 113
## Resources - API Spec: https://company.atlassian.net/wiki/API-Design - Network accessline 114
- API Spec: https://company.atlassian.net/wiki/API-Design - Network accessline 114
- API Spec: https://company.atlassian.net/wiki/API-Design - Network accessline 147
## Resources - Bug Report: https://company.atlassian.net/wiki/BUG-456 - Network accessline 147
## Resources - Bug Report: https://company.atlassian.net/wiki/BUG-456 - Network accessline 148
- Bug Report: https://company.atlassian.net/wiki/BUG-456 - Network accessline 148
- Bug Report: https://company.atlassian.net/wiki/BUG-456 - Network accessline 181
## Resources - Migration RFC: https://company.atlassian.net/wiki/PG15-Migration - Network accessline 181
## Resources - Migration RFC: https://company.atlassian.net/wiki/PG15-Migration - Network accessline 182
- Migration RFC: https://company.atlassian.net/wiki/PG15-Migration - Network accessline 182
- Migration RFC: https://company.atlassian.net/wiki/PG15-Migration - Network accessline 183
- Infrastructure docs: https://wiki/Database-Setup - Network accessline 183
- Infrastructure docs: https://wiki/Database-Setup - Network accessline 218
## Resources - Design mockup: [Figma link] - WebSocket docs: https://wiki/Notifications-API - Network accessline 218
## Resources - Design mockup: [Figma link] - WebSocket docs: https://wiki/Notifications-API - Network accessline 219
- Design mockup: [Figma link] - WebSocket docs: https://wiki/Notifications-API - Related: NOTIF-123 (Notification panel component) - Network accessline 219
- Design mockup: [Figma link] - WebSocket docs: https://wiki/Notifications-API - Related: NOTIF-123 (Notification panel component) - Network accessline 220
- WebSocket docs: https://wiki/Notifications-API - Network accessline 220
- WebSocket docs: https://wiki/Notifications-API
skills/triage-issue/SKILL.md
- Network accessline 170
Status: Open | Priority: High | Created: 3 days ago Assignee: @john.doe https://yoursite.atlassian.net/browse/PROJ-456 - Network accessline 170
Status: Open | Priority: High | Created: 3 days ago Assignee: @john.doe https://yoursite.atlassian.net/browse/PROJ-456 - Network accessline 172
https://yoursite.atlassian.net/browse/PROJ-456 - Network accessline 172
https://yoursite.atlassian.net/browse/PROJ-456 - Network accessline 197
**1. PROJ-789** - Mobile app authentication failures Status: Resolved | Fixed: 2 weeks ago | Fixed by: @jane.smith https://yoursite.atlassian.net/browse/PROJ-789 - Network accessline 197
**1. PROJ-789** - Mobile app authentication failures Status: Resolved | Fixed: 2 weeks ago | Fixed by: @jane.smith https://yoursite.atlassian.net/browse/PROJ-789 - Network accessline 199
https://yoursite.atlassian.net/browse/PROJ-789 - Network accessline 199
https://yoursite.atlassian.net/browse/PROJ-789 - Network accessline 201
**2. PROJ-234** - Login timeout on slow connections Status: Open | Priority: Medium | Created: 1 month ago https://yoursite.atlassian.net/browse/PROJ-234 - Network accessline 201
**2. PROJ-234** - Login timeout on slow connections Status: Open | Priority: Medium | Created: 1 month ago https://yoursite.atlassian.net/browse/PROJ-234 - Network accessline 203
https://yoursite.atlassian.net/browse/PROJ-234 - Network accessline 203
https://yoursite.atlassian.net/browse/PROJ-234 - Network accessline 374
Added details to existing issue: **PROJ-456** https://yoursite.atlassian.net/browse/PROJ-456 - Network accessline 374
Added details to existing issue: **PROJ-456** https://yoursite.atlassian.net/browse/PROJ-456 - Network accessline 375
https://yoursite.atlassian.net/browse/PROJ-456 - Network accessline 375
https://yoursite.atlassian.net/browse/PROJ-456 - Network accessline 393
**PROJ-890** - Mobile Login: Connection timeout during authentication https://yoursite.atlassian.net/browse/PROJ-890 - Network accessline 393
**PROJ-890** - Mobile Login: Connection timeout during authentication https://yoursite.atlassian.net/browse/PROJ-890 - Network accessline 394
https://yoursite.atlassian.net/browse/PROJ-890 - Network accessline 394
https://yoursite.atlassian.net/browse/PROJ-890 - Network accessline 487
Status: Resolved (Fixed) | Fixed: 3 months ago | Fixed by: @jane.smith Resolution: [Brief description of fix] https://yoursite.atlassian.net/browse/PROJ-567 - Network accessline 487
Status: Resolved (Fixed) | Fixed: 3 months ago | Fixed by: @jane.smith Resolution: [Brief description of fix] https://yoursite.atlassian.net/browse/PROJ-567 - Network accessline 489
https://yoursite.atlassian.net/browse/PROJ-567 - Network accessline 489
https://yoursite.atlassian.net/browse/PROJ-567 - Network accessline 633
PROJ-890 - Payment API: NullPointerException in refund processing https://yoursite.atlassian.net/browse/PROJ-890 - Network accessline 633
PROJ-890 - Payment API: NullPointerException in refund processing https://yoursite.atlassian.net/browse/PROJ-890 - Network accessline 634
https://yoursite.atlassian.net/browse/PROJ-890 - Network accessline 634
https://yoursite.atlassian.net/browse/PROJ-890 - Network accessline 658
PROJ-891 - File Upload: Upload failed for files >5MB (Regression?) https://yoursite.atlassian.net/browse/PROJ-891 - Network accessline 658
PROJ-891 - File Upload: Upload failed for files >5MB (Regression?) https://yoursite.atlassian.net/browse/PROJ-891 - Network accessline 659
https://yoursite.atlassian.net/browse/PROJ-891 - Network accessline 659
https://yoursite.atlassian.net/browse/PROJ-891
skills/v1/capture-tasks-from-meeting-notes/SKILL.md
- Network accessline 39
**URL patterns:** - `https://[site].atlassian.net/wiki/spaces/[SPACE]/pages/[PAGE_ID]/[title]` - Network accessline 39
**URL patterns:** - `https://[site].atlassian.net/wiki/spaces/[SPACE]/pages/[PAGE_ID]/[title]` - Network accessline 40
- `https://[site].atlassian.net/wiki/spaces/[SPACE]/pages/[PAGE_ID]/[title]` - Network accessline 40
- `https://[site].atlassian.net/wiki/spaces/[SPACE]/pages/[PAGE_ID]/[title]` - Network accessline 325
**Source:** https://yoursite.atlassian.net/wiki/spaces/TEAM/pages/12345 - Network accessline 325
**Source:** https://yoursite.atlassian.net/wiki/spaces/TEAM/pages/12345 - Network accessline 341
1. [PROJ-123] - [Task summary] Assigned to: [Name] https://yoursite.atlassian.net/browse/PROJ-123 - Network accessline 341
1. [PROJ-123] - [Task summary] Assigned to: [Name] https://yoursite.atlassian.net/browse/PROJ-123 - Network accessline 343
https://yoursite.atlassian.net/browse/PROJ-123 - Network accessline 343
https://yoursite.atlassian.net/browse/PROJ-123 - Network accessline 345
2. [PROJ-124] - [Task summary] Assigned to: [Name] https://yoursite.atlassian.net/browse/PROJ-124 - Network accessline 345
2. [PROJ-124] - [Task summary] Assigned to: [Name] https://yoursite.atlassian.net/browse/PROJ-124 - Network accessline 347
https://yoursite.atlassian.net/browse/PROJ-124 - Network accessline 347
https://yoursite.atlassian.net/browse/PROJ-124
skills/v1/generate-status-report/SKILL.md
- Network accessline 192
- Bold (`**text**`) for emphasis - Tables for metrics if needed - Links to Jira issues: `[PROJ-123](https://yourinstance.atlassian.net/browse/PROJ-123)` - Network accessline 192
- Bold (`**text**`) for emphasis - Tables for metrics if needed - Links to Jira issues: `[PROJ-123](https://yourinstance.atlassian.net/browse/PROJ-123)` - Network accessline 194
- Links to Jira issues: `[PROJ-123](https://yourinstance.atlassian.net/browse/PROJ-123)` - Network accessline 194
- Links to Jira issues: `[PROJ-123](https://yourinstance.atlassian.net/browse/PROJ-123)`
skills/v1/generate-status-report/scripts/jql_builder.py
skills/v1/search-company-knowledge/SKILL.md
- Network accessline 266
**Source:** [Page Title](https://yoursite.atlassian.net/wiki/spaces/SPACE/pages/123456) - Network accessline 266
**Source:** [Page Title](https://yoursite.atlassian.net/wiki/spaces/SPACE/pages/123456) - Network accessline 271
**Related Tickets:** - [PROJ-123](https://yoursite.atlassian.net/browse/PROJ-123) - Brief description - Network accessline 271
**Related Tickets:** - [PROJ-123](https://yoursite.atlassian.net/browse/PROJ-123) - Brief description - Network accessline 272
- [PROJ-123](https://yoursite.atlassian.net/browse/PROJ-123) - Brief description - Network accessline 272
- [PROJ-123](https://yoursite.atlassian.net/browse/PROJ-123) - Brief description - Network accessline 273
- [PROJ-456](https://yoursite.atlassian.net/browse/PROJ-456) - Brief description - Network accessline 273
- [PROJ-456](https://yoursite.atlassian.net/browse/PROJ-456) - Brief description - Network accessline 280
**Confluence Documentation:** - [Stratus Architecture Guide](https://yoursite.atlassian.net/wiki/spaces/DOCS/pages/12345) - Network accessline 280
**Confluence Documentation:** - [Stratus Architecture Guide](https://yoursite.atlassian.net/wiki/spaces/DOCS/pages/12345) - Network accessline 281
- [Stratus Architecture Guide](https://yoursite.atlassian.net/wiki/spaces/DOCS/pages/12345) - Network accessline 281
- [Stratus Architecture Guide](https://yoursite.atlassian.net/wiki/spaces/DOCS/pages/12345) - Network accessline 282
- [Minion Configuration](https://yoursite.atlassian.net/wiki/spaces/DEVOPS/pages/67890) - Network accessline 282
- [Minion Configuration](https://yoursite.atlassian.net/wiki/spaces/DEVOPS/pages/67890) - Network accessline 284
**Jira Issues:** - [PROJ-145](https://yoursite.atlassian.net/browse/PROJ-145) - Minion scaling implementation - Network accessline 284
**Jira Issues:** - [PROJ-145](https://yoursite.atlassian.net/browse/PROJ-145) - Minion scaling implementation - Network accessline 285
- [PROJ-145](https://yoursite.atlassian.net/browse/PROJ-145) - Minion scaling implementation - Network accessline 285
- [PROJ-145](https://yoursite.atlassian.net/browse/PROJ-145) - Minion scaling implementation - Network accessline 286
- [PROJ-203](https://yoursite.atlassian.net/browse/PROJ-203) - Performance optimization - Network accessline 286
- [PROJ-203](https://yoursite.atlassian.net/browse/PROJ-203) - Performance optimization
skills/v1/spec-to-backlog/SKILL.md
- Network accessline 34
Extract the cloud ID and page ID from the URL pattern: - Standard format: `https://[site].atlassian.net/wiki/spaces/[SPACE]/pages/[PAGE_ID]/[title]` - Network accessline 34
Extract the cloud ID and page ID from the URL pattern: - Standard format: `https://[site].atlassian.net/wiki/spaces/[SPACE]/pages/[PAGE_ID]/[title]` - Network accessline 35
- Standard format: `https://[site].atlassian.net/wiki/spaces/[SPACE]/pages/[PAGE_ID]/[title]` - Network accessline 35
- Standard format: `https://[site].atlassian.net/wiki/spaces/[SPACE]/pages/[PAGE_ID]/[title]` - Network accessline 266
"key": "PROJ-123", "id": "10001", "self": "https://yoursite.atlassian.net/rest/api/3/issue/10001" - Network accessline 266
"key": "PROJ-123", "id": "10001", "self": "https://yoursite.atlassian.net/rest/api/3/issue/10001" - Network accessline 267
"id": "10001", "self": "https://yoursite.atlassian.net/rest/api/3/issue/10001" } - Network accessline 267
"id": "10001", "self": "https://yoursite.atlassian.net/rest/api/3/issue/10001" } - Network accessline 268
"self": "https://yoursite.atlassian.net/rest/api/3/issue/10001" - Network accessline 268
"self": "https://yoursite.atlassian.net/rest/api/3/issue/10001" - Network accessline 366
**Epic:** PROJ-123 - User Authentication System https://yoursite.atlassian.net/browse/PROJ-123 - Network accessline 366
**Epic:** PROJ-123 - User Authentication System https://yoursite.atlassian.net/browse/PROJ-123 - Network accessline 367
https://yoursite.atlassian.net/browse/PROJ-123 - Network accessline 367
https://yoursite.atlassian.net/browse/PROJ-123 - Network accessline 371
1. PROJ-124 - Design authentication database schema https://yoursite.atlassian.net/browse/PROJ-124 - Network accessline 371
1. PROJ-124 - Design authentication database schema https://yoursite.atlassian.net/browse/PROJ-124 - Network accessline 372
https://yoursite.atlassian.net/browse/PROJ-124 - Network accessline 372
https://yoursite.atlassian.net/browse/PROJ-124 - Network accessline 374
2. PROJ-125 - Implement user registration API endpoint https://yoursite.atlassian.net/browse/PROJ-125 - Network accessline 374
2. PROJ-125 - Implement user registration API endpoint https://yoursite.atlassian.net/browse/PROJ-125 - Network accessline 375
https://yoursite.atlassian.net/browse/PROJ-125 - Network accessline 375
https://yoursite.atlassian.net/browse/PROJ-125 - Network accessline 377
3. PROJ-126 - Implement user login API endpoint https://yoursite.atlassian.net/browse/PROJ-126 - Network accessline 377
3. PROJ-126 - Implement user login API endpoint https://yoursite.atlassian.net/browse/PROJ-126 - Network accessline 378
https://yoursite.atlassian.net/browse/PROJ-126 - Network accessline 378
https://yoursite.atlassian.net/browse/PROJ-126 - Network accessline 380
4. PROJ-127 - Build login form UI components https://yoursite.atlassian.net/browse/PROJ-127 - Network accessline 380
4. PROJ-127 - Build login form UI components https://yoursite.atlassian.net/browse/PROJ-127 - Network accessline 381
https://yoursite.atlassian.net/browse/PROJ-127 - Network accessline 381
https://yoursite.atlassian.net/browse/PROJ-127 - Network accessline 383
5. PROJ-128 - Build registration form UI components https://yoursite.atlassian.net/browse/PROJ-128 - Network accessline 383
5. PROJ-128 - Build registration form UI components https://yoursite.atlassian.net/browse/PROJ-128 - Network accessline 384
https://yoursite.atlassian.net/browse/PROJ-128 - Network accessline 384
https://yoursite.atlassian.net/browse/PROJ-128 - Network accessline 386
6. PROJ-129 - Add authentication integration to existing features https://yoursite.atlassian.net/browse/PROJ-129 - Network accessline 386
6. PROJ-129 - Add authentication integration to existing features https://yoursite.atlassian.net/browse/PROJ-129 - Network accessline 387
https://yoursite.atlassian.net/browse/PROJ-129 - Network accessline 387
https://yoursite.atlassian.net/browse/PROJ-129 - Network accessline 389
7. PROJ-130 - Write authentication tests and documentation https://yoursite.atlassian.net/browse/PROJ-130 - Network accessline 389
7. PROJ-130 - Write authentication tests and documentation https://yoursite.atlassian.net/browse/PROJ-130 - Network accessline 390
https://yoursite.atlassian.net/browse/PROJ-130 - Network accessline 390
https://yoursite.atlassian.net/browse/PROJ-130 - Network accessline 392
**Source:** https://yoursite.atlassian.net/wiki/spaces/SPECS/pages/123456 - Network accessline 392
**Source:** https://yoursite.atlassian.net/wiki/spaces/SPECS/pages/123456
skills/v1/spec-to-backlog/references/epic-templates.md
- Network accessline 45
## Source Specification https://company.atlassian.net/wiki/spaces/PRODUCT/pages/123456/Notifications-Spec - Network accessline 45
## Source Specification https://company.atlassian.net/wiki/spaces/PRODUCT/pages/123456/Notifications-Spec - Network accessline 46
https://company.atlassian.net/wiki/spaces/PRODUCT/pages/123456/Notifications-Spec - Network accessline 46
https://company.atlassian.net/wiki/spaces/PRODUCT/pages/123456/Notifications-Spec - Network accessline 115
## Source Documentation https://company.atlassian.net/wiki/spaces/ENG/pages/789012/Payment-Failure-Investigation - Network accessline 115
## Source Documentation https://company.atlassian.net/wiki/spaces/ENG/pages/789012/Payment-Failure-Investigation - Network accessline 116
https://company.atlassian.net/wiki/spaces/ENG/pages/789012/Payment-Failure-Investigation - Network accessline 116
https://company.atlassian.net/wiki/spaces/ENG/pages/789012/Payment-Failure-Investigation - Network accessline 185
## Source Documentation https://company.atlassian.net/wiki/spaces/ENG/pages/345678/PG15-Migration-RFC - Network accessline 185
## Source Documentation https://company.atlassian.net/wiki/spaces/ENG/pages/345678/PG15-Migration-RFC - Network accessline 186
https://company.atlassian.net/wiki/spaces/ENG/pages/345678/PG15-Migration-RFC - Network accessline 186
https://company.atlassian.net/wiki/spaces/ENG/pages/345678/PG15-Migration-RFC - Network accessline 262
## Source Specification https://company.atlassian.net/wiki/spaces/API/pages/456789/Public-API-v1-Spec - Network accessline 262
## Source Specification https://company.atlassian.net/wiki/spaces/API/pages/456789/Public-API-v1-Spec - Network accessline 263
https://company.atlassian.net/wiki/spaces/API/pages/456789/Public-API-v1-Spec - Network accessline 263
https://company.atlassian.net/wiki/spaces/API/pages/456789/Public-API-v1-Spec - Network accessline 273
- **Rate limiting**: 1,000 requests/hour per API key (higher tiers available) - **Versioning**: URI-based (/v1/, /v2/) - **Base URL**: https://api.company.com/v1 - Network accessline 273
- **Rate limiting**: 1,000 requests/hour per API key (higher tiers available) - **Versioning**: URI-based (/v1/, /v2/) - **Base URL**: https://api.company.com/v1 - Network accessline 275
- **Base URL**: https://api.company.com/v1 - Network accessline 275
- **Base URL**: https://api.company.com/v1 - Network accessline 343
## Source Documentation https://company.atlassian.net/wiki/spaces/DESIGN/pages/567890/Dashboard-Redesign - Network accessline 343
## Source Documentation https://company.atlassian.net/wiki/spaces/DESIGN/pages/567890/Dashboard-Redesign - Network accessline 344
https://company.atlassian.net/wiki/spaces/DESIGN/pages/567890/Dashboard-Redesign - Network accessline 344
https://company.atlassian.net/wiki/spaces/DESIGN/pages/567890/Dashboard-Redesign
skills/v1/spec-to-backlog/references/ticket-writing-guide.md
- Network accessline 113
## Resources - API Spec: https://company.atlassian.net/wiki/API-Design - Network accessline 113
## Resources - API Spec: https://company.atlassian.net/wiki/API-Design - Network accessline 114
- API Spec: https://company.atlassian.net/wiki/API-Design - Network accessline 114
- API Spec: https://company.atlassian.net/wiki/API-Design - Network accessline 147
## Resources - Bug Report: https://company.atlassian.net/wiki/BUG-456 - Network accessline 147
## Resources - Bug Report: https://company.atlassian.net/wiki/BUG-456 - Network accessline 148
- Bug Report: https://company.atlassian.net/wiki/BUG-456 - Network accessline 148
- Bug Report: https://company.atlassian.net/wiki/BUG-456 - Network accessline 181
## Resources - Migration RFC: https://company.atlassian.net/wiki/PG15-Migration - Network accessline 181
## Resources - Migration RFC: https://company.atlassian.net/wiki/PG15-Migration - Network accessline 182
- Migration RFC: https://company.atlassian.net/wiki/PG15-Migration - Network accessline 182
- Migration RFC: https://company.atlassian.net/wiki/PG15-Migration - Network accessline 183
- Infrastructure docs: https://wiki/Database-Setup - Network accessline 183
- Infrastructure docs: https://wiki/Database-Setup - Network accessline 218
## Resources - Design mockup: [Figma link] - WebSocket docs: https://wiki/Notifications-API - Network accessline 218
## Resources - Design mockup: [Figma link] - WebSocket docs: https://wiki/Notifications-API - Network accessline 219
- Design mockup: [Figma link] - WebSocket docs: https://wiki/Notifications-API - Related: NOTIF-123 (Notification panel component) - Network accessline 219
- Design mockup: [Figma link] - WebSocket docs: https://wiki/Notifications-API - Related: NOTIF-123 (Notification panel component) - Network accessline 220
- WebSocket docs: https://wiki/Notifications-API - Network accessline 220
- WebSocket docs: https://wiki/Notifications-API
skills/v1/triage-issue/SKILL.md
- Network accessline 170
Status: Open | Priority: High | Created: 3 days ago Assignee: @john.doe https://yoursite.atlassian.net/browse/PROJ-456 - Network accessline 170
Status: Open | Priority: High | Created: 3 days ago Assignee: @john.doe https://yoursite.atlassian.net/browse/PROJ-456 - Network accessline 172
https://yoursite.atlassian.net/browse/PROJ-456 - Network accessline 172
https://yoursite.atlassian.net/browse/PROJ-456 - Network accessline 197
**1. PROJ-789** - Mobile app authentication failures Status: Resolved | Fixed: 2 weeks ago | Fixed by: @jane.smith https://yoursite.atlassian.net/browse/PROJ-789 - Network accessline 197
**1. PROJ-789** - Mobile app authentication failures Status: Resolved | Fixed: 2 weeks ago | Fixed by: @jane.smith https://yoursite.atlassian.net/browse/PROJ-789 - Network accessline 199
https://yoursite.atlassian.net/browse/PROJ-789 - Network accessline 199
https://yoursite.atlassian.net/browse/PROJ-789 - Network accessline 201
**2. PROJ-234** - Login timeout on slow connections Status: Open | Priority: Medium | Created: 1 month ago https://yoursite.atlassian.net/browse/PROJ-234 - Network accessline 201
**2. PROJ-234** - Login timeout on slow connections Status: Open | Priority: Medium | Created: 1 month ago https://yoursite.atlassian.net/browse/PROJ-234 - Network accessline 203
https://yoursite.atlassian.net/browse/PROJ-234 - Network accessline 203
https://yoursite.atlassian.net/browse/PROJ-234 - Network accessline 374
Added details to existing issue: **PROJ-456** https://yoursite.atlassian.net/browse/PROJ-456 - Network accessline 374
Added details to existing issue: **PROJ-456** https://yoursite.atlassian.net/browse/PROJ-456 - Network accessline 375
https://yoursite.atlassian.net/browse/PROJ-456 - Network accessline 375
https://yoursite.atlassian.net/browse/PROJ-456 - Network accessline 393
**PROJ-890** - Mobile Login: Connection timeout during authentication https://yoursite.atlassian.net/browse/PROJ-890 - Network accessline 393
**PROJ-890** - Mobile Login: Connection timeout during authentication https://yoursite.atlassian.net/browse/PROJ-890 - Network accessline 394
https://yoursite.atlassian.net/browse/PROJ-890 - Network accessline 394
https://yoursite.atlassian.net/browse/PROJ-890 - Network accessline 487
Status: Resolved (Fixed) | Fixed: 3 months ago | Fixed by: @jane.smith Resolution: [Brief description of fix] https://yoursite.atlassian.net/browse/PROJ-567 - Network accessline 487
Status: Resolved (Fixed) | Fixed: 3 months ago | Fixed by: @jane.smith Resolution: [Brief description of fix] https://yoursite.atlassian.net/browse/PROJ-567 - Network accessline 489
https://yoursite.atlassian.net/browse/PROJ-567 - Network accessline 489
https://yoursite.atlassian.net/browse/PROJ-567 - Network accessline 632
PROJ-890 - Payment API: NullPointerException in refund processing https://yoursite.atlassian.net/browse/PROJ-890 - Network accessline 632
PROJ-890 - Payment API: NullPointerException in refund processing https://yoursite.atlassian.net/browse/PROJ-890 - Network accessline 633
https://yoursite.atlassian.net/browse/PROJ-890 - Network accessline 633
https://yoursite.atlassian.net/browse/PROJ-890 - Network accessline 657
PROJ-891 - File Upload: Upload failed for files >5MB (Regression?) https://yoursite.atlassian.net/browse/PROJ-891 - Network accessline 657
PROJ-891 - File Upload: Upload failed for files >5MB (Regression?) https://yoursite.atlassian.net/browse/PROJ-891 - Network accessline 658
https://yoursite.atlassian.net/browse/PROJ-891 - Network accessline 658
https://yoursite.atlassian.net/browse/PROJ-891
How the signals fit together
Facts from a static read of the files at the pinned commit. They describe what the code does, not why.
Some files could not be read; the facts below still hold.
Signal confidence: 325 facts
- Network access in prose of documentationskills/README.md:3Low confidence
- Network access in prose of documentationskills/README.md:4Low confidence
- Network access in prose of documentationskills/README.md:5Low confidence
- Network access in prose of documentationskills/README.md:32Low confidence
- Network access in prose of documentationskills/README.md:33Low confidence
- Network access in prose of the SKILL.mdskills/capture-tasks-from-meeting-notes/SKILL.md:40Low confidence
- Network access in prose of the SKILL.mdcapture-tasks-from-meeting-notes/SKILL.md:40Low confidence
- Network access in prose of the SKILL.mdskills/capture-tasks-from-meeting-notes/SKILL.md:41Low confidence
- Network access in prose of the SKILL.mdcapture-tasks-from-meeting-notes/SKILL.md:41Low confidence
- Network access in code of the SKILL.mdskills/capture-tasks-from-meeting-notes/SKILL.md:340High confidence
- Network access in code of the SKILL.mdcapture-tasks-from-meeting-notes/SKILL.md:340High confidence
- Network access in code of the SKILL.mdskills/capture-tasks-from-meeting-notes/SKILL.md:356High confidence
- Network access in code of the SKILL.mdcapture-tasks-from-meeting-notes/SKILL.md:356High confidence
- Network access in code of the SKILL.mdskills/capture-tasks-from-meeting-notes/SKILL.md:358High confidence
- Network access in code of the SKILL.mdcapture-tasks-from-meeting-notes/SKILL.md:358High confidence
- Network access in code of the SKILL.mdskills/capture-tasks-from-meeting-notes/SKILL.md:360High confidence
- Network access in code of the SKILL.mdcapture-tasks-from-meeting-notes/SKILL.md:360High confidence
- Network access in code of the SKILL.mdskills/capture-tasks-from-meeting-notes/SKILL.md:362High confidence
- Network access in code of the SKILL.mdcapture-tasks-from-meeting-notes/SKILL.md:362High confidence
- Network access in prose of the SKILL.mdskills/generate-status-report/SKILL.md:233Low confidence
- Network access in prose of the SKILL.mdgenerate-status-report/SKILL.md:233Low confidence
- Network access in prose of the SKILL.mdskills/generate-status-report/SKILL.md:235Low confidence
- Network access in prose of the SKILL.mdgenerate-status-report/SKILL.md:235Low confidence
- Executable script in code of a file that runsskills/generate-status-report/scripts/jql_builder.py:1High confidence
- Executable script in code of a file that runsgenerate-status-report/scripts/jql_builder.py:1High confidence
- Network access in code of the SKILL.mdskills/search-company-knowledge/SKILL.md:284High confidence
- Network access in code of the SKILL.mdsearch-company-knowledge/SKILL.md:284High confidence
- Network access in code of the SKILL.mdskills/search-company-knowledge/SKILL.md:289High confidence
- Network access in code of the SKILL.mdsearch-company-knowledge/SKILL.md:289High confidence
- Network access in code of the SKILL.mdskills/search-company-knowledge/SKILL.md:290High confidence
- Network access in code of the SKILL.mdsearch-company-knowledge/SKILL.md:290High confidence
- Network access in code of the SKILL.mdskills/search-company-knowledge/SKILL.md:291High confidence
- Network access in code of the SKILL.mdsearch-company-knowledge/SKILL.md:291High confidence
- Network access in code of the SKILL.mdskills/search-company-knowledge/SKILL.md:298High confidence
- Network access in code of the SKILL.mdsearch-company-knowledge/SKILL.md:298High confidence
- Network access in code of the SKILL.mdskills/search-company-knowledge/SKILL.md:299High confidence
- Network access in code of the SKILL.mdsearch-company-knowledge/SKILL.md:299High confidence
- Network access in code of the SKILL.mdskills/search-company-knowledge/SKILL.md:300High confidence
- Network access in code of the SKILL.mdsearch-company-knowledge/SKILL.md:300High confidence
- Network access in code of the SKILL.mdskills/search-company-knowledge/SKILL.md:302High confidence
- Network access in code of the SKILL.mdsearch-company-knowledge/SKILL.md:302High confidence
- Network access in code of the SKILL.mdskills/search-company-knowledge/SKILL.md:303High confidence
- Network access in code of the SKILL.mdsearch-company-knowledge/SKILL.md:303High confidence
- Network access in code of the SKILL.mdskills/search-company-knowledge/SKILL.md:304High confidence
- Network access in code of the SKILL.mdsearch-company-knowledge/SKILL.md:304High confidence
- Network access in prose of the SKILL.mdskills/spec-to-backlog/SKILL.md:34Low confidence
- Network access in prose of the SKILL.mdspec-to-backlog/SKILL.md:34Low confidence
- Network access in prose of the SKILL.mdskills/spec-to-backlog/SKILL.md:35Low confidence
- Network access in prose of the SKILL.mdspec-to-backlog/SKILL.md:35Low confidence
- Network access in code of the SKILL.mdskills/spec-to-backlog/SKILL.md:276High confidence
and 275 more
Works with
| Agent | Status | Evidence | Install to |
|---|---|---|---|
| Claude Code | Native | Manifest .claude-plugin/marketplace.json | .claude/skills/<skill-name>/ |
| Codex | Compatible | Standard SKILL.md skills/atlassian-mcp-code-search/SKILL.md | .agents/skills/<skill-name>/ |
| Cursor | Compatible | Standard SKILL.md skills/atlassian-mcp-code-search/SKILL.md | .cursor/skills/<skill-name>/ |
| Gemini CLI | Native | Manifest gemini-extension.json | .gemini/skills/<skill-name>/ |
| GitHub Copilot | Compatible | Standard SKILL.md skills/atlassian-mcp-code-search/SKILL.md | .github/skills/<skill-name>/ |
| OpenCode | Compatible | Standard SKILL.md skills/atlassian-mcp-code-search/SKILL.md | .opencode/skills/<skill-name>/ |
- Native The repository ships a manifest, folder or frontmatter field for this agent.
- Compatible A standard SKILL.md that this agent can read.
- Unknown No evidence either way.
Derived automatically from paths, manifests and frontmatter. Not tested on each agent.
Add this badge to your README
It updates every night and links to this page.
[](https://hotskills.dev/skill/atlassian-atlassian-mcp-server/)