# 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).

- Skill: `ngocsangyem/mk-jira-admin` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add ngocsangyem/mk-jira-admin`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ngocsangyem/mk-jira-admin/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: ngocsangyem (https://skillmd.com/u/ngocsangyem)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/ngocsangyem/mk-jira-admin

---


# 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.

## 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)