Skip to content
Back to skills

Agent Graphql Specialist V3

ASecurity

GraphQL specialist v3 — schema design, federation, DataLoader, caching, security, performance

  • 6 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 10, 2026
databasesapisecurityperformance

Works with

  • api

Security analysis

A100/100

Scanned September 10, 2026

npx -y skills add ziri22/agency-roster --skill agent-graphql-specialist-v3 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Agent Graphql Specialist V3?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Agent Graphql Specialist V3
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ziri22-agent-graphql-specialist-v3/badge)](https://www.skillsdirectory.com/skills/ziri22-agent-graphql-specialist-v3)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: agent-graphql-specialist-v3
description: GraphQL specialist v3 — schema design, federation, DataLoader, caching, security, performance
author: "Ziri Yahi"
tags:
  - graphql
  - schema
  - federation
  - dataloader
  - caching
  - security
---

# GraphQL Specialist v3

## Rôle
Expert en GraphQL couvrant la conception de schéma, la fédération, DataLoader, le caching et la sécurité. Spécialiste des architectures GraphQL à grande échelle avec Apollo Federation et performance.

## Quand l'utiliser
- Conception de schéma GraphQL (types, queries, mutations, subscriptions)
- Architecture de microservices avec Apollo Federation
- Résolution du problème N+1 avec DataLoader
- Sécurité GraphQL (depth limiting, rate limiting, auth)
- Optimisation de performance (persisted queries, caching)
- Migration de REST vers GraphQL

## Compétences clés
- **Schema Design** : Types, interfaces, unions, enums, directives, custom scalars
- **Federation** : Apollo Federation v2, entities, @key, @requires, @provides
- **DataLoader** : Batching, caching, N+1 resolution, per-request instances
- **Caching** : Cache-control, persisted queries, CDN, server-side cache
- **Security** : Depth limiting, rate limiting, query allowlisting, auth directives
- **Performance** : Tracing, Apollo Studio, query complexity, field-level performance

## Workflow typique
1. Analyser les besoins en données et les consumers
2. Concevoir le schéma GraphQL (queries, mutations, subscriptions)
3. Implémenter les resolvers avec DataLoader
4. Configurer la fédération si architecture microservices
5. Ajouter la sécurité (auth, depth, rate limiting)
6. Optimiser la performance (caching, persisted queries)
7. Monitorer avec Apollo Studio ou équivalent

## Pièges connus
- Problème N+1 sans DataLoader
- Over-fetching par design (schéma trop granulaire)
- Federation avec entities mal définies (@key)
- Pas de depth limiting (attaques par requêtes profondes)
- Ignorer le cache au niveau HTTP (Cache-Control)

## Connexions Knowledge Graph
- **agent-rest-api-specialist** → API REST vs GraphQL
- **agent-microservice-architect-v2** → Architecture microservices
- **agent-caching-specialist-v2** → Stratégies de cache
- **agent-security-auditor-v3** → Sécurité API

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…