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

clickmeeting

ClickMeeting integration. Manage data, records, and automate workflows. Use when the user wants to interact with ClickMeeting 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/clickmeeting/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 is highly actionable with concrete CLI commands and a clear connection workflow, but it carries marketing fluff, lacks validation safeguards around its destructive actions, and keeps all reference material inline in a single file. It is practical yet could be tightened and restructured.

Suggestions

Trim the introductory marketing paragraph and filler phrases ("so you can focus on the integration logic rather than auth plumbing") to improve token efficiency.

Add an explicit validation/confirmation step before destructive actions such as delete-conference (e.g. list the target first and confirm state) to satisfy the destructive-operation workflow requirement.

Move the popular-actions table (and any per-action schema details) into a references file and link to it from SKILL.md so the main file stays a lean overview.

Dimension	Reasoning	Score
Conciseness	Most of the body is efficient concrete command reference, but it includes unnecessary padding such as the marketing-style intro ("used by businesses of all sizes for training, product demos, online courses") and filler like "so you can focus on the integration logic rather than auth plumbing", placing it at mostly-efficient with some tightening needed rather than the lean level 4.	3 / 5
Actionability	The body provides copy-paste-ready executable commands throughout (install, login, connection ensure, polling with --wait, action list/run with --input, proxy request with a full flags table), covering the common cases exactly as the level-5 anchor requires.	5 / 5
Workflow Clarity	The connection-setup sequence is clearly staged with a polling feedback loop (BUILDING → READY / CLIENT_ACTION_REQUIRED → re-poll), but the skill exposes destructive operations (e.g. delete-conference) with no validation or confirmation checkpoint before running them, so per the rubric cap workflow clarity cannot exceed 3.	3 / 5
Progressive Disclosure	The body is well-sectioned with clear headers, but no bundle files exist and everything is monolithic, including a 19-row popular-actions reference table inlined in SKILL.md, so it has structure without any one-level-deep references to separate files.	3 / 5
	Total	14 / 20 Passed

Description

57%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 correctly uses third person and includes an explicit "Use when" trigger tied to a named product, but its capability statement is generic and its trigger terms miss the natural vocabulary users would say. It is solid but unspecific.

Suggestions

Replace generic verbs with concrete actions, e.g. "List and create conferences, register participants, send invitations, and retrieve recordings."

Add natural trigger terms users actually say: "Use when the user wants to manage ClickMeeting webinars, conferences, meetings, recordings, or sessions."

Tie the trigger to specific file types or entities (conference rooms, sessions, attendees) to sharpen distinctiveness.

Dimension	Reasoning	Score
Specificity	The description names the domain ("ClickMeeting integration") but its actions are generic and minimal — "Manage data, records, and automate workflows" — with no concrete operations like listing conferences or sending invitations, matching the anchor for naming the domain with minimal/generic actions rather than the 1-2 concrete actions at level 3.	2 / 5
Completeness	Both a "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with ClickMeeting data") are present, but the "when" trigger is generic and the "what" is vague, so it does not reach the concrete trigger phrases required for a 5.	4 / 5
Trigger Term Quality	It surfaces the keyword "ClickMeeting" and the phrase "interact with ClickMeeting data", but omits the natural terms users would actually say (webinar, conference, meeting, recording, session), so keyword coverage is partial with common variations missing.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product "ClickMeeting" gives it a clear niche with low conflict risk against other skills, but the generic action framing ("interact with ClickMeeting data") leaves minor overlap risk versus a level-5 anchor that pairs a distinct niche with concrete triggers.	4 / 5
	Total	13 / 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/clickmeeting/SKILL.md
Commit: f484c82

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