Name: webiny-api-graphql-catalog
Rating: 51.2 (1 reviews)
Author: webiny

Blog Docs Log in Get started

webiny-api-graphql-catalog

api/graphql — 7 abstractions.

Quality

55%

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/graphql/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 body is an efficient, well-structured catalog that gives concrete import paths and source locations for each abstraction with no padding. Its main gap is the absence of usage examples and any verification step, which keeps actionability and workflow clarity at 4 rather than 5.

Suggestions

Add a short inline usage snippet for the most common helper (e.g. `Response` or `ListResponse`) so the import lines are paired with executable usage.

Note the risk that import paths assume a specific Webiny version; consider flagging when source paths may move so Claude verifies against the actual repo.

For batch or code-generating use, add a verification step (e.g. re-read the source signature after importing) to lift workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is a lean catalog: each abstraction lists only Name, Import, Source, and a one-line Description with no padding or explanation of concepts Claude already knows, fitting 'lean and efficient; assumes Claude's competence; every token earns its place'.	5 / 5
Actionability	Each entry gives a copy-paste-ready import statement and a precise source path, but no usage examples of how to actually invoke the helpers, fitting 'mostly executable guidance; concrete code or commands with minor gaps'.	4 / 5
Workflow Clarity	The 'How to Use' section is a clear 4-step sequence with an explicit checkpoint ('You MUST read the source file'), but it lacks any validation/feedback loop; it fits 'clear sequence with most checkpoints present; minor validation gaps'.	4 / 5
Progressive Disclosure	Content is well organized into 'How to Use' and 'Abstractions' with one-level-deep pointers to source files and sibling skills, fitting 'good structure; most content appropriately placed; references mostly clear' though the 7 entries are all inlined.	4 / 5
	Total	17 / 20 Passed

Description

28%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 a terse domain label plus an item count rather than a capability statement; it conveys neither what the skill does nor when to invoke it. It is distinct enough within the Webiny ecosystem but fails as trigger guidance.

Suggestions

Rewrite the description as a capability statement, e.g. 'Catalogs the 7 GraphQL API abstractions (Response, ListResponse, ErrorResponse, etc.) in webiny/api/graphql with import paths and source locations.'

Add an explicit trigger clause such as 'Use when implementing or debugging Webiny GraphQL API handlers and you need the correct response helper or schema abstraction.'

Surface the natural trigger terms users would say ('GraphQL response', 'Webiny API', 'GraphQL schema') instead of only the technical path 'api/graphql'.

Dimension	Reasoning	Score
Specificity	The phrase 'api/graphql — 7 abstractions' names a concrete domain but contains no action verb, matching the anchor 'names the domain but actions are minimal or generic'; it is above 1 because the domain is specific rather than entirely vague.	2 / 5
Completeness	It offers a vague 'what' (a catalog of 7 abstractions) and no 'when' guidance at all, matching 'has a vague what and no when'; the missing 'Use when' clause also caps it well below 3.	2 / 5
Trigger Term Quality	Only 'graphql' is a keyword a user might naturally say; 'api' is generic and 'abstractions' is technical jargon, so it fits 'one or two generic keywords; missing the natural phrases users say'.	2 / 5
Distinctiveness Conflict Risk	The 'api/graphql' niche is fairly specific and unlikely to conflict with unrelated skills, but it could overlap with sibling webiny GraphQL skills referenced in the body, fitting 'somewhat specific but could still overlap'.	3 / 5
	Total	9 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: webiny/webiny-js
Path: skills/user-skills/generated/api/graphql/SKILL.md
Commit: d98a4e8

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.