Name: webiny
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

webiny

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

Quality

63%

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

Quality

Content

65%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 command-rich and largely executable with a sensible connection/action workflow, but it over-inlines a long entity catalog that belongs in a separate file and lacks validation checkpoints for its batch/destructive operations, capping workflow clarity.

Suggestions

Move the ~50-item Webiny entity list into a references file (e.g. references/entities.md) and link to it, improving progressive disclosure and conciseness.

Add explicit validation/verification steps after `membrane action run` and proxy mutations, e.g. checking the `output` field for errors or confirming the action succeeded before proceeding.

Trim the opening 'Webiny is a serverless CMS platform built on...' paragraph, which restates platform basics Claude already knows.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and command-driven, but the long flat bullet list of ~50 Webiny entity types (Page, API Route, Form, etc.) and the opening 'Webiny is a serverless CMS platform...' overview add mild padding Claude largely does not need.	4 / 5
Actionability	Provides concrete, copy-pasteable commands throughout (npm install, membrane login, connection ensure, action run/list, request proxy) with a clear flag table; minor gaps such as CONNECTION_ID placeholder handling keep it just short of fully copy-paste ready.	4 / 5
Workflow Clarity	The connection flow is sequenced with state handling, but operations that are effectively batch/destructive (action run, proxy mutations) lack explicit validation or verification checkpoints — the rubric caps workflow clarity at 3 when destructive/batch steps omit validation.	3 / 5
Progressive Disclosure	Sections are present and the large entity list arguably belongs in a separate reference file, but there are no bundle files and no external references; the inlined 50-item entity catalog and proxy reference would be better split out, leaving structure only partially organized.	3 / 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 adequate and brand-distinct, covering both what and when in third person, but its action list ('manage data, records, automate workflows') is generic and it omits the concrete Webiny-specific concepts and feature terms users would naturally mention.

Suggestions

Replace the generic action list with Webiny-specific actions, e.g. 'Manage headless CMS content models and entries, build pages and forms, and automate Webiny workflows'.

Expand the 'Use when' clause with natural trigger phrases such as 'headless CMS', 'page builder', 'form builder', or 'Webiny content models'.

Keep the third-person voice but add a few synonyms/file types users might say to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the Webiny domain and two concrete actions ('Manage data, records, and automate workflows') but the actions are generic and not comprehensive — no specifics about what can actually be done with Webiny.	3 / 5
Completeness	States both the 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Webiny data'), though the 'when' is somewhat generic rather than listing concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes the keyword 'Webiny' and the 'Use when...' clause references 'interact with Webiny data', but lacks common variations, synonyms, or specific feature terms (e.g. headless CMS, page builder, forms) a user might say.	3 / 5
Distinctiveness Conflict Risk	The branded term 'Webiny' gives it a clear niche with minimal conflict risk against other skills, though the generic 'manage data, records, automate workflows' phrasing could marginally overlap with broad data-management skills.	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/webiny/SKILL.md
Commit: f484c82

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