graphql-mutation-builder
Build graphql mutation builder operations. Auto-activating skill for API Development. Triggers on: graphql mutation builder, graphql mutation builder Part of the API Development skill category. Use when working with graphql mutation builder functionality. Trigger with phrases like "graphql mutation builder", "graphql builder", "graphql". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill graphql-mutation-builder --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Graphql Mutation Builder ## Overview This skill provides automated assistance for graphql mutation builder tasks within the API Development domain. ## When to Use This skill activates automatically when you: - Mention "graphql mutation builder" in your request - Ask about graphql mutation builder patterns or best practices - Need help with api development skills covering rest, graphql, openapi,
What does the graphql-mutation-builder skill do?
Build graphql mutation builder operations. Auto-activating skill for API Development. Triggers on: graphql mutation builder, graphql mutation builder Part of the API Development skill category. Use when working with graphql mutation builder functionality. Trigger with phrases like "graphql mutation builder", "graphql builder", "graphql". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill graphql-mutation-builder --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.