Mk jira ops
Skill ngocsangyem/MeowKit/packages/mewkit/src/migrate/modules/cursor/root/.cursor/skills/mk-jira-ops
JIRA-side cache + project-context discovery via jira-as, diagnostic-only, no Atlassian state changes. NOT issue CRUD or project admin (mk:jira-admin).From its SKILL.md
npx -y skills add ngocsangyem/MeowKit --skill mk-jira-opsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 15 stars15 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.2 KB, 280 tokens by cl100k_base, as published. Nobody here has run it
mk:jira-ops
Forks to the jira-ops agent. Diagnostic surface only.
Triggers
- "jira cache status"
- "clear jira cache"
- "discover project context for PROJ"
Examples
- Cache check: "is the jira-as cache fresh?"
- Cache clear: "clear the cache, my admin renamed a status"
- Discovery: "what's the default issue type and mandatory field set for PROJ?"
Power-User Note
cache-warm is intentionally NOT exposed as a primary trigger. If a user explicitly needs it, they can invoke directly:
bash $(git rev-parse --show-toplevel)/.cursor/skills/jira/scripts/jira-as.sh ops cache-warm --project PROJ
See also
- Agent:
../../agents/jira-ops.md - Shared:
../jira/references/{install-and-auth,cli-idioms,safety-framework}.md - Domain refs:
references/rate-limits.md— Atlassian rate-limit ceilings + back-off behaviour
- Peer leaves: any leaf hitting Atlassian-side throttling first lands here for diagnosis.
mk:jira-bulkis the most common trigger for cache-warm + rate-limit awareness.
Gotchas
- (none yet)
What ships with it: 1 file
2.2 KB alongside SKILL.md
references/
- rate-limits.md2.2 KB