integrate-agentforce-android
Installation
SKILL.md
integrate-agentforce-android
This skill walks a consumer through wiring the Agentforce Mobile SDK into their Android app. It is interactive — ask the user the questions in each phase before generating code. Don't assume; the wrong auth flow is the most common integration mistake.
Operating rules
- Run inside the consumer's project, not inside the SDK repo. If the working directory contains
agentforce-sdk/oragentforce-service/Gradle modules at the root, refuse and tell the user tocdinto their app first. - Discover before deciding. Always run Phase 1 (use-case discovery) before recommending an auth flow. Don't ask "which auth flow do you want?" — most consumers don't know.
- Don't suggest
Guest(url)orOrgJWTby default. They're only correct in specific situations. Recommend the path that matches the user's described use case. - Hold the
AgentforceClientfor the conversation's lifetime. Stash it in your Application or a long-lived ViewModel; if it's recreated mid-chat the conversation is lost. - Default to the latest stable public release. Use
15.130.4(Agentforce Mobile 262.1.3) for both core and voice unless the project already pins another compatible version. Keep all Agentforce artifacts on exactly the same version. - Match the project's Kotlin/Compose toolchain. On Kotlin 2.x, apply
org.jetbrains.kotlin.plugin.composeat the same Kotlin version. On Kotlin 1.9.x, preserve the compatible legacy Compose compiler configuration instead of adding the Kotlin 2.x plugin. - Use
AskUserQuestionfor branching choices. Don't free-text prompts — give 2–4 explicit options. - Substitute placeholders, don't leave
{{TOKENS}}in the final files. Collect values up front; if the user can't provide a value, leave a clearly-marked// TODO:comment instead.
Phase 0 — Detect the target project
Look in the current working directory for: