Name: webiny-api-cms-catalog
Rating: 57.599999999999994 (1 reviews)
Author: webiny

Blog Docs Log in Get started

webiny-api-cms-catalog

API — Headless CMS — 124 abstractions. Entry, model, and group event handlers and use cases.

Quality

67%

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/user-skills/generated/api/cms/SKILL.md

Quality

Content

77%

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 exact imports, source paths, and an explicit must-read-source workflow, but it is a monolithic inline catalog with repetitive separators that could be split into per-domain reference files. Token efficiency is good yet the volume and undifferentiated repetition leave room to tighten.

Suggestions

Split the 124-entry catalog into per-domain reference files (e.g. references/entry.md, references/model.md, references/group.md, references/opensearch.md) and keep SKILL.md as an overview with one-level-deep links.

Replace the repeated horizontal-rule separators and per-entry bold labels with a compact table or grouped sections to cut redundant tokens.

Add brief descriptions to the entries that currently only have Name/Import/Source (e.g. the OpenSearch block) so every entry earns its place.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's intelligence with no concept bloat, but ~124 near-identical blocks separated by horizontal rules and many entries lacking descriptions are tightening opportunities, fitting anchor 2 rather than 3.	2 / 3
Actionability	Every entry provides a copy-paste-ready import statement and a precise source file path, and the instructions explicitly direct reading the source for exact types, fully matching the executable anchor 3.	3 / 3
Workflow Clarity	The "How to Use" section gives a clear 4-step sequence with an explicit "MUST read the source file" checkpoint and pointers to implementation-pattern skills, which is unambiguous for this single-purpose lookup skill.	3 / 3
Progressive Disclosure	No bundle files exist and the 124-entry catalog is rendered fully inline rather than split into per-domain reference files, fitting anchor 2's "content that should be separate is inline".	2 / 3
	Total	10 / 12 Passed

Description

57%

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 clearly scopes a distinct webiny Headless CMS niche and uses third-person voice, but it lacks an explicit "Use when..." trigger and leans on internal jargon ("124 abstractions") without listing concrete actions. It is adequate but not exemplary.

Suggestions

Add an explicit trigger clause, e.g. ".Use when working with webiny Headless CMS entry, model, or group event handlers and use cases."

Replace the jargon "124 abstractions" with concrete user-facing actions (create, list, validate, publish entries; define models and groups).

Cover natural keyword variations users would say ("content model", "model group", "entry lifecycle", "publish/unpublish").

Dimension	Reasoning	Score
Specificity	Names the domain and concrete categories ("Entry, model, and group event handlers and use cases") but lists no specific user-facing actions, fitting anchor 2 rather than the multi-action anchor 3.	2 / 3
Completeness	The "what" (catalogs entry/model/group handlers and use cases) is stated, but there is no "Use when..." trigger clause, which caps completeness at 2 per the rubric guideline.	2 / 3
Trigger Term Quality	Natural terms like "Headless CMS", "entry", "model", and "group" appear, but the jargon "124 abstractions" and missing common variations keep it at anchor 2 rather than 3.	2 / 3
Distinctiveness Conflict Risk	Scoped via context "webiny-api" and "Headless CMS" to a distinct niche, with third-person voice, making it unlikely to trigger for unrelated skills.	3 / 3
	Total	9 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (881 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: webiny/webiny-js
Path: skills/user-skills/generated/api/cms/SKILL.md
Commit: 484553b

Reviewed: about 13 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.