agentsclimarketplace

Mk jira jsm

Skill ngocsangyem/MeowKit/packages/mewkit/src/migrate/modules/cursor/root/.cursor/skills/mk-jira-jsm

JIRA Service Management via jira-as: service desks, requests, customers, orgs, queues, SLAs, approvals. Requires JSM tenant + agent role. NOT core issue ops (mk:jira-issue) or admin (mk:jira-admin).From its SKILL.md

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

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

1.8 KB, 422 tokens by cl100k_base, as published. Nobody here has run it

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: '<message>'" → 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.

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)

What ships with it: 2 files

16.0 KB alongside SKILL.md

references/

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.