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.

6.69x

Quality

88%

Does it follow best practices?

Impact

87%

6.69x

Average score across 2 eval scenarios

Securityby

Low

Low-risk findings worth noting

Quality

Content

77%Weight 40%Scale 1-3

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 concrete commands and clear, validated workflows, and it correctly assumes Claude's competence rather than explaining basics. Its main weaknesses are length/repetition and a monolithic structure with no progressive file separation.

Suggestions

Consolidate the Common Operations section — the dual CLI/MCP examples repeat patterns already shown in Creating Issues; cross-reference instead of re-listing to reduce tokens.

Move detailed reference catalogs (custom-field mappings, label tables, story-point scale, link types) into a separate reference file (e.g. references/fields.md) and link from SKILL.md to enable progressive disclosure.

Add a brief verification step after create/edit operations (e.g. re-view the ticket to confirm the change applied) to complement the existing error-recovery checkpoints for transitions and closing.

Dimension	Reasoning	Score
Conciseness	The body is overwhelmingly project-specific operational knowledge (field keys, transition names, gotchas) rather than concepts Claude already knows, but at ~490 lines the dual CLI/MCP examples and the long Common Operations catalog repeat patterns and could be tightened.	2 / 3
Actionability	Provides fully executable, copy-paste-ready CLI commands and MCP calls with real flags and field keys (e.g., '--custom "story-points=3"', 'customfield_27258'), matching the anchor for concrete executable guidance.	3 / 3
Workflow Clarity	Multi-step processes (tool selection/fallback, closing issues, scope-creep follow-ups) are clearly sequenced with checkpoints — authorization before changes, required-fields guidance, and explicit error-recovery loops ('read the error for valid transition names', 'use jira_search_fields').	3 / 3
Progressive Disclosure	Sections are well-organized with clear headers and tables, but the skill is a single ~490-line monolithic file with no bundle references; detailed catalogs (labels, custom fields, story-point scale, link types) are inline and could be split into reference files.	2 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 strong across all dimensions: it enumerates concrete actions, provides natural-language triggers and exclusions, and is tightly scoped to DOCSP Jira operations. It clearly answers both what the skill does and when to invoke it.

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 anchor for enumerating several specific operations.	3 / 3
Completeness	Explicitly answers what ('any Jira operation ... creating, viewing, searching ...') and when ('TRIGGER when: user mentions a DOCSP-XXXXX ticket number ...') with an explicit SKIP exclusion list, satisfying both halves.	3 / 3
Trigger Term Quality	Covers natural terms users would say — 'DOCSP-XXXXX ticket number', 'Jira ticket URL', 'view, open, check, update, transition, close, comment on, link, or search', and colloquial 'the ticket', 'the Jira', 'open a ticket'.	3 / 3
Distinctiveness Conflict Risk	Scoped to a clear niche (Jira operations in the DOCSP project) with distinct triggers (DOCSP-XXXXX, Jira ticket URLs) and explicit skip conditions for GitHub issues and non-Jira platforms, making conflict unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 2 missing	Warning

	Total	15 / 16 Passed

Repository: mongodb/docs
Path: .claude/skills/jira/SKILL.md
Commit: 96839d3

Reviewed: 5 days 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.