jira-issues
Create, read, update, and delete Jira issues. Use when managing Stories, Tasks, Bugs, or Epics - includes field updates and metadata.
86
Quality
82%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/skills-md/01000001-01001110/agent-jira-skills/jira-issues/SKILL.mdDiscovery
100%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 is a well-crafted skill description that follows best practices. It uses third person voice, lists concrete CRUD actions, specifies the domain (Jira) and issue types, and includes an explicit 'Use when...' clause with natural trigger terms. The description is concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Create, read, update, and delete Jira issues' plus 'field updates and metadata'. Also specifies issue types (Stories, Tasks, Bugs, Epics). | 3 / 3 |
Completeness | Clearly answers both what ('Create, read, update, and delete Jira issues...field updates and metadata') and when ('Use when managing Stories, Tasks, Bugs, or Epics') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'Jira', 'issues', 'Stories', 'Tasks', 'Bugs', 'Epics'. These are the exact terms users would use when requesting Jira-related work. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on Jira issue management. The mention of 'Jira' and specific issue types (Stories, Tasks, Bugs, Epics) creates distinct triggers unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a functional, actionable skill with complete code examples for Jira issue CRUD operations. However, it's verbose with extensive type definitions Claude doesn't need spelled out, and lacks validation checkpoints for destructive operations like delete and bulk create. The content would benefit from being split into a concise overview with references to detailed documentation.
Suggestions
Add validation/error handling guidance for delete and bulk operations (e.g., 'Verify issue exists before delete', 'Check bulk create results for partial failures')
Condense TypeScript interfaces - Claude can infer types from examples; keep only the essential CreateIssueInput and UpdateIssueInput
Split ADF format documentation and API reference table into separate reference files, keeping only a brief example in the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes verbose type definitions and repetitive code patterns. The interface definitions and multiple similar function implementations could be condensed, and Claude doesn't need full TypeScript interfaces spelled out in such detail. | 2 / 3 |
Actionability | Provides fully executable TypeScript code and curl examples that are copy-paste ready. Each CRUD operation has complete, working implementations with proper request bodies and headers. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but there are no validation checkpoints or error handling guidance. The bulk create operation lacks feedback loops for partial failures, and delete operations have no confirmation or rollback guidance. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the skill is monolithic with ~300 lines that could benefit from splitting. The API reference table and ADF format documentation could be separate files, with the main skill focusing on quick-start patterns. | 2 / 3 |
Total | 9 / 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.
- 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.