Back to catalog
Human reviewedDesign

Skill dossier

graphql-architect

Source declaration

Use when designing GraphQL schemas, implementing Apollo Federation, or building real-time subscriptions. Invoke for schema design, resolvers with DataLoader, query optimization, federation directives.

The author's original description, preserved in English. It describes intent, not verified performance.

Use when designing GraphQL schemas, implementing Apollo Federation, or building real-time subscriptions. Invoke for schema design, resolvers with DataLoader, query optimization, federation directives.

designreferences

Research summary

Human reviewed

Skill Atlas editorial review · editorial-preview-1.0.0

An API design Skill for GraphQL schemas, Apollo Federation and subscriptions, with schema composition checks, DataLoader resolvers and query complexity limits.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Maps business domains to a GraphQL type system and designs schemas with federation directives.
  • Runs schema composition checks and confirms @key entities resolve across subgraphs.
  • Writes resolvers with DataLoader batching to avoid N+1 queries.
  • Adds query complexity limits, depth limiting and field-level authorization.

Limitations & scope

  • Focused on Apollo Federation 2.5+ and Apollo Server; other GraphQL stacks are not covered.
  • The composition check relies on tooling that the skill does not name or provide.
  • Schemas and resolvers are not verified here.

Relevant for

  • API architects designing federated graphs
  • Backend developers adding DataLoader and complexity controls

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
7
Markdown files
7
scripts
0
references
6
Size
79.7 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/graphql-architect/references/federation.mdReference9 KB
skills/graphql-architect/references/migration-from-rest.mdReference24.4 KB
skills/graphql-architect/references/resolvers.mdReference10 KB
skills/graphql-architect/references/schema-design.mdReference6.4 KB
skills/graphql-architect/references/security.mdReference12.9 KB
skills/graphql-architect/references/subscriptions.mdReference11.9 KB
skills/graphql-architect/SKILL.mdInstruction5.1 KB

SKILL.md frontmatter

{
  "name": "graphql-architect",
  "description": "Use when designing GraphQL schemas, implementing Apollo Federation, or building real-time subscriptions. Invoke for schema design, resolvers with DataLoader, query optimization, federation directives.",
  "license": "MIT",
  "metadata": {
    "author": "https://github.com/Jeffallan",
    "company": "https://synergetic.solutions",
    "version": "1.1.0",
    "domain": "api-architecture",
    "triggers": "GraphQL, Apollo Federation, GraphQL schema, API graph, GraphQL subscriptions, Apollo Server, schema design, GraphQL resolvers, DataLoader",
    "role": "architect",
    "scope": "design",
    "output-format": "schema",
    "related-skills": "api-designer, microservices-architect, database-optimizer"
  }
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Input

    Model the domain

    Map business domains to the GraphQL type system.

  2. 02
    Action

    Design and validate schema

    Create types with federation directives and run a composition check confirming @key entities resolve.

  3. 03
    Decision

    Handle composition failures

    If composition fails, review @key directives, mismatched definitions and @external fields, then re-run.

  4. 04
    Output

    Deliver schema and resolvers

    Provide SDL, DataLoader resolvers, example operations and a brief explanation of design decisions.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

189 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useObserved
Medium

Network access is mentioned

23 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 23 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

159 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 159 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Credential or secret material is referenced

7 occurrences

This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 7 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Editorial security note

Verify that complexity and depth limits are actually enforced and that authorization is not hardcoded in resolvers.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
git clone https://github.com/Jeffallan/claude-skills.git cd claude-skills # Copy this skill directory into one of: # ~/.claude/skills/graphql-architect # .claude/skills/graphql-architect
  1. Open the pinned source at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/graphql-architect/SKILL.md.
  2. Review the license, prerequisites and all bundled reference files.
  3. Copy the skill directory into a personal or project-level Claude Code skills directory.
  4. Restart or refresh Claude Code so the skill can be discovered.
Verify installation

Ask Claude Code to design a small two-subgraph schema and confirm it checks composition and adds a DataLoader.

Prerequisites

  • Focused on Apollo Federation 2.5+ and Apollo Server; other GraphQL stacks are not covered.
  • The composition check relies on tooling that the skill does not name or provide.
  • Schemas and resolvers are not verified here.

Example prompts

Representative task

Use the graphql-architect skill to design a products and reviews federated schema with @key on Product, a per-request DataLoader for review authors, and a query complexity limit with example queries.

Inspect before use

Read the graphql-architect skill at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/graphql-architect/SKILL.md. Explain its workflow, required tools, permissions and the main risks before I decide whether to install it.

A decision, with its limits attached

Strengths

  • Provides recovery steps for failed composition and exceeded complexity thresholds.
  • Constraints name N+1, depth limiting and non-null handling explicitly.

Considerations

  • Limits such as the example complexity of 1000 are placeholders to tune for your service.
  • Federation adds operational complexity that smaller APIs may not need.
Research conclusion

A focused schema-first guide that suits teams adopting federation and wanting N+1 and abuse protections built in.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

Jeffallanclaude-skillsskills/graphql-architect
Source type
Community
Commit
67c1961b180dc92cf08983344627109e983e8f51
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
MIT
Repository stars
12,464
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.