jira

Use this skill for any Jira operation in the DOCSP project — creating, viewing, searching, updating, transitioning, commenting on, or linking tickets. Also handles follow-up ticket creation to manage scope creep. TRIGGER when: user mentions a DOCSP-XXXXX ticket number or any Jira ticket URL; user asks to view, open, check, update, transition, close, comment on, link, or search tickets; user references "the ticket", "the Jira", or "open a ticket". SKIP: GitHub issues; non-Jira platforms; questions unrelated to ticket operations.

3.09x

Quality

—

Does it follow best practices?

Impact

99%

3.09x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with clear, validated workflows built around real CLI/MCP gotchas. Its main weakness is progressive disclosure: a single long file where reference-style tables could be split into bundle files, plus minor length-related conciseness concerns.

Suggestions

Move stable lookup tables (labels, story-point scale, custom-field mappings, resolution values) into a references/ file and link to it from SKILL.md so the main file stays a lean overview.

De-duplicate the closing guidance — required-close fields and the 'close from Internal/External Review' note are restated across the Ticket Lifecycle and Closing Issues sections.

Consolidate the trailing scattered flag notes (--plain, --raw, --csv, etc.) into the Non-Interactive Mode or CLI Gotchas section to reduce loose fragments.

Dimension	Reasoning	Score
Conciseness	The body is dense and almost entirely non-obvious operational knowledge (CLI gotchas, project-specific field keys, lifecycle), but at roughly 480 lines with some repetition around closing procedures it is longer than necessary; it is not level 3 because not every token earns its place, and not level 1 because it avoids explaining concepts Claude already knows.	2 / 3
Actionability	Provides fully executable CLI bash and MCP python examples with specific flags, field keys, and copy-paste-ready snippets across create/edit/transition/comment/link operations; it is not level 2 because the guidance is concrete and complete rather than pseudocode.	3 / 3
Workflow Clarity	Multi-step processes are clearly sequenced with validation checkpoints and feedback loops — tool selection with quick-fail fallback, closing issues with 'read the error for valid transition names' and 'use jira_search_fields' recovery, and a numbered scope-creep workflow with a confirmation step.	3 / 3
Progressive Disclosure	Content is well-organized into clear sections, but everything lives inline in one ~480-line file with no bundle references; large lookup tables (labels, story points, field mappings) that could be split into reference files are inline, so it is not level 3, though it avoids being a disorganized wall of text.	2 / 3
	Total	10 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, trigger-rich, complete, and well-scoped with explicit TRIGGER and SKIP guidance. It is a strong example of a skill description.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'creating, viewing, searching, updating, transitioning, commenting on, or linking tickets' plus 'follow-up ticket creation to manage scope creep' — matching the 'lists multiple specific concrete actions' anchor; it is not the level below because it goes well beyond naming only a domain and some actions.	3 / 3
Completeness	Clearly answers both what (Jira operations plus follow-up ticket creation) and when (explicit 'TRIGGER when' and 'SKIP' clauses); it is not level 2 because the when is explicit rather than merely implied.	3 / 3
Trigger Term Quality	Explicit TRIGGER clause covers natural user phrasing — 'DOCSP-XXXXX ticket number', 'Jira ticket URL', 'view, open, check, update, transition, close, comment on, link, or search tickets', and '"the ticket", "the Jira", or "open a ticket"' — giving good coverage of terms users would actually say.	3 / 3
Distinctiveness Conflict Risk	Scoped to the DOCSP project and Jira with a SKIP clause excluding 'GitHub issues; non-Jira platforms', giving it a clear niche unlikely to trigger for the wrong skill.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: mongodb/docs
Commit: e765459

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.