agentleFS
saleorsaleor/saleor-dashboard/.claude/skills/saleor-dashboard-graphql-batching/SKILL.md

saleor-dashboard-graphql-batching

Skill1.1k starsChanged 8 days agoBSD-3-ClauseView on GitHub

Saleor API request limits for batched GraphQL documents. Use when sending several aliased mutations or queries in one request, building GraphQL documents at runtime, or choosing a chunk size for bulk assign/unassign/update loops.

Trending

Less talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 3 mentionsMar 2026: 5 mentionsApr 2026: 0 mentionsMay 2026: 1 mentionJun 2026: 33 mentionsJul 2026: 3 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 2 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the saleor/saleor-dashboard repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about saleor/saleor-dashboard

The biggest 5 of 50 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 50

Talked about on GitHub (50 times).

On GitHub · 50

45 more on GitHub

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep aliased queries well under 100 aliases per document, counting nested aliases.

    line 27
  2. Very specific:

    Use errorPolicy: "all" and treat a missing alias in data as a failure, so a rejected document reports every entity in that chunk as failed.

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Batched GraphQL requests

Saleor validates every document against per-request limits before running it. Over a limit, the whole request fails with a top-level error and data: null; no part of it runs.

LimitDefaultEnv varWhat counts
Mutations4GRAPHQL_MUTATION_COUNT_LIMITTop-level fields of every mutation operation in the document, aliased or not
Aliases100GRAPHQL_ALIAS_COUNT_LIMITEvery aliased field anywhere in the document, nested ones included
Query complexity50000GRAPHQL_QUERY_MAX_COMPLEXITYCost of the whole document

Source: saleor/graphql/core/validators/ and saleor/settings.py in Saleor core.

Rules

  • Chunk aliased mutations at 4 or fewer per document. Do not assume an instance raised the limit; test instances often use 10, which hides the bug locally.
  • Keep aliased queries well under 100 aliases per document, counting nested aliases.
  • Name the chunk size as a constant with a comment citing the limit, and cover it with a unit test.
  • Use errorPolicy: "all" and treat a missing alias in data as a failure, so a rejected document reports every entity in that chunk as failed.

See runWarehouseLinkUpdates in src/warehouses/warehouseChannelMembership.ts for an example: it chunks by MEMBERSHIP_UPDATE_CHUNK_SIZE and marks a rejected chunk as failed.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.