jira-issues

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

Quality

68%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Risky

Do not use without reviewing

Optimize this skill with Tessl

npx tessl skill review --optimize ./data/skills-md/01000001-01001110/agent-jira-skills/jira-issues/SKILL.md

Quality

Discovery

100%

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

This is a strong, well-crafted skill description that concisely covers concrete actions, includes natural trigger terms, and clearly delineates both what the skill does and when to use it. It uses proper third-person voice and is specific enough to be easily distinguishable from other skills while remaining concise.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions (create, read, update, delete) and specifies the domain (Jira issues) along with specific issue types (Stories, Tasks, Bugs, Epics) and mentions field updates and metadata.	3 / 3
Completeness	Clearly answers both 'what' (CRUD operations on Jira issues, field updates, metadata) and 'when' ('Use when managing Stories, Tasks, Bugs, or Epics') with explicit trigger guidance.	3 / 3
Trigger Term Quality	Includes strong natural keywords users would say: 'Jira', 'issues', 'Stories', 'Tasks', 'Bugs', 'Epics', and CRUD-related terms. These are terms users naturally use when requesting Jira work.	3 / 3
Distinctiveness Conflict Risk	Clearly scoped to Jira issue management with specific issue types mentioned. The 'Jira' keyword and specific issue type names (Stories, Tasks, Bugs, Epics) create a distinct niche unlikely to conflict with other skills.	3 / 3
	Total	12 / 12 Passed

Implementation

37%

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

The skill provides highly actionable, executable code for Jira CRUD operations but is excessively verbose, including full type definitions and duplicate examples (TypeScript + curl) that Claude could generate from minimal specifications. The numbered 'steps' are misleadingly labeled as a workflow when they're independent operations, and critical validation/error handling is absent for destructive operations like delete and bulk create.

Suggestions

Drastically reduce verbosity: replace full TypeScript implementations with a concise API reference table (endpoint, method, key fields, gotchas) and one representative code example. Claude can generate the rest.

Add validation and error handling: include response status checking after each operation, especially for delete (confirm issue exists first) and bulk create (handle partial failures).

Restructure the 'steps' as independent operations rather than a sequential workflow, or create an actual workflow (e.g., 'create issue → verify creation → update fields → validate update').

Move the ADF format reference and curl examples into separate bundle files, keeping SKILL.md as a concise overview with pointers.

Dimension	Reasoning	Score
Conciseness	The skill is extremely verbose at ~300 lines. It includes full TypeScript interface definitions and function implementations that Claude could easily generate from a concise specification. The JiraIssue interface alone is ~30 lines of type definitions Claude already knows. The curl examples largely duplicate the TypeScript code. The 'Required Fields by Issue Type' section repeats the same three fields for Story, Task, and Bug with minimal variation.	1 / 3
Actionability	The code is fully executable TypeScript with complete function signatures, proper ADF formatting, and working curl examples. Both programmatic and CLI approaches are provided with concrete, copy-paste ready examples including proper headers and JSON payloads.	3 / 3
Workflow Clarity	The 'steps' are not a workflow but rather independent CRUD operations labeled as steps 1-6. There is no validation after create/update/delete operations, no error handling guidance, and the bulk create operation (a batch/destructive operation) has no validation or error recovery. The delete operation has no confirmation or safety checks.	1 / 3
Progressive Disclosure	The content has some structure with sections and a reference table, but it's a monolithic file with no bundle files to offload detail. The full TypeScript implementations, curl examples, and ADF format documentation could be split into separate reference files. The references to external Atlassian docs are good but the inline content is too heavy.	2 / 3
	Total	7 / 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: NeverSight/skills_feed
Commit: df877a9

Reviewed: 3 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.