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 follows the recommended pattern closely, using third person voice and a clear 'Use when...' clause. The only minor improvement would be expanding trigger terms to include related concepts like 'backlog' or 'sprint planning'.
| 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' ('Use when listing boards, creating sprints, or moving issues to/from sprints') with explicit trigger guidance. | 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
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 far too verbose for what it teaches. Most of the TypeScript boilerplate (interfaces, class extensions, URLSearchParams construction) is knowledge Claude already has — the real value is in the API endpoint paths, the agile/1.0 vs api/3 distinction, and the common mistakes section. The content would be significantly more effective condensed to the API summary table, curl examples, and gotchas.
Suggestions
Drastically reduce the TypeScript code — replace full implementations with the API endpoints summary table plus one brief example showing the agile base URL pattern. Claude can generate the TypeScript wrappers from endpoint information.
Add validation steps for destructive operations: verify sprint state before moving issues, confirm sprint creation succeeded before adding issues, handle partial failures in batch issue moves.
Split into a lean SKILL.md (API table, key gotchas, one curl example) and a separate REFERENCE.md for full code examples and all curl commands.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~200+ lines. Full TypeScript interface definitions and class implementations are unnecessary — Claude knows how to write TypeScript interfaces and fetch wrappers. The curl examples largely duplicate the TypeScript code. The API endpoints summary table is the most efficient part, but the rest could be dramatically condensed. | 1 / 3 |
Actionability | The code is fully executable with complete TypeScript implementations, proper type definitions, and copy-paste ready curl examples. Every operation has concrete, working code with specific API paths and request bodies. | 3 / 3 |
Workflow Clarity | The steps are numbered sequentially but they're really independent operations, not a true workflow. There are no validation checkpoints — for example, no verification after creating a sprint, no error handling guidance for moving issues to closed sprints, and no feedback loops for batch operations like moving multiple issues. | 2 / 3 |
Progressive Disclosure | The content is mostly monolithic — all TypeScript implementations, curl examples, and the API table are inline. The auth setup is appropriately referenced externally, but the detailed implementations could be split into a separate reference file, with SKILL.md containing just the API summary table, key gotchas, 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
e437c3c
- 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.