graphql-architect

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

Quality

53%

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

35%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 persona-and-capability catalog rather than actionable guidance: it lists what an expert GraphQL architect knows without providing executable code, concrete workflows with validation, or progressive references. It reads as padded domain knowledge Claude already has.

Suggestions

Replace the capability bullet catalogs with a concise overview plus executable examples (e.g. a DataLoader snippet, a federated subgraph SDL, an APQ/persisted-query setup).

Turn "Response Approach" into a concrete workflow with explicit validation checkpoints and error-recovery feedback loops (e.g. validate composed schema, run query-cost analysis, re-check on failure).

Move the detailed capability, tooling, and testing catalogs into separate reference files (e.g. FEDERATION.md, PERFORMANCE.md, SECURITY.md) and link to them one level deep from a lean SKILL.md.

Dimension	Reasoning	Score
Conciseness	Roughly 160 lines of capability bullets, behavioral traits, and a "Knowledge Base" section largely restate GraphQL domain knowledge Claude already has (e.g. "GraphQL specification and best practices"), making it noticeably padded.	2 / 5
Actionability	It only describes capabilities ("Implement DataLoader pattern", "Configure caching and security") with no executable code, commands, or concrete examples, leaving only high-level hints.	2 / 5
Workflow Clarity	The "Response Approach" gives an 8-step sequence, but steps are abstract ("Analyze business requirements", "Design scalable schema") with no validation checkpoints or error-recovery feedback loops.	3 / 5
Progressive Disclosure	No bundle files exist and the body is a single inlined catalog of capability bullets under headers; content that clearly belongs in separate reference files (e.g. the long capability/tooling lists) is not split out or signaled.	3 / 5
	Total	10 / 20 Passed

Description

71%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 reasonably strong description: it states concrete capabilities and includes explicit proactive-use guidance with a clear GraphQL niche. The main weakness is trigger-term breadth, lacking the synonyms and variation phrases users naturally say.

Suggestions

Broaden trigger terms to include natural synonyms users say, e.g. "federated GraphQL", "GraphQL subscriptions", "N+1 queries", "schema design".

Make the "when" clause list a couple of concrete trigger scenarios rather than only "GraphQL architecture or performance optimization".

Consider mentioning file/extension or tool cues (e.g. Apollo Federation, SDL) to improve distinctiveness and trigger recall.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions such as "Build scalable schemas, implement advanced caching, and design real-time systems" alongside federation and enterprise security, with only minor coverage gaps.	4 / 5
Completeness	Both a clear "what" (federation, caching, real-time systems, schema design) and an explicit "when" ("Use PROACTIVELY for GraphQL architecture or performance optimization") are present, though the trigger could be more specific.	4 / 5
Trigger Term Quality	Covers the core term "GraphQL architecture or performance optimization" but omits natural variations and synonyms a user might say (e.g. federated, subscriptions, N+1, schema design).	3 / 5
Distinctiveness Conflict Risk	"GraphQL architecture" carves out a clear niche with distinct triggers and minimal overlap risk against other skills.	5 / 5
	Total	16 / 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: rmyndharis/antigravity-skills
Path: skills/graphql-architect/SKILL.md
Commit: 3eff4af

Reviewed: 1 day 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.