agentleFS
manastalukdarmanastalukdar/ai-devstudio/skills/graphql-schema/SKILL.md

graphql-schema

Skill1 starsChanged 7 months agoMITView on GitHub

GraphQL schema validation and optimization with federation support

7 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 1

    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
  1. Distinctive:

    Caching: No persistent caching — validates current schema on each run.

    line 23

“Common” is measured: kept by at least 6 in 10 of the 7 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.

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

GraphQL Schema Validation & Optimization

I'll validate and optimize your GraphQL schema with support for federation, deprecated fields, and performance improvements.

Features:

  • Schema validation and linting
  • Query optimization suggestions
  • Federation support analysis
  • Schema stitching validation
  • Deprecated field detection
  • Breaking change detection

Token Optimization

Expected range: 1,500–2,500 tokens (initial), 100 tokens (valid schema)

Caching: No persistent caching — validates current schema on each run.

Early exit: Returns immediately if the schema is already valid with no type errors.

Patterns used: Grep-before-Read, early exit, Bash for system queries

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.