CtrlK
BlogDocsLog inGet started
Tessl Logo

ewebinar

EWebinar integration. Manage Webinars, Integrations, Users. Use when the user wants to interact with EWebinar data.

57

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/ewebinar/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 content is well-structured and highly actionable with concrete CLI commands, but lacks validation/verification checkpoints for the destructive operations it exposes, which caps workflow clarity.

Suggestions

Add an explicit validation/verification step after running actions or proxy requests (e.g. re-query to confirm the result, or check the response status before proceeding) to lift workflow clarity above the destructive-operation cap.

Give a concrete example of an --intent value (e.g. --intent='list webinars') so the action-search command is immediately usable.

Trim the product-intro paragraph and 'rather than auth plumbing' commentary to tighten conciseness toward level 5.

DimensionReasoningScore

Conciseness

The body is largely lean command examples and a flag table with only minor over-explanation ('rather than auth plumbing', the product intro paragraph), fitting 'efficient; minor instances of over-explanation that could be trimmed' rather than the fully lean level 5.

4 / 5

Actionability

Provides concrete, copy-pasteable commands for login, connect, list, search, run, and proxy with a JSON-input example and flag table, but placeholders (CONNECTION_ID, ACTION_ID) and the abstract --intent=QUERY leave minor gaps, matching 'mostly executable guidance; concrete commands with minor gaps'.

4 / 5

Workflow Clarity

The setup->connect->search->run sequence is clearly ordered with a 'Discover before you build' checkpoint, but the skill exposes destructive capability (proxy -X DELETE, arbitrary action run) with no validate/verify step, so the destructive-operation cap holds it at 3.

3 / 5

Progressive Disclosure

The ~120-line body is well-organized into clear sections (Overview, Working with EWebinar, Popular actions, Best practices) and is self-contained with no nested or buried references, but it exceeds the 50-line simple-skill threshold and has no external file split, fitting 'good structure; most content appropriately placed' rather than the reference-split level 5.

4 / 5

Total

15

/

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 answers both what and when with a distinct brand anchor, but relies on a single generic verb and one broad trigger phrase, leaving specificity and trigger coverage at mid-level.

Suggestions

Replace the generic 'Manage' with several concrete verbs (e.g. 'List, create, update, and delete Webinars, Integrations, and Users') to lift specificity.

Expand the trigger clause with concrete natural phrases a user would say (e.g. 'Use when the user asks about webinars, registrations, or EWebinar sessions').

Add common synonyms/file-ish terms (e.g. 'webinar', 'registrations', 'sessions') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('EWebinar integration') and concrete entities ('Manage Webinars, Integrations, Users'), but the single generic verb 'Manage' covers all three rather than listing several distinct actions, matching the 'names domain and 1-2 concrete actions' anchor.

3 / 5

Completeness

Both 'what' ('Manage Webinars, Integrations, Users') and 'when' ('Use when the user wants to interact with EWebinar data') are present, but the trigger clause is generic rather than listing concrete trigger phrases, matching the 'both present, when could be more specific' anchor rather than the multi-trigger level 5.

4 / 5

Trigger Term Quality

Relevant keywords ('EWebinar', 'Webinars', 'Integrations', 'Users') are present but coverage is brand-anchored and thin on common synonyms/variations (e.g. 'webinar', 'registrations', 'sessions'), fitting 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

The 'EWebinar' brand name gives it a clear, distinct niche with low conflict risk, but the generic terms 'Integrations' and 'Users' create minor overlap risk with adjacent skills, fitting 'mostly distinct; minor overlap risk'.

4 / 5

Total

14

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.