Official agent skill

Run Jira

by DataDog in DataDog/datadog-agent

Fetch a Jira issue and propose an implementation plan based on codebase analysis

OfficialApache-2.0Auto-check passedAgent Workflows

Install Run Jira

skills CLI
$ npx skills add DataDog/datadog-agent --skill run-jira -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install DataDog/datadog-agent run-jira --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/DataDog/datadog-agent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/run-jira .claude/skills/run-jira && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
run-jira
GitHub stars
3.8k
Token cost
~635 tokens
SKILL.md length
303 words
Files
1
Skills in repo
35
Repo updated
First seen
Licence
Apache-2.0

At a glance

Fetch a Jira issue and propose an implementation plan based on codebase analysis

  • Works in 5 steps: Gather Jira issue data → Summarize the issue → Fetch linked resources → …
  • Tasks that involve Planning
  • SKILL.md covers Step 1: Gather Jira issue data, Step 2: Summarize the issue, Step 3: Fetch linked resources and Step 4: Analyze the codebase, plus 1 more section
  • Calls gh

What it does

Run Jira is an agent skill from DataDog/datadog-agent, published by the product's own GitHub organization. Fetch a Jira issue and propose an implementation plan based on codebase analysis

Its SKILL.md is about 640 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering Planning and Codebase onboarding. It works with Jira, Datadog and Model Context Protocol. The repository describes itself as: Main repository for Datadog Agent. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Planning
  • Tasks that involve Codebase onboarding

Example prompts

  • “/run-jira”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Gather Jira issue data
  2. Summarize the issue
  3. Fetch linked resources
  4. Analyze the codebase
  5. Propose an implementation

What it can do on your machine

Read from SKILL.md and the folder at commit a706f1a. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • datadoghq.atlassian.net

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Run Jira loads about 635 tokens when it runs. Until then it costs about 22 tokens; SKILL.md has 303 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~22
When it runs · the whole SKILL.md, loaded when a task matches
~635

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from DataDog/datadog-agent at commit a706f1a, republished under its Apache-2.0 licence (© DataDog). 303 words, ~635 tokens.

