Skip to content
Back to skills

Graphql Schema

ASecurity

Generates or reviews a GraphQL schema with types, queries, mutations, and resolvers

  • 10 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added June 1, 2026
ai-agentsbash

Security analysis

A100/100

Scanned June 1, 2026

npx -y skills add berkcangumusisik/claude-code-practices --skill graphql-schema --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Graphql Schema?

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

Security grade badge for Graphql Schema
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/berkcangumusisik-graphql-schema/badge)](https://www.skillsdirectory.com/skills/berkcangumusisik-graphql-schema)

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: graphql-schema
description: Generates or reviews a GraphQL schema with types, queries, mutations, and resolvers
argument-hint: <entity-or-review>
user-invocable: true
allowed-tools: Read Glob Edit Grep
effort: medium
---

## GraphQL Schema

Target: **$ARGUMENTS**

1. Detect GraphQL setup:
```bash
cat package.json | grep -E '"graphql"|"apollo-server"|"pothos"|"nexus"|"typegraphql"|"@graphql-yoga"'
ls src/graphql/ src/schema/ 2>/dev/null | head -10
```

2. If reviewing existing schema:
   - N+1 problem: resolvers fetching data per parent field
   - Missing `DataLoader` for batched queries
   - Over-exposed fields (internal IDs, timestamps that shouldn't be public)
   - Missing pagination (connections pattern)
   - Mutations not returning the updated entity

3. If generating new schema for `$ARGUMENTS`:

```graphql
type $ARGUMENTS {
  id: ID!
  # ... fields
  createdAt: DateTime!
  updatedAt: DateTime!
}

type Query {
  $ARGUMENTS(id: ID!): $ARGUMENTS
  ${ARGUMENTS}s(first: Int, after: String, filter: ${ARGUMENTS}Filter): ${ARGUMENTS}Connection!
}

type Mutation {
  create$ARGUMENTS(input: Create${ARGUMENTS}Input!): ${ARGUMENTS}MutationResult!
  update$ARGUMENTS(id: ID!, input: Update${ARGUMENTS}Input!): ${ARGUMENTS}MutationResult!
  delete$ARGUMENTS(id: ID!): Boolean!
}
```

4. Generate resolver stubs and DataLoader for the entity.

5. Add input validation and proper error types.

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…