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.02x

Quality

96%

Does it follow best practices?

Impact

97%

2.02x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

92%

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

The body is exceptionally actionable and concise with strong feedback loops on fragile operations like transitions and closing. Its only meaningful gap is progressive disclosure: with no bundle files, large reference tables live inline rather than in separate one-level-deep files.

Suggestions

Extract the stable reference material — the custom-field table, label catalog, and CLI gotchas — into separate files (e.g. references/fields.md, references/labels.md) and link to them from the body, keeping SKILL.md as a tighter overview.

Move the Story Point estimation scale and resolution-values tables into a references/closing.md file so the closing workflow stays lean while the lookup tables remain one level deep.

If keeping everything inline, add a short table of contents near the top so the long single-file body is easier to navigate.

Dimension	Reasoning	Score
Conciseness	The body is dense and operational — it never explains what Jira or a PDF is, and every section (gotchas, field tables, lifecycle) carries actionable content rather than padding. It assumes Claude's competence throughout.	3 / 3
Actionability	Provides fully executable CLI and MCP code blocks (e.g. 'cat <<EOF \| jira issue create ... --no-input --raw', 'jira_transition_issue(issue_key=..., transition_id=..., fields={...})') with concrete field keys and flags — copy-paste ready.	3 / 3
Workflow Clarity	Multi-step processes (tool selection/fallback, closing issues, scope-creep follow-ups) are explicitly sequenced with validation checkpoints and feedback loops — e.g. 'attempt the move and read the error for valid transition names' and 'If the MCP transition fails with This field is required, use jira_search_fields'.	3 / 3
Progressive Disclosure	No bundle files exist and the SKILL.md is a ~497-line monolith; reference-heavy content (CLI gotchas, custom-field tables, the full label catalog) sits inline where it could be split into one-level-deep reference files for easier navigation. It is well-organized with clear sections, but lacks the split structure the top anchor calls for.	2 / 3
	Total	11 / 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 exemplary: it names concrete capabilities, provides explicit TRIGGER and SKIP guidance with natural user phrasings, and is tightly scoped to DOCSP Jira with clear deconfliction. It hits the top anchor on every dimension.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'creating, viewing, searching, updating, transitioning, commenting on, or linking tickets' — plus follow-up ticket creation, matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers both what (Jira operations and follow-up scope-creep tickets) and when via dedicated 'TRIGGER when' and 'SKIP' clauses, the clearest form of explicit trigger guidance.	3 / 3
Trigger Term Quality	Covers natural user phrasings — 'DOCSP-XXXXX ticket number', 'Jira ticket URL', 'the ticket', 'the Jira', 'open a ticket' — that a user would realistically say when needing the skill.	3 / 3
Distinctiveness Conflict Risk	Scoped to the DOCSP project with an explicit 'SKIP: GitHub issues; non-Jira platforms' clause, giving it a clear niche and low conflict risk with adjacent skills.	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
Commit: 82345bd

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.