How do I install the Mk:jira Jsm skill?

Run npx skillmds@latest add ngocsangyem/mk-jira-jsm 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 Jsm 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 Jsm?

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 Jsm free to use?

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

Who published Mk:jira Jsm?

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

Mk:jira Jsm by ngocsangyem — Agent Skill

Name: Mk:jira Jsm
Author: ngocsangyem

Mk:jira Jsm

JIRA Service Management via the jira-as wrapper: service desks, request types, requests, customers, organizations, queues, SLAs, approvals (8 sub-domains). Triggers: 'create JSM request', 'list service desks', 'SLA status for KEY', 'approve request KEY', 'list queue NAME'. Requires JSM-licensed tenant + agent role. NOT for core Jira issue ops (mk:jira-issue); NOT for project admin (mk:jira-admin).

ngocsangyem Updated Sep 17, 2026

File contents

mk:jira-jsm

Forks to the jira-jsm agent. Service Management (JSM) operations — service desks, requests, SLAs, customers, organizations, queues, approvals, request types.

Triggers

"create JSM request in service desk 'IT Support'"
"list service desks"
"SLA status for KEY-123"
"approve request KEY-123"
"list queue 'Tier 1 Support'"
"add comment to JSM request KEY-123" (agent will confirm internal vs public)

Examples

Get service desk status: "show me the queues for service desk 'IT Support'"
Customer-facing comment: "add public comment to KEY-123: ''" → agent confirms internal-vs-public per safety-framework.

Required Permissions

JSM-licensed tenant + agent or admin role. Insufficient permission → exit code 3.

Limitations

8 sub-domains, ~45 verbs total — see jira-as jsm <sub-domain> --help for the authoritative flag list.
Internal-vs-public comments are a privacy concern; the agent enforces explicit confirmation before posting customer-facing content.

Gotchas

(none yet)

---name: mk-jira-jsmdescription: JIRA Service Management via the jira-as wrapper: service desks, request types, requests, customers, organizations, queues, SLAs, approvals (8 sub-domains). Triggers: 'create JSM request', 'list service desks', 'SLA status for KEY', 'approve request KEY', 'list queue NAME'. Requires JSM-licensed tenant + agent role. NOT for core Jira issue ops (mk:jira-issue); NOT for project admin (mk:jira-admin).---# mk:jira-jsmForks to the `jira-jsm` agent. Service Management (JSM) operations — service desks, requests, SLAs, customers, organizations, queues, approvals, request types.## Triggers- "create JSM request in service desk 'IT Support'"- "list service desks"- "SLA status for KEY-123"- "approve request KEY-123"- "list queue 'Tier 1 Support'"- "add comment to JSM request KEY-123" (agent will confirm internal vs public)## Examples- Get service desk status: "show me the queues for service desk 'IT Support'"- Customer-facing comment: "add public comment to KEY-123: '<message>'" → agent confirms internal-vs-public per safety-framework.## Required PermissionsJSM-licensed tenant + agent or admin role. Insufficient permission → exit code 3.## Limitations- 8 sub-domains, ~45 verbs total — see `jira-as jsm <sub-domain> --help` for the authoritative flag list.- Internal-vs-public comments are a privacy concern; the agent enforces explicit confirmation before posting customer-facing content.## See also- Agent: `../../agents/jira-jsm.md`- Shared: `../jira/references/{install-and-auth,cli-idioms,safety-framework}.md`- Domain refs: - `references/decision-tree.md` — when to use `mk:jira-jsm` vs `mk:jira-{issue,lifecycle,collaborate}` etc. - `references/itil-workflows.md` — ITIL 4 process implementations (incident / service-request / problem / change management)- Peer leaves: `mk:jira-collaborate` (internal-vs-public discipline applies on JSM tickets too), `mk:jira-lifecycle` (`patterns/jsm-request-workflow.md`), `mk:jira-admin` (request-type / queue config)## Gotchas- (none yet)

Frequently asked questions