jira-agile
Manage Jira Agile boards and sprints. Use when listing boards, creating sprints, or moving issues to/from sprints.
68
82%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Risky
Do not use without reviewing
Quality
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 clearly delineates both what the skill does and when to use it. It uses proper third-person voice and is focused on a distinct domain (Jira Agile boards/sprints) that minimizes 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' ('Use when listing boards, creating sprints, or moving issues to/from sprints') with explicit trigger scenarios. | 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 '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 mention of 'Jira', 'Agile', 'boards', and 'sprints' together makes it 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 skill provides comprehensive, actionable coverage of Jira Agile API operations with both TypeScript and curl examples. Its main weaknesses are verbosity from duplicating operations in two formats and lack of workflow validation steps (e.g., checking board type before sprint operations, verifying sprint state before moving issues). The common mistakes section is valuable but could be integrated into the workflow as guard checks.
Suggestions
Remove either the TypeScript or curl examples to reduce duplication, or move one set to a separate reference file (e.g., CURL_EXAMPLES.md)
Add validation checkpoints such as verifying board type is 'scrum' before sprint operations and checking sprint state before moving issues
Integrate common mistakes as inline warnings at the relevant workflow steps rather than a separate section at the end
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly long with extensive TypeScript code and curl examples that cover the same operations twice. The interfaces and type definitions add bulk that Claude could infer. However, the API endpoint distinction (/rest/agile/1.0/ vs /rest/api/3/) and the summary table are genuinely useful. | 2 / 3 |
Actionability | The skill provides fully executable TypeScript code with proper type definitions, complete curl examples with real endpoint URLs, and a comprehensive API endpoints summary table. All code is copy-paste ready with concrete parameters and return types. | 3 / 3 |
Workflow Clarity | The steps are numbered sequentially but represent independent operations rather than a true workflow with dependencies. There are no validation checkpoints — for example, no guidance on verifying a sprint was created before moving issues to it, or checking if a board is scrum-type before attempting sprint operations. The 'Common Mistakes' section partially compensates but doesn't provide error recovery steps. | 2 / 3 |
Progressive Disclosure | The content is a monolithic file with no bundle files to reference. The API summary table at the end is good for quick reference, but the extensive inline code (both TypeScript and curl) could be split into separate reference files. For a skill of this length (~200+ lines), better separation would improve navigability. | 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.
- Repository
- NeverSight/skills_feed
- Commit
83d60e9
- 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.