CtrlK
BlogDocsLog inGet started
Tessl Logo

webiny-admin-graphql-client-catalog

admin/graphql-client — 1 abstractions.

44

Quality

46%

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

85%

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 lean, well-structured catalog that efficiently points the reader to the real interface in source. Its only real weakness is actionability: the workflow relies on placeholder syntax and defers the actual types to external source files rather than showing usage inline.

Suggestions

Show one concrete usage snippet for GraphQLClient instead of the placeholder `import { Name } from "<importPath>"` template, so the guidance is copy-paste ready without first reading source.

Inline the key method/signature of GraphQLClient (or a minimal type sketch) so the core interface is visible in SKILL.md rather than only reachable via the source path.

DimensionReasoningScore

Conciseness

The 24-line body explains no concepts Claude already knows and contains no padding; each line (the lookup steps, the real import, the source path) earns its place, matching the lean anchor 3.

3 / 3

Actionability

It gives a copy-paste import and a concrete source path, but the actual interface/types are deferred to the source file and step 3 uses <Name>/<importPath> placeholders, so guidance is concrete but incomplete (anchor 2).

2 / 3

Workflow Clarity

A clear unambiguous 3-step sequence (find → read source → import) for a read-only catalog with no destructive operations needing validation; the simple-skill guideline allows 3 when the action is unambiguous.

3 / 3

Progressive Disclosure

Under 50 lines with well-organized How-to-Use and Abstractions sections, no bundle files, and a single clearly-signaled Source pointer to actual source code — matching the simple-skill allowance for 3.

3 / 3

Total

11

/

12

Passed

Description

7%

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 essentially a terse label plus an abstraction count — it conveys neither what the skill does nor when to use it. It lacks any concrete actions or natural trigger terms, making it unlikely to fire on real user requests.

Suggestions

Add a concrete action clause, e.g. "Looks up and imports the GraphQLClient abstraction from webiny/admin/graphql-client" so it states what the skill does.

Append a "Use when..." trigger with natural terms such as "Use when working with webiny admin GraphQL clients or needing the GraphQLClient abstraction".

Replace the bare count "1 abstractions" with capability language so the description reads as guidance rather than a catalog header.

DimensionReasoningScore

Specificity

The description "admin/graphql-client — 1 abstractions" names the module domain but lists no actions — "1 abstractions" is a count, not a capability, so it sits below anchor 2 (which requires naming actions).

1 / 3

Completeness

It answers neither "what" (just a label plus a count) nor "when" (no Use-when trigger); both halves are weak or missing, which is anchor 1.

1 / 3

Trigger Term Quality

It contains only technical jargon ("admin/graphql-client", "abstractions") rather than natural phrasings a user would actually say, matching anchor 1.

1 / 3

Distinctiveness Conflict Risk

The specific module path carves out a narrow niche, but with no distinct triggers it could still overlap sibling webiny catalog skills, matching anchor 2.

2 / 3

Total

5

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

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.