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.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

71%Weight 40%Scale 1-5

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

A well-structured, project-specific skill body with concrete enums, clear workflows, and validation checkpoints. Its main weakness is progressive disclosure: the body points to three reference files that do not exist in the bundle.

Suggestions

Ship the missing reference files (references/cli.md, references/mcp-atlassian.md, references/devprod-gateway.md) so the body's deferrals resolve — or inline the minimal per-tool syntax each section needs.

Consolidate the repeated 'see your tool's reference file' pointers into a single per-tool reference link near each section header to reduce redundancy.

Tighten the memory-write table, which currently duplicates filename, slug, body, and MEMORY.md line across three near-identical rows.

Dimension	Reasoning	Score
Conciseness	The body is dense project-specific knowledge (enums, tables, decision rules) with no padding about concepts Claude already knows; only minor repetition of 'see your tool's reference file' and the elaborate memory-write table could be trimmed. Efficient with minor over-explanation that could be tightened; not a 5 because the tool-selection and memory sections are somewhat elaborate.	4 / 5
Actionability	Provides concrete enums (resolutions, labels, story-point scale, link types, priorities) and executable probe commands ('which jira && jira me'); the actual per-tool command syntax is deferred to reference files, leaving minor gaps. Mostly actionable and specific; not a 5 because copy-paste-ready tool commands live in the separate reference files rather than the body.	4 / 5
Workflow Clarity	Multi-step processes (tool selection 1-5, scope-creep 1-5) are clearly sequenced with validation checkpoints (confirm PR merged, check Story Points before close, plan+confirm before changes) and a quick-fail fallback feedback loop. Clear sequence with most checkpoints present and an error-recovery loop; not a 5 because transition-name lookup and some validation are deferred to reference files.	4 / 5
Progressive Disclosure	Sections are well-organized and tool-specific detail is deferred one level deep to references/cli.md, references/mcp-atlassian.md, and references/devprod-gateway.md — but those reference files are not present in the bundle, so the referenced navigation is broken. Structure and signaling are good, but the missing bundle files cap the score at 3.	3 / 5
	Total	15 / 20 Passed

Description

100%Weight 40%Scale 1-5

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

A strong, well-scoped description that covers capabilities, triggers, and exclusions concisely. It clearly distinguishes itself from adjacent skills and would reliably fire on the right intent.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete Jira actions — 'creating, viewing, searching, updating, transitioning, commenting on, or linking tickets' plus 'follow-up ticket creation' — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both 'what' (the full set of Jira operations) and 'when' via a concrete 'TRIGGER when' clause, supplemented by a 'SKIP' clause — matching the anchor for clear what-and-when with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural trigger terms including the ticket-number pattern ('DOCSP-XXXXX'), 'Jira ticket URL', common verbs ('view, open, check, update, transition, close, comment on, link, or search'), and synonyms ('the ticket', 'the Jira', 'open a ticket').	5 / 5
Distinctiveness Conflict Risk	Scoped to the DOCSP Jira project with explicit skip guidance for GitHub issues and non-Jira platforms, giving a clear niche with minimal conflict risk.	5 / 5
	Total	20 / 20 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 6 missing	Warning
referenced_paths_exist	Referenced path issues: 6 missing	Warning

	Total	13 / 16 Passed

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

Reviewed: 3 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.