dot-openapi
Compatibility router for Dot. OpenAPI work. Prefer dot-device-openapi for device operations and dot-canvas-designer for Canvas layout design.
Works with
--- name: dot-openapi description: Compatibility router for Dot. OpenAPI work. Prefer dot-device-openapi for device operations and dot-canvas-designer for Canvas layout design. license: MIT --- # Dot OpenAPI Compatibility Router This skill remains for backward compatibility with older installs that reference `dot-openapi`. Prefer the split skills: - Use `dot-device-openapi` for device interaction: - list devices - check device status - switch to next content - list tasks - send Text API, Image API, or a finished Canvas API payload - Use `dot-canvas-designer` for Canvas design: - build or revise `windowData` - design Canvas cards, dashboards, and status panels - use `$for` / `$empty`, `$ifAny` / `$then` / `$else`, `compare`, `formatDate`, and `formatCompactNumber` - reason about layout, style, overflow, and rendering boundaries If a task asks to design and send a Canvas card, use both skills in sequence: 1. `dot-canvas-designer` to produce the Canvas payload. 2. `dot-device-openapi` to send it to the device. Base URL: `https://dot.mindreset.tech` Authentication: ```http Authorization: Bearer dot_app_<your_api_key> ``` OpenAPI schema: `../../openapi/dot-openapi.yaml`
More API Design skills
lark-event
larksuite/cli
Lark/Feishu real-time event listening / subscribing / consuming: stream events as NDJSON via `lark-cli event consume <EventKey>` (covers IM messages/reactions/chat changes, Approval status changes, Task updates, VC meeting started/joined/ended, Minutes generated, Whiteboard updated, etc.). Use for Lark bots, real-time message processing, long-running subscribers, streaming webhook/push handlers. Supports `--max-events` / `--timeout` bounded runs and a stderr ready-marker contract — designed for AI agents running as subprocesses.
lark-contact
larksuite/cli
飞书 / Lark 通讯录:按姓名 / 邮箱解析成 open_id,或按 open_id 反查姓名 / 部门 / 邮箱 / 联系方式 / 个人状态 / 签名,以及按关键词搜索当前用户可见的机器人 / 智能体(agent)。当用户提到一个名字要下一步发消息 / 排日程,或拿到 open_id 想查具体信息时使用。不负责部门树遍历、按部门列员工、组织架构图,这类需求走原生 OpenAPI。
lark-openapi-explorer
larksuite/cli
飞书/Lark 原生 OpenAPI 探索:从官方文档库中挖掘未经 CLI 封装的原生 OpenAPI 接口。当用户的需求无法被现有 lark-* skill 或 lark-cli 已注册命令满足,需要查找并调用原生飞书 OpenAPI 时使用。

