Name: solarwinds-service-desk
Rating: 61.6 (1 reviews)
Author: membranedev

solarwinds-service-desk

SolarWinds Service Desk integration. Manage Incidents, Problems, Changes, Assets, Solutions, Users and more. Use when the user wants to interact with SolarWinds Service Desk data.

Quality

73%

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/solarwinds-service-desk/SKILL.md

Quality

Content

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

A well-structured, command-driven skill body that is highly actionable and easy to navigate. The main weaknesses are minor over-explanation in the intro and a couple of small structural gaps (unlabeled Step 2, thin 'Popular actions').

Suggestions

Trim the introductory paragraph describing what SolarWinds Service Desk is; Claude already knows, and the official docs link suffices.

Label 'Step 2' explicitly (e.g. '## Step 2: Discover and run actions') so the 'skip to Step 2' reference resolves.

Populate 'Popular actions' with a few real action names/ids instead of repeating the discovery command.

Dimension	Reasoning	Score
Conciseness	Mostly lean command blocks with brief explanations, but the opening paragraph ('cloud-based IT service management platform... helps streamline IT operations') over-explains concepts Claude already knows.	4 / 5
Actionability	Provides concrete, copy-paste-ready commands for install, auth, connect, search, run, and proxy with a flag table; the 'Popular actions' section only re-states the discovery command without listing actual actions, a minor gap.	4 / 5
Workflow Clarity	Clear install→auth→connect→poll sequence with a state-check/poll feedback loop and CLIENT_ACTION_REQUIRED handling, but 'skip to Step 2' references an unlabeled Step 2.	4 / 5
Progressive Disclosure	Well-organized into clear sections in a single file with no bundle files or external references needed; over 50 lines so the simple-skill exception does not grant a 5, leaving minor organization gaps.	4 / 5
	Total	16 / 20 Passed

Description

71%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 solid, third-person description that states both what the skill does and when to use it, anchored to a distinct product niche. The main weakness is the generic trigger phrasing that omits natural user terms.

Suggestions

Add concrete trigger phrases users actually say, e.g. 'Use when the user wants to create or update tickets, incidents, changes, or assets in SolarWinds Service Desk'.

Replace 'and more' with the remaining entity types (Tasks, Releases, Contracts, Locations, Departments) to close the specificity gap.

Lead with the primary verb set (create, update, search) rather than the single generic verb 'Manage'.

Dimension	Reasoning	Score
Specificity	Names the domain and lists six concrete entity types ('Manage Incidents, Problems, Changes, Assets, Solutions, Users and more'), giving several specific actions, though the single verb 'Manage' and 'and more' leave minor coverage gaps.	4 / 5
Completeness	Clearly states what it does (manage those entities) and gives an explicit 'Use when the user wants to interact with SolarWinds Service Desk data' trigger, though the 'when' could name concrete scenarios.	4 / 5
Trigger Term Quality	The product name and 'interact with SolarWinds Service Desk data' are present, but the trigger clause is generic and misses natural user phrases like 'open a ticket' or 'incident management'.	3 / 5
Distinctiveness Conflict Risk	Targets a specific named ITSM product with distinct triggers, so it is clearly distinguishable from other skills with minimal conflict risk.	5 / 5
	Total	16 / 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/solarwinds-service-desk/SKILL.md
Commit: f484c82

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