CtrlK
BlogDocsLog inGet started
Tessl Logo

graphql-architect

Use when designing GraphQL schemas, implementing Apollo Federation, or building real-time subscriptions. Invoke for schema design, resolvers with DataLoader, query optimization, federation directives.

72

Quality

88%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

This is a solid skill with strong actionability through executable code examples and good workflow clarity with explicit validation checkpoints and error recovery loops. The progressive disclosure structure is well-designed but unsupported by actual bundle files, and the content could be slightly more concise by removing the persona description and knowledge keyword dump. Overall, it provides practical, concrete guidance for GraphQL architecture tasks.

Suggestions

Remove the persona description line and the 'Knowledge Reference' keyword list at the bottom — they consume tokens without adding actionable guidance.

Provide the referenced bundle files (references/schema-design.md, references/resolvers.md, etc.) so the progressive disclosure structure actually delivers on its promises.

DimensionReasoningScore

Conciseness

Generally efficient but includes some unnecessary elements like the 'Knowledge Reference' keyword dump at the bottom and the persona description at the top ('Senior GraphQL architect specializing in...') which adds no actionable value. The constraints section has some items Claude already knows (e.g., 'Follow GraphQL naming conventions (camelCase)').

2 / 3

Actionability

Provides fully executable, copy-paste ready code examples for federation schemas (SDL), DataLoader resolver patterns, and query complexity validation. The examples are concrete, complete, and cover the key patterns (N+1 prevention, federation entity extension, complexity limiting).

3 / 3

Workflow Clarity

The core workflow is clearly sequenced with explicit validation checkpoints at steps 3 and 5, including feedback loops for error recovery (e.g., 'If composition fails: review entity @key directives... then re-run composition'). This covers the destructive/complex operation pattern well.

3 / 3

Progressive Disclosure

The reference table with 'Load When' guidance is well-structured and clearly signaled, but no bundle files were provided, meaning all six referenced files (references/schema-design.md, etc.) are missing. The skill cannot deliver on its progressive disclosure promises, though the structure itself is sound.

2 / 3

Total

10

/

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.

This is a strong skill description that clearly identifies its domain (GraphQL development), lists specific concrete capabilities, and provides explicit trigger guidance with 'Use when' and 'Invoke for' clauses. The description is concise, uses third-person voice appropriately, and includes highly distinctive technical terms that minimize conflict risk with other skills.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: designing GraphQL schemas, implementing Apollo Federation, building real-time subscriptions, writing resolvers with DataLoader, query optimization, and federation directives.

3 / 3

Completeness

Clearly answers both 'what' (designing schemas, implementing federation, building subscriptions, resolvers with DataLoader, query optimization) and 'when' with explicit trigger guidance ('Use when designing GraphQL schemas, implementing Apollo Federation, or building real-time subscriptions. Invoke for...').

3 / 3

Trigger Term Quality

Includes strong natural keywords users would say: 'GraphQL', 'schemas', 'Apollo Federation', 'subscriptions', 'resolvers', 'DataLoader', 'query optimization', 'federation directives'. These are terms developers naturally use when working in this domain.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with a clear niche around GraphQL, Apollo Federation, and related tooling. The specific technology terms (DataLoader, federation directives, subscriptions) make it very unlikely to conflict with other skills.

3 / 3

Total

12

/

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
Jeffallan/claude-skills
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.