Name: storyscale
Rating: 60 (1 reviews)
Author: membranedev

storyscale

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

Quality

70%

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/storyscale/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 content is highly actionable with executable CLI commands throughout and a well-sequenced, state-aware connection workflow that includes real validation checkpoints. Its main weaknesses are minor verbosity in the introductory framing and an unresolved 'Step 2' label in the connection section.

Suggestions

Tighten or remove the opening 'StoryScale is a platform that helps product teams...' paragraph, which restates background Claude does not need.

Define the 'Step 2' referenced by 'skip to Step 2' — relabel sections so the skip target is unambiguous, or restructure the connection flow as an explicit numbered list.

Trim the duplicated action-discovery examples (the 'Popular actions' section restates the search command already shown under 'Searching for actions').

Dimension	Reasoning	Score
Conciseness	The body is dominated by lean, executable command blocks with little padding; the only mild over-explanation is the opening 'StoryScale is a platform that helps product teams...' paragraph and a few restated hints, which keeps it just below the fully lean level-5 anchor.	4 / 5
Actionability	It provides copy-paste-ready, fully executable commands for the common cases (install, login, connection ensure, action list/run, proxy request) with concrete flags and JSON output guidance, matching the 'fully executable; copy-paste ready; specific examples cover common cases' anchor.	5 / 5
Workflow Clarity	The connection flow has explicit state-based checkpoints with a feedback loop (poll BUILDING, act on CLIENT_ACTION_REQUIRED then re-poll, inspect error on CONFIGURATION_ERROR), giving clear sequence and most checkpoints; minor gaps (an unlabeled 'Step 2' reference) keep it just below the level-5 fully-checklisted anchor.	4 / 5
Progressive Disclosure	As a self-contained single-file integration overview with no bundle files, it is well-organized under clear section headers and appropriately concise for its scope; with no references to mis-signal and good structure it sits at 'good structure; most content appropriately placed' rather than the multi-file level-5 anchor.	4 / 5
	Total	17 / 20 Passed

Description

57%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 establishes a distinct product niche and provides an explicit 'Use when' trigger, but its capability verbs are generic ('data', 'records', 'workflows') rather than concrete StoryScale-specific actions. Strengthening it with named objects and operations would lift specificity and completeness.

Suggestions

Replace generic verbs with concrete StoryScale actions and objects (e.g., 'collect user feedback, prioritize features, manage user stories and scales').

Add natural trigger synonyms a user might say beyond 'interact with StoryScale data', such as 'gathering feedback' or 'prioritizing features from user stories'.

Confirm the 'what' is product-specific so it does not read as interchangeable with any other data-management integration.

Dimension	Reasoning	Score
Specificity	Phrases like 'Manage data, records, and automate workflows' name the domain and a few actions, but the actions are generic ('data', 'records', 'workflows') rather than concrete, fitting the 'names the domain but actions are minimal or generic' anchor below the score-3 level which requires genuine concrete actions.	2 / 5
Completeness	It states both a what ('Manage data, records, and automate workflows') and an explicit when ('Use when the user wants to interact with StoryScale data'); the 'when' is present and explicit but the 'what' is somewhat generic, so it sits at 'has both what and when, when could be more explicit/specific' rather than the fully concrete level 5.	4 / 5
Trigger Term Quality	'Use when the user wants to interact with StoryScale data' surfaces the natural product name and a trigger phrase, but it lacks common synonyms or variations a user might say, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Anchoring on the distinct product name 'StoryScale' gives it a clear niche with minimal conflict risk; the generic verb phrases ('manage data, records') create only minor overlap risk with other integration skills, matching the 'mostly distinct; minor overlap risk' anchor.	4 / 5
	Total	13 / 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/storyscale/SKILL.md
Commit: f484c82

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