jira-agile
Manage Jira Agile boards and sprints. Use when listing boards, creating sprints, or moving issues to/from sprints.
86
Quality
82%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/skills-md/01000001-01001110/agent-jira-skills/jira-agile/SKILL.mdDiscovery
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 follows best practices. It clearly specifies the domain (Jira Agile), lists concrete actions (listing boards, creating sprints, moving issues), and includes an explicit 'Use when...' clause with natural trigger terms. The description is concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'listing boards', 'creating sprints', 'moving issues to/from sprints'. Uses third person voice correctly ('Manage'). | 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', 'Agile', 'boards', 'sprints', 'issues'. These are terms users naturally use when working with Jira sprint management. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on Jira Agile/sprint functionality. The combination of 'Jira', 'Agile', 'boards', and 'sprints' creates distinct triggers unlikely to conflict with general issue tracking or other project management skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with excellent executable code examples in both TypeScript and curl. The main weaknesses are the lack of validation/verification steps for sprint operations (which can fail silently or have side effects) and the monolithic structure that could benefit from splitting detailed implementations into a reference file. The content is slightly verbose with full interface definitions that could be condensed.
Suggestions
Add validation checkpoints after sprint operations (e.g., verify sprint was created by fetching it, confirm issues were moved by checking sprint contents)
Include error handling guidance for common failure scenarios (closed sprint, permission denied, invalid board type)
Consider moving detailed TypeScript implementations to a separate REFERENCE.md file, keeping only quick patterns and curl examples in the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with executable code, but includes some redundancy (full interface definitions that could be inferred, repetitive patterns across functions). The TypeScript types add value but the overall structure could be tighter. | 2 / 3 |
Actionability | Excellent actionability with fully executable TypeScript code and curl examples. Every operation has copy-paste ready code with proper types, error handling, and real API paths. | 3 / 3 |
Workflow Clarity | Steps are numbered and sequenced, but there are no validation checkpoints or error recovery guidance. For operations like moving issues to sprints or starting/ending sprints, there's no verification that the operation succeeded or how to handle failures. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the skill is monolithic with all code inline. The API endpoints summary table is helpful, but detailed TypeScript implementations could be split into a separate reference file with just the quick patterns in the main skill. | 2 / 3 |
Total | 9 / 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.
- 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.