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

sessions

Sessions integration. Manage Sessions, Persons, Organizations, Notes, Files. Use when the user wants to interact with Sessions data.

Quality

73%

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

Quality

Content

80%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 executable CLI commands and a clear, well-organized structure. Its one real gap is the absence of validation/verification checkpoints for operations that mutate external Sessions data.

Suggestions

Add explicit verification steps after connection creation and before running actions (e.g. confirm the connectionId is live via `connection list`, or check the action run output for errors before proceeding).

Include an error-recovery feedback loop for proxy/action calls (e.g. on auth-expiry or non-2xx responses, re-check the connection and retry).

Trim the few padded sentences (the "focus on integration logic" and "burn less tokens" asides) to push conciseness to fully lean.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable commands with brief, relevant context; a few sentences pad slightly (e.g. "so you can focus on the integration logic rather than auth plumbing", "burn less tokens"), which keeps it just below the 5 anchor's every-token-earns-its-place bar.	4 / 5
Actionability	It provides fully executable `npx @membranehq/cli@latest ...` commands throughout, a concrete `--input` JSON example, and a complete proxy flags table covering the common cases; this matches the copy-paste-ready, common-cases-covered anchor.	5 / 5
Workflow Clarity	The setup→connect→search→run flow is sequenced with concrete commands, but there are no explicit validation/verification checkpoints or error-recovery feedback loops for operations that drive external data (create connections, run actions, proxy POST/PUT/DELETE); the rubric caps such skills at 3.	3 / 5
Progressive Disclosure	No bundle files exist and the self-contained ~100-line body is well-organized into clearly headed sections with no nested references; the simple-skill exception allows 5 for well-organized content needing no external file references.	5 / 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 cleanly states both what the skill manages and when to use it, with a solid list of concrete entity types. Its main weakness is the trigger phrase, which is generic and lacks natural-language synonyms users would actually say.

Suggestions

Strengthen the "Use when" clause with concrete natural triggers, e.g. "Use when the user wants to manage Sessions, browse session replays/recordings, or work with Persons, Organizations, Notes, or Files."

Add natural synonyms and the product's common phrasing (e.g. "session replay", "recordings", "replays") so users' actual wording matches the trigger.

Clarify the distinct action verbs beyond the generic "Manage" (e.g. list, create, update, search) to push specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	"Manage Sessions, Persons, Organizations, Notes, Files" names the domain plus several concrete entity types, matching the several-specific-actions anchor; it is not 5 because "Manage" is one generic verb rather than multiple distinct concrete actions, and not 3 because more than 1-2 concrete items are listed.	4 / 5
Completeness	Both "what" ("Manage Sessions, Persons, Organizations, Notes, Files") and "when" ("Use when the user wants to interact with Sessions data") are present, but the "when" clause is generic and overlaps the "what", so it falls short of the 5 anchor's concrete trigger phrases.	4 / 5
Trigger Term Quality	It lists five entity nouns (Sessions, Persons, Organizations, Notes, Files) and a "interact with Sessions data" trigger, but lacks natural synonyms a user would say (e.g., "session replay", "recordings"); this sits below the 4 anchor's good-but-incomplete coverage.	3 / 5
Distinctiveness Conflict Risk	The named Sessions integration niche with its entity list is mostly distinct, though generic CRM-style terms (Persons, Organizations, Notes, Files) create minor overlap risk with related skills; not 5 because of that residual overlap.	4 / 5
	Total	15 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: membranedev/application-skills
Path: skills/sessions/SKILL.md
Commit: f484c82

Reviewed: ~20 hours 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.