jira-search
Search Jira issues using JQL queries. Use when filtering issues by project, status, assignee, date, or building reports.
82
Quality
77%
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-search/SKILL.mdDiscovery
89%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 solid skill description with excellent trigger terms and completeness. The explicit 'Use when...' clause with specific filter criteria makes it easy for Claude to know when to select this skill. The main weakness is that the capability description could be more comprehensive beyond just 'search'.
Suggestions
Expand the capabilities beyond 'search' to include other concrete actions like 'retrieve issue details, export results, generate summaries' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Jira) and primary action (search using JQL queries), but doesn't list multiple concrete actions beyond searching. Could specify capabilities like 'retrieve issue details, export results, analyze trends'. | 2 / 3 |
Completeness | Clearly answers both what ('Search Jira issues using JQL queries') and when ('Use when filtering issues by project, status, assignee, date, or building reports'). Has explicit 'Use when...' clause with specific triggers. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Jira', 'JQL', 'issues', 'project', 'status', 'assignee', 'date', 'reports'. Good coverage of common filter criteria users mention. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche with Jira-specific terminology (JQL, issues, assignee). Unlikely to conflict with other skills due to the specific platform and query language mentioned. | 3 / 3 |
Total | 11 / 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 solid, actionable skill with excellent code examples covering TypeScript implementations, curl commands, and JQL patterns. However, it's verbose for a skill file - the inline reference tables and dual TypeScript/curl coverage inflate the token count. Adding validation steps for bulk operations and splitting reference material into separate files would improve it.
Suggestions
Add validation checkpoint before bulk operations: 'Log search results count and sample issues before proceeding with bulk actions'
Move JQL Quick Reference tables and Response Structure to a separate REFERENCE.md file, keeping only essential examples inline
Add error handling guidance for pagination failures (e.g., what to do if a page request fails mid-iteration)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy - the TypeScript implementation patterns and curl examples cover similar ground. The step-by-step breakdown (Step 1-5) adds structure but also verbosity that could be condensed. | 2 / 3 |
Actionability | Excellent executable code throughout - complete TypeScript functions, working curl commands, and concrete JQL examples. All code is copy-paste ready with realistic patterns for pagination, search builders, and common use cases. | 3 / 3 |
Workflow Clarity | The steps are clearly numbered but lack validation checkpoints. For bulk operations on filtered issues (mentioned in 'When to Use'), there's no guidance on verifying search results before acting on them or handling API errors during pagination. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the skill is quite long (~200 lines) with detailed API reference tables inline. The JQL Quick Reference and Response Structure sections could be split into separate reference files, with SKILL.md providing a concise overview. | 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.