WatchSDK Agent Skill

Generate AMap WatchSDK RTOS integration code with adapter scaffolding and render loops.

54|1|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/amap-demo/amap-sdk-skills --skill watchsdk-agent-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: WatchSDK Agent Skill
Source: https://github.com/amap-demo/amap-sdk-skills/tree/main/RTOS
Command: npx skills add https://github.com/amap-demo/amap-sdk-skills --skill watchsdk-agent-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you integrate the AMap WatchSDK (RTOS Map SDK) by providing structured guidance so AI coding tools generate adapter-compliant, compile-ready initialization, rendering, overlays, and navigation code.

Core Features & Use Cases

  • Adapter-first integration: guides you to implement required SDK adapters (especially the rendering adapter) and avoid enum/struct field mismatches by insisting on header-file truth.
  • End-to-end workflow: supports the full lifecycle from initialization and device activation to map view creation and a render loop.
  • Mapping functionality: covers raster/vector rendering, map view controls, overlays (point/line/polygon), and track navigation callbacks.
  • Use Case: when you need to bring up a WatchSDK map on an RTOS device with correct render_adapter callbacks, this Skill helps you produce deterministic adapter scaffolding and a minimal render loop that makes the map visible.

Quick Start

Indent the command you want to run as: Ask the Skill to initialize WatchSDK for RTOS, implement all required adapters including a working render_adapter (begin_drawing/commit_drawing/draw_bitmap/measure_text), create a map view, add a polyline overlay, and set up navigation callbacks.

Frequently Asked Questions about WatchSDK Agent Skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I integrate AMap WatchSDK on an RTOS device?

To integrate AMap WatchSDK on an RTOS device, generate initialization instructions and code scaffolding for mapping, overlays, and navigation workflows from awk_init to view destruction. This ensures deterministic adapter requirements and strict type safety.

What render adapter callbacks are required for AMap WatchSDK RTOS map visibility?

Required render adapter callbacks for AMap WatchSDK RTOS map visibility include begin_drawing, commit_drawing, draw_bitmap, and measure_text. Implementing these adapter callbacks correctly ensures a functional timed render loop and proper map display.

How does the AMap WatchSDK navigation workflow handle track callbacks?

The AMap WatchSDK navigation workflow handles track callbacks through structured guidance that generates adapter-compliant code scaffolding. This ensures proper lifecycle correctness from initialization through map view creation and ongoing navigation tracking.

Why am I getting enum or struct field mismatches when compiling WatchSDK C code?

Enum or struct field mismatches occur when C code deviates from header-file definitions. Ensure strict type safety by generating compile-ready initialization code that insists on header-file truth for all enums and struct fields.

Can I add polyline or polygon overlays to an AMap WatchSDK RTOS map view?

Yes, you can add point, line, and polygon overlays to an AMap WatchSDK RTOS map view. The integration scaffolding supports overlay functionality alongside raster and vector rendering within the single-threaded device bring-up scenario.

What is the lifecycle sequence for a single-threaded WatchSDK map bring-up?

The lifecycle sequence for a single-threaded WatchSDK map bring-up starts with awk_init and device activation, followed by map view creation, adapter wiring, and a timed render loop using awk_map_do_render, concluding with view destruction.