agentsclimarketplace

Graphql

Skill kimtth/agent-skill-100-lines-or-less/skills/graphql

🧿 Minimal but effective AI agent skill definitions in 100 lines or less.

Install
npx -y skills add kimtth/agent-skill-100-lines-or-less --skill graphql

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when: design or review GraphQL schemas and resolvers with safe, efficient data access.

SKILL.md

1.0 KB, as published. Nobody here has run it

Goal: a typed GraphQL schema that is expressive and not abusable.

Use for:

  • designing schemas, types, and mutations
  • reviewing resolver efficiency and security
  • fixing N+1 queries and over-fetching risks

Workflow:

  1. Design the schema from the client's data needs.
  2. Model nullability and types precisely.
  3. Batch and cache resolver data with a dataloader pattern.
  4. Limit query depth and complexity to prevent abuse.
  5. Handle errors as typed results where it aids clients.
  6. Verify with schema tests and performance checks.

Patterns:

  • dataloaders to batch and dedupe per request
  • pagination via connections/edges
  • input types for mutations
  • persisted queries for trusted clients

Rules:

  • prevent N+1 with batching, not eager joins everywhere
  • cap query depth and complexity on public APIs
  • never expose internal errors raw to clients
  • evolve the schema additively; deprecate before removing

Gives 0 of the 12 instructions most apis services skills give

Counted across 424 of the 426 authors here whose files we hold, read 2026-08-06

  • use plural nouns for resource namesin 41 of 424, across 32 files
  • use cursor-based pagination for large datasetsin 35 of 424, across 20 files
  • include rate limit headers in responsesin 25 of 424, across 13 files
  • Use kebab-case for multi-word resourcesin 23 of 424, across 13 files
  • version APIs in the URL pathin 19 of 424, across 9 files
  • use semantic HTTP status codesin 18 of 424, across 8 files
  • verify webhook signaturesin 18 of 424, across 11 files
  • use query parameters for filteringin 17 of 424, across 6 files
  • use async database operationsin 14 of 424, across 7 files
  • wrap successful responses in a data fieldin 13 of 424, across 3 files
  • prefix sorting parameters with a hyphen for descending orderin 13 of 424, across 3 files
  • set appropriate HTTP status codesin 13 of 424, across 6 files

Said here and by no other author read

  • model nullability and types precisely
  • batch and cache resolver data
  • handle errors as typed results
  • verify with schema tests and performance checks
  • use pagination via connections and edges

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.