jira-search

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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Risky

Do not use without reviewing

Quality

Content

65%

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

The content is highly actionable with executable code and clear sequencing, but it is somewhat verbose with redundant JQL/curl examples and lacks validation feedback loops for its batch paginated operations. No bundle files exist, so the large inline body misses an opportunity to split detail into reference files.

Suggestions

Add an error-handling/validation step around the paginated searchAllIssues loop and the API request (e.g., check HTTP status, retry/abort on failure) to introduce a feedback loop for batch operations.

Deduplicate JQL examples — the operators table, TypeScript builders, and "Common JQL Patterns" block overlap; keep one canonical reference and trim the rest.

Move the three curl examples and the full JQL quick reference into a separate reference file (e.g. references/jql-reference.md) and link to it, reducing the inline body length.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean code, tables, and references with no over-explanation of Jira/JQL basics, but it carries redundancy — JQL patterns repeat operators already shown in the TypeScript builders and operators table, three near-identical curl blocks, and pagination explained both in code and a separate formula section — so it could be tightened.	2 / 3
Actionability	It provides fully executable TypeScript functions, copy-paste curl examples, concrete JQL patterns, and a response structure, giving specific and complete actionable guidance.	3 / 3
Workflow Clarity	Steps are sequenced (Step 1–5) and pagination includes a termination check, but batch/paginated operations have no validation or error-recovery checkpoints and the API call has no failure feedback loop, which per the rubric caps workflow clarity at 2.	2 / 3
Progressive Disclosure	No bundle files exist and references point only to external Atlassian docs, while ~320 lines of inline content (builder library, three curl examples, JQL reference) could be split into separate files; sections are organized but content that should be separate is inline.	2 / 3
	Total	9 / 12 Passed

Description

90%

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 an explicit "Use when" trigger clause covering natural search terms. The only mild weakness is that specificity lists one primary action rather than a broad set of concrete capabilities.

Dimension	Reasoning	Score
Specificity	"Search Jira issues using JQL queries" names a concrete domain and action but only a single primary action rather than multiple specific concrete actions, matching the anchor that names domain and some actions but is not comprehensive.	2 / 3
Completeness	It explicitly states both what the skill does ("Search Jira issues using JQL queries") and when to use it ("Use when filtering issues by project, status, assignee, date, or building reports"), matching the anchor that clearly answers both what and when with explicit triggers.	3 / 3
Trigger Term Quality	It includes natural trigger terms users would say — "Jira issues", "JQL", and "project, status, assignee, date, building reports" — giving good coverage of common phrasings.	3 / 3
Distinctiveness Conflict Risk	The "Jira"/"JQL" niche with distinct trigger terms is clearly distinguishable and unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: NeverSight/skills_feed
Commit: ff6a653

Reviewed: 5 days 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.