Litert Lm logo

Litert Lm

Organization
google-ai-edge
litert-lm

Creates an Android app that runs an open text LLM on the device, on the CPU or the GPU, with the LiteRT-LM Kotlin API. LiteRT-LM is the recommended replacement for the MediaPipe LLM Inference API (com.google.mediapipe:tasks-genai), which is in maintenance-only mode. Use this skill to build a new chat, summarization or extraction app with a .litertlm model from Hugging Face litert-community (Gemma, Qwen, Llama, Phi) - the dependency and manifest entries, getting the model file onto the device, engine initialization, a streamed multi-turn conversation, the ViewModel and screen.

Overview

Publishergoogle-ai-edge
Repositorylitert-samples
Skill namelitert-lm
Stars
470
Forks
124
Bundled files
2
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by google-ai-edge on GitHub. Read the source before you install it.

Installation

Install the Litert Lm AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/google-ai-edge/litert-samples/tree/main/skills/litert-lm
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/google-ai-edge/litert-samples.git /tmp/litert-samples
mkdir -p .claude/skills
cp -r /tmp/litert-samples/skills/litert-lm .claude/skills/litert-lm
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Litert Lm in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Litert Lm on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Litert Lm is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

This skill provides step-by-step guidance for building an Android app that runs an open text LLM through the LiteRT-LM Kotlin API (com.google.ai.edge.litertlm; guide: https://ai.google.dev/edge/litert-lm/android, sources: https://github.com/google-ai-edge/LiteRT-LM/blob/main/README.md) on the CPU or the GPU. The model is one .litertlm file. Images, audio, tool calling and NPU backends are not covered. For vision and audio models, use the litert-runtime skill: https://github.com/google-ai-edge/litert-samples/blob/main/skills/litert-runtime/SKILL.md (LiteRT: https://github.com/google-ai-edge/litert/blob/main/README.md).

Prerequisites

  • A Kotlin Android project (Android Studio's Empty Activity template is enough). The litertlm-android 0.18.0 AAR declares minSdk 24.
  • The dependency in the app-level build.gradle.kts: implementation("com.google.ai.edge.litertlm:litertlm-android:0.18.0") from Google Maven, which lists the newer releases.
  • For the GPU backend, both lines inside <application> in AndroidManifest.xml, and <uses-permission android:name="android.permission.INTERNET"/> if the app downloads the model:
xml
<uses-native-library android:name="libvndksupport.so" android:required="false"/>
<uses-native-library android:name="libOpenCL.so" android:required="false"/>
  • The model file lives on the device's filesystem (hundreds of MB to a few GB), never in assets or in the APK.

Detailed steps

1. Pick a model from litert-community

Choose a .litertlm file at https://huggingface.co/litert-community. Start with litert-community/gemma-4-E2B-it-litert-lm (the file gemma-4-E2B-it.litertlm, 2.6 GB) or the smaller litert-community/Qwen3-0.6B (Qwen3-0.6B.litertlm, 0.6 GB); both files run on the CPU and the GPU. A SoC suffix such as _Google_Tensor_G5 or .mediatek.mt6993 marks an NPU build (not covered here). The model card names the tested backends and the size. Converting a model yourself is a separate step: get a model.

To check a file on a Mac before it goes on the phone, run it with the LiteRT-LM version the app uses: uvx litert-lm@0.18.0 run --from-huggingface-repo=litert-community/Qwen3-0.6B Qwen3-0.6B.litertlm --prompt="What is the capital of France?" (needs uv). Keep the version in the command: with litert-lm 0.17.0, the same command answers a different question and still exits with 0.

2. Put the model file on the device

For the first run, copy the file into the app's private storage with adb: adb push model.litertlm /data/local/tmp/, then adb shell run-as <package> cp /data/local/tmp/model.litertlm files/ (a debuggable build). For users, download it inside the app, with your HTTP client into filesDir or with DownloadManager into getExternalFilesDir(null) (it cannot write to internal storage), show the progress, and check the size against the model card before loading. The engine takes the absolute path.

3. Initialize the engine off the main thread

Engine(config).initialize(), with EngineConfig(modelPath = …, backend = …, cacheDir = …) as below, loads the weights and blocks for seconds, so it runs on a background thread. Backend.CPU(), the default of EngineConfig, needs nothing from the device; Backend.GPU() needs the two manifest lines: without them the engine initializes, and the first reply ends in the error Can not find OpenCL library on this device. cacheDir speeds up the second load. Engine and Conversation are AutoCloseable. A second close() on either throws IllegalStateException, and so does close() on an engine whose initialize() threw: that engine holds nothing, so the code below stores it only after initialize() returns.

4. Conversation, streaming and the screen

kotlin
data class ChatState(val ready: Boolean = false, val busy: Boolean = false, val reply: String = "", val error: String? = null)

class ChatViewModel(app: Application) : AndroidViewModel(app) {
    private val executor = Executors.newSingleThreadExecutor()
    private val scope = CoroutineScope(SupervisorJob() + executor.asCoroutineDispatcher())
    private val mutex = Mutex()
    private var engine: Engine? = null
    private var conversation: Conversation? = null
    private val _state = MutableStateFlow(ChatState())
    val state: StateFlow<ChatState> = _state.asStateFlow()

    fun load(modelPath: String, backend: Backend = Backend.CPU()) {
        scope.launch {
            mutex.withLock {
                if (engine?.engineConfig?.modelPath == modelPath) return@launch
                release()
                try {
                    val config = EngineConfig(modelPath = modelPath, backend = backend, cacheDir = getApplication<Application>().cacheDir.path)
                    engine = Engine(config).also { it.initialize() }
                    conversation = checkNotNull(engine).createConversation(ConversationConfig(systemInstruction = Contents.of("You are a helpful assistant.")))
                    _state.value = ChatState(ready = true)
                } catch (e: Exception) {
                    release()
                    _state.value = ChatState(error = e.message)
                }
            }
        }
    }

    fun send(text: String) {
        scope.launch {
            if (!_state.value.ready || _state.value.busy) return@launch
            _state.update { it.copy(busy = true, reply = "", error = null) }
            try {
                checkNotNull(conversation).sendMessageAsync(text).collect { message -> _state.update { it.copy(reply = it.reply + message) } }
            } catch (e: CancellationException) {
                throw e
            } catch (e: Exception) {
                _state.update { it.copy(error = e.message) }
            } finally {
                _state.update { it.copy(busy = false) }
            }
        }
    }

    private suspend fun release() {
        _state.update { it.copy(ready = false) }
        while (_state.value.busy) {
            conversation?.cancelProcess()
            delay(100)
        }
        conversation?.close()
        conversation = null
        engine?.close()
        engine = null
        _state.value = ChatState()
    }

    override fun onCleared() {
        scope.launch {
            mutex.withLock { release() }
            executor.shutdown()
        }.invokeOnCompletion { scope.cancel() }
    }
}

sendMessageAsync(text) returns a Flow<Message> of chunks (toString() gives a chunk's text); sendMessage(text) blocks and returns the whole reply. The conversation keeps its history, so the next send() continues the chat, and busy keeps the button disabled until the flow completes. SamplerConfig(topK = 10, topP = 0.95, temperature = 0.8) in ConversationConfig sets the sampling (all three are required; topP and temperature are Double). load() with the model path that is already loaded does nothing, whatever backend it asks for, so the screen can call it again after a rotation, also once the app has fallen back to another backend; send() runs only when the state is ready and not busy (the button's own test): a tap that lands while release() is stopping a reply does nothing, and one queued behind a load() reaches the model that load() loaded when no reply was streaming. The screen (viewModel() and collectAsStateWithLifecycle() come from androidx.lifecycle:lifecycle-viewmodel-compose and androidx.lifecycle:lifecycle-runtime-compose, 2.10.0; every import the code blocks need is listed in imports):

kotlin
@Composable
fun ChatScreen(modelPath: String, viewModel: ChatViewModel = viewModel()) {
    val state by viewModel.state.collectAsStateWithLifecycle()
    var input by remember { mutableStateOf("") }
    LaunchedEffect(modelPath) { viewModel.load(modelPath, Backend.GPU()) }
    Column {
        Text(state.reply, Modifier.weight(1f).verticalScroll(rememberScrollState()))
        state.error?.let { Text(it) }
        TextField(value = input, onValueChange = { input = it })
        Button(onClick = { viewModel.send(input); input = "" }, enabled = state.ready && !state.busy) { Text("Send") }
    }
}

5. Lifecycle

  • Keep the engine in the ViewModel for as long as its screen lives, or in an application-scoped holder when several screens share it. The ViewModel keeps its own thread and scope: viewModelScope is cancelled before onCleared() runs, so a close launched there would not run, and onCleared() cancels the scope once the close is done. release() turns ready off, calls cancelProcess() until the streaming reply's flow has ended (at the latest when the reply ends on its own), then closes the conversation and the engine, each once; onCleared() and a load() that replaces the model both go through it under the Mutex, one at a time, because release() suspends while a reply stops.
  • Create a new conversation to start a fresh chat. The reference app for this API is Google AI Edge Gallery: https://github.com/google-ai-edge/gallery/blob/main/README.md

Troubleshooting

  • First reply is slow: initialize() ran on first use; load at app start and set cacheDir.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Litert Lm AI skill do?

Creates an Android app that runs an open text LLM on the device, on the CPU or the GPU, with the LiteRT-LM Kotlin API. LiteRT-LM is the recommended replacement for the MediaPipe LLM Inference API (com.google.mediapipe:tasks-genai), which is in maintenance-only mode. Use this skill to build a new chat, summarization or extraction app with a .litertlm model from Hugging Face litert-community (Gemma, Qwen, Llama, Phi) - the dependency and manifest entries, getting the model file onto the device, engine initialization, a streamed multi-turn conversation, the ViewModel and screen.

Why use Litert Lm on TypingMind?

Because you install it once and use it with any model. Litert Lm is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Litert Lm in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/google-ai-edge/litert-samples/tree/main/skills/litert-lm. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Litert Lm?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Litert Lm?

As many as you like. As long as a model supports skills, you can use Litert Lm with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Litert Lm AI skill free?

Yes. It is published on GitHub by google-ai-edge under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