Name: cherwell-itsm
Rating: 52.8 (1 reviews)
Author: membranedev

cherwell-itsm

Cherwell ITSM integration. Manage data, records, and automate workflows. Use when the user wants to interact with Cherwell ITSM 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/cherwell-itsm/SKILL.md

Quality

Content

57%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 is highly actionable with concrete Membrane CLI commands and a sensible install-to-execute sequence, but it leads with exposition Claude already knows, lacks explicit validation/feedback loops around its destructive-capable actions, and keeps all reference material inline rather than splitting it out. The result is competent but leaves the workflow and progressive-disclosure dimensions capped.

Suggestions

Trim the opening overview paragraph ('Cherwell ITSM is a service management platform...') — Claude already knows what Cherwell is.

Add an explicit validate-then-fix feedback loop for destructive operations, e.g. after `membrane action run` and around `membrane request` with PUT/DELETE/PATCH methods.

Move the connection-state field reference and the proxy flag table into a separate reference file linked from the body to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste-ready commands, but it opens with general-purpose exposition Claude already knows ('Cherwell ITSM is a service management platform used by IT departments... It helps organizations automate workflows, manage incidents, and provide self-service options'), and the connection-state walkthrough repeats polling instructions, which could be tightened to reach a 4.	3 / 5
Actionability	It provides concrete, executable commands for the common path (login, connection ensure, action list/run, request) with flags documented in a table; it falls just short of 5 because placeholders like CONNECTION_ID and actionId are never resolved into a worked end-to-end example showing the actual output.	4 / 5
Workflow Clarity	A rough sequence exists (install -> login -> connect -> search actions -> run), but there are no explicit validation checkpoints for the destructive/batch-capable actions (action run, request with PUT/DELETE/PATCH), and the destructive-cap guideline caps workflow clarity at 3 when validation feedback loops are missing.	3 / 5
Progressive Disclosure	Content is sectioned reasonably (Overview, Working with Cherwell ITSM, Popular actions, Best practices) with no bundle files to reference, but the connection-state reference and proxy-flag table are inlined material that could live in a separate reference, and the skill relies on a single inline document rather than signaled one-level-deep references.	3 / 5
	Total	13 / 20 Passed

Description

61%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 is anchored by a distinctive product name, but it relies on generic verbs ('manage data, records') instead of concrete ITSM actions and omits common user synonyms like 'incidents' or 'tickets'. Tightening the action list and broadening trigger terms would lift it from adequate to strong.

Suggestions

Replace generic verbs with concrete ITSM actions, e.g. 'Create and update incidents, manage change requests, and query business objects.'

Add natural trigger synonyms users say, such as 'incidents', 'tickets', 'service requests', or 'change tickets'.

Keep the 'Use when the user wants to interact with Cherwell ITSM data' clause but add concrete triggers like 'when the user mentions Cherwell, incidents, or ITSM tickets'.

Dimension	Reasoning	Score
Specificity	The description names the domain (Cherwell ITSM) and three actions ('Manage data, records, and automate workflows'), but 'manage data' and 'records' are generic rather than the concrete ITSM actions (incidents, changes, assets) that anchor a score of 4-5 would require.	3 / 5
Completeness	It explicitly states both the 'what' ('Manage data, records, and automate workflows') and the 'when' ('Use when the user wants to interact with Cherwell ITSM data'), but the 'when' clause is a single broad condition rather than the concrete multi-trigger phrasing that would earn a 5.	4 / 5
Trigger Term Quality	It contains the natural product name 'Cherwell ITSM' and 'Cherwell ITSM data' as the trigger phrase, but it lacks common synonyms a user might actually say (incidents, tickets, service requests, ITSM) and a file extension, so coverage is partial rather than comprehensive.	3 / 5
Distinctiveness Conflict Risk	The explicit Cherwell ITSM product name gives it a clear niche with low conflict risk against other skills, though the generic verbs ('manage data, records') leave minor overlap risk with adjacent ITSM/service-management skills.	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/cherwell-itsm/SKILL.md
Commit: f484c82

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.