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

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 ./skills/graphql-architect/SKILL.md

Quality

Content

12%

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

The content is a long enumeration of GraphQL topic areas with no executable guidance, code, or external references. It pads the context with domains Claude already knows and provides only a vague, validation-free workflow.

Suggestions

Replace the topic bullet lists with a few concrete, copy-paste examples (e.g. a federated subgraph SDL snippet, a DataLoader resolver pattern) instead of naming the concepts.

Add validation checkpoints to the 'Response Approach' (e.g. schema-lint or query-complexity verification between steps) so destructive or production changes are checked.

Move the detailed capability catalog into a references/ file and keep SKILL.md as a lean overview with clearly signaled one-level-deep links.

Dimension	Reasoning	Score
Conciseness	The body is ~170 lines of bulleted topic enumerations ('Apollo Federation v2 and Subgraph design patterns', 'DataLoader pattern implementation for N+1 problem resolution') that re-state GraphQL domains Claude already knows, the verbose/verbose-padded anchor; it does not reach the 'mostly efficient' level 2.	1 / 3
Actionability	There is no executable code or commands anywhere; the 'Response Approach' offers vague directives like 'Design scalable schema' and 'Implement efficient resolvers' that describe rather than instruct, matching the vague/abstract anchor.	1 / 3
Workflow Clarity	The 'Response Approach' lists a numbered 8-step sequence but lacks validation checkpoints, error-recovery loops, or any verification commands, fitting 'steps listed but validation gaps'; it is not the unstructured level 1 because a sequence is present.	2 / 3
Progressive Disclosure	Everything is a monolithic wall of text in a single SKILL.md with no bundle files (references/, scripts/, assets/ do not exist) and no one-level-deep references, matching the monolithic/poor-organization anchor rather than the structured level 2.	1 / 3
	Total	5 / 12 Passed

Description

85%

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 is specific, complete with explicit 'what' and 'when' clauses, and occupies a clear niche. Its only weakness is trigger-term breadth, leaning on a narrow repeated set of GraphQL phrases rather than varied natural phrasings.

Suggestions

Broaden trigger terms with natural variations users might say, e.g. 'schema design', 'N+1 queries', 'GraphQL gateway', or 'federated subgraphs'.

Avoid repeating 'GraphQL' multiple times; fold the niche signal into one clear trigger clause.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions such as 'Build scalable schemas', 'implement advanced caching', and 'design real-time systems', matching the multiple-specific-actions anchor rather than the domain-only level 2.	3 / 3
Completeness	It states both what it does ('Build scalable schemas, implement advanced caching, and design real-time systems') and an explicit when ('Use PROACTIVELY for GraphQL architecture or performance optimization'), satisfying both halves required for level 3.	3 / 3
Trigger Term Quality	It offers relevant natural terms ('GraphQL', 'GraphQL architecture', 'performance optimization') but repeats a narrow set with no common variations or synonyms, fitting the 'some relevant keywords but missing common variations' band rather than the broad coverage of level 3.	2 / 3
Distinctiveness Conflict Risk	The 'GraphQL architecture' niche with explicit triggers is clearly distinguishable from other skills and unlikely to fire for the wrong one, matching the clear-niche anchor.	3 / 3
	Total	11 / 12 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: e63f7dd

Reviewed: about 23 hours 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.