CtrlK
BlogDocsLog inGet started
Tessl Logo

webinargeek

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

60

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/webinargeek/SKILL.md
SKILL.md
Quality
Evals
Security

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 executable CLI commands and reasonable structure, but its multi-step workflow has implicit validation and a couple of orphaned step labels that weaken clarity around risky operations.

Suggestions

Replace the loose 'Step 2' / '1b' references with a clearly numbered sequence so the install→auth→connect→run flow is unambiguous.

Add an explicit validate/retry checkpoint after destructive proxy calls (e.g., 'verify the response status before reporting success; on error, inspect the error field and retry or surface to the user').

Tighten the connection-state section by leading with the decision table and trimming explanatory prose.

DimensionReasoningScore

Conciseness

The body is mostly efficient CLI commands with minimal padding; the prose around connection states is justified operational detail rather than explaining concepts Claude already knows.

4 / 5

Actionability

It provides copy-paste-ready commands for install, login, connection ensure, action search/run with JSON params, and a full proxy-flag table — concrete and executable throughout.

5 / 5

Workflow Clarity

A rough sequence (install → auth → connect → poll → search → run) exists with state-based branching, but the dangling 'Step 2' reference and the lack of explicit validate→fix→retry checkpoints for potentially destructive proxy/action operations leave validation gaps.

3 / 5

Progressive Disclosure

The single SKILL.md is organized into clear sections (Overview, Working with, Install, Auth, Connecting, Searching, Popular actions, Best practices) with no bundle files needed; minor inconsistency from the orphaned '1b' / 'Step 2' labels keeps it just below excellent.

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 cleanly answers both what and when and is highly distinct due to the named product, but its capability language ('data, records, workflows') is generic and the trigger coverage is narrow.

Suggestions

Replace generic actions ('Manage data, records') with concrete webinar operations (e.g., 'list webinars, manage registrants, retrieve event recordings').

Broaden trigger terms to include natural user phrasing like 'webinars', 'registrants', or 'event replays' rather than only 'WebinarGeek data'.

DimensionReasoningScore

Specificity

It names the domain (WebinarGeek) and a few actions ('Manage data, records, and automate workflows'), but 'data' and 'records' are generic rather than concrete, webinar-specific operations.

3 / 5

Completeness

Both 'what' (manage data, records, automate workflows) and 'when' ('Use when the user wants to interact with WebinarGeek data') are explicitly present, though the 'when' clause is fairly generic.

4 / 5

Trigger Term Quality

'WebinarGeek' and 'interact with WebinarGeek data' give a relevant keyword, but coverage lacks common synonyms or variations a user might naturally say (webinars, registrants, events).

3 / 5

Distinctiveness Conflict Risk

The product name 'WebinarGeek' carves a clear niche with distinct triggers and minimal overlap risk against other skills.

5 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.