graphql
Skill2 starsChanged 4 months agoMITView on GitHub
Write, explain, or optimize a GraphQL operation or schema — queries, mutations, fragments, resolvers — with attention to the real schema, over-fetching, and the N+1 problem. Use when the user says "write a GraphQL query", "explain this query", "why is this resolver slow", "design a GraphQL schema", "fix N+1 in resolvers", or pastes an operation and asks what it does.
25 other projects use a version of this.
Adopted by
Most recently taken up by
- AtilaMedeiros/skillstheir own version, first seen Nov 16, 2026
- stu1612/basketball-sitetheir own version, first seen Nov 16, 2026
- Ivan-propio/claude-skillstheir own version, first seen Nov 16, 2026
- TheBeardedBearSAS/claude-crafttheir own version, first seen Nov 11, 2026
- mahumadad/quarrytheir own version, first seen Nov 8, 2026
- SubhiSec/claude-ai-cyber-security-skillstheir own version, first seen Oct 25, 2026
Used with
Projects with it also use oauth-oidc, ssti and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
SubhiSecSkilloauth-oidc
Hunt OAuth 2.0 and OIDC flaws — redirect_uri abuse, state CSRF, PKCE bypass, scope manipulation, implicit-flow token theft, postMessage origin tricks, ID token sub claim swap, JWKS confusion, response_type confusion, and OAuth-CSRF. Use when an app has Google/GitHub/Facebook/Apple/custom OAuth or OpenID Connect.
Also in 3 projects that use this
SubhiSecSkillssti
Hunt Server-Side Template Injection (SSTI) in Jinja2, Twig, Freemarker, Velocity, Smarty, ERB, Handlebars, Mustache, and Spring (SpEL). Use when input is reflected in a way that suggests template rendering — error pages, email templates, PDF generators, dynamic content systems.
Also in 5 projects that use this
blacklanternsecuritySkillssrf
Guide server-side request forgery (SSRF) exploitation during authorized penetration testing.
Also in 5 projects that use this
blacklanternsecuritySkilljwt-attacks
Exploit JWT (JSON Web Token) vulnerabilities during authorized penetration testing.
Also in 3 projects that use this
zebbernSkillsubdomain-enum
Enumerate subdomains for a target domain using passive and active reconnaissance techniques. Use when starting reconnaissance on a new target, when you need to discover the attack surface, when expanding scope from a root domain, or when the user provides a domain to investigate.
Also in 3 projects that use this
iAskShahramSkillfile-upload
Uploads a local file to Cloudflare R2 bucket `public` with wrangler and returns the public URL on assets.shahram.dev. Use when the user wants a public link, public URL, or to host/upload a local image or file to R2.
Also in 4 projects that use this
- +3 more from SubhiSec
- +1 more from blacklanternsecurity
Other versions25 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 25
- ParabolInc/parabol★ 2ksame name
- Mindrally/skills★ 275same name
- kid-sid/claude-spellbook★ 190same name
- TheBeardedBearSAS/claude-craft★ 108same name
- SubhiSec/claude-ai-cyber-security-skills★ 45same name
- 0xGhostCAT/claude-ai-cyber-security-skills★ 41same name
- nimadorostkar/Claude-Skills-collection★ 37same name
- G1Joshi/Agent-Skills★ 15same name
- crowdin/skills★ 10same name
- xfstudio/skills★ 9same name
15 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository68 other files it gives its agents.
- a11ySkill
- api-docsSkill
- audit-logSkill
- benchmarkSkill
- bisectSkill
- cacheSkill
- changelogSkill
- cherry-pickSkill
- ci-setupSkill
- codeownersSkill
- commit-messageSkill
- connection-poolSkill
- contributingSkill
- coverageSkill
- db-migrateSkill
- dead-codeSkill
- debugSkill
- depsSkill
- diagramSkill
- dockerizeSkill
- docstringSkill
- e2eSkill
- env-exampleSkill
- error-handlingSkill
- explainSkill
- feature-flagSkill
- flaky-testSkill
- gitignoreSkill
- graceful-shutdownSkill
- healthcheckSkill
- i18nSkill
- idempotencySkill
- licenseSkill
- lint-fixSkill
- loggingSkill
- migrateSkill
- mockSkill
- onboardSkill
- optimizeSkill
- paginationSkill
- pr-descriptionSkill
- pre-commitSkill
- profileSkill
- prune-branchesSkill
- rate-limitSkill
- readmeSkill
- rebaseSkill
- refactorSkill
- regexSkill
- releaseSkill
- resolve-conflictsSkill
- retrySkill
- review-diffSkill
- scaffoldSkill
- secrets-scanSkill
- security-headersSkill
- seedSkill
- soft-deleteSkill
- sqlSkill
- squashSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 20 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 26
Call out the assumption about schema shape and how variables are supplied.
- Distinctive: line 40
Never guess at schema field/type names silently — verify against the SDL/type defs or state the assumption.
- Distinctive: line 42
Treat the N+1 resolver problem as the default suspect for slow list queries — don't optimize blindly without naming the batching fix.
“Common” is measured: kept by at least 6 in 10 of the 20 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Schema & resolver hints
!find . -type d \( -name node_modules -o -name .git -o -name dist -o -name build \) -prune -o -type f \( -iname '*.graphql' -o -iname '*.gql' -o -iname 'schema.*' -o -iname '*resolver*' -o -iname '*typedefs*' \) -print 2>/dev/null | head -20
Instructions
Handle the GraphQL request in $ARGUMENTS. It's one of: write an operation/schema from a description, explain a given operation, or optimize a slow query/resolver. If unclear, ask which.
Determine the schema first
- Find the real schema (SDL
.graphqlfiles, code-first type defs, or introspection) and use actual type, field, and argument names. Don't invent fields; if the schema is unknown, state your assumptions explicitly. - Note the server/framework (Apollo, GraphQL Yoga, Nexus, graphql-ruby, Strawberry, Hasura) since resolver patterns and tooling differ.
Writing an operation or schema
- Produce a valid operation: a named operation, typed
$variables(not inline literals), only the fields actually needed, and fragments for reused selections. - For schema design: model nullability deliberately, use enums/interfaces/unions where they fit, follow connection/edge pagination conventions for lists, and keep mutations returning the affected object (and a payload type) rather than a bare scalar.
- Call out the assumption about schema shape and how variables are supplied.
Explaining an operation
Walk the selection set from the root field outward: what each field, argument, fragment, and directive resolves to, and what the response shape looks like. Flag surprises — deeply nested selections that fan out, fields with side-effectful resolvers, or aliases that mask multiple calls to the same field.
Optimizing
- Identify the likely cost: N+1 resolvers (the classic — a list field whose item resolver hits the DB per element), over-fetching deep nested selections, missing pagination, or unbounded query depth/complexity.
- Recommend concrete fixes: a DataLoader/batch-load to collapse N+1, pagination on list fields, query depth/complexity limits, projecting only requested fields to the data source, and caching where appropriate. Show the improved operation or resolver sketch.
- Suggest measuring with the server's tracing/
extensionstiming to confirm the win.
Rules
- Never guess at schema field/type names silently — verify against the SDL/type defs or state the assumption.
- Validate operations against the schema's nullability and argument types; flag a selection that wouldn't type-check.
- Treat the N+1 resolver problem as the default suspect for slow list queries — don't optimize blindly without naming the batching fix.
- Watch security/cost: recommend depth/complexity limits and pagination for any client-facing schema, and don't expose unbounded list fields without them.
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
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.

