CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

webiny-custom-graphql-api

Adding custom GraphQL queries and mutations using GraphQLSchemaFactory. Use this skill when the developer wants to add custom GraphQL endpoints, create custom queries or mutations, add business logic to the API layer, build custom resolvers, inject backend services (identity, tenancy, CMS use-cases) into their GraphQL schema, add authorization checks to resolvers, or build dynamic GraphQL inputs from CMS models. Covers the full pattern from simple queries to complex resolvers with dependency injection and permission transformers.

Quality

87%

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

SKILL.md
Quality
Evals
Security

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.

A high-quality, code-dense skill body: complete copy-paste-ready examples that consistently show the same end-to-end pattern, with a genuinely valuable section on the schema-caching security pitfall of constructor DI. The main improvement levers are reducing the triple restatement of the DI rule and adding an explicit verification step to the workflow.

DimensionReasoningScore

Conciseness

The body is code-first and teaches only Webiny-specific machinery (GraphQLSchemaFactory, schema caching semantics) rather than concepts Claude already knows, but the constructor-DI prohibition is restated in the TL;DR warnings, the dedicated section, Key Rules, and code comments, which could be trimmed slightly.

4 / 5

Actionability

Every example is complete, executable TypeScript with imports, resolver wiring, createImplementation export, and extension registration, covering the common cases (simple query, DI, namespaced mutations, dynamic CMS inputs, permission transformers) plus a concrete deploy command.

5 / 5

Workflow Clarity

The TL;DR lays out the sequence (implement interface, addTypeDefs/addResolver, createImplementation, register as Api.Extension) and the build-failure warnings act as pre-emptive checkpoints, but there is no explicit post-deploy verification loop, so it sits just below the top anchor.

4 / 5

Progressive Disclosure

With no bundle files, the single file is well organized — TL;DR, clear section headers, an internal anchor link, a Quick Reference, and a Related Skills map — though the more advanced sections (Dynamic Input Fields from CMS Model, Permission Transformer) are inlined where a leaner split could be considered.

4 / 5

Total

17

/

20

Passed

Description

88%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.

A strong description: it states concrete capabilities in third person and provides an explicit, enumerated "Use this skill when..." trigger list covering the full pattern scope. Trigger-term coverage is good but misses a few natural synonyms, and broad phrases like "add business logic to the API layer" create minor overlap risk with related Webiny skills.

DimensionReasoningScore

Specificity

The description enumerates many concrete actions — "add custom GraphQL endpoints", "build custom resolvers", "inject backend services (identity, tenancy, CMS use-cases) into their GraphQL schema", "add authorization checks to resolvers", "build dynamic GraphQL inputs from CMS models" — giving comprehensive, not merely several, coverage.

5 / 5

Completeness

It answers "what" explicitly and in third person ("Adding custom GraphQL queries and mutations using GraphQLSchemaFactory") and "when" with an explicit, enumerated "Use this skill when the developer wants to..." clause listing concrete trigger scenarios.

5 / 5

Trigger Term Quality

Natural developer phrasings like "custom GraphQL endpoints", "create custom queries or mutations", "resolvers", and "authorization checks" are well covered, but a few natural variants ("extend the GraphQL API", "Webiny API", "GraphQL schema extension") are missing, so it falls just short of the synonym-inclusive top anchor.

4 / 5

Distinctiveness Conflict Risk

The GraphQLSchemaFactory/Webiny niche is distinct with clear triggers, but phrases like "add business logic to the API layer" and "inject backend services" overlap with the closely related skills it itself references (use-case and dependency-injection skills).

4 / 5

Total

18

/

20

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.

Validation — 15 / 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

Path

skills/user-skills/api/graphql-api/SKILL.md

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.