jira-projects
Manage Jira projects. Use when listing projects, getting project configuration, retrieving issue types, or managing components and versions.
67
58%
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-projects/SKILL.mdQuality
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description is functional and follows good structure with an explicit 'Use when...' clause. It identifies the Jira project management domain clearly but could be more specific about concrete actions (e.g., 'list all projects, view project configuration, retrieve available issue types') and include more natural trigger terms users might say. The risk of overlap with other Jira-related skills (issue management, search) is moderate.
Suggestions
Add more natural trigger term variations users might say, such as 'JIRA board', 'project settings', 'project config', 'available issue types', or 'project versions'.
Make actions more concrete by replacing vague terms like 'manage components and versions' with specific operations like 'create/update/delete components, list and manage project versions'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Jira projects) and lists some actions (listing projects, getting configuration, retrieving issue types, managing components and versions), but the actions are somewhat generic — 'manage' and 'getting configuration' are vague rather than concrete specific operations. | 2 / 3 |
Completeness | Clearly answers both 'what' (manage Jira projects) and 'when' with an explicit 'Use when...' clause listing specific trigger scenarios: listing projects, getting project configuration, retrieving issue types, managing components and versions. | 3 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Jira', 'projects', 'issue types', 'components', and 'versions', but misses common user variations like 'JIRA board', 'project settings', 'sprints', 'workflows', or 'project details'. The terms are reasonable but not comprehensive. | 2 / 3 |
Distinctiveness Conflict Risk | Specifying 'Jira projects' provides a clear domain, but there could be overlap with other Jira-related skills (e.g., Jira issue management, Jira search). Terms like 'issue types' and 'components' could trigger conflicts with a broader Jira skill. | 2 / 3 |
Total | 9 / 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 is highly actionable with complete, executable code examples and a useful API summary table, but it is significantly over-verbose for a skill file. Full TypeScript interface definitions and repeated curl patterns inflate the token cost without adding proportional value—Claude can infer types and patterns from minimal examples. The numbered steps suggest a workflow but are actually independent operations with no validation or error handling.
Suggestions
Drastically reduce verbosity: replace full interface definitions with a single compact example showing one function with inline type annotations, and note that other endpoints follow the same pattern.
Consolidate curl examples to a single template with a note about substituting the endpoint path, rather than repeating the auth header three times.
Add error handling guidance: what to do on 403 (check permissions), 404 (verify project key vs name), and pagination (loop until isLast is true).
Move detailed type definitions and full function implementations to a separate reference file, keeping SKILL.md as a concise overview with one example and the endpoints table.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is excessively verbose with full TypeScript interface definitions and function implementations that Claude doesn't need spelled out in this detail. The curl examples repeat the same auth header pattern three times. The API endpoints summary table duplicates information already shown in the code. This could be reduced to ~30% of its current size. | 1 / 3 |
Actionability | The skill provides fully executable TypeScript code with complete type definitions, concrete curl examples with real URLs and headers, and a clear API endpoints summary table. Everything is copy-paste ready. | 3 / 3 |
Workflow Clarity | The steps are labeled Step 1-5 but they aren't really sequential steps in a workflow—they're independent API operations. There's no validation, error handling, or guidance on what to do when requests fail (e.g., 403 permissions, 404 project not found). The 'Common Mistakes' section hints at issues but doesn't provide recovery steps. | 2 / 3 |
Progressive Disclosure | The content is a monolithic file with all interface definitions, implementations, and curl examples inline. The type definitions and detailed function implementations could be in a separate reference file, with the SKILL.md serving as a concise overview. The reference to jira-auth skill is good but the main content is too heavy for an overview. | 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
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.