jira-search
Search Jira issues using JQL queries. Use when filtering issues by project, status, assignee, date, or building reports.
58
66%
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-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 in 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
Add more specific concrete actions beyond 'search', such as 'filter, sort, and export Jira issues' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Jira issues) and one 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', 'issues', 'JQL', 'project', 'status', 'assignee', 'date', 'reports' — good coverage of terms a user would naturally use when needing this skill. | 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 excellent concrete examples (JQL patterns, curl commands, TypeScript code, response structures), but suffers from significant verbosity. Much of the TypeScript implementation code (interfaces, search builders, wrapper functions) is boilerplate that Claude can generate without instruction. The content would benefit greatly from trimming to focus on JQL-specific knowledge and API details, with better organization across multiple files.
Suggestions
Remove or drastically reduce the TypeScript implementation pattern (Steps 1-5) — Claude can generate these wrappers. Focus on JQL syntax, API endpoint details, and common pitfalls.
Split the JQL Quick Reference and curl examples into separate referenced files (e.g., JQL_REFERENCE.md, CURL_EXAMPLES.md) to improve progressive disclosure.
Add error handling guidance and validation steps — what does a failed JQL query response look like? How should Claude verify results before bulk operations?
Consolidate the 'Common Mistakes' section with inline warnings at the relevant code examples rather than listing them separately at the end.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is excessively verbose at ~250 lines. It includes extensive TypeScript wrapper functions (SearchOptions interface, search builders, advanced search examples) that Claude could easily generate on its own. The JQL quick reference and curl examples are useful, but the TypeScript implementation pattern is unnecessary scaffolding that bloats the content significantly. | 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 and specific. | 3 / 3 |
Workflow Clarity | The steps are clearly sequenced (define types → basic search → paginated search → builders → advanced examples), and pagination logic is well-explained. However, there are no validation checkpoints — no error handling for failed searches, rate limiting, invalid JQL, or verification that results are correct before proceeding with bulk operations. | 2 / 3 |
Progressive Disclosure | The content is a monolithic wall of text with everything inline — TypeScript interfaces, implementation functions, JQL reference tables, curl examples, response structures, and pagination formulas all in one file. The JQL reference, curl examples, and TypeScript patterns could easily be split into separate referenced files. No bundle files exist to offload this content. | 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
df877a9
- 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.