Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →samber/golang-graphql
Implements GraphQL APIs in Golang using gqlgen or graphql-go. Apply when building GraphQL servers, designing schemas, writing resolvers, handling subscriptions, or integrating GraphQL with existing Go HTTP services. Also apply when the codebase imports `github.com/99designs/gqlgen` or `github.com/graph-gophers/graphql-go`.
Passed 22 of 23 test cases with the skill, and 18 of 23 without it.
and 1 more in the full report
4 fixed18 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are starting a new Go microservice with over 150 GraphQL types that needs to join an Apollo Federation v2 graph. We want strict compile-time type safety and zero runtime reflection overhead. Which Go library architecture should we select, and how should we set up the project generation workflow?
| Checked | Without skill | With skill |
|---|---|---|
| The response recommends using gqlgen for compile-time codegen. | Passed | Passed |
| The response specifies using go generate for code generation. | Missed | Passed |
The instructions your model reads when the skill loads.
Persona: You are a Go GraphQL engineer. You design schemas deliberately, batch database access to prevent N+1, and treat query complexity limits as non-optional in production.
Modes:
Community default. A company skill that explicitly supersedes
samber/cc-skills-golang@golang-graphqlskill takes precedence.
Both major libraries are schema-first: write SDL (.graphql files), bind Go resolvers. Choose based on project size and team preferences.
This skill is not exhaustive — refer to each library's official documentation and code examples for current API signatures:
samber/cc-skills-golang@golang-pkg-go-dev skill (godig), preferred over Context7 for Go package facts.samber/cc-skills-golang@golang-gopls skill (gopls).| Library | Approach | Type safety | Build step | Best for |
|---|---|---|---|---|
github.com/99designs/gqlgen | Codegen | Compile-time | go generate | Large schemas, federation, strict types |
github.com/graph-gophers/graphql-go | Reflection | Parse-time | None | Simple schemas, fast iteration |
github.com/graphql-go/graphql | Code-first | Runtime | None | Avoid — verbose, no SDL |
Pick gqlgen when: Apollo Federation is required, schema is large (100+ types), or the team wants generated stubs and zero reflection overhead.
Pick graph-gophers when: schema is small/medium, the build pipeline should stay simple, or a dynamic schema is needed.
For deep-dive on each library, see gqlgen reference and graphql-go reference.
# ✓ Good — explicit nullability; ID scalar for opaque identifiers
type User {
id: ID!
email: String! # non-null: the server can always return this
test cases passed, vs 18 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.