Individual skill

wearable_device_skills

Use when the user asks to discover, inspect, or invoke an agentic capability dynamically published by a paired phone or wearable, including device controls, app actions, camera or media actions, and smart-home actions.

Meta/muse-agent/skills/wearable-device-skills/SKILL.md

Read pinned source

Source commit 9e00d9751f95564bc2de984d3f1c5b4b14aa50cc

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Instructions only
Last checked: Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.

Repository context

Repository stars (not skill ratings): 71,086
Repository last updated: Nov 8, 2026
License: CC0-1.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

ai Repository topic
anthropic Repository topic
chatbot Repository topic
chatgpt Repository topic
claude Repository topic
claude-code Repository topic
codex Repository topic
gemini Repository topic
generative-ai Repository topic
google Repository topic
engineering Derived category

Declared tags are partial or unavailable.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 3,354 bytes

Read excerpt


# Wearable Device Skills

## Purpose

Use agentic capabilities that a paired phone or wearable publishes through its
live device registry. The current registry is authoritative; command names,
schemas, permissions, and availability can change between turns and must not be
copied into this skill or inferred from conversation history.

## Workflow

1. Call `device.list` at the start of each request.
2. Build the candidate set from the live roster. An explicitly named device
   must resolve unambiguously. Otherwise inspect the first device marked