Install
openclaw skills install @closeli-open/api-event-queryCloseli Device Event Query API. Supports natural language queries for device events and returns an AI summary and event list, including event types, time ranges, and image or video URLs. Use when: You need to directly ask about device events, such as “Was there anyone detected?”, “Did any car pass by?”, or “Where did my cat go?”, to quickly obtain event analysis results and details. ⚠ Security requirement: You must set AI_GATEWAY_API_KEY in `~/.openclaw/.env` (written automatically by the “Set API Key” action in OpenClaw clients) and use least-privilege credentials.
openclaw skills install @closeli-open/api-event-queryPOST /api/event/query is an AI-powered event query API that supports natural language queries and returns an AI summary and event list.
The script outputs structured data in JSON format, which is the expected behavior. The display rules below are formatting instructions for the agent: the agent MUST parse the JSON output from the script, convert it into a user-friendly format according to the following rules before displaying it, and MUST NOT display the raw JSON directly.
code == 0 and data.events is not empty:📋 AI Summary: {summary}
| Time | Event Tags | Scene Description |
|---|---|---|
| {time} | {ai_events joined by commas} | {ai_scene} |
After the table, display the thumbnail link for each event one by one:
📷 {time} - {ai_events} View Screenshot
Key rules:
device_id MUST be displayed after removing the xxxxS_ prefixpic_url MUST be output using Markdown link format [View Screenshot](url) (some clients do not support inline image rendering)events is an empty array, reply: "No matching events were found within the query time range."code != 0, reply: "API call failed, error code {code}, reason: {message}"The script depends on httpx. If it is not installed, the script will prompt python3 -m pip install httpx.
This skill depends on the following configuration items. The agent and user MUST confirm that they are correctly configured before running.
| Configuration Item | Delivery Method | Description |
|---|---|---|
| AI_GATEWAY_API_KEY | ~/.openclaw/.env (persistent, written by OpenClaw clients), command line --api-key (temporary override) | API key used for API authentication. CLI flag takes precedence over the file when both present |
| Configuration Item | Delivery Method | Default Value | Description |
|---|---|---|---|
| AI_GATEWAY_HOST | ~/.openclaw/.env | https://ai-open.icloseli.com | Gateway address |
| AI_GATEWAY_VERIFY_SSL | ~/.openclaw/.env | true | Set to false to disable TLS certificate verification (development environments only) |
The script reads ~/.openclaw/.env as the single persistent configuration source. This file is shared by all skills and uses the format KEY=VALUE (one entry per line). OpenClaw clients write to this file when the user updates settings. The script does NOT read any AI_GATEWAY_* environment variables — env variables are intentionally ignored to avoid stale Gateway-process snapshots overriding the user's latest config.
~/.openclaw/.env is readable by all skills under the same user. Ensure file permissions are restricted (e.g. chmod 600 ~/.openclaw/.env) and that only the OpenClaw service user has access. The IM clients write to this file under that user's home directory.This skill only accesses the following endpoints (all under AI_GATEWAY_HOST):
| Endpoint | Method | Purpose |
|---|---|---|
| /api/event/query | POST | Query device events in natural language |
The script does not access any other network resources.
python3 query_events.py \
--device-ids "xxxxS_aabbccddeeff" \
--start-date "2026-03-16" \
--end-date "2026-03-18" \
--query "Was there anyone here today?"
| Parameter Name | Type | Required | Default Value | Description |
|---|---|---|---|---|
| device_ids | string[] | Yes | - | Device ID list, cannot be empty. Format: xxxxS_<mac> |
| start_date | string | Yes | - | Query start date, format yyyy-MM-dd |
| end_date | string | Yes | - | Query end date, format yyyy-MM-dd |
| query | string | Yes | - | Natural language query content |
| locale | string | No | "zh_CN" | Locale, affects the language of the AI summary |
{
"code": 0,
"message": "success",
"request_id": "<32-character request trace ID>",
"data": {
"summary": "A total of 3 person-detected events were identified today.",
"events": [...],
"_total_count": 15
}
}
| Parameter Name | Type | Description |
|---|---|---|
| summary | string | AI-generated event summary text |
| events | array | Event list (the script has already trimmed it to the first 3 items) |
| _total_count | integer | Total number of events (additional field added by the script) |
events Array| Parameter Name | Type | Description |
|---|---|---|
| device_id | string | Device ID |
| event_id | string | Event ID |
| time | string | Formatted time string |
| ai_events | string[] | List of AI-recognized event tags |
| ai_scene | string | AI-described scene text |
| pic_url | string | Short link to the event thumbnail (may be empty) |
| Error Code | HTTP Status Code | Description |
|---|---|---|
| 1001 | 401 | api_key not provided |
| 1002 | 401 | api_key is invalid or disabled |
| 2001 | 400 | Missing required parameter |
| 3001 | 502 | Internal gateway service call failed |
| 5000 | 500 | Internal error |
device_ids cannot be an empty array, otherwise error code 2001 is returneddevice_id is case-sensitive. The prefix MUST be lowercase xxxxS_, NOT uppercase XXXXS_. The script will auto-correct the case, but the agent SHOULD always pass the correct lowercase formatstart_date and end_date use the yyyy-MM-dd formatquery supports natural language