Name: demodesk
Rating: 59.2 (1 reviews)
Author: membranedev

demodesk

Demodesk integration. Manage data, records, and automate workflows. Use when the user wants to interact with Demodesk data.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/demodesk/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.

The body is highly actionable with executable commands and a validated connection workflow, but it loses conciseness to marketing prose and has a couple of structural ambiguities in step labeling and inline reference material.

Suggestions

Delete the marketing opener ("Demodesk is an AI-powered meeting platform...") and other explanatory fluff; keep only what Claude needs to operate the integration.

Fix the step references: either label "Step 1"/"Step 2" explicitly or remove the "skip to Step 2" phrasing so the workflow navigation is unambiguous.

De-duplicate the action-list command, which appears nearly identically in both "Searching for actions" and "Popular actions".

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with well-placed code blocks, but the opening marketing paragraph ("AI-powered meeting platform... close more deals") and phrases like "so you can focus on the integration logic rather than auth plumbing" are unnecessary explanation Claude does not need.	3 / 5
Actionability	Commands are fully executable and copy-paste ready across the common cases — install, login, connection ensure, polling, action list/run, and proxy requests — each with concrete flags and JSON output examples.	5 / 5
Workflow Clarity	The connect-to-run sequence has explicit validation checkpoints and feedback loops (poll until state changes, re-poll after client action, check the error field), but references like "skip to Step 2" point to a step that is never labeled, leaving a minor structural gap.	4 / 5
Progressive Disclosure	Content is well organized into clearly headed sections in a single file with no nested references, but longer reference-like material (the clientAction state table, proxy flag table) is inlined rather than split out, leaving minor organization gaps.	4 / 5
	Total	16 / 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 answers both what and when and is anchored to a distinct product, but its capability list and trigger terms are generic rather than reflecting Demodesk's actual meeting/demo use cases shown in the body.

Suggestions

Replace generic actions ("Manage data, records, and automate workflows") with concrete Demodesk capabilities such as scheduling meetings, running demos, and managing attendees.

Expand the "Use when" clause with natural trigger phrases users would say, e.g. "Use when the user mentions Demodesk, wants to schedule or automate Demodesk meetings, or run demos."

Dimension	Reasoning	Score
Specificity	The description names the domain ("Demodesk integration") and a few actions ("Manage data, records, and automate workflows"), but those actions are generic rather than concrete Demodesk-specific capabilities like scheduling meetings or running demos.	3 / 5
Completeness	Both halves are present — a clear "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Demodesk data"), though the trigger clause is somewhat generic rather than listing concrete trigger phrases.	4 / 5
Trigger Term Quality	"Demodesk" and "Demodesk data" are relevant natural terms, but common variations a user would say (meetings, demos, scheduling) are absent, matching the anchor with some keywords but missing synonyms.	3 / 5
Distinctiveness Conflict Risk	Tying the skill to the named product "Demodesk" gives it a clear niche with low conflict risk, but the generic "manage data, records" portion leaves minor overlap with other data-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/demodesk/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.