Mk jira

Skill ngocsangyem/MeowKit/packages/mewkit/src/migrate/modules/codex/root/.agents/skills/mk-jira

Routing skill — recommends the correct mk:jira-* leaf for any Jira task. Triggers: 'jira', 'jira ticket', ambiguous Jira intent. NOT an executor — every actual operation forks via a leaf skill.From its SKILL.md

Install

npx -y skills add ngocsangyem/MeowKit --skill mk-jira

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

14 stars14 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.6 KB, 889 tokens by cl100k_base, as published. Nobody here has run it

mk:jira — Routing Skill

This skill is a pure routing layer. Its sole purpose: identify the right mk:jira-* leaf for the user's Jira task, then point at it. No execution.

Routing Table

User intent	Leaf skill
Get/create/update/delete a single issue	`mk:jira-issue`
Find issues by criteria; export; filters	`mk:jira-search`
Transition through workflow; assign; resolve	`mk:jira-lifecycle`
Comments, attachments, watchers, notify	`mk:jira-collaborate`
Issue links, blockers, dependencies	`mk:jira-relationships`
Worklogs, time tracking, time reports	`mk:jira-time`
Epics, sprints, backlog, story points	`mk:jira-agile`
Custom field discovery + configuration	`mk:jira-fields`
Bulk ops (10+ issues, dry-run mandatory)	`mk:jira-bulk`
Service Management (queues, SLAs, customers)	`mk:jira-jsm`
Project/user/group/scheme administration	`mk:jira-admin`
Git/PR/branch-name integration	`mk:jira-dev`
Cache + project-context discovery	`mk:jira-ops`
Evaluate ticket complexity + inconsistencies	`mk:jira-evaluator`
Estimate story points (heuristic)	`mk:jira-estimator`
Analyze ticket context + media; RCA	`mk:jira-analyst`

Setup

See references/install-and-auth.md for one-time setup (.codex/scripts/bin/setup-workflow installs jira-as into .agents/skills/.venv; populate .codex/.env with the 3 MEOW_JIRA_* vars).

Shared Resources (used by leaves)

scripts/jira-as.sh — env-translating wrapper (MEOW_JIRA_* → JIRA_*, sets JIRA_OUTPUT=json)
scripts/jql-sanitize.sh — JQL escaping for user-derived terms
scripts/requirements.txt — pip dependency manifest auto-discovered by .codex/scripts/bin/setup-workflow
references/install-and-auth.md — setup, exit codes, DC/mTLS caveats
references/cli-idioms.md — verified jira-as syntax + jq projection rules
references/safety-framework.md — 4-tier safety model
references/evaluation-rubric.md — used by mk:jira-evaluator
references/estimation-guide.md — used by mk:jira-estimator
../jira-fields/references/field-discovery.md — used by mk:jira-fields (moved from jira/references/)

Handoff

mk:intake → recommends mk:jira-* leaf based on triage
mk:cook (build pipeline) → may invoke mk:jira-issue to create implementation tickets
mk:ship (ship pipeline) → may invoke mk:jira-dev for branch-name + PR-description
mk:planning-engine → consumes Jira tickets via this hub for sprint planning analysis (mk:jira-evaluator / mk:jira-estimator outputs enrich the planning report)
mk:confluence → sister hub for Confluence Cloud; mk:planning-engine accepts both Jira tickets (--tickets) and Confluence specs (--spec <report-path>) as input

Gotchas

mk:jira itself never executes; if you're in this skill thinking about jira-as commands, you're in the wrong place — forward to a leaf.
Escape hatch: if jira-as is unusable (mTLS, multi-profile), users may invoke Atlassian MCP directly per references/install-and-auth.md. The router does NOT auto-fallback.

What ships with it: 9 files

30.9 KB alongside SKILL.md, 3 of them executable