Name: jira-service-desk
Rating: 52.8 (1 reviews)
Author: membranedev

jira-service-desk

Jira Service Desk integration. Manage Tickets, Customers, Agents. Use when the user wants to interact with Jira Service Desk data.

Quality

59%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/jira-service-desk/SKILL.md

Quality

Content

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

The skill delivers executable, well-structured CLI guidance with a solid connection-setup workflow, but it is undermined by a massively padded and duplicated entity catalog and an unnecessary intro paragraph that inflate the token budget.

Suggestions

Delete the duplicated/padded "Insight Object Type Attribute ..." list (lines 67-166); keep only real Jira Service Management objects, and move the full catalog to a separate reference file.

Remove the "Jira Service Desk is a help desk and service management software..." intro paragraph that restates common knowledge.

Fix the broken "skip to Step 2" navigation and add a brief post-run validation note (check the output/error field before proceeding).

Dimension	Reasoning	Score
Conciseness	The ~100-line "Insight Object Type Attribute ..." catalog (lines 67-166) is heavily padded with duplicated entries (e.g. "Calculated", "Validated", "Created" each appear twice), plus a "what is Jira Service Desk" intro Claude already knows — several padded sections despite otherwise efficient CLI docs.	2 / 5
Actionability	Concrete, executable membrane CLI commands with flags, JSON input examples, and proxy usage cover the common cases, but placeholders like CONNECTION_ID and <actionId> and the "QUERY" intent need substitution, leaving minor gaps.	4 / 5
Workflow Clarity	The install → auth → connection ensure → poll → search → run sequence is clear, and connection polling has explicit state branches (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), but the broken "skip to Step 2" reference (no Step 2 exists) and absent post-run validation are minor gaps.	4 / 5
Progressive Disclosure	Section headers give some structure, but with no bundle files the entire bulk (the padded entity catalog and the popular-actions table) is inlined in SKILL.md rather than split into a one-level-deep reference.	3 / 5
	Total	13 / 20 Passed

Description

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

The description answers both what and when and targets a distinct niche, but it relies on a single generic action verb ("Manage") and a generic trigger phrase without the natural synonyms (tickets, requests, incidents) users actually say.

Suggestions

Replace the generic verb "Manage" with concrete actions, e.g. "List, create, update, and delete customer requests, organizations, service desks, and customers."

Expand the trigger clause with natural synonyms, e.g. "Use when the user mentions Jira Service Desk, JSD tickets, service requests, help desk requests, or incidents."

Align the named entities with the API's actual objects (Customer Request, Organization, Service Desk) rather than the loosely-mapped "Tickets, Customers, Agents".

Dimension	Reasoning	Score
Specificity	"Manage Tickets, Customers, Agents" names the domain plus three managed entities, but the only action verb is the generic "Manage", so it is not a comprehensive list of concrete actions (closer to 3 than 4).	3 / 5
Completeness	It has both a clear "what" ("Manage Tickets, Customers, Agents") and an explicit "Use when the user wants to interact with Jira Service Desk data" clause, but the when lacks concrete trigger phrases so it stops short of 5.	4 / 5
Trigger Term Quality	"Jira Service Desk" is a natural term users say, but the trigger "interact with Jira Service Desk data" omits common synonyms like tickets, service requests, help desk, or incidents, leaving keyword coverage partial.	3 / 5
Distinctiveness Conflict Risk	"Jira Service Desk integration" carves a clear niche, but it could overlap with a broader Jira/Jira Service Management skill, so there is minor conflict risk rather than none.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/jira-service-desk/SKILL.md
Commit: f484c82

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.