Download SKILL.mdSave it as .claude/skills/run-jira/SKILL.md (or your agent's skills folder).
name
run-jira
description
Fetch a Jira issue and propose an implementation plan based on codebase analysis
argument-hint
<JIRA-KEY e.g. ACTP-1234>
model
sonnet

Fetch the Jira issue $ARGUMENTS from the Datadog Atlassian instance and use it as the basis for a codebase analysis and implementation proposal.

Step 1: Gather Jira issue data

Use the Atlassian MCP tools to fetch the issue. Only request the fields you need to avoid huge responses:

  1. Call mcp__atlassian__getJiraIssue with:
    • cloudId: datadoghq.atlassian.net
    • issueIdOrKey: $ARGUMENTS
    • fields: ["summary", "description", "status", "assignee", "issuetype", "comment", "priority"]
  2. Extract the title (summary), description, status, assignee, and comments from the response.

If the issue cannot be found, stop and inform the user.

Step 2: Summarize the issue

Present a clear summary of the Jira issue:

Step 3: Fetch linked resources

Scan the issue description and comments for links to external resources and fetch them for additional context:

  • Datadog notebooks / postmortems (app.datadoghq.com/notebook/<id>): use mcp__datadog-mcp__get_datadog_notebook with the notebook ID
  • GitHub PRs (github.com/.../pull/<number>): use gh pr view <number> via Bash
  • GitLab commits/pipelines or other URLs: use WebFetch if accessible

This step is critical — linked resources often contain the root cause analysis, timelines, and technical details that the Jira description alone does not capture.

Step 4: Analyze the codebase

Based on the issue requirements and linked resources, explore the codebase to understand:

  • Which files and packages are relevant
  • Existing patterns and conventions that should be followed
  • Dependencies and potential impacts

Use Glob, Grep, and Read tools extensively. For broad exploration, use the Task tool with subagent_type=Explore.

Step 5: Propose an implementation

Enter plan mode with EnterPlanMode and write a detailed implementation plan that includes:

  • A breakdown of the changes needed, organized by file
  • Any new files that need to be created
  • Test strategy
  • Potential risks or open questions

Wait for user approval before implementing.

© DataDog, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/run-jira of DataDog/datadog-agent.

Open the folder on GitHubat commit a706f1a

Compare with similar skills

Run Jira next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Run Jira compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Run Jira this skillDataDog/datadog-agent3.8k—~635Automated safety check: PassApache-2.0
Piv Plan Implementationcoleam00/skills674—~4.9kAutomated safety check: PassMIT
Codex with ChatGPT Planning LoopXiaoDuoYa/codex-with-chatgpt7.1k—~11kAutomated safety check: NotesMIT
CodegraphcontextCodeGraphContext/CodeGraphContext4.3k—~675Automated safety check: NotesMIT
Agentic Tool Integrationsamugit83/redamon3k—~1.3kAutomated safety check: PassMIT
Codebase SearchHelweg/open-codebase-index216—~1.3kAutomated safety check: PassMIT

Similar skills

  • Creates a comprehensive, context-rich implementation plan through deep codebase analysis, a short clarifying interview, and external research.

    674 GitHub stars~4.9k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Codex with ChatGPT Planning Loop

    XiaoDuoYa/codex-with-chatgpt

    Uses ChatGPT in the browser as the planning and review brain for a Codex session, with Codex keeping all execution and ChatGPT reading the workspace through a bridge.

    7.1k GitHub stars~11k tokensUpdated 8 days ago
    Agent WorkflowsAuto-check: notes
  • Codegraphcontext

    CodeGraphContext/CodeGraphContext

    Use CodeGraphContext (CGC) to index a repo into a graph DB and query it via CLI or MCP.

    4.3k GitHub stars~675 tokensUpdated 9 days ago
    Agent WorkflowsAuto-check: notes
  • Agentic Tool Integration

    samugit83/redamon

    Wiring a new tool the AI agent can call (not the recon pipeline): the tool registry, the phase map, the hardcoded dispatch chokepoint, and the duplicated execution paths that make a tool work in…

    3k GitHub stars~1.3k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Codebase Search

    Helweg/open-codebase-index

    Chooses the right retrieval tool for code questions: compact context for unfamiliar repos, direct lookup for known symbols, call graphs for relationships and grep for exhaustive matches.

    216 GitHub stars~1.3k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • agtx Task Planning

    fynnfluegge/agtx

    Analyzes the codebase for an agtx task, writes a plan with analysis, steps and risks to .agtx/plan.md, then stops and waits for approval before any change.

    1.7k GitHub stars~439 tokensUpdated 6 days ago
    Agent WorkflowsAuto-check passed

More from DataDog/datadog-agent

All 35 skills in this repo
  • Triage CI Failure

    DataDog/datadog-agent

    Official

    Classify a failed CI as either caused by an active incident, flakiness, or a true code regression.

    3.8k GitHub stars~2.3k tokensUpdated today
    Auto-check passed
  • Elicit

    DataDog/datadog-agent

    Official

    Run a structured discovery session to build an Allium specification through conversation.

    3.8k GitHub starsUsed in 1 repo~3.7k tokens
    Auto-check passed
  • Follow PR

    DataDog/datadog-agent

    Official

    Monitor the current PR's GitLab pipeline to completion, then report success, auto-fix, or investigate a failure.

    3.8k GitHub stars~3.2k tokensUpdated today
    Auto-check passed
  • Create Epic Recap

    DataDog/datadog-agent

    Official

    A skill your agent uses when an engineer or manager asks to recap, summarize, or post an update on a Jira Epic — a progress update for an in-progress Epic (how far along it is, what's shipped so…

    3.8k GitHub stars~5k tokensUpdated today
    Auto-check: notes
  • Explain Lading Config

    DataDog/datadog-agent

    Official

    Explains a lading.yaml config file from the regression test suite, using the lading Rust source as ground truth for field meanings and defaults.

    3.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Distill

    DataDog/datadog-agent

    Official

    Extract an Allium specification from an existing codebase. An agent skill from DataDog/datadog-agent.

    3.8k GitHub starsUsed in 1 repo~7k tokens
    Auto-check passed

Categories

Questions about Run Jira

What does Run Jira do?

Fetch a Jira issue and propose an implementation plan based on codebase analysis. Run Jira is an agent skill from DataDog/datadog-agent, published by the product's own GitHub organization.

When should I use Run Jira?

Run Jira fits situations like: tasks that involve Planning; tasks that involve Codebase onboarding.

How do I install Run Jira in Claude Code?

Run `npx skills add DataDog/datadog-agent --skill run-jira -a claude-code`. Or copy the skill folder (.agents/skills/run-jira in DataDog/datadog-agent) into .claude/skills/run-jira in your project. Claude Code loads it when a task matches its description.

How do I install Run Jira in Codex?

Run `npx skills add DataDog/datadog-agent --skill run-jira -a codex`. Or copy the skill folder (.agents/skills/run-jira in DataDog/datadog-agent) into .agents/skills/run-jira in your project. Codex loads it when a task matches its description.

Can I use Run Jira in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add DataDog/datadog-agent --skill run-jira -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/run-jira, .gemini/skills/run-jira, .github/skills/run-jira and .opencode/skills/run-jira in your project.

What does Run Jira need to run?

Going by SKILL.md and its folder, Run Jira needs the command-line tools its instructions call (gh).

Does Run Jira access the network?

SKILL.md names 1 domain. As links in the text: datadoghq.atlassian.net. This is read from the text; nothing was executed.

Is Run Jira safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Run Jira use?

Run Jira is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Run Jira use?

About 635 tokens (SKILL.md is roughly 2.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Run Jira?

Skills that share tags, products or a category with Run Jira: Piv Plan Implementation (coleam00/skills, 674 stars), Codex with ChatGPT Planning Loop (XiaoDuoYa/codex-with-chatgpt, 7.1k stars), Codegraphcontext (CodeGraphContext/CodeGraphContext, 4.3k stars) and Agentic Tool Integration (samugit83/redamon, 3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Run Jira?

DataDog (a GitHub organization, an official publisher) maintains it in DataDog/datadog-agent, which has 3,759 GitHub stars. The repository holds 35 skills in this directory. The repository was last updated on October 9, 2026.

Source: DataDog/datadog-agent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.