Name: graphql-architect
Rating: 45.6 (1 reviews)
Author: administrakt0r

graphql-architect

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

Quality

48%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/graphql-architect/SKILL.md

The canonical home for this skill is graphql-architect in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

31%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 a verbose, persona-style enumeration of GraphQL capabilities with no executable guidance, abstract workflow steps lacking validation, and a broken reference to a missing playbook file.

Suggestions

Replace the bullet-list capability catalog with a concise overview and move detailed capability/technique catalogs into reference files (e.g., references/federation-patterns.md, references/performance.md) linked one level deep.

Add concrete, executable examples or commands for the core tasks (e.g., a DataLoader snippet, an APQ config, a federation subgraph SDL) instead of only naming patterns.

Create the referenced resources/implementation-playbook.md (or fix the path) so the 'open resources/implementation-playbook.md' instruction resolves, and add explicit validation/verification checkpoints to the Response Approach steps.

Dimension	Reasoning	Score
Conciseness	The body is a lengthy enumeration of capabilities, behavioral traits, and a knowledge base that largely restates GraphQL concepts Claude already knows (Apollo Federation, DataLoader, JWT, RBAC), matching anchor 2's noticeably verbose, padded-with-unnecessary-lists profile.	2 / 5
Actionability	No executable code or concrete commands appear anywhere; the Instructions ('Clarify goals...', 'Apply relevant best practices') and Response Approach steps are high-level hints, fitting anchor 2's minimal concrete guidance with missing specific steps.	2 / 5
Workflow Clarity	The 'Response Approach' provides an 8-step numbered sequence, but the steps are abstract and lack explicit validation checkpoints or feedback loops, matching anchor 3's sequence-present-but-checkpoints-missing profile.	3 / 5
Progressive Disclosure	The large capability catalog is inlined monolithically in SKILL.md rather than split into reference files, and the one signaled reference ('resources/implementation-playbook.md') does not exist, matching anchor 2's inlined-content-with-buried/broken-references profile.	2 / 5
	Total	9 / 20 Passed

Description

65%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 names a clear, distinctive GraphQL niche with several concrete actions and good trigger terms, but uses second-person imperative voice and omits any explicit 'Use when...' trigger clause, which together cap specificity and completeness.

Suggestions

Rewrite in third person (e.g., 'Designs and builds scalable GraphQL schemas...') to avoid the second-person voice penalty.

Add an explicit 'Use when...' clause naming concrete trigger phrases (e.g., 'Use when designing federated GraphQL schemas, eliminating N+1 queries, or migrating REST APIs to GraphQL').

Add common synonyms and tooling terms users would actually say (e.g., 'Apollo Federation', 'DataLoader', 'subscriptions', '.graphql') to lift trigger-term coverage toward anchor 5.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Build scalable schemas, implement advanced caching, and design real-time systems') which sits at anchor 4, but the imperative second-person voice ('Master...', 'Build...') incurs the rubric's -1 specificity penalty, dropping it to 3.	3 / 5
Completeness	It clearly states what the skill does, but contains no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric completeness is capped at anchor 3 rather than reaching the 4/5 anchors that require an explicit 'when'.	3 / 5
Trigger Term Quality	Includes natural terms users would say ('GraphQL', 'schemas', 'caching', 'real-time systems') with good coverage, but misses common synonyms and file extensions, matching anchor 4 rather than the comprehensive anchor 5.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear GraphQL-architecture niche with distinct triggers (federation, schema design, subscriptions) and minimal overlap risk with other skills, matching anchor 5.	5 / 5
	Total	15 / 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/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.