CtrlK
BlogDocsLog inGet started
Tessl Logo

livesession

LiveSession integration. Manage Sessions, Users. Use when the user wants to interact with LiveSession data.

54

Quality

61%

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

Quality

Content

61%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 executable Membrane CLI commands and a solid connection-state feedback loop, but it is held back by an unnecessary product intro, a broken 'Step 2' reference, and missing validation for destructive action execution. Fixing the dangling Step 2 and trimming the intro would noticeably raise quality.

Suggestions

Define or remove the dangling 'Step 2' references, since the document jumps from connection setup straight to action search with no Step 2 section.

Add a validation/verification checkpoint before running actions that could modify or delete LiveSession data (e.g. confirm the action and review its outputSchema first).

Cut the introductory paragraph explaining what LiveSession is and the editorial 'focus on the integration logic rather than auth plumbing' line to respect the token budget.

DimensionReasoningScore

Conciseness

Mostly efficient commands and tables, but it opens by explaining what LiveSession is and includes editorial padding like 'so you can focus on the integration logic rather than auth plumbing' that Claude does not need.

3 / 5

Actionability

It provides copy-paste-ready CLI commands for install, login, connection, action discovery, action execution, and proxy requests with a clear flag table, with only minor gaps such as undefined placeholders.

4 / 5

Workflow Clarity

The connection flow has a good state-polling feedback loop, but it repeatedly says 'skip to Step 2' without ever defining Step 2, and action execution (potentially destructive user/session changes) lacks any validation checkpoint, capping it at 3.

3 / 5

Progressive Disclosure

The single self-contained file is well organized into clearly headed sections with no nested references, though the redundant 'Searching for actions' and 'Popular actions' sections and the inline flag table show minor organization gaps.

4 / 5

Total

14

/

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 answers both what and when and is anchored by a distinct brand name, but it is thin on specific actions and natural-language synonyms. Tightening 'Manage' into concrete verbs and adding common trigger terms would lift it.

Suggestions

Replace the generic verb 'Manage' with specific actions, e.g. 'List, replay, and analyze LiveSession sessions and users'.

Add natural trigger synonyms such as 'session replay', 'product analytics', or 'user recordings' to the 'Use when' clause.

Expand the 'when' clause with concrete triggers, e.g. 'Use when the user asks about session replays, user recordings, or LiveSession analytics'.

DimensionReasoningScore

Specificity

Names the domain and the concrete entities 'Manage Sessions, Users', but 'Manage' is a generic verb and only two object types are listed, so coverage is not comprehensive.

3 / 5

Completeness

It states both what ('Manage Sessions, Users') and when ('Use when the user wants to interact with LiveSession data'), but the 'when' clause is generic rather than listing concrete trigger phrases, so it is not a 5.

4 / 5

Trigger Term Quality

The natural keyword 'LiveSession' and the phrase 'interact with LiveSession data' are present, but common synonyms a user would say (session replay, product analytics, recordings) are missing.

3 / 5

Distinctiveness Conflict Risk

The branded term 'LiveSession' gives it a clear niche with low conflict risk, though the generic entities 'Sessions, Users' create minor overlap with general user-management skills.

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.