CtrlK
BlogDocsLog inGet started
Tessl Logo

webinarkit

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

61

Quality

72%

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/webinarkit/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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, copy-paste-ready CLI commands and a clear workflow including validation via state polling. The main gaps are minor: some editorial padding and inconsistent step numbering.

Suggestions

Fix the step numbering: label "Step 1a/1b" and "Step 2" consistently, or remove the dangling "skip to Step 2" references.

Trim the editorial "Best practices" framing into terse imperative bullets to reduce token cost.

Consider moving the proxy flag reference table into a separate reference file so SKILL.md stays a lean overview.

DimensionReasoningScore

Conciseness

The body is mostly lean executable commands with brief explanations and a tight flag table; minor editorial padding (the "Best practices" bullets and the Membrane-value framing) could be trimmed without losing clarity.

4 / 5

Actionability

It provides copy-paste-ready commands for every common case (install, login, connection ensure/get, action list/run, request proxy) with documented flags and JSON output examples, fully executable end to end.

5 / 5

Workflow Clarity

A clear install→auth→connect→search→run sequence with an explicit state machine (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and feedback loops ("poll again", "keep polling until"), but step numbering is inconsistent ("skip to Step 2" with no labeled Step 2; "1b" without a "1a").

4 / 5

Progressive Disclosure

Well-organized into clear headed sections with no nested references and no bundle files to misroute, though the single file mixes overview, command reference, and a flag table that could live in a separate reference for a cleaner overview.

4 / 5

Total

17

/

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 cleanly covers both what and when for a distinct, named platform, but the actions listed are generic and the trigger phrasing lacks concrete task examples or synonyms. It is solid but not exemplary.

Suggestions

Replace generic verbs ("Manage data, records") with concrete WebinarKit tasks such as "schedule webinars, manage registrations, and configure email automations".

Add concrete trigger phrases users would actually say, e.g. "Use when the user wants to schedule a webinar, manage attendees, or build a webinar funnel in WebinarKit".

Include synonyms and related terms (webinars, registrations, funnels, automations) to improve natural-keyword coverage.

DimensionReasoningScore

Specificity

Names the WebinarKit domain plus a few actions ("Manage data, records, and automate workflows"), but the actions are generic ("manage data") rather than concrete verbs like "register attendees" or "schedule webinars".

3 / 5

Completeness

Clearly states both what ("WebinarKit integration. Manage data, records, and automate workflows") and when ("Use when the user wants to interact with WebinarKit data"), though the when clause is somewhat generic rather than task-specific.

4 / 5

Trigger Term Quality

Includes the core keyword "WebinarKit" and "interact with WebinarKit data", but offers no synonyms, related phrases (webinars, registrations, funnels), or variations a user might naturally say.

3 / 5

Distinctiveness Conflict Risk

Targets a named, niche platform with distinct triggers, so conflict risk with other skills is low; minor overlap risk remains with generic integration skills due to the broad "interact with data" phrasing.

4 / 5

Total

14

/

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.