- Home
- Skills
- Agents & Orchestration
- ZoaK - Zepp OS Knowledge Base
Works with the AI Agents you already use
ZoaK - Zepp OS Knowledge Base
ZoaK its your missing layer between Zepp OS docs and your agent.
Free
ZoaK - Zepp OS Knowledge Base
Example session with this skill installed
Example 1 — zepp-os-mcp skill (consumption by MCP tools)
User request
"Can I use LocalStorage in an app for Amazfit Bip 5?"
Sequence of calls made by the agent (order required in skills/zepp-os-mcp/SKILL.md:17 and :61):
- get_freshness()
- lookup(name: "LocalStorage") → resolves the name owner
- check_compatibility(ids: ["@zos/storage.LocalStorage"], device: "Amazfit Bip 5")
- get_device(name: "Amazfit Bip 5") → both axes, as mandated by the skill
Relevant returns
// check_compatibility
{ "id": "@zos/storage.LocalStorage", "verdict": "TOO_NEW", "minApiLevel": 3,
"contra": { "apiLevel": 2.1, "device": "Amazfit Bip 5" },
"reason": "Requires a minimum of 3, above the target 2.1.",
"cite": "api/zos-storage.md#zosstoragelocalstorage" }
// lookup("LocalStorage") — two owners, not a duplicate
[ { "owner": "@zos/storage.LocalStorage", "runtimes": ["device-app"], "minApiLevel": 3 },
{ "owner": "@zos/share-storage.LocalStorage", "runtimes": ["device-app"], "minApiLevel": 3 } ]
- Read your context and instructions
- Compiled the zoak - zepp
Response returned by the agent
No. @zos/storage.LocalStorage declares minApiLevel: 3 and Amazfit Bip 5 caps at 2.1 → verdict TOO_NEW, not UNKNOWN. Source: check_compatibility → api/zos-storage.md#zosstoragelocalstorage. Two details before you decide:
- lookup("LocalStorage") returns two owners — @zos/storage and @zos/share-storage. I chose the @zos/storage one (device-app); share-storage involves reading storage published by another app and also requires API level >= 3.
- If you only need to read/write key-value pairs, there is @zos/storage.localStorage-instance with minApiLevel: 2 (getItem/setItem), which the Bip 5 supports. Check the permission in manifest/index.md before finalizing.
Connects securely to your tools. The creator never sees your data.
About this skill
A compatibility-aware knowledge base that sits between the official Zepp OS sources and the AI agents that write Zepp OS code.
This is not a documentation mirror. Official docs exist, but they aren't in a shape an agent can consume reliably when the question is "can I call this API in this runtime, at this API_LEVEL?". This project extracts those sources into a structured layer where that question has a checkable answer.
Sources: zepp-health/zeppos-docs (reference pages and the LLM-oriented content in static/llms) and zepp-health/zeppos-samples (real usage in shipped example apps).
API_LEVEL is not stated for watchface (hm*) or Settings App symbols. Entry points for some runtimes are observed from samples only, not official contracts.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
This skill has been used 2 times.
Trust & safety
Security scan
Security scan passed 24 days ago
- Free with an Agensi account
Requires
Permissions
Allowed Hosts