jira
Manage Jira issues, boards, sprints, and projects via the jira-cli. Search, create, update, and transition issues directly from the command line.
80
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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.
This description has strong specificity with concrete actions and clear distinctiveness around Jira/jira-cli. However, it lacks explicit trigger guidance ('Use when...') and could benefit from additional natural trigger terms users commonly use when discussing Jira work items.
Suggestions
Add a 'Use when...' clause such as 'Use when the user asks about Jira tickets, sprint planning, issue tracking, or project management in Jira.'
Include common synonyms and variations like 'ticket', 'story', 'bug', 'backlog', 'epic' that users naturally say when referring to Jira items.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Manage Jira issues, boards, sprints, and projects', 'Search, create, update, and transition issues'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what' (manage Jira via CLI, search/create/update/transition issues), but lacks an explicit 'Use when...' clause or trigger guidance for when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Includes good domain terms like 'Jira', 'issues', 'boards', 'sprints', 'projects', but missing common variations users might say like 'ticket', 'backlog', 'story', 'bug', or 'JIRA' (caps). | 2 / 3 |
Distinctiveness Conflict Risk | Very distinct niche - specifically targets Jira and jira-cli. Unlikely to conflict with other skills due to the specific tool and platform mentioned. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality CLI reference skill that is concise, actionable, and well-organized. The command examples are complete and copy-paste ready. The main weakness is that the safety notes at the end about confirming with users before destructive operations are disconnected from the actual command workflows rather than integrated as explicit checkpoints.
Suggestions
Integrate the confirmation guidance directly into the create/edit/transition command sections (e.g., '**Before executing**: Show the user what will be created/changed and get confirmation')
Add a brief workflow example for bulk operations showing the validate-then-execute pattern mentioned in the notes
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what Jira is or how CLI tools work. Every line provides actionable command syntax or essential configuration. | 3 / 3 |
Actionability | Fully executable commands throughout with specific syntax, flags, and examples. Copy-paste ready for all common operations including JQL queries. | 3 / 3 |
Workflow Clarity | Setup steps are clear and sequential. However, the notes mention confirming before creating/editing/transitioning but don't integrate this into a workflow with explicit validation checkpoints for potentially destructive operations. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections (Setup, Issues, Sprints, Boards, etc.). For a CLI reference skill of this scope, the flat structure with logical groupings is appropriate and easy to navigate. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
62%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_examples | No examples detected (no code fences and no 'Example' wording) | Warning |
Total | 10 / 16 Passed | |
- 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.