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.

2.25x

Quality

85%

Does it follow best practices?

Impact

88%

2.25x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

70%

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

This is a highly actionable and well-structured Jira operations skill with excellent concrete examples for both CLI and MCP tools, strong workflow clarity with validation checkpoints, and useful gotcha documentation. Its main weakness is that it's a large monolithic file (~400 lines) with no progressive disclosure—reference tables, label taxonomies, and detailed gotchas should be split into supporting files to reduce token cost per invocation. Some minor verbosity exists in explanations Claude wouldn't need.

Suggestions

Split reference content (label taxonomy, link types table, story point scale, CLI gotchas) into separate bundle files (e.g., LABELS.md, REFERENCE.md, CLI-GOTCHAS.md) and link from the main SKILL.md to reduce token cost.

Remove explanatory text Claude already knows, such as describing what each link type direction means conceptually—just provide the table with 'When to use' guidance.

Add a quick-reference summary section at the top listing the most common operations with one-line examples, pushing detailed sections into referenced files.

Dimension	Reasoning	Score
Conciseness	The skill is comprehensive and mostly efficient, but includes some content Claude already knows (e.g., explaining what link types mean, what story points represent conceptually). The tables and examples are well-structured but the overall length (~400 lines) could be tightened—some sections like the label taxonomy and link types table could be moved to a reference file.	2 / 3
Actionability	Excellent actionability throughout. Every operation includes fully executable CLI commands and MCP function calls with real parameter names, field keys, and concrete examples. The custom field mappings, gotchas with specific wrong/correct patterns, and transition requirements are all highly specific and copy-paste ready.	3 / 3
Workflow Clarity	The ticket lifecycle is clearly sequenced with explicit validation checkpoints—checking transitions before moving, confirming PR merge before closing, required fields at each transition point, and error recovery strategies (read error for valid transitions, fallback tool strategy). The closing workflow includes a clear feedback loop for missing fields.	3 / 3
Progressive Disclosure	This is a monolithic ~400-line file with no references to supporting files. The label taxonomy, link types, story point scale, component details, and CLI gotchas could all be split into separate reference files. Everything is inline, making it a wall of content that competes for context window space on every invocation.	1 / 3
	Total	9 / 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.

This is an excellent skill description that hits all the marks. It provides specific concrete actions, comprehensive natural trigger terms, explicit 'when to use' and 'when to skip' guidance, and is clearly scoped to a distinct niche (DOCSP Jira operations). The inclusion of both TRIGGER and SKIP clauses makes it particularly effective for disambiguation among many skills.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: creating, viewing, searching, updating, transitioning, commenting on, linking tickets, and follow-up ticket creation for scope creep. These are all concrete, actionable operations.	3 / 3
Completeness	Clearly answers both 'what' (Jira operations in DOCSP project — creating, viewing, searching, etc.) and 'when' (explicit TRIGGER clause with specific patterns like ticket numbers, URLs, and natural phrases). Also includes a SKIP clause for negative triggers, which adds further clarity.	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms: 'DOCSP-XXXXX ticket number', 'Jira ticket URL', 'view, open, check, update, transition, close, comment on, link, search tickets', 'the ticket', 'the Jira', 'open a ticket'. These are terms users would naturally say.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive: scoped to a specific project (DOCSP), a specific platform (Jira), and explicitly excludes GitHub issues and non-Jira platforms. The SKIP clause further reduces conflict risk with other skills.	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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: mongodb/docs
Commit: be9d4af

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.