How do I install the Adynato Atlassian skill?

Run npx skillmds@latest add adynato/adynato-atlassian in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Adynato Atlassian safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Adynato Atlassian?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Adynato Atlassian free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Adynato Atlassian?

adynato (@adynato) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Adynato Atlassian by adynato — Agent Skill

Name: Adynato Atlassian
Rating: 4.5 (4 reviews)
Author: adynato

Adynato Atlassian

Work with Jira, Confluence, and Atlassian Cloud links via Atlassian MCP instead of browser automation. Covers reading `atlassian.net` URLs, preferring MCP over Puppeteer for tickets and pages, summarizing issue state and comments, and falling back only when visual inspection is explicitly needed or MCP is unavailable. Use when a prompt includes Jira tickets, Confluence pages, or Atlassian links.

adynato Updated Sep 10, 2026

File contents

Atlassian Skill

Use this skill when a prompt includes Jira tickets, Confluence pages, or atlassian.net links.

Prefer Atlassian MCP for Atlassian Links

If the user provides an atlassian.net link, use Atlassian MCP to read it first
Do not default to Puppeteer or browser automation just to inspect Jira or Confluence content
Prefer MCP because it returns structured, authenticated Atlassian data instead of brittle rendered UI
Use browser automation only if the user explicitly asks for a visual/UI check or Atlassian MCP is genuinely unavailable after confirming setup

Ticket Handling Workflow

When reading a Jira issue through Atlassian MCP, capture the parts the next decision depends on:

Issue key and summary
Status, assignee, priority, and type
Description, acceptance criteria, reproduction notes, or implementation details
Recent comments, blockers, and open questions
Linked issues, related pages, or dependent work when relevant

Prefer MCP follow-up queries over manually clicking through browser pages.

Confluence and Related Context

Use Atlassian MCP for Confluence page content when a page link is provided
Follow linked Jira or Confluence context through MCP when it matters to the task
Avoid scraping rendered HTML when structured content is available from MCP

If Atlassian MCP Is Not Set Up

Prefer setting up Atlassian MCP in .omp/mcp.json rather than using the browser as the default workaround
Follow the repo-local setup conventions in adynato-omp-mcp
Do not act like browser automation is an equivalent replacement for authenticated MCP access

Atlassian Rovo MCP Endpoint

Use the official endpoint for new setups:

https://mcp.atlassian.com/v1/mcp

Prefer /mcp for new configurations; Atlassian is deprecating /sse.

---name: adynato-atlassiandescription: Work with Jira, Confluence, and Atlassian Cloud links via Atlassian MCP instead of browser automation. Covers reading `atlassian.net` URLs, preferring MCP over Puppeteer for tickets and pages, summarizing issue state and comments, and falling back only when visual inspection is explicitly needed or MCP is unavailable. Use when a prompt includes Jira tickets, Confluence pages, or Atlassian links.---# Atlassian SkillUse this skill when a prompt includes Jira tickets, Confluence pages, or `atlassian.net` links.## Prefer Atlassian MCP for Atlassian Links- If the user provides an `atlassian.net` link, use Atlassian MCP to read it first- Do not default to Puppeteer or browser automation just to inspect Jira or Confluence content- Prefer MCP because it returns structured, authenticated Atlassian data instead of brittle rendered UI- Use browser automation only if the user explicitly asks for a visual/UI check or Atlassian MCP is genuinely unavailable after confirming setup## Ticket Handling WorkflowWhen reading a Jira issue through Atlassian MCP, capture the parts the next decision depends on:- Issue key and summary- Status, assignee, priority, and type- Description, acceptance criteria, reproduction notes, or implementation details- Recent comments, blockers, and open questions- Linked issues, related pages, or dependent work when relevantPrefer MCP follow-up queries over manually clicking through browser pages.## Confluence and Related Context- Use Atlassian MCP for Confluence page content when a page link is provided- Follow linked Jira or Confluence context through MCP when it matters to the task- Avoid scraping rendered HTML when structured content is available from MCP## If Atlassian MCP Is Not Set Up- Prefer setting up Atlassian MCP in `.omp/mcp.json` rather than using the browser as the default workaround- Follow the repo-local setup conventions in `adynato-omp-mcp`- Do not act like browser automation is an equivalent replacement for authenticated MCP access## Atlassian Rovo MCP EndpointUse the official endpoint for new setups:```texthttps://mcp.atlassian.com/v1/mcp```Prefer `/mcp` for new configurations; Atlassian is deprecating `/sse`.

Frequently asked questions