CtrlK
BlogDocsLog inGet started
Tessl Logo

graphql-design

GraphQL schema design, resolver patterns, subscriptions, DataLoader for N+1 prevention, and error handling

70

Quality

85%

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

87%

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

A highly actionable, concise reference with strong code examples and clean organization; its main gap is the absence of an explicit review/validation workflow with feedback checkpoints.

Suggestions

Add a short sequenced design-review workflow with a validation checkpoint (e.g. 'Check N+1 risk → verify pagination → confirm error payloads → run depth/complexity limits').

Cross-reference the checklist items to the relevant code sections so each verification step is unambiguous.

DimensionReasoningScore

Conciseness

Lean and token-efficient: code blocks plus one-line guidance, with no padding or explanation of GraphQL/library basics Claude already knows.

3 / 3

Actionability

Fully executable, complete TypeScript and GraphQL examples (schema, resolvers, DataLoader factory, subscriptions) that are copy-paste ready, plus concrete anti-patterns.

3 / 3

Workflow Clarity

The skill is a patterns reference rather than a sequenced process; a closing checklist provides some verification but there is no explicit validate→fix→retry feedback loop for the design workflow.

2 / 3

Progressive Disclosure

Single self-contained file with clearly organized sections (Schema Design, Resolvers, DataLoader, Subscriptions, Anti-Patterns, Checklist) and no nested or missing references.

3 / 3

Total

11

/

12

Passed

Description

82%

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 specific, well-targeted description with good natural trigger terms, but it omits an explicit 'Use when' clause so Claude lacks clear invocation guidance.

Suggestions

Add an explicit trigger clause, e.g. 'Use when designing or reviewing GraphQL schemas, writing resolvers, adding subscriptions, or fixing N+1 query problems.'

Consider leading with a third-person verb phrase ('Designs GraphQL schemas, implements resolvers...') to match the active-voice convention.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'GraphQL schema design, resolver patterns, subscriptions, DataLoader for N+1 prevention, and error handling' — rather than vague abstractions.

3 / 3

Completeness

The 'what' is clearly stated, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 2 per the guidelines.

2 / 3

Trigger Term Quality

Natural terms a GraphQL user would actually say are well covered: 'GraphQL', 'schema design', 'resolvers', 'subscriptions', 'DataLoader', 'N+1'.

3 / 3

Distinctiveness Conflict Risk

GraphQL schema design is a distinct, well-scoped niche with specific technical triggers unlikely to collide with other skills.

3 / 3

Total

11

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
rohitg00/awesome-claude-code-toolkit
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.