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 includes an explicit 'Use when...' clause, which is a strength. However, the actions listed are somewhat high-level ('managing components and versions') rather than enumerating specific concrete operations. The trigger terms cover the basics but could benefit from more natural user language variations and clearer boundaries to distinguish this from other potential Jira skills.
Suggestions
Make actions more concrete by specifying operations like 'list all Jira projects, view project configuration and schemes, retrieve available issue types for a project, create/update/delete components and versions'.
Add more natural trigger term variations users might say, such as 'project settings', 'release versions', 'project categories', or 'Jira project setup'.
| 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 and could be more concrete about specific operations like 'create components', 'update version release dates', etc. | 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 'project settings', 'project schemes', 'Jira board', or natural phrases users might say like 'what projects are in Jira' or 'add a version'. | 2 / 3 |
Distinctiveness Conflict Risk | The focus on Jira projects is fairly distinct, but 'manage Jira projects' could overlap with other Jira-related skills (e.g., issue management, sprint management). The mention of 'issue types' in particular could cause confusion with a Jira issue management 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 provides comprehensive, executable code for Jira project management but is significantly over-verbose for a skill file. Full TypeScript interface definitions and wrapper functions are things Claude can generate from API endpoint descriptions alone. The content would be much more effective as a concise API reference table with one or two examples, linking to detailed code if needed.
Suggestions
Drastically reduce the TypeScript code—replace full interface definitions and function implementations with the API endpoints summary table plus one brief example showing the client.request pattern and pagination handling.
Remove the curl examples section or keep only one example, since they duplicate the TypeScript examples and Claude knows how to construct curl requests from endpoint information.
Add error handling guidance (e.g., what to do on 403, 404, rate limiting) instead of the verbose interface definitions.
Move detailed type definitions to a separate reference file and keep SKILL.md as a concise overview with the endpoints table and key patterns.
| 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 interface definitions for JiraProject, ProjectsResponse, IssueType, Component, Version, and all the wrapper functions are boilerplate that Claude can generate on its own. The curl examples largely duplicate the TypeScript examples. This could be condensed 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 headers and URLs, 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 permission errors, project not found). For read-only operations this is less critical, but the pagination note in 'Common Mistakes' suggests there should be a pagination handling pattern shown. | 2 / 3 |
Progressive Disclosure | There's a reference to the jira-auth skill and an external API link, which is good. However, the content is monolithic—all the TypeScript interfaces and functions could be in a separate reference file, with the SKILL.md providing just the API summary table, curl examples, and key patterns. The inline 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
f772de4
- 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.