Apollo Kotlin

What it does

This workflow links Gradle configuration, schema acquisition, operation generation and client behavior. It covers authentication, interceptors and caching while recognizing that Android and multiplatform projects have different build and source-set boundaries. That makes project discovery a necessary first step rather than an optional setup detail.

Best for

Kotlin teams adding typed GraphQL operations or maintaining an existing generated client integration.

Tradeoffs and requirements

The compatible Gradle, Kotlin and Apollo versions must be checked together. A successful code-generation task can still target an outdated schema, and a shared multiplatform interface does not prove that every platform implementation handles storage or authentication correctly.

JVM 8+, Kotlin 1.9+, Gradle 8+, Android/JVM/Kotlin Multiplatform projects.

Install from the source

Inspect the pinned source snapshot and its supporting files first. The command selects this skill through the open-source skills CLI. Node.js and agent-specific setup may be required. Installation can download code. Catalog ingestion never executes skill instructions or install scripts.

npx skills add https://github.com/apollographql/skills/tree/9dda1397730370aeb8df4ff8f2015c34c86b5003/skills/apollo-kotlin --skill apollo-kotlin

Review pinned skill folder ↗ · CLI documentation ↗

After source review, use npx skills check and npx skills update to inspect and apply upstream updates. Re-check changed instructions before running them.

Safety & review signals

Static review only. This is not a security audit or a guarantee of safety.

SKILL.md text only; scripts, dependencies and runtime behavior not audited.

No configured text patterns matched. Unmatched or concealed behavior can still exist.

Allowed tools declaration: Bash(./gradlew:*) Bash(gradle:*) Bash(curl:*) Read Write Edit Glob Grep WebFetch. Runtime permissions and network behavior: Unknown.

AI Craft Pad Skill Score

84/100 · Metadata coverage 100% · Model 1.0

Scores summarize observable discovery signals. Popularity and repository activity apply to the whole repository. Unknown runtime safety earns no certification.

Documentation

94/100

94

Maintenance

100/100

100

License Clarity

100/100

100

Repository Health

100/100

100

Compatibility Evidence

80/100

80

Popularity

38/100

38

Originality

80/100

80

Static Safety

60/100

60

Suggested workflow

Inspect plugins and source sets, identify the GraphQL service and configure a reproducible schema input. Generate a small operation, route credentials through the existing client configuration and define the expected cache behavior before adding more complex mutations or subscriptions.

How to judge the result

Run generation and relevant platform builds, then exercise malformed responses, missing optional fields and authentication changes. Check generated artifacts into the repository only if that matches its policy, and record which targets were actually built or tested.