Individual skill
project-jira
Jira issue tracking and incident management. Use when creating, searching, or updating Jira issues. Supports JQL queries for incident ticket analysis and alert fatigue tracking.
sre-agent/.claude/skills/project-jira/SKILL.md
Source commit 2323af0551856ff4669b73dc36329d16aa19ed24
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 7, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 179
- Repository last updated
- Nov 9, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-sre Repository topic
- site-reliability-engineering Repository topic
- ai-agent Repository topic
- devops Repository topic
- episodic-memory Repository topic
- incident-investigation Repository topic
- incident-response Repository topic
- knowledge-graph Repository topic
- sre-agent Repository topic
- self-hosted Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 6,271 bytesSKILL.mdcore · 6,271 bytesSKILL.mdcore · 6,271 bytesSKILL.mdcore · 6,271 bytesSKILL.mdcore · 6,271 bytesSKILL.mdcore · 6,271 bytesSKILL.mdcore · 6,271 bytesSKILL.mdcore · 6,271 bytesSKILL.mdcore · 6,271 bytesSKILL.mdcore · 6,271 bytesscripts/add_comment.pyruns · 1,409 bytesscripts/create_issue.pyruns · 4,268 bytesscripts/get_issue.pyruns · 2,800 bytesscripts/jira_client.pyruns · 10,815 bytesscripts/list_issues.pyruns · 2,606 bytesscripts/markdown_to_adf.pyruns · 7,373 bytesscripts/search_issues.pyruns · 3,918 bytesscripts/update_issue.pyruns · 3,003 bytes
Read excerpt
# Jira Integration
## Authentication
**IMPORTANT**: In proxy/production mode, credentials are injected automatically by a proxy layer. Do NOT check for `JIRA_API_TOKEN` or `JIRA_EMAIL` in environment variables in that mode — they won't be visible to you. Just run the scripts directly; authentication is handled transparently.
In **direct/local mode** the scripts also support self-hosted Jira Data Center via a Personal Access Token (PAT). Set the following env vars (see `.env.example` for the full block):
- Cloud (atlassian.net): `JIRA_URL`, `JIRA_EMAIL`, `JIRA_API_TOKEN`. Leave `JIRA_AUTH_SCHEME`/`JIRA_API_VERSION` unset → defaults to Basic auth + REST API v3 (ADF bodies).
[Credential-related source omitted]
Do **not** set `JIRA_AUTH_SCHEME=bearer` for Cloud — Cloud API tokens require Basic auth (`email:token`). Bearer is for Data Center PATs only.
Configuration environment variables you CAN check (non-secret):