How do I install the Mk Jira skill?

Run npx skillmds@latest add ngocsangyem/mk-jira-3 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Mk Jira safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Mk Jira?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Mk Jira free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Mk Jira?

ngocsangyem (@ngocsangyem) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Mk Jira by ngocsangyem — Agent Skill

Name: Mk Jira
Author: ngocsangyem

File contents

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 (setup-workflow installs jira-as into .cursor/skills/.venv; populate .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 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.

---name: mk-jira-3description: 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.---# mk:jira — Routing SkillThis 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` |## SetupSee `references/install-and-auth.md` for one-time setup (`setup-workflow` installs `jira-as` into `.cursor/skills/.venv`; populate `.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 `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.

Frequently asked questions

Mk Jira