Name: webiny-custom-graphql-api
Rating: 71.2 (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

87%

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

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.

The body is highly actionable with executable examples and a clear pattern progression, well-structured for navigation. It could tighten a few explanatory passages and add an explicit validation/deploy-check step, and longer examples could be split into reference files.

Suggestions

Add an explicit validation checkpoint after registration (e.g. run the deploy/build and query the new endpoint to confirm it resolves) to strengthen the workflow feedback loop.

Move the lengthy Dynamic Input Fields from CMS Model example into a separate reference file and link to it from SKILL.md to improve progressive disclosure.

Trim explanatory prose such as the "Note:" lines and the DI comparison paragraph, trusting Claude's understanding of dependency injection.

Dimension	Reasoning	Score
Conciseness	Largely efficient with executable code and minimal concept over-explanation, but a few prose passages (e.g. the DI explanation and repeated "Note" lines) could be trimmed for token economy.	4 / 5
Actionability	Provides fully executable, copy-paste-ready TypeScript examples covering the common cases (simple query, per-resolver DI, UseCase pattern, namespaced mutations, dynamic CMS inputs, permission transformer) plus a Quick Reference.	5 / 5
Workflow Clarity	The implement -> addTypeDefs/addResolver -> createImplementation -> register as Api.Extension sequence is clear and reinforced by Key Rules and Quick Reference, but there is no explicit build/deploy validation checkpoint to confirm the schema works.	4 / 5
Progressive Disclosure	Well-organized into clearly headed sections with a Quick Reference and a Related Skills pointer; however all content (including a long dynamic-input example) is inlined with no separate reference files, which is appropriate for a pattern skill but leaves minor organization gaps.	4 / 5
	Total	17 / 20 Passed

Description

92%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 specific, complete, and clearly differentiated, with an explicit Use-when clause and a rich set of concrete capabilities. Trigger-term coverage is strong but could add a few more natural synonyms.

Suggestions

Add one or two natural synonyms or shorthand phrases (e.g. "custom GraphQL resolvers", "extend the GraphQL schema") to broaden trigger-term matching.

Consider mentioning the deployment/registration context briefly in the trigger clause so users searching for "register a GraphQL extension" land on this skill.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ("add custom GraphQL endpoints", "create custom queries or mutations", "build custom resolvers", "inject backend services", "build dynamic GraphQL inputs from CMS models") giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly states both what ("Adding custom GraphQL queries and mutations using GraphQLSchemaFactory") and when ("Use this skill when the developer wants to...") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural phrases a developer would say ("add custom GraphQL endpoints", "custom queries or mutations", "build custom resolvers"), but lacks synonym variants and file/extension cues that would push it to full comprehensiveness.	4 / 5
Distinctiveness Conflict Risk	Scoped tightly to GraphQLSchemaFactory-based custom GraphQL APIs in Webiny with niche-specific triggers (identity/tenancy/CMS injection, permission transformers), giving minimal conflict risk with other skills.	5 / 5
	Total	19 / 20 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: 796cd01

Reviewed: 5 days 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.