nexus-jira
Skill0 starsChanged 37 days agoApache-2.0View on GitHub
Use when creating, updating, transitioning, or commenting on jira issues via the nexus-jira MCP tools — the exact param surface, valid transitions, and parent rules. ~35 transcript-audited errors came from guessing this surface.
In this repository21 other files it gives its agents.
- browserbaseSkill
- cairnSkill
- developmentSkill
- dispatchSkill
- house-styleSkill
- kimi-subagentSkill
- lean-design-standardSkill
- mergeSkill
- nexus-authSkill
- orchestrateSkill
- orchestratorSkill
- planningSkill
- releaseSkill
- remote-opsSkill
- reviewSkill
- securitySkill
- specSkill
- ticket-pipelineSkill
- vision-reviewSkill
- workflow-basicsSkill
- writing-skillsSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
No parent field for Epics.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
nexus-jira MCP — the real tool surface
Reference distilled from the live tool schemas + transcript-audited failure signatures (2026-07-08). When in doubt, ToolSearch the schema — don't guess params.
Params that get guessed wrong (the failure class)
jira_comment(key, body)— exactly those names. NOTissue_key, NOTcomment(7 failures: "key and body are required"). Body is plain text; newlines become paragraphs.jira_update_status(key, status, comment?)— status by NAME from the workflow: To Do · In Progress · In Review · Done. There is no "Cancelled" (4 failures) — cancel = transition to Done with a comment saying cancelled/won't-do, or leave in To Do with a closing comment.jira_create(summary, issue_type, …)— required:summary,issue_type(one of Epic, Story, Task, Subtask, Bug). Optional:parent(issue KEY),project(KEY, e.g. "WKS"; defaults to the client's bound project),description(markdown — rendered as an ADF code block),labels,component.jira_update(key, …)— only provided fields are written.labels: []clears all labels;component: ""clears component; omit = unchanged.
Parent rules (8 failures: "Please select valid parent issue")
- Parent must be a valid hierarchy parent for the child type: Stories/Tasks/Bugs parent to an Epic; Subtasks parent to a Story/Task. A Story cannot parent a Story.
- The parent must exist in the same project you're creating into. Cross-project parenting fails.
- No parent field for Epics.
Project routing (4 failures: "target project doesn't exist or no permission")
- Omit
project→ the MCP client's bound project (aspect-dependent). Passprojectexplicitly when filing elsewhere (e.g. "WKS" for WakeStone) — and verify the key exists (jira_searchon it) before batch-creating; a bad key fails every create in the batch.
Cheap look-before-write
jira_get(key)before update/transition when state matters — transitions are state-dependent.jira_searchto confirm a project key or find a parent's key.- Batch-creating an epic + children: create the Epic first, capture its key, then children with
parent=<epic-key>— don't parallelize the children ahead of the parent existing.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

