CtrlK
BlogDocsLog inGet started
Tessl Logo

webiny-admin-graphql-client-catalog

admin/graphql-client — 1 abstractions.

56

Quality

70%

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-client/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 an exemplary lean abstraction catalog: concise, well-organized, with exact import and source-file pointers and an unambiguous lookup workflow. Its only gap is the absence of a minimal usage example for the listed abstraction, leaving the reader to consult the source for how to actually use it.

Suggestions

Add a one-line usage snippet per abstraction (e.g. how GraphQLClient executes a query) so the common case is covered without reading the source.

Note what the abstraction is for in a few words (e.g. 'GraphQLClient — sends GraphQL requests from admin apps') so the catalog supports choosing the right abstraction without opening every source file.

DimensionReasoningScore

Conciseness

The body is a lean catalog: 'Find the abstraction you need below', 'You MUST read the source file to get the exact interface and types!', and the exact import and source path. It explains nothing Claude already knows and every token earns its place, matching anchor 5.

5 / 5

Actionability

The guidance is concrete and copy-paste ready ('import { GraphQLClient } from "webiny/admin/graphql-client"' plus an exact source path), but there is no usage example and the common case is deferred entirely to reading the source file, so it falls short of anchor 5's 'specific examples cover the common cases'.

4 / 5

Workflow Clarity

This is a simple single-purpose catalog under 50 lines, and the 3-step sequence (find abstraction → read source for exact interface and types → import) is unambiguous and correctly ordered. No destructive or batch operations exist, so the validation cap does not apply, satisfying the simple-skill exception for a 5.

5 / 5

Progressive Disclosure

For a skill under 50 lines with no bundle files, the two well-organized sections ('How to Use', 'Abstractions') and a single one-level-deep pointer to the real source file ('@webiny/app/features/graphqlClient/abstractions.ts') exemplify appropriate detail deferral, matching anchor 5.

5 / 5

Total

19

/

20

Passed

Description

32%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 bare catalog label: it identifies the domain but describes no actions, includes no natural trigger terms, and omits any 'use when' guidance. It is narrowly distinguishable by its domain path, but as a skill description it fails to communicate what the skill does or when to invoke it.

Suggestions

Add concrete capability actions in third person, e.g. 'Provides the GraphQLClient abstraction for sending GraphQL requests from Webiny admin apps'.

Add an explicit trigger clause, e.g. 'Use when working in Webiny admin code that needs to query or mutate data via GraphQL'.

Include natural user-facing terms such as 'GraphQL client', 'admin API requests', and 'query/mutate' so the skill matches how users actually phrase the need.

DimensionReasoningScore

Specificity

The description is only 'admin/graphql-client — 1 abstractions.' — it names the domain but contains no action verbs at all, sitting between the 'entirely vague' (1) and 'names the domain but actions are minimal' (2) anchors; the domain label keeps it just above entirely vague.

2 / 5

Completeness

There is only a vague 'what' (a domain label with no described capability) and no 'when' or 'Use when' clause whatsoever, matching anchor 2 ('has a vague what and no when'). Not anchor 1 only because the domain path conveys minimal purpose information.

2 / 5

Trigger Term Quality

Only technical jargon ('admin/graphql-client', 'abstractions') appears; no natural phrases a user would say such as 'GraphQL client' or 'send GraphQL requests'. It is domain-specific rather than entirely generic, so anchor 2 fits better than anchor 1.

2 / 5

Distinctiveness Conflict Risk

'admin/graphql-client' is a narrow, specific niche within Webiny's admin layer with minimal overlap risk against generic skills. It misses anchor 5 because it has no distinct trigger phrases that would separate it from sibling Webiny catalog skills.

4 / 5

Total

10

/

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.