Name: livestorm
Rating: 63.2 (1 reviews)
Author: membranedev

livestorm

Livestorm integration. Manage Persons, Organizations, Deals, Leads, Activities, Notes and more. Use when the user wants to interact with Livestorm data.

Quality

75%

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

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 body is highly actionable with concrete, copy-paste-ready CLI commands and a clear connect-then-act workflow including state-based error recovery, with only minor conciseness and organizational redundancy issues.

Suggestions

Trim the conceptual intro ("Livestorm is a video engagement platform... used by marketing, sales, and customer success teams") and the editorializing about auth plumbing — Claude can infer these.

Label the referenced "Step 2" (e.g. "### Step 2: Search for actions") so the "skip to Step 2" pointer resolves.

Merge the redundant "Popular actions" section into "Searching for actions" to remove the duplicated `action list --intent` example.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and command-driven, but the opening paragraph ("video engagement platform... used by marketing, sales, and customer success teams") and editorializing like "so you can focus on the integration logic rather than auth plumbing" are minor over-explanation that could be trimmed, fitting the 4 anchor rather than the fully lean 5.	4 / 5
Actionability	It provides copy-paste-ready commands for every common case (login, connection ensure, action list/run, request proxy) plus a complete flags table, matching the 5 anchor for fully executable guidance covering the common cases.	5 / 5
Workflow Clarity	The install→login→connect→search→run sequence is clear with a state-machine feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR plus poll-again), but the "skip to Step 2" reference points to an unlabeled step, leaving a minor validation/sequencing gap below the 5 anchor.	4 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections with no bundle files or nested references (appropriate for this scope), but the "Popular actions" section redundantly repeats `action list` from "Searching for actions" and the proxy/connection detail could be split out, matching the 4 anchor with minor organization gaps.	4 / 5
	Total	17 / 20 Passed

Description

67%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 clearly identifies the Livestorm domain and lists concrete entities with an explicit "Use when" trigger, but the trigger phrasing is generic and omits natural synonyms like webinars and virtual events that users would actually say.

Suggestions

Add concrete trigger phrases beyond "interact with Livestorm data", e.g. "Use when the user wants to manage webinars, registrants, or session recordings in Livestorm".

Replace the generic verb "Manage" with specific actions (create, list, update) and drop "and more" to avoid over-claims.

Align the entity list with the body's actual objects (Meeting, Registration, Participant, Recording, etc.) — the description's Persons/Deals/Leads do not appear in the skill overview.

Dimension	Reasoning	Score
Specificity	"Manage Persons, Organizations, Deals, Leads, Activities, Notes and more" lists several concrete entities, but the single generic verb "Manage" and the vague "and more" leave minor coverage gaps, fitting the 4 anchor better than the comprehensive 5.	4 / 5
Completeness	It answers both what ("Livestorm integration. Manage Persons, Organizations, Deals, Leads, Activities, Notes...") and when ("Use when the user wants to interact with Livestorm data"), but the "when" clause is generic rather than concrete trigger phrases, so it falls short of the explicit 5 anchor.	4 / 5
Trigger Term Quality	"Livestorm" and "interact with Livestorm data" are natural terms, but the description omits common synonyms the body itself uses (webinars, online meetings, virtual events), so relevant keywords are present while common variations are missing.	3 / 5
Distinctiveness Conflict Risk	Scoping to the named app "Livestorm" makes it mostly distinct, but the generic CRM entities (Persons, Organizations, Deals, Leads) create minor overlap risk with sales/CRM skills, matching the 4 anchor rather than the minimal-conflict 5.	4 / 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/livestorm/SKILL.md
Commit: f484c82

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