EarLLM One — Build & Maintain

Overview

This public intake copy packages

plugins/antigravity-awesome-skills/skills/earllm-build

https://github.com/sickn33/antigravity-awesome-skills

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses

metadata.json

ORIGIN.md

EarLLM One — Build & Maintain

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: How It Works, Project Location, Module Dependency Graph, Modules And Key Files, Build Configuration, Target Hardware.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

• When the user mentions "earllm" or related topics
• When the user mentions "earbudllm" or related topics
• When the user mentions "earbud app" or related topics
• When the user mentions "voice pipeline kotlin" or related topics
• When the user mentions "bluetooth audio android" or related topics
• When the user mentions "sco microphone" or related topics

Operating Table

metadata.json

ORIGIN.md

SKILL.md

SKILL.md

## Related Skills

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

1. Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
2. Read the overview and provenance files before loading any copied upstream support files.
3. Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
4. Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
5. Validate the result against the upstream expectations and the evidence you can point to in the copied files.
6. Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.
7. Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify.

Imported Workflow Notes

Imported: Overview

Build, maintain, and extend the EarLLM One Android project — a Kotlin/Compose app that connects Bluetooth earbuds to an LLM via voice pipeline.

Imported: How It Works

EarLLM One is a multi-module Android app (Kotlin + Jetpack Compose) that captures voice from Bluetooth earbuds, transcribes it, sends it to an LLM, and speaks the response back.

Examples

Example 1: Ask for the upstream workflow directly

Use @earllm-build-v2 to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @earllm-build-v2 against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @earllm-build-v2 for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @earllm-build-v2 using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

• Provide clear, specific context about your project and requirements
• Review all suggestions before applying them to production code
• Combine with other complementary skills for comprehensive analysis
• Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
• Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.
• Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.
• Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate.

Imported Operating Notes

Imported: Best Practices

• Provide clear, specific context about your project and requirements
• Review all suggestions before applying them to production code
• Combine with other complementary skills for comprehensive analysis

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in

plugins/antigravity-awesome-skills/skills/earllm-build

metadata.json

ORIGIN.md

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated

SKILL.md

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

• @development-v2

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @devops-deploy-v2

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @devops-troubleshooter-v2

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @differential-review-v2

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

references

references/n/a

examples

examples/n/a

scripts

scripts/n/a

agents

agents/n/a

assets

assets/n/a

Imported Reference Notes

Imported: Stt Engine Reference

Imported: Project Location

C:\Users\renat\earbudllm

Imported: Module Dependency Graph

app ──→ voice ──→ audio ──→ core-logging
  │       │
  ├──→ bluetooth ──→ core-logging
  └──→ llm ──→ core-logging

Imported: Modules And Key Files

EarLogger.kt

PerformanceTracker.kt

BluetoothController.kt

BluetoothState.kt

BluetoothPermissions.kt

AudioRouteController.kt

VoiceCaptureController.kt

HeadsetButtonController.kt

SpeechToTextController.kt

TextToSpeechController.kt

VoicePipeline.kt

LlmClient.kt

StubLlmClient.kt

RealLlmClient.kt

SecureTokenStore.kt

MainViewModel.kt

EarLlmForegroundService.kt

Imported: Build Configuration

• SDK: minSdk 26, targetSdk 34, compileSdk 34
• Build tools: AGP 8.2.2, Kotlin 1.9.22, Gradle 8.5
• Compose BOM: 2024.02.00
• Key deps: OkHttp, AndroidX Security (EncryptedSharedPreferences), DataStore, Media

Imported: Target Hardware

Imported: Critical Technical Facts

These are verified facts from official documentation and device testing. Treat them as ground truth when making decisions:

1. Bluetooth SCO is limited to 8kHz mono input on most devices. Some support 16kHz mSBC. BLE Audio (Android 12+,

   TYPE_BLE_HEADSET = 26

   ) supports up to 32kHz stereo. Always prefer BLE Audio when available.

