CtrlK
BlogDocsLog inGet started
Tessl Logo

webinarfuel

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

56

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

68%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 comprehensive executable Membrane CLI commands and a clear connection state machine, but it opens with marketing fluff and lacks validation feedback loops around the destructive action-running operations. Structure is solid given there are no bundle files to reference.

Suggestions

Trim or remove the opening marketing paragraph ("automated webinar platform... used by marketers, coaches, and entrepreneurs") since Claude does not need that background.

Add a verification checkpoint after running actions that change state (e.g., re-list or fetch the affected resource to confirm the result), which would lift workflow_clarity above the destructive-operations cap.

Either populate the "Popular actions" section with a few concrete action names or remove the empty header.

DimensionReasoningScore

Conciseness

The bulk is efficient executable commands, but the opening paragraph explaining what WebinarFuel is and its marketing audience ("primarily used by marketers, coaches, and entrepreneurs to generate leads...") is unnecessary context Claude does not need; matches anchor 3 with some unnecessary explanation that could be tightened.

3 / 5

Actionability

Fully executable copy-paste commands cover the common cases (install, interactive and headless auth, connection ensure with state polling, action list/run with JSON input, proxy with a full flag table); matches anchor 5.

5 / 5

Workflow Clarity

The connection sub-flow is well sequenced with state handling (READY/BUILDING/CLIENT_ACTION_REQUIRED), but running actions mutates external webinar and automation data with no validation or verification checkpoint; per the rubric cap for destructive/batch operations, workflow clarity cannot exceed 3.

3 / 5

Progressive Disclosure

No bundle files exist and none are referenced, so structure is judged on organization; clear sections (Overview, Working with WebinarFuel, Best practices) with content appropriately inline, matching anchor 4, though the "Popular actions" header promises content it does not deliver.

4 / 5

Total

15

/

20

Passed

Description

61%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 answers both what and when and is clearly branded, but its actions are generic and its trigger phrasing lacks the concrete natural terms a user would say. It is distinctive but could be sharpened with specific capabilities and synonyms.

Suggestions

Replace generic verbs like "Manage data, records, and automate workflows" with concrete capabilities such as list webinars, register attendees, pull registrant data, or trigger automation funnels.

Expand the "Use when" clause with concrete user phrases, e.g. "Use when the user mentions WebinarFuel webinars, registrants, or webinar funnels".

DimensionReasoningScore

Specificity

Names the WebinarFuel domain plus a couple of generic actions ("Manage data, records, and automate workflows") but no concrete operations such as listing webinars or registering attendees; closest to anchor 2 where actions are minimal or generic rather than truly concrete.

2 / 5

Completeness

Provides both a "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with WebinarFuel data"), but the trigger is vague rather than concrete, fitting anchor 4 where the when could be more specific.

4 / 5

Trigger Term Quality

Includes the brand keyword "WebinarFuel" and "interact with WebinarFuel data" but misses natural variations users would say (webinars, registrants, funnels, exports); matches anchor 3 with some relevant keywords but missing common synonyms.

3 / 5

Distinctiveness Conflict Risk

The WebinarFuel brand name gives it a clear niche with distinct triggers and minimal conflict risk, matching anchor 5.

5 / 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.