jira-search
Search Jira issues using JQL queries. Use when filtering issues by project, status, assignee, date, or building reports.
73
66%
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-search/SKILL.mdQuality
Discovery
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 that clearly communicates its purpose and when to use it. It excels at trigger term coverage and completeness with an explicit 'Use when' clause. The main weakness is that it only describes one action (search) rather than listing multiple concrete capabilities, which limits its specificity score.
Suggestions
Consider listing additional concrete actions beyond 'search', such as 'filter', 'export', or 'aggregate' to improve specificity of capabilities.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Jira issues) and one specific action (search using JQL queries), but doesn't list multiple concrete actions like creating issues, updating fields, or managing workflows. | 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) with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Jira', 'JQL', 'issues', 'project', 'status', 'assignee', 'date', 'reports' — these cover common variations of how users would phrase Jira search requests. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of 'Jira', 'JQL queries', and specific filter dimensions (project, status, assignee) creates a clear niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is highly actionable with executable code and concrete examples, but suffers significantly from verbosity and poor content organization. It tries to be both a tutorial, API reference, and JQL cheatsheet in a single file, resulting in excessive token consumption. The lack of validation steps for bulk operations and the monolithic structure are notable weaknesses.
Suggestions
Split the JQL reference tables, curl examples, and response structure into separate reference files (e.g., JQL_REFERENCE.md, CURL_EXAMPLES.md) and link to them from a concise overview.
Remove the TypeScript interface definitions and search builder helper functions — Claude can trivially construct these. Keep only the paginated search pattern and a few JQL examples.
Add validation/error handling guidance: what to do when JQL is invalid (400 response), how to verify result counts before bulk operations, and rate limiting considerations.
Reduce the 'Common JQL Patterns' section to 3-4 essential patterns instead of 9, since Claude already understands JQL syntax from the operators table.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is excessively verbose at ~200+ lines. It explains TypeScript interfaces Claude already knows, provides redundant search builder functions that are trivial to write, and includes both TypeScript implementations AND curl examples for the same operations. The JQL reference table, while useful, combined with the extensive code makes this far too long. | 1 / 3 |
Actionability | The skill provides fully executable TypeScript code, complete curl commands with proper headers and JSON bodies, concrete JQL examples, and a clear response structure. Everything is copy-paste ready. | 3 / 3 |
Workflow Clarity | The steps are clearly sequenced (define types → basic search → paginated search → builders → advanced examples), but there are no validation checkpoints. For bulk operations on filtered issues (mentioned in 'When to Use'), there's no guidance on verifying results before acting, and no error handling or feedback loops for failed searches or invalid JQL. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of content. The JQL reference tables, curl examples, TypeScript implementations, and response structures are all inline when they could easily be split into separate reference files. The skill would benefit greatly from a concise overview with links to JQL_REFERENCE.md, EXAMPLES.md, etc. | 1 / 3 |
Total | 7 / 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
f772de4
- 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.