CtrlK
BlogDocsLog inGet started
Tessl Logo

jira-issues

Create, read, update, and delete Jira issues. Use when managing Stories, Tasks, Bugs, or Epics - includes field updates and metadata.

64

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Risky

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

A highly actionable body with executable code and concrete API details, but it is over-long for a single file, repeats the ADF pattern across sections, and lacks validation/verification steps for destructive and batch operations.

Suggestions

Add validation/verification checkpoints for delete and bulk-create (e.g., confirm the issue key was returned, handle per-issue failures in bulk operations) before proceeding.

Reduce duplication by defining the ADF paragraph helper once and reusing it in the create/update functions and curl examples.

Split the large API reference (interfaces, curl examples, required-fields, ADF) into one-level-deep reference files and keep SKILL.md as an overview with clearly signaled links.

DimensionReasoningScore

Conciseness

The body is mostly efficient and free of generic concept explanation, but duplicates the same ADF construction across the TypeScript create/update functions, the curl examples, and the standalone ADF section, so it could be meaningfully tightened.

2 / 3

Actionability

It provides fully executable TypeScript functions, runnable curl commands, an endpoint summary table, and required-fields lists that are copy-paste ready.

3 / 3

Workflow Clarity

Steps 1-6 are sequenced, but destructive (delete) and batch (bulk create) operations have no validation or verification checkpoints, which caps workflow clarity at 2 per the rubric.

2 / 3

Progressive Disclosure

No bundle files exist and the ~360-line body keeps all reference material (interfaces, functions, curl, ADF, common mistakes) inline rather than splitting it into one-level-deep reference files.

2 / 3

Total

9

/

12

Passed

Description

85%

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 concise, third-person description that clearly states capabilities and includes an explicit Use-when trigger. It is specific and distinct; the only gap is missing common colloquial trigger terms like "ticket".

Suggestions

Add common natural variations such as "tickets" and "subtasks" to the trigger clause to improve keyword coverage.

Consider mentioning transitions/status changes explicitly, since "field updates and metadata" understates the workflow/transition capability.

DimensionReasoningScore

Specificity

"Create, read, update, and delete Jira issues" lists multiple concrete CRUD actions, matching the anchor for listing several specific actions rather than naming only a domain.

3 / 3

Completeness

It answers both what (CRUD on Jira issues) and when via an explicit "Use when managing Stories, Tasks, Bugs, or Epics" trigger clause.

3 / 3

Trigger Term Quality

It surfaces natural terms ("Jira issues", "Stories, Tasks, Bugs, or Epics") but omits very common colloquial variations such as "ticket" and "subtask" that users routinely say.

2 / 3

Distinctiveness Conflict Risk

The Jira-issues niche with distinct issue-type triggers is clearly distinguishable and unlikely to fire for unrelated skills.

3 / 3

Total

11

/

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.

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.