Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From mk
Creates, reads, updates, and deletes single Jira issues (bugs, tasks, stories). Use for quick issue management without leaving the terminal.
How this skill is triggered — by the user, by Claude, or both
Slash command
/mk:jira-issueWhen to use
Use to create / read / update / delete a single Jira issue. NOT for state transitions (use mk:jira-lifecycle).
jira-issueThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Forks to the `jira-issue` agent (system prompt at `.claude/agents/jira-issue.md`). The skill body is the task brief — the host runtime injects this content into the forked agent.
Forks to the jira-issue agent (system prompt at .claude/agents/jira-issue.md). The skill body is the task brief — the host runtime injects this content into the forked agent.
../../agents/jira-issue.md../jira/references/{install-and-auth,cli-idioms,safety-framework}.mdreferences/issue-templates.md — canonical templates (Bug/Story/Epic/Task) + body markdownreferences/field-formats.md — ADF, user assignment, custom-field formatsreferences/decision-matrices.md — issue-type / priority / template decision tablesmk:jira-fields (custom field IDs), mk:jira-lifecycle (post-create transitions), mk:jira-collaborate (comments/attachments), mk:jira-relationships (linking)npx claudepluginhub ngocsangyem/meowkit --plugin mkCore JIRA issue CRUD - create bugs/tasks/stories, get issue details, update fields, delete issues. TRIGGERS: 'show me [KEY]', 'get issue [KEY]', 'view issue', 'create a bug/task/story', 'update [KEY]', 'delete [KEY]', 'details of [KEY]', 'look up [KEY]', 'what's in [KEY]'. NOT FOR: epics (use jira-agile), transitions/status changes (use jira-lifecycle), comments/attachments (use jira-collaborate), time tracking (use jira-time), bulk operations on 10+ issues (use jira-bulk), dependencies/blockers (use jira-relationships), branch names/PR descriptions (use jira-dev).
Creates, updates, and manages Jira issues from natural language via REST API or MCP server. Use for logging bugs, creating tickets, updating status, or handling backlogs.
Creates Jira issues via CLI flags or work-item files. Converts Markdown body to ADF, previews payload, requires confirmation, then POSTs to Jira.