CtrlK
BlogDocsLog inGet started
Tessl Logo

webiny-admin-graphql-playground-catalog

admin/graphql-playground — 4 abstractions.

60

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/user-skills/generated/admin/graphql-playground/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 clean, token-efficient catalog that gives exact imports and source locations with a clear usage sequence. Its only weakness is that it instructs reading the source for interfaces rather than inlining the key signatures.

DimensionReasoningScore

Conciseness

The body is extremely lean: a three-step usage list plus four compact abstraction entries with imports and source paths, with no padding or explanation of concepts Claude already knows.

5 / 5

Actionability

Each abstraction provides a copy-paste import statement and a concrete source path, but step 2 defers the actual interface/types to the source file rather than surfacing them, leaving a minor gap.

4 / 5

Workflow Clarity

This is a simple single-purpose catalog skill under 50 lines with an unambiguous three-step sequence (find abstraction, read source, import); no destructive or batch operations exist, so the simple-skill exception applies.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external reference files; content is organized into clear 'How to Use' and 'Abstractions' sections, satisfying the simple-skill exception for a top score.

5 / 5

Total

19

/

20

Passed

Description

45%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 short and points at a specific module, but it omits any 'when to use' guidance and relies on technical jargon rather than natural trigger terms. It is distinct but not actionable as a trigger.

Suggestions

Add an explicit 'Use when...' clause stating when Claude should consult this catalog, e.g. 'Use when working with the Webiny admin GraphQL playground client or tab registry.'

Replace jargon-only phrasing with natural terms users would say, such as 'GraphQL playground client', 'playground tabs', or 'Webiny admin playground'.

Name the concrete actions the skill enables, e.g. 'Find and import playground client factories and tab registries' instead of the bare '4 abstractions'.

DimensionReasoningScore

Specificity

The description names the domain ('admin/graphql-playground') and a concrete artifact type ('4 abstractions'), but states no concrete actions beyond cataloging, so it is not comprehensive.

3 / 5

Completeness

There is only a vague 'what' (4 abstractions) and no 'when'/'Use when...' clause at all, so it fails the explicit-trigger requirement and cannot exceed 3, settling at 2 for the missing when.

2 / 5

Trigger Term Quality

It relies on the technical path 'admin/graphql-playground' and the term 'abstractions', which are jargon a user would rarely utter naturally; no common variations or synonyms are included.

2 / 5

Distinctiveness Conflict Risk

The specific module path 'admin/graphql-playground' carves a clear niche with minimal overlap risk against other skills, though it lacks trigger phrases that would sharpen distinction further.

4 / 5

Total

11

/

20

Passed

Validation

100%

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
Reviewed

Table of Contents

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.