Name: screendesk
Rating: 62.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

screendesk

Screendesk integration. Manage Organizations. Use when the user wants to interact with Screendesk data.

Quality

74%

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/screendesk/SKILL.md

Quality

Content

82%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 is highly actionable with copy-paste-ready CLI commands and a well-sequenced connection flow with state-based checkpoints. Its main weaknesses are minor over-explanation in the intro, a broken 'Step 2' cross-reference, and a single-file structure that could offload some heavy inline reference material.

Suggestions

Define the missing 'Step 2' target (or reword 'skip to Step 2' to point to a real section) and fix the '1b'-without-'1a' numbering.

Trim the marketing-style Screendesk intro and filler phrases ('fastest way to get a connection') for token efficiency.

Consider moving the full clientAction enum and proxy flags table into a separate reference file with a clear pointer, since the body exceeds the simple-skill size threshold.

Dimension	Reasoning	Score
Conciseness	The body is mostly executable commands with brief framing, but a few spots could be trimmed — the marketing-style intro ('helps businesses manage and resolve customer issues more efficiently') and filler like 'This is the fastest way to get a connection' — matching 'efficient; minor instances of over-explanation' rather than the fully lean 5 anchor.	4 / 5
Actionability	Fully executable, copy-paste-ready commands cover the common cases (install, login, connection ensure, action list/run, request proxy) with a clear flags table and explained placeholders like <actionId> and CONNECTION_ID, matching the 'fully executable; copy-paste ready; covers common cases' anchor.	5 / 5
Workflow Clarity	The connect flow is well sequenced with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-again feedback loop, but 'skip to Step 2' references a Step 2 that does not exist and numbering jumps oddly ('1b' with no '1'/'1a'), matching 'clear sequence with most checkpoints present; minor validation gaps' below the 5 anchor.	4 / 5
Progressive Disclosure	A single well-organized file with clear sections (Overview, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) and no nested references; the ~140-line size exceeds the 'under 50 lines' exception for a 5, and the full clientAction enum plus proxy flags table are somewhat heavy inline, matching 'good structure; most content appropriately placed; minor organization gaps'.	4 / 5
	Total	17 / 20 Passed

Description

66%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 has an explicit 'Use when...' clause and strong distinctiveness via a unique brand name, but its capability specificity and trigger-term coverage are thin — only 'Manage Organizations' as an action and the bare word 'Screendesk' as a trigger.

Suggestions

Expand the 'what' with concrete actions beyond 'Manage Organizations' (e.g., manage tickets, live chat, meetings, contacts) to lift specificity.

Add natural task phrases users would say (tickets, support conversations, help desk, knowledge base) to the trigger clause instead of generic 'interact with Screendesk data'.

Make the 'when' clause concrete with explicit triggers (e.g., 'Use when the user mentions Screendesk tickets, live chat, or customer support data').

Dimension	Reasoning	Score
Specificity	Names the Screendesk domain plus a single concrete action ('Manage Organizations') but offers no enumeration of what that entails, matching the 'names domain and 1-2 concrete actions, not comprehensive' anchor and falling below the 'several specific actions' anchor at 4.	3 / 5
Completeness	It has both a 'what' ('Manage Organizations') and an explicit 'when' ('Use when the user wants to interact with Screendesk data'), but the 'when' is generic rather than concrete trigger phrases, matching the 'has both what and when; when could be more explicit' anchor below the 5 anchor.	4 / 5
Trigger Term Quality	The only natural keyword is the proper noun 'Screendesk' in the 'Use when the user wants to interact with Screendesk data' trigger; common task phrases (tickets, chat, conversations, meetings) and synonyms are absent, matching 'some relevant keywords but missing common variations' rather than the 'good keyword coverage' at 4.	3 / 5
Distinctiveness Conflict Risk	'Screendesk integration' and 'interact with Screendesk data' carve a clear niche around a unique proper noun with minimal conflict risk against other skills, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.	5 / 5
	Total	15 / 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/screendesk/SKILL.md
Commit: f484c82

Reviewed: ~20 hours 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.