How do I install the Mk:jira Admin skill?

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

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

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

Who published Mk:jira Admin?

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

Mk:jira Admin by ngocsangyem — Agent Skill

Name: Mk:jira Admin
Author: ngocsangyem

Mk:jira Admin

JIRA project / user / group / scheme / automation administration via the jira-as wrapper (11 sub-domains, ~65 verbs). Triggers: 'create JIRA project', 'list users', 'delete user USERNAME', 'list permission schemes', 'create group NAME'. Requires admin role. Destructive ops (project/user/group delete) require 2-step token confirmation. NOT for per-issue ops (mk:jira-issue / mk:jira-lifecycle); NOT for JSM admin (mk:jira-jsm).

ngocsangyem ff2dcc1 2 files · 11.9 KB Updated Sep 17, 2026

File contents

mk:jira-admin

Forks to the jira-admin agent. Highest-blast-radius leaf in the family.

Triggers

"create JIRA project"
"list users"
"delete user USERNAME"
"list permission schemes"
"create group NAME"
"enable automation rule X on PROJ"

Examples

Project create: "create project KEY 'Project Name' as Software-Scrum"
Project delete (DESTRUCTIVE): "delete project STAGING" → agent enforces 2-step token confirmation: human types literal project key to confirm.
User deactivate: "deactivate user alice@..." (preferred over delete — preserves attribution)

Required Permissions

Admin role. Insufficient permission → exit code 3.

DESTRUCTIVE Operations

project delete — IRREVERSIBLE
user delete — IRREVERSIBLE (use deactivate instead when possible)
group delete with members — affects member access globally

The agent enforces 2-step token confirmation for these. The skill triggers them via natural language; the agent never auto-executes without explicit human-typed confirmation.

Limitations

11 sub-domains, ~65 verbs total — see jira-as admin <sub-domain> --help for the authoritative flag list.

Gotchas

(none yet)

---name: mk-jira-admindescription: JIRA project / user / group / scheme / automation administration via the jira-as wrapper (11 sub-domains, ~65 verbs). Triggers: 'create JIRA project', 'list users', 'delete user USERNAME', 'list permission schemes', 'create group NAME'. Requires admin role. Destructive ops (project/user/group delete) require 2-step token confirmation. NOT for per-issue ops (mk:jira-issue / mk:jira-lifecycle); NOT for JSM admin (mk:jira-jsm).---# mk:jira-adminForks to the `jira-admin` agent. Highest-blast-radius leaf in the family.## Triggers- "create JIRA project"- "list users"- "delete user USERNAME"- "list permission schemes"- "create group NAME"- "enable automation rule X on PROJ"## Examples- Project create: "create project KEY 'Project Name' as Software-Scrum"- Project delete (DESTRUCTIVE): "delete project STAGING" → agent enforces 2-step token confirmation: human types literal project key to confirm.- User deactivate: "deactivate user alice@..." (preferred over delete — preserves attribution)## Required PermissionsAdmin role. Insufficient permission → exit code 3.## DESTRUCTIVE Operations- `project delete` — IRREVERSIBLE- `user delete` — IRREVERSIBLE (use `deactivate` instead when possible)- `group delete` with members — affects member access globallyThe agent enforces 2-step token confirmation for these. The skill triggers them via natural language; the agent never auto-executes without explicit human-typed confirmation.## Limitations- 11 sub-domains, ~65 verbs total — see `jira-as admin <sub-domain> --help` for the authoritative flag list.## See also- Agent: `../../agents/jira-admin.md`- Shared: `../jira/references/{install-and-auth,cli-idioms,safety-framework}.md`- Domain refs: - `references/voodoo-constants.md` — magic numbers (event IDs, scheme IDs, common custom field IDs) and how to discover yours- Peer leaves: `mk:jira-fields` (field admin overlap; `fields create` requires admin), `mk:jira-jsm` (JSM-specific admin lives in jira-jsm). Most users invoke `mk:jira-admin` once per project setup, then never again.## Gotchas- (none yet)

Frequently asked questions