GraphQL & gRPC Helper
Designs GraphQL schemas, resolvers, query/mutation/subscription patterns, and protobuf definitions for gRPC services.
- Context cost
- 1.5k tokensestimated from the bundle, loaded when it triggers
- Bundle
- 1 file · 6.0 kBtext throughout, nothing executable
- Licence
- MITpaid listing
- Last change
- —v1.0
- Servers it uses
- Noneruns standalone
What it does
Designs GraphQL schemas, resolvers, query/mutation/subscription patterns, and protobuf definitions for gRPC services. Use whenever the user asks about GraphQL, "design a GraphQL schema", "write mutations for", "GraphQL subscriptions", "DataLoader pattern", "gRPC service", "protobuf definition", "proto file", "service definition", or "when should I use GraphQL vs REST vs gRPC". Triggers on any mention of: schema definition language, SDL, resolvers, N+1 problem, federation, stitching, proto3, streaming RPC, unary RPC, or gRPC-gateway.
Installed, it changes the agent in these ways.
What this skill changes about the agent is not written down here yet. The listing was collected from its source, and the description is in its own SKILL.md.
And these are the jobs people reach for it for.
Domain judgement the base model does not have.
The skill itself
This is the whole product. A skill is instructions the model reads, so there is nothing behind the listing you cannot see first — the front matter loads with every session, and the body below it loads when the skill triggers.
Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.
What it costs in context
Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.
1.5k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Middling. Fine to keep on in a project where you use it weekly, worth unloading in one where you never do.
A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.
Before and after
The same question, put to the same model twice: once as it comes, and once with these instructions loaded.
No worked example has been published for this skill yet.
The procedure it runs
The procedure has not been published here. It is in the skill’s own SKILL.md, which its author has not sent to the marketplace yet.
These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.
Servers it uses
None. This skill calls no MCP servers at all.
Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.
It writes no files and reaches no network. All it changes is how the model reasons and writes.
Read from the allowed-tools line of this skill’s own SKILL.md. A skill grants no permissions of its own — it can only ask for tools your client already has.
What it will not do
Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.
What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.
What is in the bundle
1 file, 6.0 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.
- SKILL.md6.0 kB
No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 1 file you can review in full before installing. The MIT licence covers the templates and examples as well as the instructions.
Install
Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.
You can read the whole bundle before paying — the SKILL.md above is the product, not a preview of it. What the money buys is the delivery: the folder packaged and handed to your machine by key, every update its author ships, and our support if it does not do what this listing says. The terms of use are MIT, set by the author and unchanged by buying it here.
Payment runs through Stripe, on a page like this one rather than a redirect. Once there is an account it joins the same mcprush invoice as everything else you run, so there is never a second card to enter.
# GraphQL & gRPC Helper · 1.5k tokens when loaded
npx mcprush@latest skill add lambdatest/graphql-grpc-helperWrites to .claude/skills/graphql-grpc-helper/ in the current project. Add --global to put it in your home directory instead, for every project.
Which clients pick it up on their own
A skill is a folder of text. A client with a skills folder reads it without being told; everywhere else the same text works, it is just handed to the model rather than found.
Versions
v1.0 is what is on the shelf; no release here carries a date. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.
- No earlier releases have been published to the marketplace.
Put lambdatest/graphql-grpc-helper@1.0 in the install command to hold this exact version. Without the suffix you get whatever is current the day you install, and nothing moves under you afterwards.
Reviews
Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.
Only accounts that have had the skill installed for fourteen days, so a review is written after living with it rather than after reading it. Publishers may reply once.