facebook/meta-wearables-dat-ios/live-debugging-mcp

Claude Code and agent skill by facebook/meta-wearables-dat-ios

Trust tier 2
  • community
LLM review pending
Source check pending

Checking that the SKILL.md file is still in the repository.

Use this whenever debugging an iOS DAT app with local DAT Inspector MCP tools, live device events, Meta AI app/device boundary issues, permissions, registration, sessions, streaming, callbacks, or user reports that the app cannot communicate with glasses.

Install

npx vskill@latest install facebook/meta-wearables-dat-ios/live-debugging-mcp

SKILL.md

The same SKILL.md was published earlier as facebook/meta-wearables-dat-ios/live-debugging-mcp.

Live DAT Debugging with MCP (iOS)

Use this skill when a developer is debugging an iOS DAT app and has a local DAT Inspector MCP server or DAT debug server available to the agent. This is the live-runtime counterpart to dat-docs-mcp: use docs search for API lookup, and use this skill for observed app/device behavior.

Ground rules

  • Stay read-only unless the user explicitly asks for an app code change.
  • Do not mutate Meta AI app, device, account, permission, registration, or app

state.

  • Treat companion-app/device results as boundary diagnosis from app-visible DAT

events, not as direct access to companion app internals.

  • Use live DAT evidence before guessing: registration, permissions, device

selection, link state, session state, stream state, typed errors, and SDK logs.

  • If the MCP tools are not configured, ask the developer to enable their local

DAT debug setup and fall back to logs plus search_dat_docs.

Normal agent loop

  1. Discover and connect to the running app debug server:
  • discover_debug_servers
  • connect_to_debug_server
  1. Establish the baseline with all three calls before diagnosing deeper:
  • get_connection_status
  • get_sdk_state
  • get_dat_readiness

Do not skip get_connection_status; it separates MCP/debug-server connectivity from SDK, registration, permission, session, and stream state.

  1. If the issue looks like Meta AI app or device boundary behavior, inspect:
  • get_companion_boundary_diagnosis
  • get_device_path
  • get_permissions
  • get_device_properties
  1. Ask the developer to reproduce the failing iOS flow while connected.
  2. Wait for narrow evidence instead of polling everything:
  • wait_for_events with category or source
  • get_errors
  • get_event_digest
  1. For handoff, collect a redacted bundle:
  • export_diagnostic_bundle

Evidence map

  • Configuration: app logs around Wearables.configure()
  • URL callbacks: Wearables.shared.handleUrl(_:) return handling
  • Registration: Wearables.shared.startRegistration() and

wearables.registrationState

  • Device availability: device selectors, wearables.devices,

device.compatibility, and device.properties

  • Device link: device.linkState
  • Permissions: DAT permission APIs, device.permission, check_permissions,

and get_permissions

  • Session: DeviceSession creation/start, deviceSession.state,

session.state, and session errors

  • Stream: stream start, stream.state, frame counters, and stream errors
  • DAM/DWA-visible transport: DAM/DWA error values

Diagnosis patterns

  • Registration blocked: verify Info.plist DAT configuration, app URL scheme,

Developer Mode setup, and callback handling.

  • No eligible device: inspect discovered devices, selector behavior, device

compatibility, and device.linkState before changing stream code.

  • Permission failure: use get_permissions and get_companion_boundary_diagnosis;

do not assume iOS system permission is the same as DAT permission through the Meta AI app/device boundary.

  • Session fails before stream creation: inspect session errors and selected

device compatibility before changing camera code.

  • Stream fails after session start: inspect stream state, camera permission, and

recent errors before changing frame processing.

Output expectations

When summarizing, name the evidence plane, the blocking state, and the next developer action. Example:

text
DAT readiness is blocked at registration: the app-visible registration state is
not registered. Check the Info.plist DAT URL scheme and MetaAppID, complete the
Meta AI callback through handleUrl(_:), then retry while the MCP connection waits
for registration and device-link events.

Security

  • Security scanPassed, 100 of 100Pattern checks on the skill's files.
  • Model reviewNot runA model review is scheduled for the next rescan.

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

Repository stars
576
Repository forks
129
7-day trend score
31

Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/facebook/meta-wearables-dat-ios/live-debugging-mcp/badge)](https://verified-skill.com/skills/facebook/meta-wearables-dat-ios/live-debugging-mcp)

Something wrong with this skill or its page? Tell us.