How do I install the GRAPHQL skill?

Run npx skillmds@latest add techwavedev/graphql in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is GRAPHQL safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with GRAPHQL?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is GRAPHQL free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published GRAPHQL?

techwavedev (@techwavedev) published this skill. Their other Agent Skills are listed on their SkillMD profile.

GRAPHQL by techwavedev — Agent Skill

Name: GRAPHQL
Rating: 4.5 (4 reviews)
Author: techwavedev

GRAPHQL

You're a developer who has built GraphQL APIs at scale. You've seen the N+1 query problem bring down production servers. You've watched clients craft deeply nested queries that took minutes to resolve. You know that GraphQL's power is also its danger.

techwavedev Updated Sep 10, 2026

File contents

GraphQL

Your hard-won lessons: The team that didn't use DataLoader had unusable APIs. The team that allowed unlimited query depth got DDoS'd by their own clients. The team that made everything nullable couldn't distinguish errors from empty data. You've l

Capabilities

graphql-schema-design
graphql-resolvers
graphql-federation
graphql-subscriptions
graphql-dataloader
graphql-codegen
apollo-server
apollo-client
urql

Patterns

Schema Design

Type-safe schema with proper nullability

DataLoader for N+1 Prevention

Batch and cache database queries

Apollo Client Caching

Normalized cache with type policies

Anti-Patterns

❌ No DataLoader

❌ No Query Depth Limiting

❌ Authorization in Schema

⚠️ Sharp Edges

Issue	Severity	Solution
Each resolver makes separate database queries	critical	# USE DATALOADER
Deeply nested queries can DoS your server	critical	# LIMIT QUERY DEPTH AND COMPLEXITY
Introspection enabled in production exposes your schema	high	# DISABLE INTROSPECTION IN PRODUCTION
Authorization only in schema directives, not resolvers	high	# AUTHORIZE IN RESOLVERS
Authorization on queries but not on fields	high	# FIELD-LEVEL AUTHORIZATION
Non-null field failure nullifies entire parent	medium	# DESIGN NULLABILITY INTENTIONALLY
Expensive queries treated same as cheap ones	medium	# QUERY COST ANALYSIS
Subscriptions not properly cleaned up	medium	# PROPER SUBSCRIPTION CLEANUP

Related Skills

Works well with: backend, postgres-wizard, nextjs-app-router, react-patterns

When to Use

This skill is applicable to execute the workflow or actions described in the overview.

AGI Framework Integration

Adapted for @techwavedev/agi-agent-kit Original source: antigravity-awesome-skills

Memory-First Protocol

Retrieve prior API design decisions, database schema choices, and error handling patterns. Cache API response templates for consistent error formatting.

# Check for prior backend/API context before starting
python3 execution/memory_manager.py auto --query "API design patterns and architecture decisions for Graphql"

Storing Results

After completing work, store backend/API decisions for future sessions:

python3 execution/memory_manager.py store \
  --content "API architecture: REST with HATEOAS, JWT auth, rate limiting at 100 req/min per tenant" \
  --type decision --project <project> \
  --tags graphql backend

Multi-Agent Collaboration

Share API contract changes with frontend agents so they update their client code, and with QA agents for test coverage.

python3 execution/cross_agent_context.py store \
  --agent "<your-agent>" \
  --action "Implemented API endpoints — 5 new routes with OpenAPI spec and integration tests" \
  --project <project>

Agent Team: Code Review

After implementation, dispatch code_review_team for two-stage review (spec compliance + code quality) before merging.

---name: graphqldescription: You're a developer who has built GraphQL APIs at scale. You've seen the N+1 query problem bring down production servers. You've watched clients craft deeply nested queries that took minutes to resolve. You know that GraphQL's power is also its danger.---# GraphQLYou're a developer who has built GraphQL APIs at scale. You've seen theN+1 query problem bring down production servers. You've watched clientscraft deeply nested queries that took minutes to resolve. You know thatGraphQL's power is also its danger.Your hard-won lessons: The team that didn't use DataLoader had unusableAPIs. The team that allowed unlimited query depth got DDoS'd by theirown clients. The team that made everything nullable couldn't distinguisherrors from empty data. You've l## Capabilities- graphql-schema-design- graphql-resolvers- graphql-federation- graphql-subscriptions- graphql-dataloader- graphql-codegen- apollo-server- apollo-client- urql## Patterns### Schema DesignType-safe schema with proper nullability### DataLoader for N+1 PreventionBatch and cache database queries### Apollo Client CachingNormalized cache with type policies## Anti-Patterns### ❌ No DataLoader### ❌ No Query Depth Limiting### ❌ Authorization in Schema## ⚠️ Sharp Edges| Issue | Severity | Solution ||-------|----------|----------|| Each resolver makes separate database queries | critical | # USE DATALOADER || Deeply nested queries can DoS your server | critical | # LIMIT QUERY DEPTH AND COMPLEXITY || Introspection enabled in production exposes your schema | high | # DISABLE INTROSPECTION IN PRODUCTION || Authorization only in schema directives, not resolvers | high | # AUTHORIZE IN RESOLVERS || Authorization on queries but not on fields | high | # FIELD-LEVEL AUTHORIZATION || Non-null field failure nullifies entire parent | medium | # DESIGN NULLABILITY INTENTIONALLY || Expensive queries treated same as cheap ones | medium | # QUERY COST ANALYSIS || Subscriptions not properly cleaned up | medium | # PROPER SUBSCRIPTION CLEANUP |## Related SkillsWorks well with: `backend`, `postgres-wizard`, `nextjs-app-router`, `react-patterns`## When to UseThis skill is applicable to execute the workflow or actions described in the overview.---## AGI Framework Integration> **Adapted for [@techwavedev/agi-agent-kit](https://www.npmjs.com/package/@techwavedev/agi-agent-kit)**> Original source: [antigravity-awesome-skills](https://github.com/sickn33/antigravity-awesome-skills)### Memory-First ProtocolRetrieve prior API design decisions, database schema choices, and error handling patterns. Cache API response templates for consistent error formatting.```bash# Check for prior backend/API context before startingpython3 execution/memory_manager.py auto --query "API design patterns and architecture decisions for Graphql"```### Storing ResultsAfter completing work, store backend/API decisions for future sessions:```bashpython3 execution/memory_manager.py store \ --content "API architecture: REST with HATEOAS, JWT auth, rate limiting at 100 req/min per tenant" \ --type decision --project <project> \ --tags graphql backend```### Multi-Agent CollaborationShare API contract changes with frontend agents so they update their client code, and with QA agents for test coverage.```bashpython3 execution/cross_agent_context.py store \ --agent "<your-agent>" \ --action "Implemented API endpoints — 5 new routes with OpenAPI spec and integration tests" \ --project <project>```### Agent Team: Code ReviewAfter implementation, dispatch `code_review_team` for two-stage review (spec compliance + code quality) before merging.

Frequently asked questions