Name: webiny-custom-graphql-api
Rating: 68 (1 reviews)
Author: webiny

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, 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

82%

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

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with complete, copy-paste-ready TypeScript patterns, but it is somewhat verbose due to duplicated summary sections and lacks explicit build-verification checkpoints and external reference files for its advanced patterns.

Suggestions

Collapse the duplication between the inline examples, the 'Key Rules' list, and the 'Quick Reference' block into a single canonical set to tighten token usage.

Add an explicit verification step such as 'run `yarn webiny build api` and confirm no errors before deploying', with a fix-and-retry feedback loop for build failures.

Move the advanced patterns (Dynamic Input Fields from CMS Model, Permission Transformer) into separate reference files linked from the overview to enable one-level-deep progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is code-forward and free of basic-concept padding, but duplicates content across inline examples, the 'Key Rules' list, and the 'Quick Reference' block (e.g. createImplementation({ implementation, dependencies: [] }) appears repeatedly), so it could be tightened rather than being lean at score 3.	2 / 3
Actionability	Provides complete, executable TypeScript examples with imports, schema classes, resolver factories, createImplementation exports, and Api.Extension registration that are copy-paste ready, matching the score-3 anchor.	3 / 3
Workflow Clarity	The core sequence is clear (implement Interface, use the builder, export via createImplementation, register as Api.Extension) and two 'YOU MUST ... will cause a build failure' warnings exist, but there is no explicit build/verify checkpoint or fix-retry feedback loop, matching score-2 (sequence present, checkpoints implicit).	2 / 3
Progressive Disclosure	Internal sections are well organized, but all content sits inline in a ~400-line SKILL.md with no one-level-deep detail-file references, and advanced patterns (Dynamic Input Fields, Permission Transformer) that could be split out are kept inline, fitting score-2 rather than the split-and-linked score-3.	2 / 3
	Total	9 / 12 Passed

Description

100%

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 specific, third-person, and explicitly pairs a 'what' statement with a rich 'Use this skill when' trigger clause covering natural developer terms. It carves out a distinct Webiny GraphQL niche with low conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions such as 'add custom GraphQL endpoints, create custom queries or mutations, add business logic to the API layer, build custom resolvers, inject backend services ... build dynamic GraphQL inputs from CMS models', matching the multi-action score-3 anchor rather than the partial score-2.	3 / 3
Completeness	Explicitly answers both what ('Adding custom GraphQL queries and mutations using GraphQLSchemaFactory') and when ('Use this skill when the developer wants to ...'), with the required explicit trigger clause so it is not capped at 2.	3 / 3
Trigger Term Quality	Uses natural developer phrasing ('custom GraphQL endpoints', 'custom queries or mutations', 'build custom resolvers') with good coverage of terms a user would actually say, exceeding the 'some relevant keywords' bar of score 2.	3 / 3
Distinctiveness Conflict Risk	Targets a clear Webiny GraphQL-API niche with distinct triggers (custom GraphQL endpoints/resolvers), making it unlikely to fire for unrelated skills; not merely 'somewhat specific' as at score 2.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
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
Commit: 484553b

Reviewed: about 13 hours 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.