Name: stormboard
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

stormboard

Stormboard integration. Manage Organizations. Use when the user wants to interact with Stormboard data.

Quality

66%

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

Quality

Content

67%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 solid, executable guide to driving Stormboard through the Membrane CLI, with a well-sequenced connection workflow and real state-handling checkpoints. Its weaknesses are mild padding in the intro, a 'Popular actions' section that promises specifics but only repeats discovery, and no validation guidance before destructive action or proxy calls.

Suggestions

Trim audience/marketing padding (the 'used by teams of all sizes' sentence and the 'focus on integration logic rather than auth plumbing' aside) to tighten token use.

Make 'Popular actions' actually list a few common Stormboard actions (e.g., create storm, add idea, list ideas) instead of restating the discovery command.

Add a brief validation/verification note before running mutating actions or proxy requests (e.g., confirm the action's inputSchema, prefer QUERY/discovery first, or dry-check the endpoint) so destructive operations have an explicit checkpoint.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command documentation, but it includes unnecessary padding such as the 'used by teams of all sizes... project managers, designers' intro and 'so you can focus on the integration logic rather than auth plumbing', which the 3 anchor treats as tighten-able over-explanation.	3 / 5
Actionability	Provides concrete, executable commands throughout (install, login, connection ensure, action run, request with a flags table) with only minor gaps such as unresolved placeholders and a 'Popular actions' section that re-states discovery instead of listing actual popular actions.	4 / 5
Workflow Clarity	The connection flow is a clearly sequenced process with explicit state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a re-poll feedback loop, but destructive action/proxy runs lack an explicit pre-run validation step, keeping it at 4 rather than 5.	4 / 5
Progressive Disclosure	The body is well-sectioned (Overview, Authentication, Connecting, Searching, Proxy, Best practices) with no nested references and content appropriately kept inline for a single-file CLI skill, with only minor organization gaps such as the thin Overview hierarchy.	4 / 5
	Total	15 / 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 correctly identifies the product and includes an explicit 'Use when' trigger, but its capability list is narrow ('Manage Organizations') and omits the brainstorming/whiteboard work users most associate with Stormboard. Trigger terms cover the product name but lack natural synonyms.

Suggestions

Broaden the 'what' beyond 'Manage Organizations' to include the core capabilities users actually need (e.g., create storms, add/manage ideas, organize boards, work with templates).

Add natural trigger synonyms a user would say, such as 'brainstorm', 'whiteboard', 'sticky notes', or 'collaborate visually', not just 'interact with Stormboard data'.

Make the 'when' clause concrete by listing a few example scenarios (e.g., 'Use when the user wants to brainstorm, run a retrospective, or manage Stormboard organizations and ideas').

Dimension	Reasoning	Score
Specificity	Names the domain ('Stormboard integration') and one concrete action ('Manage Organizations'), but offers no broader coverage of what the integration actually does, fitting the 1-2-actions anchor rather than the comprehensive 5.	3 / 5
Completeness	Both 'what' (Stormboard integration, manage Organizations) and an explicit 'when' clause are present, but the 'what' is thin and the 'when' could name more concrete trigger phrases, so it sits at 4 rather than 5.	4 / 5
Trigger Term Quality	'Use when the user wants to interact with Stormboard data' supplies a relevant trigger and the product name, but misses natural variations a user might say (brainstorm, whiteboard, sticky notes) that the 4-5 anchors require.	3 / 5
Distinctiveness Conflict Risk	'Stormboard' is a specific named product with a clear niche and explicit triggers, giving minimal overlap with other skills as the 5 anchor describes.	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/stormboard/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.