atlassian SKILL.md skillA
atlassian from dreadnode/capabilities is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add dreadnode/capabilities/atlassian@git:20260728.e04a3aePins git:20260728.e04a3ae in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- dreadnode/capabilities
- Path
capabilities/atlassian/skills/atlassian/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260728.e04a3ae, committed Jul 28, 2026
- Size
- 4,702 bytes
- Repository stars
- 21
- License
- MIT
Use when the user wants to connect to Jira, Confluence, or Compass — search issues with JQL, read or create issues and pages, link content across products, or set up Atlassian auth. The connector — not security tradecraft.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Atlassian (Jira / Confluence / Compass) Connector for Atlassian Cloud via the official Rovo remote MCP — one server, three products. The agent sees the tool surface once it loads — this skill covers auth, the per-product query languages, and the idioms. Security triage methodology — dedup, severity, SLA, owner inference — is deliberately out of scope; pair this with whichever triage capability your workflow uses. ## Auth Native HTTP MCP with OAuth 2.1 + DCR; the runtime drives the flow, no `mcp-remote` bridge. Atlassian doesn't publish an RFC 9728 protected-resource document, so discovery resolves through the authorization-server metadata on `mcp.atlassian.com`, which points at `cf.mcp.atlassian.com` for authorize/token/register. Nothing to configure — but if you're debugging a failed connect, that's the chain to walk, and it's why the `.well-known/ oauth-protected-resource` probes you'd try first come back 404. ### A. OAuth 2.1 (default) On first connect, `atlassian` shows in Services as `needs authentication`. Click **Authenticate** → browser → sign in and grant the Rovo scopes; tokens persist to …
Read the whole file at its exact version.
How to install
mdr add dreadnode/capabilities/atlassian@sha256:09050f7aad19389dThe line at the top of this page pins the label git:20260728.e04a3ae, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_2tscs4itjraidng4)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jul 28, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4702 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
dreadnode/capabilities · 21 stars · license MIT · pushed 2026-11-02 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_2tscs4itjraidng4 GET https://markdownregistry.com/api/v1/resolve?ref=dreadnode/capabilities/atlassian GET https://markdownregistry.com/api/v1/blob/09050f7aad19389d599db59b1faeecf803129c01a6e09dd59e67a535bd09689f
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from dreadnode/capabilities
Every file in dreadnode/capabilities