Content
57%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-structured, genuinely actionable reference for driving Jira via Rube MCP, with exact tool slugs, parameters, and per-workflow pitfalls. Its weaknesses are redundancy (repeated pitfalls, a filler closing section), absent validation checkpoints for write and batch operations, and an all-in-one layout that puts the full tool catalog inline in SKILL.md.
Suggestions
Add validation checkpoints after write/batch operations, e.g., after JIRA_MOVE_ISSUE_TO_SPRINT or JIRA_CREATE_ISSUE, verify the result (re-fetch the issue) before proceeding.
De-duplicate repeated guidance: state the custom-field-ID and account-ID pitfalls once in Known Pitfalls and remove the per-workflow repeats, and delete the empty 'When to Use' section.
Move the 18-row Quick Reference table and JQL syntax catalog into a references/ file (e.g., TOOL_CATALOG.md) and link to it, keeping SKILL.md as a lean overview.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense reference material without concept-explanation padding, but it contains clear waste: the closing 'When to Use' section ('This skill is applicable to execute the workflow or actions described in the overview') is pure filler, 'Always call RUBE_SEARCH_TOOLS first' appears in both Prerequisites and Setup, and the custom-field pitfall is repeated three times. This is more than the 'minor instances' of anchor 4, fitting 'mostly efficient but could be tightened'. | 3 / 5 |
Actionability | Concrete, executable guidance throughout: exact tool slugs (e.g., 'JIRA_SEARCH_FOR_ISSUES_USING_JQL_POST'), parameters with example values (jql: 'project = PROJ AND status = "In Progress"'), JQL operator examples, and a pagination formula. Minor gaps — no full example tool-call payloads — keep it at anchor 4 rather than the copy-paste-ready completeness of anchor 5. | 4 / 5 |
Workflow Clarity | Each workflow has a clearly numbered tool sequence with [Required]/[Optional]/[Prerequisite] markers, and Setup includes verification steps, but workflows lack post-write validation checkpoints, and the batch-capable 'JIRA_MOVE_ISSUE_TO_SPRINT' (params 'sprintId, issues') has no validation. Per the guideline, missing validation in batch operations caps workflow clarity at 3. | 3 / 5 |
Progressive Disclosure | This is a single-file skill (no references/, scripts/, or assets/ bundle exists), ~180 lines all inline, including an 18-row Quick Reference catalog that could live in a separate reference file. Sections are well-organized, but the under-50-lines exception for a 5 does not apply, and content that should be separate is inline — matching anchor 3 rather than anchor 4's 'most content appropriately placed'. | 3 / 5 |
Total | 13 / 20 Passed |