mcpField
A
atlassian

atlassian

github.com/i9wa4Productivity1269 installsUpdated 1d ago
Repository

About atlassian

A skill for using Jira and Confluence through API requests when Atlassian credentials may be available. It emphasizes checking credentials, starting with read-only access, and confirming the target and change before writes.

Key features

  1. 01Check whether environment variables are set
  2. 02Make targeted Jira REST requests
  3. 03Make targeted Confluence REST requests
  4. 04Confirm targets and changes before writes
  5. 05Report access status with minimal evidence

Use cases

  1. 01Check a Jira issue's status and summary
  2. 02Search Confluence pages or spaces
  3. 03Update an issue or page after confirmation
  4. 04Identify authentication, permission, or network blocks

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/i9wa4/dotfiles --skill atlassian

After installing, type/atlassianin Claude Code to confirm it loaded.

Bundled filesreferences/api-token.mdreferences/usage.md

Details

From the project README

Atlassian

Use this skill when a task asks to use Jira or Confluence and the environment may already contain Atlassian credentials. Treat credentials as available only after confirming required variables are present.

Read Usage before authenticated Atlassian requests.

1. Required Env

  • ATLASSIAN_SITE: Atlassian Cloud site URL.
  • ATLASSIAN_EMAIL: account email for API token auth.
  • ATLASSIAN_API_TOKEN: Atlassian API token.
  • ATLASSIAN_CLOUD_ID: optional for Confluence APIs that require cloud id.

If ATLASSIAN_API_TOKEN is missing, follow API Token.

Check presence, not values. Use the reference command or an equivalent that prints only set or missing. Never print credential values, authorization headers, cookies, or shell traces.

2. Workflow

  • Confirm required env vars before access. Do not infer access from a URL.
  • Jira: use targeted REST calls for issues, searches, comments, transitions, or metadata; for access checks request minimal fields like summary,status.
  • Confluence: use targeted REST calls for pages, search, comments, or spaces; request only the body representation required by the task.
  • Prefer read-only checks first. For writes, confirm the exact issue or page and summarize the intended change before executing.

3. Reporting

State whether access is readable, blocked by auth, blocked by permissions, blocked by network, or not found. Include minimal evidence only, such as Jira issue key/title/status or Confluence page id/title/status plus HTTP result.

Comments

Markdown supported