graphql-architect

Master modern GraphQL with federation, performance optimization, and enterprise security. Build scalable schemas, implement advanced caching, and design real-time systems.

Quality

25%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/graphql-architect/SKILL.md

Quality

Content

10%Scale 1-5

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

This skill is essentially a persona description or role prompt rather than an actionable skill file. It consists almost entirely of capability lists, behavioral traits, and knowledge areas that Claude already possesses, with zero executable code, no concrete examples, and no specific workflows. The single reference to a bundle file (implementation-playbook.md) is broken as no bundle exists.

Suggestions

Replace the capability/trait/knowledge lists with concrete, executable code examples for the most common tasks (e.g., a DataLoader implementation, a federation subgraph schema, a caching configuration).

Add specific multi-step workflows with validation checkpoints for complex operations like REST-to-GraphQL migration or federation setup, including commands to run and expected outputs.

Create the referenced 'resources/implementation-playbook.md' bundle file and move detailed patterns there, keeping SKILL.md as a concise overview with clear navigation links.

Remove sections that describe Claude's persona ('Behavioral Traits', 'Knowledge Base', 'Example Interactions') as they consume tokens without adding actionable guidance.

Dimension	Reasoning	Score
Conciseness	Extremely verbose and padded. The content is essentially a long list of capabilities, behavioral traits, and knowledge areas that Claude already knows. It reads like a job description or persona prompt rather than a skill file. Sections like 'Capabilities', 'Behavioral Traits', 'Knowledge Base', and 'Example Interactions' are pure padding with no actionable content.	1 / 5
Actionability	There is no concrete, executable guidance anywhere in the skill. No code examples, no specific commands, no schemas, no configuration snippets. The 'Response Approach' is a vague 8-step list of abstract activities ('Analyze business requirements', 'Design scalable schema'). The instruction to 'open resources/implementation-playbook.md' is the only semi-concrete directive, but no bundle file exists to support it.	1 / 5
Workflow Clarity	The 'Response Approach' section provides a rough 8-step sequence but steps are entirely abstract with no validation checkpoints, no error recovery, and no concrete actions. For a skill covering destructive or complex operations like schema migration and federation setup, the lack of any validation steps is a significant gap.	2 / 5
Progressive Disclosure	The skill references 'resources/implementation-playbook.md' but no bundle files exist, making this a broken reference. The massive amount of content that should be in separate reference files (capabilities lists, tool inventories, testing strategies) is inlined as a monolithic wall of bullet points with no meaningful structure for navigation.	2 / 5
	Total	6 / 20 Passed

Description

41%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 identifies GraphQL as its domain and mentions several relevant subtopics, but reads more like a course catalog blurb than a functional skill description. It lacks a 'Use when...' clause entirely, uses marketing-style language ('Master modern', 'enterprise security'), and doesn't provide concrete enough actions or trigger terms for reliable skill selection.

Suggestions

Add an explicit 'Use when...' clause with natural trigger phrases like 'Use when the user asks about GraphQL APIs, writing queries/mutations, setting up resolvers, schema design, or Apollo federation.'

Replace marketing language ('Master modern', 'enterprise') with concrete actions: e.g., 'Designs GraphQL schemas, writes resolvers, configures federation gateways, optimizes query performance with DataLoader and caching, implements subscriptions for real-time updates.'

Include common synonyms and related terms users might mention: 'API', 'query', 'mutation', 'subscription', 'resolver', 'Apollo', 'schema stitching', '.graphql files'.

Dimension	Reasoning	Score
Specificity	Names the domain (GraphQL) and lists several areas like federation, caching, schemas, and real-time systems, but these are more like topic categories than concrete actions. 'Build scalable schemas' and 'implement advanced caching' are somewhat concrete but still high-level.	3 / 5
Completeness	Has a somewhat clear 'what' (build schemas, implement caching, design real-time systems with GraphQL), but completely lacks any 'when' clause or trigger guidance. The absence of a 'Use when...' clause caps this at 3 per guidelines, and the 'what' is more aspirational than concrete, bringing it to 2.	2 / 5
Trigger Term Quality	Includes relevant keywords like 'GraphQL', 'federation', 'caching', 'schemas', and 'real-time systems', but misses natural user phrases like 'API', 'query', 'mutation', 'subscription', 'resolver', 'Apollo', or 'schema stitching'. Users asking about GraphQL would likely use more specific terms.	3 / 5
Distinctiveness Conflict Risk	GraphQL is a specific enough domain to provide some distinctiveness, but terms like 'performance optimization', 'enterprise security', and 'real-time systems' are very broad and could overlap with many other skills covering APIs, backend development, or security.	3 / 5
	Total	11 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/graphql-architect/SKILL.md
Commit: 57c135b

Reviewed: 4 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.