jira-projects
Manage Jira projects. Use when listing projects, getting project configuration, retrieving issue types, or managing components and versions.
53
58%
Does it follow best practices?
Impact
—
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 with reasonable triggers, which is its main strength. However, the actions listed are somewhat generic ('manage', 'getting configuration'), and the trigger terms could be more comprehensive to cover natural user phrasings. There is moderate overlap risk with other potential Jira-related skills.
Suggestions
Add more specific concrete actions such as 'list all Jira projects, view project settings, retrieve available issue types for a project, create/update/delete components and versions'.
Include additional natural trigger terms users might say, such as 'project settings', 'project details', 'JIRA project config', or 'add a component to a project'.
| 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 general — 'manage' and 'getting configuration' are not highly concrete compared to examples like 'fill forms, merge documents'. | 2 / 3 |
Completeness | Clearly answers both 'what' (manage Jira projects) and 'when' (explicit 'Use when' clause listing specific triggers: 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 phrasings such as 'project settings', 'project details', 'JIRA board', 'project info', or 'create component'. Coverage of natural variations is incomplete. | 2 / 3 |
Distinctiveness Conflict Risk | The focus on Jira projects is fairly specific, but 'manage Jira projects' could overlap with other Jira-related skills (e.g., issue management, board management, sprint management). The mention of 'issue types' in particular could cause confusion with an issue-focused 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 comprehensive, actionable API coverage for Jira project management with executable code and curl examples, but is significantly over-engineered for a skill file. The full TypeScript interface definitions and repeated patterns inflate the token count substantially. The step numbering creates a false sense of sequential workflow when these are actually independent operations.
Suggestions
Drastically reduce verbosity by removing full TypeScript interface definitions — Claude can infer response shapes from the API paths and a brief description of key fields. A compact table or brief field list would suffice.
Remove the Step 1-5 numbering since these are independent operations, not a sequential workflow. Use descriptive headers like '## List Projects', '## Get Project Details' instead.
Consolidate the curl examples into a single example with a note that the same auth pattern applies to all endpoints, referencing the API endpoints summary table for paths.
Consider moving detailed interface definitions and curl examples into a separate reference file, keeping SKILL.md as a concise overview with the endpoint summary table and one brief 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 interface definitions for JiraProject, ProjectsResponse, Component, Version, IssueType are boilerplate that inflate token count significantly. The curl examples repeat the same auth header pattern three times. The API endpoints summary table duplicates information already shown in the code examples. | 1 / 3 |
Actionability | The skill provides fully executable TypeScript code with proper type definitions, concrete curl examples with real endpoint URLs, and a clear API endpoints summary table. Both programmatic and command-line approaches are covered with copy-paste ready examples. | 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. The numbering implies a sequence that doesn't exist. There are no validation checkpoints or error handling patterns, though these are read-only operations so the risk is lower. | 2 / 3 |
Progressive Disclosure | The content is a monolithic file with all interface definitions, implementations, and curl examples inline. The detailed TypeScript interfaces and multiple curl examples could be split into reference files. There's a reference to the jira-auth skill but no bundle files to support progressive disclosure. | 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
e8584ad
- 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.