How do I install the Vibe Bluetooth skill?

Run npx skillmds@latest add arnie016/vibe-bluetooth in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Vibe Bluetooth safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Vibe Bluetooth?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Vibe Bluetooth free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Vibe Bluetooth?

Arnie016 (@arnie016) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Vibe Bluetooth by arnie016 — Agent Skill

Name: Vibe Bluetooth
Author: Arnie016

Vibe Bluetooth

Build, run, troubleshoot, or extend the VibeWidget macOS SwiftUI app and widget. Use when Codex needs to work on a VibeWidget or VibeBluetooth workspace, especially the repo app at `apps/vibe-widget`; regenerate the Xcode project; launch it in Xcode; run local doctor, build, or typecheck checks; or modify the HomeKit, Spotify, widget, voice panel, or shared-core flows.

Arnie016 4021796 8 files · 18.8 KB Updated Sep 17, 2026

File contents

VibeBluetooth

Use this skill for the VibeWidget app workspace. If the current repo contains apps/vibe-widget, use that by default. Otherwise, pass --workspace /path/to/vibe-widget to the runner script.

Quick Start

Use bash scripts/run_vibe_bluetooth.sh doctor from the repo root, or pass --workspace /path/to/vibe-widget if the app lives elsewhere.
Use bash scripts/run_vibe_bluetooth.sh inspect before editing so the app, widget, and core-test layout stay visible.
Use bash scripts/run_vibe_bluetooth.sh generate after project spec changes.
Use bash scripts/run_vibe_bluetooth.sh open to open the Xcode project.
Use bash scripts/run_vibe_bluetooth.sh typecheck for a lightweight local sanity pass.
Use bash scripts/run_vibe_bluetooth.sh test after core, widget, parser, or shared-state changes.
Use bash scripts/run_vibe_bluetooth.sh build only after the Xcode license has been accepted on the machine.
Use bash scripts/run_vibe_bluetooth.sh run when you need the built app relaunched from the local build output.

Workflow

Before Editing

Read references/project-map.md for the current target layout and main files.
If the task changes app or widget targets, inspect project.yml in the target workspace first.
If the task is UI-heavy, preserve the existing visual direction: dark glass, low chrome, strong type, and a compact high-signal layout.

Running The App

Prefer the local runner script before manually typing xcodegen or xcodebuild.
If doctor reports the Xcode license is not accepted, stop and tell the user to run sudo xcodebuild -license.
Use test after changes to VibeWidgetCore, widget intents, or app orchestration when you want the repo's unit coverage before a full build.
Use run after app UI or launch-path changes so you can verify the relaunch path from the local build output.
If generate succeeds but build fails only under Command Line Tools, switch to full Xcode and rerun.

Editing Guidance

Keep the project Apple-only for speaker flow. Do not add private Bluetooth automation.
Keep secrets in Keychain only. Do not move OpenAI or Spotify tokens into files or defaults.
Shared models and snapshot state belong in VibeWidgetCore.
Widget actions should enqueue shared actions and let the app process them.
HomeKit code must keep the compile-safe fallback path for environments that only expose Command Line Tools.

Resources

scripts/run_vibe_bluetooth.sh: local doctor/inspect/generate/open/build/test/typecheck runner for the VibeWidget workspace.
references/project-map.md: target map, key files, and run/build caveats.

---name: vibe-bluetoothdescription: Build, run, troubleshoot, or extend the VibeWidget macOS SwiftUI app and widget. Use when Codex needs to work on a VibeWidget or VibeBluetooth workspace, especially the repo app at `apps/vibe-widget`; regenerate the Xcode project; launch it in Xcode; run local doctor, build, or typecheck checks; or modify the HomeKit, Spotify, widget, voice panel, or shared-core flows.---# VibeBluetoothUse this skill for the VibeWidget app workspace. If the current repo contains `apps/vibe-widget`, use that by default. Otherwise, pass `--workspace /path/to/vibe-widget` to the runner script.## Quick Start1. Use `bash scripts/run_vibe_bluetooth.sh doctor` from the repo root, or pass `--workspace /path/to/vibe-widget` if the app lives elsewhere.2. Use `bash scripts/run_vibe_bluetooth.sh inspect` before editing so the app, widget, and core-test layout stay visible.3. Use `bash scripts/run_vibe_bluetooth.sh generate` after project spec changes.4. Use `bash scripts/run_vibe_bluetooth.sh open` to open the Xcode project.5. Use `bash scripts/run_vibe_bluetooth.sh typecheck` for a lightweight local sanity pass.6. Use `bash scripts/run_vibe_bluetooth.sh test` after core, widget, parser, or shared-state changes.7. Use `bash scripts/run_vibe_bluetooth.sh build` only after the Xcode license has been accepted on the machine.8. Use `bash scripts/run_vibe_bluetooth.sh run` when you need the built app relaunched from the local build output.## Workflow### Before Editing- Read `references/project-map.md` for the current target layout and main files.- If the task changes app or widget targets, inspect `project.yml` in the target workspace first.- If the task is UI-heavy, preserve the existing visual direction: dark glass, low chrome, strong type, and a compact high-signal layout.### Running The App- Prefer the local runner script before manually typing `xcodegen` or `xcodebuild`.- If `doctor` reports the Xcode license is not accepted, stop and tell the user to run `sudo xcodebuild -license`.- Use `test` after changes to `VibeWidgetCore`, widget intents, or app orchestration when you want the repo's unit coverage before a full build.- Use `run` after app UI or launch-path changes so you can verify the relaunch path from the local build output.- If `generate` succeeds but `build` fails only under Command Line Tools, switch to full Xcode and rerun.### Editing Guidance- Keep the project Apple-only for speaker flow. Do not add private Bluetooth automation.- Keep secrets in Keychain only. Do not move OpenAI or Spotify tokens into files or defaults.- Shared models and snapshot state belong in `VibeWidgetCore`.- Widget actions should enqueue shared actions and let the app process them.- HomeKit code must keep the compile-safe fallback path for environments that only expose Command Line Tools.## Resources- `scripts/run_vibe_bluetooth.sh`: local doctor/inspect/generate/open/build/test/typecheck runner for the VibeWidget workspace.- `references/project-map.md`: target map, key files, and run/build caveats.

Frequently asked questions