Name: best-roi-task
Rating: 60.8 (1 reviews)
Author: AndreJorgeLopes

Blog Docs Log in Get started

best-roi-task

Find the best ROI task in a Jira Epic — highest story points for least effort, filtered to unassigned To Do tasks only.

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./devflow-plugin/skills/best-roi-task/SKILL.md

The canonical home for this skill is best-roi-task in AndreJorgeLopes/devflow

Quality

Content

75%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.

The content is highly actionable and reasonably concise with a clear numbered workflow, but its batch read-and-rank operation lacks validation/verification checkpoints, capping workflow clarity at 3. Progressive disclosure is good for a self-contained skill.

Suggestions

Add a validation step after the Jira fetch (verify issues were returned, confirm customfield_10028/10188 exist, handle pagination beyond maxResults=50) to lift workflow clarity above 3.

Tighten the step-3 blockers paragraph by collapsing the two redundant inward/outward explanations into one concise rule.

Consider moving the Aircall-specific custom-field IDs and t-shirt mapping into a referenced file if this skill is reused across Jira instances, to reduce instance-specific density.

Dimension	Reasoning	Score
Conciseness	The body is lean and operational (JQL, field IDs, effort table, ROI formula, output templates) with only minor over-explanation in the step-3 blockers paragraph ('specifically, links with…', 'In practice: check for…') that could be trimmed.	4 / 5
Actionability	Provides the exact MCP tool name, concrete JQL, specific custom-field IDs, a copy-paste effort-mapping table, the ROI formula, and ready-to-use output table templates — fully executable guidance covering the common cases.	5 / 5
Workflow Clarity	The 8-step sequence is clear, but this batch operation (fetching and ranking up to 50 issues) has no validation/verification checkpoint — no response-shape check, pagination handling, or field-presence confirmation — so workflow clarity is capped at 3 per the batch-operation rule.	3 / 5
Progressive Disclosure	A self-contained single SKILL.md with well-organized sections (Preflight, Inputs, Steps, Important) and no nested or buried references; appropriately structured, though somewhat dense rather than exemplary.	4 / 5
	Total	16 / 20 Passed

Description

66%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.

The description is specific, distinct, and uses natural Jira vocabulary, but it lacks an explicit 'Use when…' trigger clause, which caps its completeness at 3. It is strong on distinctiveness and reasonably concrete on action.

Suggestions

Add an explicit 'Use when…' clause (e.g., 'Use when deciding which unassigned To Do task to pick up next from a Jira Epic') to lift completeness above 3.

Include a common user synonym like 'quickest win' or 'next task to pick up' to broaden natural trigger coverage.

Consider naming the secondary actions (filtering, ranking, surfacing blocked tasks) explicitly to push specificity toward 5.

Dimension	Reasoning	Score
Specificity	Quotes 'Find the best ROI task', 'highest story points for least effort', and 'filtered to unassigned To Do tasks only' describe one concrete composite action with specific filter criteria, but not a list of multiple discrete actions.	4 / 5
Completeness	The 'what' is clear (find the best ROI task in a Jira Epic) but there is no explicit 'Use when…' trigger clause, so 'when' is only weakly implied — the missing trigger guidance caps completeness at 3.	3 / 5
Trigger Term Quality	Natural Jira terms ('ROI task', 'Jira Epic', 'story points', 'To Do tasks') are present, though common user phrasings like 'which task should I pick up' or 'quickest win' are missing.	4 / 5
Distinctiveness Conflict Risk	'Best ROI task in a Jira Epic' is a narrow, specific niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	16 / 20 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: AndreJorgeLopes/devflow
Path: devflow-plugin/skills/best-roi-task/SKILL.md
Commit: bd4b70c

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