jira-search

Search Jira issues using JQL queries. Use when filtering issues by project, status, assignee, date, or building reports.

Quality

70%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

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.md

Quality

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. The explicit 'Use when...' clause with multiple trigger scenarios is a strength. The main weakness is that the 'what' portion is somewhat narrow—it only mentions searching, so if the skill also supports other Jira operations, those should be listed.

Suggestions

Consider listing additional concrete actions if the skill supports them (e.g., 'Search Jira issues using JQL queries, filter by fields, and export results').

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 an explicit 'Use when...' clause.	3 / 3
Trigger Term Quality	Includes strong natural keywords users would say: 'Jira', 'JQL', 'issues', 'project', 'status', 'assignee', 'date', 'reports', and 'filtering'. 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, date) creates a clear niche that is unlikely to conflict with other skills.	3 / 3
	Total	11 / 12 Passed

Implementation

50%

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—it includes extensive reference material (JQL operators, date formats, common patterns) that Claude already knows, plus TypeScript wrapper functions that over-engineer a simple REST API call. The workflow lacks error handling and validation steps, and the monolithic structure would benefit from splitting reference content into separate files.

Suggestions

Drastically reduce content by removing the JQL quick reference tables, date format tables, and common JQL patterns—Claude already knows JQL syntax. Keep only the API endpoint, a single search example, and pagination pattern.

Remove the TypeScript interface definitions and helper function builders; a single concrete search function and one curl example would suffice.

Add error handling and validation: check for HTTP errors, handle rate limiting (429 responses), validate JQL syntax errors in the response, and add a checkpoint before bulk operations.

Split the JQL reference and curl examples into a separate REFERENCE.md file, keeping SKILL.md as a concise overview with links.

Dimension	Reasoning	Score
Conciseness	The skill is excessively verbose at ~200+ lines. It includes TypeScript interface definitions, multiple helper function builders, and extensive JQL reference tables that Claude already knows. The curl examples, response structure, and pagination formula all add bulk that could be drastically condensed.	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	Steps are numbered and sequenced (Step 1-5), and pagination is handled with a clear loop pattern. However, there are no validation checkpoints—no error handling for failed API calls, rate limiting, invalid JQL, or verification that results are correct before proceeding with bulk operations.	2 / 3
Progressive Disclosure	The content is organized with clear sections and headers, and references external links. However, the JQL quick reference, curl examples, response structure, and common mistakes are all inline when much of this could be split into separate reference files, making the main skill leaner.	2 / 3
	Total	8 / 12 Passed

Validation

100%

Warnings & errors only

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: aa009ea

Reviewed: about 1 hour ago

Table of Contents

Discovery Implementation Validation

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.