Skip to content
Back to skills

Add Gemini Nano

ASecurity

Plan a privacy-aware Android on-device AI integration using verified ML Kit GenAI APIs and explicit availability checks. Use for Gemini Nano, offline Android AI, or on-device inference.

  • 3 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 4, 2026
developmentgokotlinapibackenddocumentation

Works with

  • api

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned October 4, 2026

npx -y skills add khadinakbarlabs/expo-mobile-app-builder --skill add-gemini-nano --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Add Gemini Nano?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Add Gemini Nano
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/khadinakbarlabs-add-gemini-nano/badge)](https://www.skillsdirectory.com/skills/khadinakbarlabs-add-gemini-nano)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: "add-gemini-nano"
description: "Plan a privacy-aware Android on-device AI integration using verified ML Kit GenAI APIs and explicit availability checks. Use for Gemini Nano, offline Android AI, or on-device inference."
---

# Add On-Device AI with Gemini Nano

Assess the app's task and device support before promising offline AI. Start with Google's official ML Kit GenAI documentation: https://developers.google.com/ml-kit/genai and the selected API's Android setup guide. Gemini Nano via AICore and downloadable MediaPipe models are distinct approaches; do not label an arbitrary local model as Gemini Nano.

## Choose an integration

Inspect the Expo SDK, native build and supported Android versions. Select an official ML Kit task API or Prompt API where currently supported, then plan a narrow Kotlin bridge through Expo Modules. Verify documented dependency versions, permissions, model availability and licensing before proposing changes. Third-party wrappers require a separate maintainer, source and compatibility review; do not automatically install an unverified package.

Check feature status using the selected API's documented runtime availability method. Handle unavailable, downloadable, downloading and available states. A phone model name alone does not prove API availability. Model downloads may require connectivity, storage and user approval; describe this before starting them.

## Privacy and fallback

Keep prompts and outputs out of diagnostics by default. Test whether the chosen integration sends telemetry or data before describing it as private. On-device processing does not remove applicable AI content, disclosure or reporting requirements.

For unsupported devices, show a useful unavailable state. A cloud fallback is a separate user choice: identify the provider and data transferred, obtain applicable consent, authenticate through a backend and enforce rate limits. Never send a prompt to the cloud automatically after a local failure. Never place provider credentials in mobile code.

## Deliver and verify

Produce an integration plan with exact dependencies, supported API states and privacy boundaries. Test supported and unsupported physical devices, denied downloads, low storage, cancellation, error handling and a network-disconnected inference after model readiness. Record measured latency and output quality without invented device coverage or speed estimates.

Pair with `play-ai-disclosure`, `add-foundation-models` and `add-openai-streaming-rn` as applicable.

Files in this skill

  • SKILL.md2.5 KB
  • agents/openai.yaml176 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…