Automatically filed by Claude (however, the problem is real)

Problem

The jira-ticket-creation skill (.agents/skills/jira-ticket-creation/SKILL.md, surfaced to agents through the tracked .claude/skills -> ../.agents/skills symlink) documents a jira_create_issue call that the Jira MCP tool rejects. An agent following the skill as written gets:

Jira API returned 400: {"errorMessages":[],"errors":{"project":"project is required"}}

The documented parameters do not match the tool's schema:

The skill also references a tool named jira_get_issue_MCP_DOCKER (line 201), which is not among the currently exposed tools.

Affected sections: the "Required Fields" block (lines 19-30), the "Example" block (lines 150-175), and the "Common Errors and Troubleshooting" section (lines 188-203), which tells the reader to use the same parameters that cause the failure.

How it got this way

The skill was imported wholesale from MMS in SERVER-122909 (aecfd92a0063, 2026-03-30). Its content has not been edited since; the only other commit touching it is the repo-wide prettier reformat in SERVER-124136 (3305c1e2ee3a). The MMS copy is presumably stale in the same way, so a fix applied only to the mongo copy risks being overwritten by the next import.

The staleness has gone unnoticed because the skill's own opening line directs readers to the jira-cli skill and treats the MCP path as a fallback for when the jira CLI is unavailable. On machines without the CLI installed, that fallback is the only path.

Suggested fix

Correct the three parameter names in the two code blocks and the troubleshooting section, and drop or rename the jira_get_issue_MCP_DOCKER reference. Worth checking whether the MMS original needs the same change so the two do not diverge.

Notes

Reported from a session that hit this while filing SERVER-135934. Filing rather than sending a PR because .agents/skills/OWNERS.yml assigns the ** catch-all to 10gen/devprod-build, with no per-skill override for jira-ticket-creation.