Name: webinarjam
Rating: 60.8 (1 reviews)
Author: membranedev

webinarjam

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

Quality

71%

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

Quality

Content

76%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 CLI commands and a thorough flags table, and is reasonably well-organized into clear sections. Its weak spots are a verbose introductory paragraph and the absence of validation/verification steps for destructive operations the proxy and action-run paths enable.

Suggestions

Trim the opening paragraph to one line and remove explanatory prose Claude can infer (e.g. who uses WebinarJam) to tighten token efficiency.

Add an explicit verify step before destructive proxy/action calls, e.g. dry-run or GET-then-confirm before POST/PUT/DELETE, to lift workflow clarity above the destructive-ops cap.

Fix the loose step numbering — label 'Step 1 / Step 2' explicitly or remove the dangling 'skip to Step 2' reference — so the connection-to-action sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command/flag documentation, but the opening paragraph ('used by businesses, marketers, and educators... generate leads, and sell products') and a few prose explanations are over-explanation that could be trimmed, fitting 'efficient; minor instances of over-explanation'.	4 / 5
Actionability	Provides fully executable, copy-paste-ready commands across every common case (install, login, connection ensure/get, action list/run, request) plus a complete flags table, matching 'fully executable; specific examples cover the common cases'.	5 / 5
Workflow Clarity	A rough sequence exists with good state-machine checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED), but the step numbering is loose ('skip to Step 2' with Step 2 unlabeled) and there is no validation/verification step for destructive operations enabled via proxy (DELETE) and action run, so the destructive-ops cap at 3 applies.	3 / 5
Progressive Disclosure	No bundle files exist, so all content lives in one well-sectioned SKILL.md with clear headers and no nested references — good structure with minor organization gaps, fitting 'good structure; most content appropriately placed' rather than 5 since the ~140-line single file could benefit from splitting reference material out.	4 / 5
	Total	16 / 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 is clear and well-formed with both a 'what' and an explicit 'Use when' trigger, and naming a specific platform keeps conflict risk low. Its main weakness is generic, non-webinar-specific action language and missing natural trigger terms like 'webinars' or 'registrants'.

Suggestions

Replace generic actions with concrete WebinarJam operations, e.g. 'manage webinars, registrants, and replays, and automate webinar workflows'.

Expand the trigger clause to include natural user phrases, e.g. 'Use when the user wants to manage webinars, registrants, replays, or webinar series'.

Mention key WebinarJam entities (registrants, replays, webinar series) so the description surfaces the terms users actually say.

Dimension	Reasoning	Score
Specificity	Names the domain (WebinarJam) plus a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete webinar-specific operations like registering attendees or fetching replays, fitting the 'names domain and 1-2 concrete actions, not comprehensive' anchor.	3 / 5
Completeness	Explicitly answers both what ('WebinarJam integration. Manage data, records, and automate workflows.') and when ('Use when the user wants to interact with WebinarJam data.'), but the 'when' is generic rather than concrete trigger phrases, so it sits at 'has both what and when; when could be more specific' rather than 5.	4 / 5
Trigger Term Quality	Includes the relevant brand keyword 'WebinarJam' and a trigger ('interact with WebinarJam data') but misses the natural terms users would say — webinars, registrants, attendees, replays — matching 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	Names a specific named platform (WebinarJam) with a distinct trigger, giving it a clear niche with minimal overlap risk against other skills.	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/webinarjam/SKILL.md
Commit: f484c82

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