jira-agile
Manage Jira Agile boards and sprints. Use when listing boards, creating sprints, or moving issues to/from sprints.
77
71%
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 what the skill does and when to use it. It uses third person voice, lists specific concrete actions, and includes natural trigger terms that users would employ. The description is focused and distinctive enough to avoid conflicts with related but different 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 other skills like general Jira issue management or project management tools. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
42%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 with good coverage of Jira Agile API operations, but is far too verbose for a skill file. It includes redundant representations (TypeScript + curl + API table) all inline, and lacks validation/verification steps for operations that modify sprint state. Significant restructuring to separate reference material and add error handling guidance would greatly improve it.
Suggestions
Reduce the SKILL.md to a concise overview with the API endpoints table and one brief code pattern (e.g., the agileRequest method), moving full TypeScript implementations and curl examples to separate referenced files like EXAMPLES.md or API_REFERENCE.md.
Remove TypeScript interface definitions that Claude can infer from the API response descriptions — just document the key fields inline.
Add validation checkpoints for destructive operations: verify sprint state before moving issues, confirm sprint exists before starting/ending, and check response status after mutations.
Eliminate redundancy between the TypeScript code, curl examples, and API summary table — pick one primary representation and reference the others if needed.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~200+ lines, with extensive TypeScript interface definitions and full function implementations that Claude could easily generate from a concise API reference. The curl examples largely duplicate the TypeScript code. The API summary table, while useful, combined with everything else makes this far too long. | 1 / 3 |
Actionability | The code is fully executable TypeScript with complete type definitions, concrete curl examples with real URLs and headers, and a comprehensive API endpoints table. Everything is copy-paste ready. | 3 / 3 |
Workflow Clarity | Steps are numbered and sequenced logically (create client → list boards → get sprints → get issues → move issues → create sprint → start/end sprint), but there are no validation checkpoints or error recovery steps. Moving issues to sprints and starting/ending sprints are potentially destructive operations that lack verification steps. | 2 / 3 |
Progressive Disclosure | Everything is in a single monolithic file with no content split into supporting files. The extensive TypeScript implementations, curl examples, and API reference table could easily be separated into referenced files, keeping the SKILL.md as a concise overview. | 1 / 3 |
Total | 7 / 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
aa009ea
- 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.