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.

67

Quality

80%

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

SKILL.md
Quality
Evals
Security

Quality

Content

68%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 with executable code and curl for all operations, but it repeats the ADF format several times and omits validation/verification checkpoints for destructive delete and batch bulk-create operations. Splitting reference detail into bundle files would improve organization.

Suggestions

Consolidate the Atlassian Document Format example into one place and reference it from createIssue/updateIssue/curl instead of repeating the structure four times.

Add verification steps after destructive and batch operations, e.g., re-fetch the issue after update/delete and handle partial failures in bulkCreateIssues instead of relying on bare Promise.all.

Move the detailed ADF format reference and the required-fields-by-issue-type tables into a separate references file to keep SKILL.md a lean overview.

DimensionReasoningScore

Conciseness

Content is code-heavy and mostly earns its place, but the Atlassian Document Format structure is repeated verbatim in createIssue, updateIssue, the curl example, and a dedicated ADF section, which is padding that could be consolidated.

3 / 5

Actionability

Provides fully executable TypeScript functions for every CRUD operation plus copy-paste curl examples covering the common cases, with complete request bodies and endpoints.

5 / 5

Workflow Clarity

The Step 1-6 sections are individual operations rather than a sequenced pipeline, and the destructive delete and batch bulk-create operations lack any validation or verification checkpoints, capping this dimension at 3 per the rubric.

3 / 5

Progressive Disclosure

Well-organized into clear sections with one-level-deep external references clearly signaled in a References section; no bundle files exist, and the single ~360-line file is well structured though some content (ADF detail, required-fields tables) could be split out.

4 / 5

Total

15

/

20

Passed

Description

92%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, third-person description that clearly states capabilities and an explicit 'Use when' trigger with concrete issue types. Minor improvement possible by adding synonyms like 'tickets' for broader natural-language coverage.

DimensionReasoningScore

Specificity

Names four concrete CRUD actions ('Create, read, update, and delete Jira issues') plus 'field updates and metadata', giving comprehensive coverage of the domain's operations rather than generic language.

5 / 5

Completeness

Explicitly answers both what ('Create, read, update, and delete Jira issues... includes field updates and metadata') and when ('Use when managing Stories, Tasks, Bugs, or Epics') with concrete trigger phrases.

5 / 5

Trigger Term Quality

'Use when managing Stories, Tasks, Bugs, or Epics' supplies natural issue-type keywords users say, but omits common synonyms like 'tickets' or 'Jira tickets'.

4 / 5

Distinctiveness Conflict Risk

Scoped to Jira issues with specific issue-type triggers (Stories, Tasks, Bugs, Epics), creating a clear niche with minimal overlap risk against other skills.

5 / 5

Total

19

/

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.