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 provides highly actionable, concrete code examples with good API coverage, but is significantly over-verbose for a skill file. Full TypeScript interfaces and repetitive curl examples inflate the token cost without adding proportional value — Claude can infer interface shapes from a single example. The 'Step 1-5' framing implies a sequential workflow but these are independent operations that would be better presented as a reference catalog.
Suggestions
Remove or drastically condense the TypeScript interface definitions — a single compact example with one function would suffice, with a note that the same pattern applies to all endpoints.
Consolidate the curl examples into one with a note about substituting the endpoint path, rather than repeating the auth header three times.
Remove the 'When to Use' section as it duplicates the Purpose section, and remove the 'Step N' numbering since these are independent operations, not a sequential workflow.
Move detailed interface definitions and expanded curl examples to a separate REFERENCE.md file, keeping SKILL.md as a concise overview with the endpoint summary table and one representative code example.
| 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 'When to Use' section largely duplicates the 'Purpose' section. This could be condensed to ~30% of its current size. | 1 / 3 |
Actionability | The code is fully executable with concrete TypeScript functions and curl commands that are copy-paste ready. Interface definitions, endpoint paths, query parameters, and expand options are all specific and complete. | 3 / 3 |
Workflow Clarity | The steps are labeled 1-5 but they aren't really a sequential workflow — they're independent API operations presented as a sequence. 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 numbered 'Step' framing is misleading. | 2 / 3 |
Progressive Disclosure | There's a reference to the jira-auth skill and external API docs, which is good. However, the full interface definitions and multiple curl examples are inlined when they could be in a separate reference file. The API Endpoints Summary table is a nice touch but the overall content is too heavy for a SKILL.md 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
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.