Name: storyous
Rating: 62.4 (1 reviews)
Author: membranedev

storyous

Storyous integration. Manage data, records, and automate workflows. Use when the user wants to interact with Storyous data.

Quality

74%

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/storyous/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 copy-paste-ready Membrane CLI commands and a clear connection-readiness feedback loop. Its weak spots are minor: light padding in the intro, a dangling 'Step 2' reference, and slight redundancy between the 'Searching for actions' and 'Popular actions' sections.

Suggestions

Resolve the dangling 'Step 2' references by labeling explicit numbered steps (Step 1 connect, Step 2 search/run) so the workflow reads as a checklist.

Trim the POS introductory paragraph and 'rather than auth plumbing' filler to tighten conciseness toward a 5.

Merge or differentiate the 'Popular actions' and 'Searching for actions' sections to remove the duplicated `action list` command and improve navigation.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and command-focused with executable snippets throughout; only minor over-explanation ('Storyous is a point-of-sale (POS) system...', 'rather than auth plumbing') could be trimmed. It is efficient with minor padding, matching the 4 anchor rather than the pristine 5 or the noticeably-verbose 3.	4 / 5
Actionability	It provides copy-paste-ready executable commands for every common case — install (`npm install -g @membranehq/cli@latest`), login, `connection ensure`, `connection get --wait`, `action list`, `action run`, `request` — plus a flag table. This matches the 'fully executable; copy-paste ready' 5 anchor.	5 / 5
Workflow Clarity	The install → authenticate → connect → poll-until-ready → handle client action → search → run sequence is clear, with an explicit feedback loop (poll state, act on CLIENT_ACTION_REQUIRED, re-poll) and error-state handling. It falls short of 5 because of a dangling 'Step 2' reference and the absence of an explicit numbered checklist, and the destructive/batch cap does not apply to this setup workflow.	4 / 5
Progressive Disclosure	No bundle files exist (references/scripts/assets absent); the single SKILL.md is well-sectioned into Overview, Auth, Connecting, Searching, Actions, Proxy, Best practices. Structure is good with minor gaps — the 'Popular actions' section repeats the `action list` command from 'Searching for actions' — matching the 4 anchor rather than a pristine 5 or a structure-poor 3.	4 / 5
	Total	17 / 20 Passed

Description

66%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 compact and clearly tied to a specific named product, with an explicit 'Use when...' trigger and low conflict risk. Its main weakness is generic action language ('manage data, records, automate workflows') and thin keyword synonym coverage.

Suggestions

Replace generic verbs with concrete capabilities, e.g. 'Manage orders, payments, products, and inventory; pull sales reports' to lift specificity.

Add natural trigger variations users would say, e.g. 'Use when the user wants to query Storyous orders, payments, or sales reports'.

Make the 'when' clause name the specific Storyous tasks (orders, tables, products, reports) rather than the generic 'interact with Storyous data'.

Dimension	Reasoning	Score
Specificity	It names the domain (Storyous) and a few action phrases ('Manage data, records, and automate workflows'), but those actions are generic and abstract rather than concrete capabilities. It sits above the single-generic-action anchor (2) yet below the several-specific-actions anchors (4-5).	3 / 5
Completeness	It answers both 'what' (Storyous integration; manage data, records, automate workflows) and 'when' via an explicit 'Use when...' clause, so it is not capped at 3. The 'when' is present but could be more specific about which Storyous tasks trigger it, matching the 4 anchor rather than the fully-concrete 5 anchor.	4 / 5
Trigger Term Quality	The product name 'Storyous' is a strong natural keyword and the explicit trigger 'Use when the user wants to interact with Storyous data' is reasonable, but beyond 'data' and 'records' there is little synonym or variation coverage. It matches 'some relevant keywords but missing common variations' rather than the comprehensive 4-5 anchors.	3 / 5
Distinctiveness Conflict Risk	'Storyous integration' tied to a named POS product gives it a clear niche with a distinct trigger ('interact with Storyous data') and minimal overlap risk with other skills, matching the 5 anchor.	5 / 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/storyous/SKILL.md
Commit: f484c82

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