CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

jira-search

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

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

—

The risk profile of this skill

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.

Highly actionable content with executable TypeScript, curl, and JQL examples and a clear implementation sequence. The main weaknesses are inlined JQL reference material that duplicates Claude's existing knowledge and a monolithic single-file structure that would benefit from splitting into reference files.

Suggestions

Move the JQL Quick Reference and Common JQL Patterns sections into a one-level-deep reference file (e.g. references/jql.md) and keep only the most common patterns inline in SKILL.md.

Trim or remove the JQL operators table, which restates syntax Claude already knows; keep only Jira-specific nuances such as accountId vs email for assignee.

Add a short validation step for search workflows, e.g. checking the API response for JQL error messages before paginating, to strengthen feedback loops for batch result retrieval.

DimensionReasoningScore

Conciseness

The TypeScript, curl, and pagination sections are dense and instructional, but the JQL Quick Reference operators table and Common JQL Patterns block (roughly lines 180-234) restate JQL syntax Claude already knows, fitting anchor 3's 'mostly efficient but includes some unnecessary explanation'.

3 / 5

Actionability

Fully executable copy-paste-ready code: searchIssues with a real endpoint and request body, a working paginated searchAllIssues loop, complete curl commands, and concrete JQL builders covering the common cases, which matches anchor 5 exactly.

5 / 5

Workflow Clarity

The Step 1-5 implementation pattern is clearly sequenced from interfaces to basic search, pagination, builders, and composed examples, but there are no validation or error-recovery steps for invalid JQL or failed requests, matching anchor 4's 'clear sequence with minor validation gaps'; search is read-only so the destructive-operation cap does not apply.

4 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/), so all 315 lines including the JQL quick reference, curl examples, and response structure are inlined in SKILL.md; sections are well organized but content that clearly belongs in separate one-level-deep reference files is inline, matching anchor 3.

3 / 5

Total

15

/

20

Passed

Description

87%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.

A strong description: third person, concise, with explicit what and when clauses and concrete trigger terms. Minor room to improve by adding synonyms like "tickets" or "find issues" and mentioning pagination or field selection.

DimensionReasoningScore

Specificity

"Search Jira issues using JQL queries" plus "filtering issues by project, status, assignee, date, or building reports" names several concrete actions with only minor gaps (pagination and field selection appear in the body but not the description), matching the anchor for several specific actions rather than the 1-2 of anchor 3.

4 / 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, structurally parallel to the anchor-5 good example; the when-clause is fully explicit, not weakly implied as in anchor 4.

5 / 5

Trigger Term Quality

Natural keywords like "Jira", "issues", "JQL", "project", "status", "assignee", and "reports" give good coverage of phrases a user would say, but common synonyms such as "tickets" or "find/list issues" are missing, so it falls short of anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

"Jira issues using JQL queries" carves a clear search niche that is easily distinguished from related skills such as jira-auth or issue-creation skills, with minimal conflict risk and no evident overlap with closely related skills.

5 / 5

Total

18

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

NeverSight/learn-skills.dev

Path

data/skills-md/01000001-01001110/agent-jira-skills/jira-search/SKILL.md

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.