jwmossmoz/jira
skills/jira/SKILL.md
Search, create, modify, comment, link, or transition issues in Mozilla JIRA (mozilla-hub.atlassian.net) via the extract_jira.py script. Markdown → ADF conversion is built in. Prefer this skill over the Atlassian MCP for JIRA work — it handles RELOPS defaults, sprint queries, comment edit/append, and bulk modify with dry-run.
$ install --global
skillsauthnpx skillsauth add jwmossmoz/agent-skills jiraInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 14, 2026, 7:04 AM162.9s4 files scanned
SKILL.md
- name:
- jira
- description:
- >
- version:
- 1.0
JIRA
Interact with Mozilla JIRA via scripts/extract_jira.py.
Prerequisites
export JIRA_API_TOKEN="your-api-token" # From https://id.atlassian.com/manage-profile/security/api-tokens
export JIRA_EMAIL="[email protected]"
Optional: JIRA_OUTPUT_DIR, JIRA_DEFAULT_PROJECT. Precedence: CLI args > env vars > config.toml > defaults.
Usage
uv run ~/.claude/skills/jira/scripts/extract_jira.py [options]
| Operation | Command |
|-----------|---------|
| Query current sprint | --current-sprint --summary |
| Query your issues | --my-issues |
| Query specific issue | --jql "key = RELOPS-123" |
| Create issue | --create --create-summary "Title" |
| Modify issue | --modify RELOPS-123 --set-status "In Progress" |
| Append description | --modify RELOPS-123 --append-description "New notes" |
| Edit comment | --modify RELOPS-123 --edit-comment 1242534 --comment-body "Updated content" |
| Link issues | --modify RELOPS-123 --link-issue RELOPS-456 |
| Output to stdout | --stdout --quiet |
Markdown Formatting
Use standard Markdown for descriptions and comments. The tool automatically converts Markdown to Atlassian Document Format (ADF).
DO NOT use old Jira wiki markup syntax like [text|url] - it will not render correctly.
| Element | Correct (Markdown) | Wrong (Wiki Markup) |
|---------|-------------------|---------------------|
| Links | [text](https://url) | [text\|https://url] |
| Bold | **text** | *text* |
| Lists | - item or 1. item | * item or # item |
| Code | `code` or code | {code}code{code} |
| Headings | ## Heading | h2. Heading |
Creating Stories
When creating JIRA stories, follow this workflow:
- Draft the story - Create the summary and description based on requirements
- Humanize the description - Use
/humanizerto remove AI writing patterns from the description text - Submit the story - Use the humanized description with
--create
Example Workflow
# 1. Draft description (you do this in memory)
# 2. Run humanizer on the description
# 3. Create story with humanized description
uv run ~/.claude/skills/jira/scripts/extract_jira.py --create \
--create-summary "Implement new feature" \
--description "The feature adds capability to process tasks. It handles edge cases and provides error handling." \
--epic-create RELOPS-2019
Use /humanizer to remove AI writing patterns from story descriptions before submitting.
Gotchas
- Use Markdown, not Jira wiki markup (
*bold*,[text|url],h2.). The script converts Markdown to ADF; wiki markup renders as raw text. - Run
/humanizeron the description before--create— JIRA stories surface to other humans, and AI tells. JIRA_API_TOKENis account-scoped.JIRA_EMAILmust match the token owner; mismatched email gives an opaque 401.- Default project is RELOPS via this skill. Pass
--jql "project = X AND ..."to query other projects.
Resources
- Full examples: references/examples.md
- All options:
uv run ~/.claude/skills/jira/scripts/extract_jira.py --help - Output:
~/moz_artifacts/jira_stories.json(default)
Related Skills
jwmossmoz/azure-cost-duckdb
development
VerifiedTrustedCommunity
Download Azure Cost Management exports and query local Parquet/CSV in DuckDB. Use when refreshing local Azure cost caches or writing DuckDB SQL over exports. DO NOT USE FOR live Cost Management API diagnosis; use azure-cost-analysis.
3SKILL.mdUpdated May 30, 2026
jwmossmoz/self-review
data-ai
VerifiedTrustedCommunity
Use when creating performance self-reviews from local notes, prior reviews, review prompts, and verified evidence. Helps draft H1/H2, annual, and promotion self evaluations, example answers, and rich review-form paste output. Do not use for routine status or 1:1 summaries; use one-on-one.
3SKILL.mdUpdated May 23, 2026
jwmossmoz/one-on-one
tools
VerifiedTrustedCommunity
Prepare one-on-one/status bullets from ~/moz_artifacts using qmd and copy a topic-organized HTML/RTF list with embedded links to the macOS clipboard. Use when summarizing recent Mozilla work for a manager, 1:1, or status update. DO NOT USE FOR generating raw daily logs; use daily-log.
3SKILL.mdUpdated May 20, 2026
jwmossmoz/worker-ready-tracing
development
VerifiedTrustedCommunity
Use when tracing Taskcluster Azure VM startup from worker-manager request through in-VM boot scripts to generic-worker `workerReady` with tc-logview, paperctl, Splunk Web, and Yardstick Prometheus. Applies to Windows worker provisioning latency. DO NOT USE FOR task failure triage (use worker-image-investigation).
3SKILL.mdUpdated May 16, 2026