2. startBluetoothSco()

   is deprecated since Android 12 (API 31). Use

   AudioManager.setCommunicationDevice(AudioDeviceInfo)

   and

   clearCommunicationDevice()

   instead. The project already implements both paths in

   AudioRouteController.kt

   .

3. Samsung One UI 7/8 has a known HFP corruption bug where A2DP playback corrupts the SCO link. The app handles this with silence detection and automatic fallback to the phone's built-in mic.

4. Redmi Buds 6 Pro tap controls must be set to "Default" (Play/Pause) in the Xiaomi Earbuds companion app. If set to ANC or custom functions, events are handled internally by the earbuds and never reach Android.

5. Android 14+ requires

   FOREGROUND_SERVICE_MICROPHONE

   permission and

   foregroundServiceType="microphone"

   in the service declaration.

   RECORD_AUDIO

   must be granted before

   startForeground()

   .

6. VOICE_COMMUNICATION

   audio source enables AEC (Acoustic Echo Cancellation), which is critical to prevent TTS audio output from feeding back into the STT microphone input. Never change this source without understanding the echo implications.

7. Never play TTS (A2DP) while simultaneously recording via SCO. The correct sequence is: stop playback → switch to HFP → record → switch to A2DP → play response.

Imported: Data Flow

Headset button tap
  → MediaSession (HeadsetButtonController)
  → TapAction.RECORD_TOGGLE
  → VoicePipeline.toggleRecording()
  → VoiceCaptureController captures PCM (16kHz mono)
  → stopRecording() returns ByteArray
  → SpeechToTextController.transcribe(pcmData)
  → LlmClient.chat(messages)
  → TextToSpeechController.speak(response)
  → Audio output via A2DP to earbuds

Imported: Adding A New Feature

1. Identify which module(s) are affected
2. Read existing code in those modules first
3. Follow the StateFlow pattern — expose state via

   MutableStateFlow

   /

   StateFlow

4. Update

   MainViewModel.kt

   if the feature needs UI integration
5. Add unit tests in the module's

   src/test/

   directory
6. Update docs if the feature changes behavior

Imported: Modifying Audio Capture

• VoiceCaptureController.kt

  handles PCM recording at 16kHz mono
• WAV headers use hex byte values (not char literals) to avoid shell quoting issues
• VU meter: RMS calculation → dB conversion → normalized 0-1 range
• Buffer size:

  getMinBufferSize().coerceAtLeast(4096)

Imported: Changing Bluetooth Behavior

• BluetoothController.kt

  manages discovery, pairing, profile proxies
• Earbuds detection uses name heuristics: "buds", "earbuds", "tws", "pods", "ear"
• Always handle both Bluetooth Classic and BLE Audio paths

Imported: Modifying The Llm Integration

• LlmClient.kt

  defines the interface — keep it generic

• StubLlmClient.kt

  for offline testing (500ms simulated delay)

• RealLlmClient.kt

  uses OkHttp to call OpenAI-compatible APIs
• API keys stored in

  SecureTokenStore.kt

  (EncryptedSharedPreferences)

Imported: Generating A Build Artifact

After code changes, regenerate the ZIP:

#### Imported: From Project Root

powershell -Command "Remove-Item 'EarLLM_One_v1.0.zip' -Force -ErrorAction SilentlyContinue; Compress-Archive -Path (Get-ChildItem -Exclude '*.zip','_zip_verify','.git') -DestinationPath 'EarLLM_One_v1.0.zip' -Force"

Imported: Running Tests

./gradlew test --stacktrace          # Unit tests
./gradlew connectedAndroidTest       # Instrumented tests (device required)

Imported: Phase 2 Roadmap

• Real-time streaming voice conversation with LLM through earbuds
• Smart assistant: categorize speech into meetings, shopping lists, memos, emails
• Vosk offline STT integration (currently stubbed)
• Wake-word detection to avoid keeping SCO open continuously
• Streaming TTS (Android built-in TTS does NOT support streaming)

Imported: Common Pitfalls

• Using this skill for tasks outside its domain expertise
• Applying recommendations without understanding your specific context
• Not providing enough project context for accurate analysis

Imported: Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.