Name: storyblok
Rating: 60.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

storyblok

Storyblok integration. Manage Stories, Spaces. Use when the user wants to interact with Storyblok data.

Quality

71%

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

Quality

Content

68%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 concrete CLI commands and a clear connection/search/run flow, but it is held back by a low-value 20-row action table, broken step numbering, and missing validation before destructive operations. Structure is good for a single-file skill.

Suggestions

Add an explicit validation/check step before running create/delete actions (e.g., confirm the target story id and dry-run where possible) so destructive workflows clear the workflow-clarity cap.

Fix the step numbering: define a "Step 1a/1b" and a labeled "Step 2" so the "skip to Step 2" reference resolves.

Trim or externalize the 20-row "Popular actions" table whose descriptions are all "No description"; keep only actions with real guidance or move the full list to a reference file.

Dimension	Reasoning	Score
Conciseness	Most sections are efficient with executable commands, but the 20-row "Popular actions" table where every row says "No description" is low-value padding, and the opening headless-CMS paragraph restates context Claude largely already knows.	3 / 5
Actionability	It provides copy-paste-ready bash commands for install, login, connection ensure/get, action list/run, and proxy requests with real flags, covering the common cases concretely.	5 / 5
Workflow Clarity	The connection flow has a sequence with state checks (READY/BUILDING/CLIENT_ACTION_REQUIRED), but step numbering is broken ("skip to Step 2" with no Step 2, a "1b" with no "1a") and there is no validation checkpoint before running destructive create/delete actions, capping it at 3.	3 / 5
Progressive Disclosure	No bundle files exist, so everything is inline, but the body is well-organized into clear sections (install, auth, connecting, searching, running, proxy, best practices); the bulky inlined action table is the main organization gap keeping it from a 5.	4 / 5
	Total	15 / 20 Passed

Description

73%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 product-specific with an explicit use-when clause and good trigger terms, but its capability list ("Manage Stories, Spaces") is thin and generic. It is clearly distinguishable and low-conflict, just not comprehensive on the "what".

Suggestions

Replace the generic "Manage Stories, Spaces" with several concrete verbs (e.g., "Create, update, and list Stories, Components, Datasources, and Assets") to lift specificity.

Expand the trigger phrase to mention common user cues like "content entries", "components", or "datasources" so the "when" matches more natural phrasings.

Dimension	Reasoning	Score
Specificity	It names the domain ("Storyblok integration") and a couple of actions ("Manage Stories, Spaces"), but "Manage" is generic and only two entities are listed, so it does not reach the several-specific-actions bar of a 4.	3 / 5
Completeness	Both a "what" ("Manage Stories, Spaces") and an explicit "when" ("Use when the user wants to interact with Storyblok data") are present, but the "what" is thin relative to the full entity set, so it stops short of a 5.	4 / 5
Trigger Term Quality	"Storyblok", "Stories", and "Spaces" are the natural terms a user would say for this product; coverage is good for a named-product integration, though a few variations are absent.	4 / 5
Distinctiveness Conflict Risk	"Storyblok integration" tied to "interact with Storyblok data" is a clear, product-specific niche with distinct triggers and minimal overlap with other skills.	5 / 5
	Total	16 / 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/storyblok/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.