Name: illumidesk
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

illumidesk

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

Quality

61%

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

Quality

Content

61%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 body is highly actionable with concrete Membrane CLI commands and a clear setup workflow, but it lacks validation checkpoints around its destructive create/update/delete actions and carries some padded introductory prose.

Suggestions

Add a validation/verification step before destructive actions (e.g., run a get/list action to confirm the target exists, or require explicit user confirmation before delete-user/delete-project/delete-team).

Trim the generic overview paragraph about what Illumidesk is and who uses it; assume Claude's competence and keep only CLI-specific guidance.

Clarify how to resolve the placeholders (CONNECTOR_ID, CONNECTION_ID, ACTION_ID) by cross-referencing the commands that produce them, or show a worked end-to-end example with substituted values.

Dimension	Reasoning	Score
Conciseness	The content is mostly command-focused and efficient, but the opening overview paragraph ("Illumidesk is a project management and collaboration platform...") and some explanatory prose in the proxy section are unnecessary padding that could be trimmed, matching the 'mostly efficient with some unnecessary explanation' anchor.	3 / 5
Actionability	It provides concrete, copy-paste-ready CLI commands with flags (login, connect, action list/run, request) and a populated popular-actions table, with only minor gaps from placeholders (CONNECTOR_ID, CONNECTION_ID, ACTION_ID, QUERY) and the indirection of extracting the connector ID from output.	4 / 5
Workflow Clarity	The setup sequence (install → login → connect → search → run) is clearly ordered, but destructive operations exposed via the table (delete-user, delete-project, delete-team) and create/update actions have no validation or verification checkpoint, which per the rubric caps this dimension at 3.	3 / 5
Progressive Disclosure	The skill is a single self-contained file with no bundle references and is well-organized under clear section headers; the inline popular-actions table is reasonable, leaving only minor organization gaps versus the ideal one-level-deep-reference anchor.	4 / 5
	Total	14 / 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 is third-person, concise, and includes an explicit 'Use when' trigger, which keeps it functional. Its main weaknesses are thin action coverage (only 'Manage Organizations') and limited trigger-term variation.

Suggestions

Expand the 'what' to list the key concrete actions the skill supports (e.g., manage users, projects, teams, servers, tickets, comments) instead of only 'Manage Organizations'.

Broaden the trigger phrase to cover natural user variations, e.g., 'Use when the user wants to manage Illumidesk users, projects, teams, tickets, or organizations.'

Avoid the slight over-claim risk by aligning the description's stated capabilities with the body's actual popular actions.

Dimension	Reasoning	Score
Specificity	Names the domain ("Illumidesk integration") and one concrete action ("Manage Organizations"), but the action coverage is minimal and not comprehensive, matching the anchor for 1-2 concrete actions without full coverage.	3 / 5
Completeness	It states a 'what' ("Illumidesk integration. Manage Organizations.") and an explicit 'when' ("Use when the user wants to interact with Illumidesk data"), so both are present with the 'when' slightly thin rather than missing, matching the anchor for having both with an improvable trigger.	4 / 5
Trigger Term Quality	The phrase "interact with Illumidesk data" surfaces the product name users would say, but it lacks common variations or synonyms beyond the single brand term, fitting the anchor for some relevant keywords with missing variations.	3 / 5
Distinctiveness Conflict Risk	Tying triggers to the specific named product "Illumidesk" makes it mostly distinct with only minor overlap risk against other integration skills, rather than the clearly-distinct-niche anchor of 5.	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/illumidesk/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.