CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

jira-transitions

Move Jira issues through workflow states. Use when transitioning issues (To Do, In Progress, Done) or setting resolutions.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

—

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./data/skills-md/01000001-01001110/agent-jira-skills/jira-transitions/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 highly actionable, well-sequenced skill with executable TypeScript and curl examples and good error coverage. Its weaknesses are token duplication (TS + curl for the same operations), the absence of verification after batch transitions, and no use of bundle files to keep SKILL.md to an overview.

Suggestions

Add a post-transition verification step (e.g., re-fetch the issue status and confirm it matches the target, with a retry/report loop) to satisfy the batch-operation validation requirement in bulkTransition.

Deduplicate the TypeScript and curl sections — either keep curl as the canonical executable examples and trim the TS functions, or move the full implementations into a references/ file linked from SKILL.md.

Move the transition/resolution lookup tables and the discovery-pattern helper into a references/ or scripts/ bundle so SKILL.md stays a concise overview with one-level-deep, clearly signaled references.

DimensionReasoningScore

Conciseness

The body is mostly efficient — dense code with little tutorial-style padding — but every operation is implemented twice (TypeScript functions in Steps 1-6 and equivalent curl examples), and the 'Workflow Discovery Pattern' console-logging helper largely restates earlier functions. This duplication is unnecessary content that could be trimmed, matching the 'mostly efficient but includes some unnecessary explanation' anchor rather than the 'efficient, minor trims' 4.

3 / 5

Actionability

Fully executable, copy-paste-ready TypeScript functions and curl commands with real payloads, plus concrete error-response JSON and lookup tables for resolutions and common transitions. This matches the 5 anchor: specific examples cover the common cases with no pseudocode.

5 / 5

Workflow Clarity

The sequence (query transitions → find by name → execute → high-level helper → bulk) is clear with a key 'Always query available transitions first' checkpoint and an error-handling table. However, the skill includes batch operations (bulkTransition) with no post-transition verification step (e.g., re-fetchting status to confirm the move succeeded), so the batch-operation cap of 3 applies even though the sequence itself would warrant a 4.

3 / 5

Progressive Disclosure

Sections are well-organized with clear headers and a single external API reference link, but this is a 340-line monolithic file: content that plausibly belongs in separate reference files (full TypeScript implementations, curl examples, resolution/transition tables) is all inlined. No bundle files exist to offload it, matching the 3 anchor ('some structure but content that should be separate is inline') rather than the well-split 4.

3 / 5

Total

14

/

20

Passed

Description

78%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 description: concise, third-person, with an explicit 'Use when...' trigger clause naming concrete statuses and actions. The main gaps are the missing mention of querying available transitions and a few natural synonyms like 'close' or 'resolve'.

DimensionReasoningScore

Specificity

The description names the domain ('Jira issues', 'workflow states') and two concrete actions — 'Move Jira issues through workflow states' and 'setting resolutions' — matching the anchor for 1-2 concrete actions. It does not rise to 4 because it omits capabilities covered by the body such as querying available transitions and bulk operations.

3 / 5

Completeness

It explicitly answers both: what ('Move Jira issues through workflow states') and when ('Use when transitioning issues (To Do, In Progress, Done) or setting resolutions') with concrete trigger phrases. It clearly matches the 5 anchor rather than the 4 anchor, whose 'when' clause is less specific.

5 / 5

Trigger Term Quality

Natural phrases users would say are present: 'transitioning issues', 'To Do, In Progress, Done', and 'setting resolutions'. It falls short of the 5 anchor because common variations like 'close', 'resolve', 'reopen', 'status', or 'ticket' are missing.

4 / 5

Distinctiveness Conflict Risk

The Jira transitions niche is clear and mostly distinct, but other Jira skills (issue creation, comments, resolution) could overlap on triggers like 'setting resolutions' or 'Done'. Minor overlap risk with closely related skills matches the 4 anchor rather than the clear-niche 5 anchor.

4 / 5

Total

16

/

20

Passed

Validation

100%

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

NeverSight/learn-skills.dev

Path

data/skills-md/01000001-01001110/agent-jira-skills/jira-transitions/SKILL.md

Reviewed

Table of Contents

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.