From mk
Routes ambiguous Jira tasks to the correct mk:jira-* leaf skill (issue, search, agile, etc.). Triggers on 'jira' or 'jira ticket' intents. Does not execute operations itself.
How this skill is triggered — by the user, by Claude, or both
Slash command
/mk:jiraWhen to use
Use when user has a Jira intent but the specific leaf isn't clear. NOT for direct execution — forward to mk:jira-{specific}.
The summary Claude sees in its skill listing — used to decide when to auto-load this 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.**
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.
| 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 |
See references/install-and-auth.md for one-time setup (.claude/scripts/bin/setup-workflow installs jira-as into .claude/skills/.venv; populate .claude/.env with the 3 MEOW_JIRA_* vars).
scripts/jira-as.sh — env-translating wrapper (MEOW_JIRA_* → JIRA_*, sets JIRA_OUTPUT=json)scripts/jql-sanitize.sh — JQL escaping for user-derived termsscripts/requirements.txt — pip dependency manifest auto-discovered by .claude/scripts/bin/setup-workflowreferences/install-and-auth.md — setup, exit codes, DC/mTLS caveatsreferences/cli-idioms.md — verified jira-as syntax + jq projection rulesreferences/safety-framework.md — 4-tier safety modelreferences/evaluation-rubric.md — used by mk:jira-evaluatorreferences/estimation-guide.md — used by mk:jira-estimatorreferences/field-discovery.md — used by mk:jira-fields (moved from jira/references/)mk:intake → recommends mk:jira-* leaf based on triagemk:cook (build pipeline) → may invoke mk:jira-issue to create implementation ticketsmk:ship (ship pipeline) → may invoke mk:jira-dev for branch-name + PR-descriptionmk: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 inputreferences/install-and-auth.md. The router does NOT auto-fallback.npx claudepluginhub ngocsangyem/meowkit --plugin mkJIRA automation hub routing to 13 specialized skills for any JIRA task: issues, workflows, agile, search, time tracking, service management, and more.
Manages Jira issues via CLI scripts: search, create, update, transition, comment, log work, manage sprints/boards, and handle attachments. Auto-triggers on Jira URLs and issue keys.