Name: fullstory
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

fullstory

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

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/fullstory/SKILL.md

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 a well-structured, executable guide for the Membrane/Fullstory integration with strong command coverage and a checkpointed connection workflow. It loses points on padding, missing validation around destructive actions, and a couple of confusing step references.

Suggestions

Add explicit validation/verification guidance before running destructive or batch actions (e.g., confirm user identity and preview before delete-user).

Trim padding: remove the general FullStory platform intro and filler lines that restate what the commands already show.

Fix the dangling 'Step 2' reference and the '1b' heading to give the connection workflow a clean, numbered sequence.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete CLI commands, but includes trimmable padding such as the introductory FullStory platform explanation and filler lines like "Use action names and parameters as needed." that could be tightened.	3 / 5
Actionability	Provides concrete, copy-paste-ready commands (login, connection ensure, action list/run, request) and a populated popular-actions table, covering common cases with only minor placeholder substitution expected.	4 / 5
Workflow Clarity	The connection setup has a clear sequence with state-based checkpoints and a re-poll feedback loop, but destructive operations (e.g. delete-user) appear in the actions list with no validation/verification guidance, which caps workflow clarity.	3 / 5
Progressive Disclosure	Well-organized single-file skill with clear section headers and appropriately scoped inline content (getting-started, actions table, proxy options); minor gaps such as the dangling 'Step 2' reference and '1b' labeling keep it just short of excellent.	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 is a compact third-person statement that covers both what and when with an explicit trigger, anchored to a distinct named platform. Its main weakness is generic verb choice and limited keyword breadth.

Suggestions

Replace the generic verb "Manage" with specific concrete actions (e.g., "Search sessions, list and update users, retrieve session events").

Broaden trigger keywords with natural synonyms and product-specific terms users say (e.g., "FullStory sessions, user events, recordings, funnels").

Tighten the 'when' clause to concrete use cases rather than the broad "interact with Fullstory data".

Dimension	Reasoning	Score
Specificity	Names the domain ("Fullstory integration") and two concrete objects ("Users, Sessions"), but the verb "Manage" is generic and coverage is limited; it lists entities rather than multiple specific actions.	3 / 5
Completeness	Answers both what ("Manage Users, Sessions") and when ("Use when the user wants to interact with Fullstory data") with an explicit trigger clause, though the 'when' is somewhat broad and could be more specific.	4 / 5
Trigger Term Quality	Includes relevant terms ("Fullstory", "Users", "Sessions", "interact with Fullstory data") but lacks common synonyms or variations a user might naturally say, so coverage is partial rather than comprehensive.	3 / 5
Distinctiveness Conflict Risk	The named platform (Fullstory) gives it a clear, distinct niche with minimal conflict risk, but the broad trigger "interact with Fullstory data" leaves minor overlap room rather than a tightly bounded trigger.	4 / 5
	Total	14 / 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/fullstory/SKILL.md
Commit: f484c82

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