jira-agile
Manage Jira Agile boards and sprints. Use when listing boards, creating sprints, or moving issues to/from sprints.
80
75%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/skills-md/01000001-01001110/agent-jira-skills/jira-agile/SKILL.mdQuality
Discovery
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 a well-crafted skill description that concisely covers specific capabilities, includes natural trigger terms, and explicitly states both what the skill does and when to use it. It uses proper third-person voice and is clearly scoped to Jira Agile board and sprint management, minimizing conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'listing boards', 'creating sprints', 'moving issues to/from sprints'. These are clear, actionable operations rather than vague language. | 3 / 3 |
Completeness | Clearly answers both 'what' (manage Jira Agile boards and sprints) and 'when' (explicit 'Use when' clause with specific triggers: listing boards, creating sprints, moving issues to/from sprints). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'Jira', 'boards', 'sprints', 'issues', 'Agile'. These are terms users would naturally use when requesting these operations. Could potentially include more variations like 'backlog' or 'sprint planning', but coverage is good. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Jira Agile boards and sprints specifically, which is a distinct niche. The combination of 'Jira', 'Agile', 'boards', and 'sprints' makes it unlikely to conflict with general issue tracking or other project management skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides highly actionable, executable code for Jira Agile operations but is excessively verbose — Claude doesn't need full TypeScript interface definitions and class hierarchies spelled out. It lacks validation checkpoints for destructive operations (closing sprints, moving issues) and would benefit from splitting detailed implementations into separate reference files while keeping SKILL.md as a lean overview.
Suggestions
Drastically reduce the TypeScript code — provide one example function and the API endpoints table; Claude can generate the rest from the endpoint patterns and its knowledge of the Jira API.
Add validation/verification steps for destructive operations: e.g., confirm sprint state before closing, verify issues exist before moving them, check board type before attempting sprint operations.
Move detailed TypeScript implementations and curl examples into separate referenced files (e.g., EXAMPLES.md, API_REFERENCE.md) and keep SKILL.md as a concise overview with the endpoints table and key gotchas.
Remove the interface/type definitions entirely — Claude knows how to type Jira API responses and these add significant token cost without unique value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~200+ lines. Full TypeScript interface definitions and class implementations are things Claude can generate on its own. The curl examples largely duplicate the TypeScript examples. The API endpoints summary table, while useful, combined with all the code makes this far too long. | 1 / 3 |
Actionability | The code is fully executable TypeScript with proper type definitions, and the curl examples are copy-paste ready with real endpoint URLs and headers. Every operation has a concrete, complete implementation. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced and labeled, but there are no validation checkpoints. Operations like moving issues to sprints or starting/ending sprints are potentially destructive (e.g., closing a sprint moves incomplete issues) yet lack any verification or error recovery guidance. | 2 / 3 |
Progressive Disclosure | The content is mostly monolithic — all TypeScript implementations, curl examples, and the API table are inline. The TypeScript class and individual operations could be split into referenced files, with SKILL.md serving as a concise overview with the API table and curl examples. | 2 / 3 |
Total | 8 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- NeverSight/skills_feed
- Commit
caee3d2
- 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.