Name: manageengine-servicedesk-plus-cloud
Rating: 55.2 (1 reviews)
Author: membranedev

manageengine-servicedesk-plus-cloud

Manageengine Servicedesk Plus Cloud integration. Manage data, records, and automate workflows. Use when the user wants to interact with Manageengine Servicedesk Plus Cloud data.

Quality

63%

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/manageengine-servicedesk-plus-cloud/SKILL.md

Quality

Content

65%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 content delivers concrete, executable Membrane CLI commands with a coherent integration workflow and connection-state validation, but suffers from broken step numbering and keeps all detail inline with no reference files. Fixing the step labels and splitting the proxy/state-machine detail into a referenced file would improve clarity and disclosure.

Suggestions

Fix the step numbering: label the connect step '1', rename '1b' to '1b' under it, and define the missing 'Step 2' (searching/running actions) explicitly so cross-references resolve.

Move the proxy flag table and the clientAction state-machine details into a referenced file (e.g. REFERENCE.md) and link to it from the body.

De-duplicate the action-discovery command (it appears under both 'Searching for actions' and 'Popular actions') and trim the product-intro paragraph to assumed knowledge.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands and a tight flag table, though the product intro paragraph and the repeated action-list command add minor padding; not a 5 because of those small redundancies.	4 / 5
Actionability	Concrete, copy-paste-ready membrane commands appear for install, auth, connection, action search/run, and proxy requests; minor gaps (placeholders like CONNECTION_ID/actionId) keep it just below fully executable 5.	4 / 5
Workflow Clarity	The install->auth->connect->search->run sequence exists with connection-state polling, but step numbering is broken (references 'Step 2' and a '1b' subsection with no labeled Step 1 or Step 2), leaving checkpoints implicit and gaps in the sequence.	3 / 5
Progressive Disclosure	Headers organize the single file reasonably, but there are no bundle files and content that could be split (the proxy flag table, clientAction state details) is inlined; not a 4 because references/signaling to separate materials are absent.	3 / 5
	Total	14 / 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 clearly names the target product and includes an explicit 'Use when' trigger, giving it good completeness and distinctiveness, but its capability actions are generic ('Manage data, records, automate workflows') rather than concrete. Tightening the action list with specific operations would raise specificity and trigger-term quality.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete capabilities such as 'create and track requests, manage technicians, and query service categories'.

Add natural synonym/abbreviation triggers users might say, e.g. 'ServiceDesk Plus', 'SDP Cloud', or 'ITSM tickets'.

Tie the 'when' clause to concrete user intents (e.g. 'Use when the user wants to create, update, or query ServiceDesk Plus tickets, requests, or assets').

Dimension	Reasoning	Score
Specificity	It names the domain but the actions ('Manage data, records, and automate workflows') are minimal and generic rather than concrete capabilities; not the level-3 anchor because the actions are not specific concrete operations.	2 / 5
Completeness	It states both what it does ('Manage data, records, and automate workflows') and when to use it ('Use when the user wants to interact with Manageengine Servicedesk Plus Cloud data'); the 'what' is somewhat generic, keeping it just below a 5.	4 / 5
Trigger Term Quality	'Manageengine Servicedesk Plus Cloud' and 'interact with ... data' are relevant keywords a user would say, but no synonyms, abbreviations, or variations are included, matching the level-3 anchor.	3 / 5
Distinctiveness Conflict Risk	The named product gives it a clear niche with a distinct trigger phrase and minimal overlap risk with other skills.	5 / 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/manageengine-servicedesk-plus-cloud/SKILL.md
Commit: f484c82

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