atlassian-itsm

atlassian-itsm is a skill for Claude Code, Codex from automateyournetwork/netclaw. It costs 21 tokens per session (3,747 once invoked), scanned A, original, Apache-2.0.

A set of Jira and Confluence workflows for IT service management, covering operational issues, changes, incidents, and documentation.

In plain words
What is it for?
Use it to discover Jira projects and issue types, track incidents and changes, coordinate tasks, and create or maintain Confluence runbooks and postmortems.
Why use it?
It organizes service work in Jira and keeps runbooks, postmortems, and other operational knowledge in Confluence, with human confirmation for changes.

Skill for Claude CodeCodex

Which agent this was written for is unclear — built for openclaw. Also seen: built for openclaw.

Good fit Use it to discover Jira projects and issue types, track incidents and changes, coordinate tasks, and create or maintain Confluence runbooks and postmortems.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/automateyournetwork/netclaw/atlassian-itsm
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add automateyournetwork/netclaw --skill atlassian-itsm
Clone the repo
git clone --depth 1 https://github.com/automateyournetwork/netclaw

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for atlassian-itsm

README.md
[![agentmods](https://agentmods.dev/badge/skills/automateyournetwork/netclaw/atlassian-itsm/github.svg)](https://agentmods.dev/skills/automateyournetwork/netclaw/atlassian-itsm)
Your own site
<a href="https://agentmods.dev/skills/automateyournetwork/netclaw/atlassian-itsm"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/atlassian-itsm/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for atlassian-itsm

Your own site · 80×15
<a href="https://agentmods.dev/skills/automateyournetwork/netclaw/atlassian-itsm"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/atlassian-itsm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,747 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00021 $0.03747
Opus 5 $0.00010 $0.01873
Sonnet 5 $0.00004 $0.00749
Haiku 4.5 $0.00002 $0.00375

Measured 10d ago against content hash fc07783fa069, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

atlassian-itsm scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

workspace/skills/atlassian-itsm/SKILL.md · 424 lines

How it starts

The opening of the file, as written. The whole thing — 424 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Atlassian ITSM Skill

IT Service Management workflows using Jira for incident/change tracking and Confluence for runbooks, postmortems, and documentation.

Purpose

This skill provides ITSM-focused workflows for network operations teams using Atlassian tools:

  • Jira: Incident tracking, change requests, problem management, and task coordination
  • Confluence: Runbook documentation, postmortem reports, and knowledge base maintenance

All write operations require human-in-the-loop confirmation per Constitution XIV.

Jira Read Workflows (User Story 1)

Discovering Projects and Issue Types

Before creating or searching issues, discover the available projects and their issue types.

Step-by-step workflow:

  1. List accessible projects: Call jira_get_projects to see all projects the authenticated user can access
  2. Get project details: Call jira_get_project(project_key) for specific project configuration
  3. List issue types: Call jira_get_issue_types(project_key) to see available issue types (Bug, Task, Story, etc.)
  4. List available fields: Call jira_get_fields to see standard and custom fields

Example prompts:

  • "Show me all Jira projects I have access to"
  • "What issue types are available in project NET?"
  • "List the custom fields in our Jira instance"

Searching Issues with JQL

Search issues using Jira Query Language (JQL) for powerful filtering.

Step-by-step workflow:

  1. Construct JQL query: Build query using project, status, assignee, label, and date filters
  2. Execute search: Call jira_search(jql_query, max_results) with the JQL string
  3. Review results: Parse the returned issue list with key, summary, status, assignee

Common JQL patterns:

# Open issues in project NET assigned to me
project = NET AND assignee = currentUser() AND status != Done

# Critical/blocker issues created this week
project = NET AND priority IN (Critical, Blocker) AND created >= -7d

# Issues with specific label
project = NET AND labels = "outage"

# Unassigned issues in backlog
project = NET AND assignee IS EMPTY AND status = "To Do"

# Issues updated in the last 24 hours
project = NET AND updated >= -1d

Read the full file on GitHub · 424 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago First seen · 424 lines · 21 tokens per session scan A fc07783fa069

Subscribe to this mod's changes

atlassian-itsm is a skill published in the GitHub repository automateyournetwork/netclaw (652 stars, last pushed 3d ago), licensed Apache-2.0. It adds 21 tokens to every session and 3,747 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

Donchitos/Claude-Code-Game-Studios · 77 tokens

autotask-creator

Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.

Orkas-AI/Orkas · 5 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens