aqara-open-api-local
Route Aqara Open API requests across device, space, and automation skills with a relationship-first router, shared CLI contract, and structured handoff contract. Supports AQARA_OPEN_API_TOKEN and AQARA_ENDPOINT_URL through environment variables or AQARA CLI config.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/aqara/aqara-open-api-localAqara Open API Skill
This file is the single entry router for the Aqara Open Platform HTTP API skill package.
Read this file first. Use it to do four things:
- Classify whether the user request lands in
device,space, orautomation. - Preserve the shared request envelope, credential rules, and non-guessing rules.
- Build a structured handoff contract instead of forwarding raw user prose.
- Decide whether the next step may use cache-first execution or must upgrade to stricter validation.
Child skills:
aqara-open-api-local/device/SKILL.mdaqara-open-api-local/space/SKILL.mdaqara-open-api-local/automation/SKILL.md
Quick Route Table
Use this table before reading any child skill in depth.
| User asks for | Final intent | Next file |
|---|---|---|
| list devices, count devices, read state, control a device | device | aqara-open-api-local/device/SKILL.md |
| list spaces, create or rename spaces, move devices between spaces | space | aqara-open-api-local/space/SKILL.md |
| create automation, inspect automation, update automation config, enable or disable automation, delete automation | automation | aqara-open-api-local/automation/SKILL.md |
| room-scoped device query such as "what lights are in the living room" | device | confirm room identity, then query devices from data/devices.json |
| room-related automation such as "turn on the light when someone is in the living room" | automation | resolve room and device evidence first, then enter automation |
Language Policy
- user-facing explanations, routing notes, and clarification questions should use Chinese Simplified
- Open API request types, field names, file paths, enums, and code examples must keep exact English identifiers
- do not mix Chinese and English in one rule sentence unless an exact identifier must be quoted
Package Model
Treat the three business entities as related, not isolated:
spaceis the container and grouping scope for devicesdeviceis the concrete instance that can be queried, counted, and controlledautomationis the orchestration layer that references rooms, devices, and device traits
Route by the final action target, not by keyword count alone.
Important relationship rule:
- for room-scoped device queries,
spaceis the filter key anddeviceis the answer source GetSpacesRequestconfirms that a room exists or resolvesspaceId; it does not answer which devices are inside the room- the actual room-to-device result must come from
data/devices.jsonby filtering devices whose room membership matches the resolved room
Examples:
- "what devices are in the living room" -> final intent is
device - "move all lights from the master bedroom to the second bedroom" -> final intent is
space - "create an automation that turns on the light when someone is in the living room" -> final intent is
automation
Shared Runtime Contract
Runti...
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-aqara-aqara-open-api-local": {
"enabled": true,
"auto_update": true
}
}
}