Add Wear Os App logo

Add Wear Os App

Community
khadinakbarlabs
add-wear-os-app

Add a Wear OS companion app (Compose for Wear). Always native Kotlin - RN doesn't run on Wear. Use when the user says 'wear os app', 'android watch app', 'wearable companion'.

Overview

Publisherkhadinakbarlabs
Repositoryexpo-mobile-app-builder
Skill nameadd-wear-os-app
Stars
3
Forks
0
Bundled files
1
LicenseMIT
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.

  • 1 bundled files

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

  • Open source

    Published by khadinakbarlabs on GitHub. Read the source before you install it.

Installation

Install the Add Wear Os App 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/khadinakbarlabs/expo-mobile-app-builder/tree/main/skills/add-wear-os-app
  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/khadinakbarlabs/expo-mobile-app-builder.git /tmp/expo-mobile-app-builder
mkdir -p .claude/skills
cp -r /tmp/expo-mobile-app-builder/skills/add-wear-os-app .claude/skills/add-wear-os-app
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Add Wear Os App 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 Add Wear Os App 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 Add Wear Os App 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.

Add Wear OS App

Wear OS 5 (current 2026). Compose for Wear is the only viable UI.

Reality

  • Wear OS app = separate Compose module, not RN
  • Pair with main app via Wearable Data Layer API
  • Build separately in wear/ directory in your repo
  • Submit as separate Play Store entry OR bundled

When to build

  • Activity tracking (fitness, sleep)
  • Notifications + replies on wrist
  • Quick logging (habit, tasks, mood)
  • Glanceable data (counter, streak, next workout)

When NOT to build

  • Casual content consumption
  • Anything text-heavy
  • One-off feature (low ROI — small Wear user base)

Project setup

Open Android Studio → New → Wear OS module in your existing project.

android/
  app/             # Phone app
  wear/            # Wear OS app

Build with Gradle:

bash
cd android
./gradlew :wear:assembleRelease

Compose for Wear

kotlin
// MainActivity.kt
@Composable
fun MainScreen() {
  ScalingLazyColumn {
    item { Text("Today's streak") }
    item { Card { Text("7 days") } }
    item { Chip(onClick = { logHabit() }, label = { Text("Log it") }) }
  }
}

Data Layer (sync from phone)

kotlin
// Send data from phone:
Wearable.getDataClient(context).putDataItem(...)

// Receive on watch:
class WearListener : WearableListenerService() {
  override fun onDataChanged(events: DataEventBuffer) { ... }
}

Health permissions (if fitness-related)

  • ACTIVITY_RECOGNITION
  • BODY_SENSORS
  • Permissions checked separately on watch

Common gotchas

  • Wear emulator is slow → test on real Wear device
  • Battery is brutal — limit background work
  • No web view, no RN — Kotlin only
  • Wear apps can submit separately or as embedded in phone app's APK
  • Battery-conscious UI: dark backgrounds, no animations

Build constraint

This skill is for if the user is OK dropping to Kotlin. Otherwise: skip Wear OS for MVP, add post-launch if data shows demand.

Pair with

  • add-gemini-nano (Wear devices don't support, so skip)
  • set-up-eas-android (Wear is a separate Gradle task)

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 Add Wear Os App AI skill do?

Add a Wear OS companion app (Compose for Wear). Always native Kotlin - RN doesn't run on Wear. Use when the user says 'wear os app', 'android watch app', 'wearable companion'.

Why use Add Wear Os App on TypingMind?

Because you install it once and use it with any model. Add Wear Os App 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 Add Wear Os App in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/khadinakbarlabs/expo-mobile-app-builder/tree/main/skills/add-wear-os-app. 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 Add Wear Os App?

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 Add Wear Os App?

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

Is the Add Wear Os App AI skill free?

Yes. It is published on GitHub by khadinakbarlabs under the MIT 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 👇