← Back to Skills Marketplace
djc00p

Jira Ops

by Deonte Cooper · GitHub ↗ · v1.0.0 · MIT-0
linuxdarwinwin32 ✓ Security Clean
105
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install jira-ops
Description
Retrieve, analyze, and update Jira tickets directly. Supports MCP-based (recommended) and direct REST API approaches. Trigger phrases: fetch Jira ticket, upd...
README (SKILL.md)

Jira Integration

Retrieve, analyze, and update Jira tickets with MCP or direct REST API.

When to Activate

  • Fetching ticket requirements and acceptance criteria
  • Adding progress comments or status updates
  • Transitioning ticket status (To Do → In Progress → Done)
  • Searching for issues via JQL queries
  • Linking PRs or branches to tickets

Setup

Option A: MCP Server (Recommended)

Install mcp-atlassian via uvx:

{
  "jira": {
    "command": "uvx",
    "args": ["mcp-atlassian==0.21.0"],
    "env": {
      "JIRA_URL": "https://YOUR_ORG.atlassian.net",
      "JIRA_EMAIL": "[email protected]",
      "JIRA_API_TOKEN": "your-api-token"
    }
  }
}

Get your API token: https://id.atlassian.com/manage-profile/security/api-tokens

Option B: Direct REST API

Set these environment variables:

  • JIRA_URL — Jira instance URL
  • JIRA_EMAIL — Your account email
  • JIRA_API_TOKEN — API token (never hardcode)

MCP Tools

With mcp-atlassian configured:

  • jira_search — JQL queries
  • jira_get_issue — Fetch issue details
  • jira_create_issue — Create new issues
  • jira_update_issue — Update fields
  • jira_transition_issue — Change status
  • jira_add_comment — Add comments
  • jira_get_transitions — List available transitions

Analyzing Tickets

Extract from tickets:

  • Functional requirements — What needs to be built
  • Acceptance criteria — Testable conditions
  • Test types — Unit, integration, E2E
  • Edge cases — Error scenarios, boundary conditions
  • Dependencies — Linked issues, APIs, systems

Updating Tickets

Workflow Jira Action
Start work Transition to "In Progress" + comment branch name
Tests done Comment with test coverage summary
PR created Comment with link, transition if needed
Merged Transition to "Done"

Security

  • Never hardcode API tokens
  • Use environment variables or secrets manager
  • Add .env to .gitignore
  • Rotate tokens if exposed
  • Use least-privilege scopes
Usage Guidance
This skill appears to do what it says: read and update Jira issues. Before installing or enabling it, verify the following: 1) Only provide a Jira API token scoped with the minimum permissions needed (prefer read or limited write scopes), store it in a secrets manager or env var, and rotate it if exposed. 2) If you plan to use the MCP path, confirm you trust the 'uvx' tool and the 'mcp-atlassian' package source before installing—the SKILL.md recommends installation but the registry metadata does not declare uvx as a required binary. 3) Remember the agent (if allowed) can perform writes to your Jira project; consider restricting autonomous invocation or using a token with limited update rights for safer testing. 4) If you need higher assurance, request an install spec or package provenance from the publisher and test with a sandbox Jira project first.
Capability Analysis
Type: OpenClaw Skill Name: jira-ops Version: 1.0.0 The jira-ops skill bundle is a documentation-based integration for managing Jira tickets via MCP or REST API. It follows standard security practices, such as advising against hardcoding credentials and using environment variables for sensitive tokens. No malicious code, suspicious execution patterns, or exfiltration attempts were identified in SKILL.md or _meta.json.
Capability Assessment
ℹ Purpose & Capability
Name/description match the requested environment variables (JIRA_URL, JIRA_EMAIL, JIRA_API_TOKEN) and the described capabilities (search, fetch, update, transition). Minor inconsistency: SKILL.md recommends installing an MCP client via the 'uvx' tool, but the skill metadata does not declare 'uvx' as a required binary or provide an install spec.
✓ Instruction Scope
SKILL.md only instructs the agent to interact with Jira (via MCP tooling or direct REST API) and to use the declared environment variables. It does not ask the agent to read unrelated files, exfiltrate data to third parties, or access system paths outside the Jira integration context.
ℹ Install Mechanism
This is an instruction-only skill with no install spec or shipped code (lowest disk risk). It suggests using 'uvx' to install 'mcp-atlassian==0.21.0' but does not provide an install specification or provenance for that package; if you choose MCP, verify the uvx tool and package source before installing.
✓ Credentials
The three required environment variables (JIRA_URL, JIRA_EMAIL, JIRA_API_TOKEN) are appropriate and expected for a Jira integration. They are sensitive credentials, so least-privilege token scopes and secret storage are advised (the SKILL.md already recommends not hardcoding tokens).
✓ Persistence & Privilege
The skill does not request persistent system presence (always: false), does not modify other skills' configurations, and has no config-path requirements. It is user-invocable and may be called autonomously by the agent (platform default) but that is not unusual for skills.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install jira-ops
  3. After installation, invoke the skill by name or use /jira-ops
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release. Jira ticket retrieval, analysis, and updates via MCP or REST API. Adapted from everything-claude-code by @affaan-m (MIT)
Metadata
Slug jira-ops
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Jira Ops?

Retrieve, analyze, and update Jira tickets directly. Supports MCP-based (recommended) and direct REST API approaches. Trigger phrases: fetch Jira ticket, upd... It is an AI Agent Skill for Claude Code / OpenClaw, with 105 downloads so far.

How do I install Jira Ops?

Run "/install jira-ops" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Jira Ops free?

Yes, Jira Ops is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Jira Ops support?

Jira Ops is cross-platform and runs anywhere OpenClaw / Claude Code is available (linux, darwin, win32).

Who created Jira Ops?

It is built and maintained by Deonte Cooper (@djc00p); the current version is v1.0.0.

More Skills
self-improving agent
Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Clau...
⬇ 463283 · by pskoett
Skill Vetter
Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns.
⬇ 259410 · by spclaudehome
Polymarket
Query Polymarket prediction markets. Check odds, find trending markets, search events, track price movements.
⬇ 232503 · by joelchance
Self-Improving + Proactive Agent
Self-reflection + Self-criticism + Self-learning + Self-organizing memory. Agent evaluates its own work, catches mistakes, and improves permanently. Use when...
⬇ 200423 · by ivangdavila
Github
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
⬇ 191115 · by steipete
ontology
Typed knowledge graph for structured agent memory and composable skills. Use when creating/querying entities (Person, Project, Task, Event, Document), linkin...
⬇ 190156 · by oswalpalash

💬 Comments