CtrlK
BlogDocsLog inGet started
Tessl Logo

jira-search

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

64

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./data/skills-md/01000001-01001110/agent-jira-skills/jira-search/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is actionable and well-sequenced with executable code and useful reference tables, respecting Claude's competence without padding. Its main weakness is organization: substantial reference material lives inline in a single file rather than being split into clearly signaled one-level-deep references.

Suggestions

Move the JQL quick reference (operators, date formats, patterns) and curl examples into a separate references file, leaving SKILL.md as an overview with a clearly signaled link.

De-duplicate the pagination logic: keep either the searchAllIssues implementation or the Pagination Formula section, not both, to tighten token usage.

Add a short error-handling note (e.g., handling 400 JQL syntax errors or rate limits) to give the search workflow an explicit feedback loop.

DimensionReasoningScore

Conciseness

The body is mostly lean code and reference tables with little concept re-teaching, but the curl examples and pagination formula partly duplicate the TypeScript implementations and could be trimmed.

4 / 5

Actionability

Concrete, mostly executable TypeScript functions and curl commands cover common search cases; minor gap is the TypeScript examples depend on an undefined JiraClient/JiraIssue type sourced externally.

4 / 5

Workflow Clarity

The Step 1-5 implementation pattern is a clear sequence (types -> basic search -> pagination -> builders -> examples) with a pagination termination check; as a read-only skill it needs no destructive-validation checkpoint, though no error-handling feedback loop is shown.

4 / 5

Progressive Disclosure

The ~315-line body is well sectioned but monolithic: the JQL quick reference, curl examples, and response structure are inlined where a separate reference file would aid navigation, and no bundle files are used.

3 / 5

Total

15

/

20

Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise, third-person, and clearly states both the capability and explicit trigger conditions. It is slightly thin on distinct concrete actions beyond search, but its trigger guidance is strong.

DimensionReasoningScore

Specificity

"Search Jira issues using JQL queries" names the domain and one concrete action (search via JQL); the filtering variations are trigger contexts rather than distinct capabilities, so coverage is not comprehensive.

3 / 5

Completeness

It explicitly answers both what ("Search Jira issues using JQL queries") and when ("Use when filtering issues by project, status, assignee, date, or building reports") with concrete trigger phrases.

5 / 5

Trigger Term Quality

"filtering issues by project, status, assignee, date, or building reports" supplies good natural keyword coverage of criteria users actually mention, though synonyms like "tickets" are missing.

4 / 5

Distinctiveness Conflict Risk

"Jira issues" and "JQL queries" carve a clear niche with minimal conflict risk, though it could overlap with sibling Jira skills such as jira-auth.

4 / 5

Total

16

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
NeverSight/skills_feed
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.