← Voltar para o catálogo
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
Ver no GitHub ↗
Copiar URL do repo
Copiar link do SKILL.md Licença: MIT
Como adicionar
Copiar comando
/plugin marketplace add ngocsangyem/MeowKit
O comando exato pode variar conforme o repositório. Confira o README no GitHub.
Para o autor da skill
Cole no README do seu repo
Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.
[](https://www.skillteca.com.br/skills/mk-jira-admin)
Copiar snippet
利用AI大模型，一键生成高清短视频 Generate short videos with one click using AI LLM.
Automação
por harry0703
Creates an SVG weather card showing the current temperature for Dubai. Writes the SVG to orchestration-workflow/weather.svg and updates orchestration-workflow/output.md.
Automação
#ai
por shanraisshan
Automate Asana tasks via Rube MCP (Composio): tasks, projects, sections, teams, workspaces. Always search tools first for current schemas.
Automação
#git
#github
por sickn33
Integrate Stripe, PayPal, and payment processors. Handles checkout flows, subscriptions, webhooks, and PCI compliance. Use PROACTIVELY when implementing payments, billing, or subscription features.
Automação
#git
#github
por sickn33
Alerta por categoria
1 email curto, só com as skills novas de Automação. 4 minutos de leitura, sem spam, cancela com 1 clique.
Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.
Ler descrição completa Recolher descrição 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 — IRREVERSIBLEuser 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 yoursPeer 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
Compartilhar
X
LinkedIn
Copiar link
