CtrlK
BlogDocsLog inGet started
Tessl Logo

graphql-implementation

Builds GraphQL APIs with schema design, resolvers, error handling, and performance optimization using Apollo or Graphene. Use when creating flexible query APIs, migrating from REST, or implementing real-time subscriptions.

64

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/graphql-implementation/skills/graphql-implementation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 useful, code-rich reference that handles progressive disclosure well by offloading the Graphene/Flask implementation to a dedicated file. Its main weaknesses are a duplicated Best Practices section and the absence of explicit workflow sequencing or validation checkpoints for data-mutating operations.

Suggestions

Remove the duplicate "## Best Practices" section (lines 93-99) and keep only the richer Do/Don't version, eliminating the five repeated bullets.

Add explicit validation/verification guidance for mutations (e.g., check input validity and return meaningful errors before persisting createUser/createPost).

Make the Apollo snippet self-contained by noting where typeDefs and dataSources come from, or reference a complete example file, so the code is copy-paste ready.

DimensionReasoningScore

Conciseness

Mostly lean code-focused sections, but the opening line restates the description and the "Best Practices" section appears twice with five identical bullets repeated (Use DataLoader, query complexity limits, design around client needs, validate inputs, descriptive naming), which should be tightened.

3 / 5

Actionability

Provides concrete, mostly executable code for schema SDL, Apollo resolvers, DataLoader, and GraphQLError, but snippets reference undefined symbols (typeDefs, dataSources, User model) that prevent full copy-paste readiness.

4 / 5

Workflow Clarity

Sections follow a loose logical order (schema → server → DataLoader → errors → practices) but there is no explicit sequenced workflow, and the write/mutation operations lack any validation or verification checkpoints.

3 / 5

Progressive Disclosure

The Python/Graphene detail is cleanly split into a real, well-signaled one-level-deep reference (references/python-graphene.md) with a description of its contents, though the duplicate "Best Practices" header is a minor organization gap.

4 / 5

Total

14

/

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.

A strong, specific description that clearly states capabilities and provides explicit trigger guidance for when to use the skill. Minor room for more keyword synonyms, but it cleanly distinguishes itself and answers both what and when.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "schema design, resolvers, error handling, and performance optimization" — covering the core pillars of GraphQL implementation comprehensively, with tooling (Apollo or Graphene) named.

5 / 5

Completeness

Explicitly answers both what ("Builds GraphQL APIs with schema design, resolvers, error handling, and performance optimization") and when ("Use when creating flexible query APIs, migrating from REST, or implementing real-time subscriptions") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural trigger phrases users would say ("GraphQL APIs", "migrating from REST", "real-time subscriptions", "query APIs"), but lacks synonyms and file/extension variants that would push it to comprehensive.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear GraphQL-specific niche with distinct triggers (REST migration, subscriptions, query APIs) and minimal overlap risk with other skills.

5 / 5

Total

19

/

20

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
secondsky/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.