Terminal
Terminal/Skill
Guides live debugging of an iOS app's connection to Meta glasses through a local Meta Wearables Device Access Toolkit inspector.
By Meta
Works with
npx skills add facebook/meta-wearables-dat-ios --skill live-debugging-mcpUse 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.
search_dat_docs.discover_debug_serversconnect_to_debug_serverget_connection_statusget_sdk_stateget_dat_readiness
Do not skip get_connection_status; it separates MCP/debug-server
connectivity from SDK, registration, permission, session, and stream state.get_companion_boundary_diagnosisget_device_pathget_permissionsget_device_propertieswait_for_events with category or sourceget_errorsget_event_digestexport_diagnostic_bundleWearables.configure()Wearables.shared.handleUrl(_:) return handlingWearables.shared.startRegistration() and
wearables.registrationStatewearables.devices,
device.compatibility, and device.propertiesdevice.linkStatedevice.permission, check_permissions,
and get_permissionsDeviceSession creation/start, deviceSession.state,
session.state, and session errorsstream.state, frame counters, and stream errorssdk.usesDam and DAM/DWA error valuesdevice.linkState before changing stream code.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.When summarizing, name the evidence plane, the blocking state, and the next developer action. Example:
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.