Writing a skill

A skill is a markdown file (SKILL.md) that teaches an agent how to operate the platform via the dtc_* tools. PlatformDTC ships a reference skill (mcp-platformdtc/SKILL.md) you can adapt.

Anatomy

Role & prime directive

One or two lines: the agent runs a PlatformDTC store and takes real actions on the merchant’s behalf.

Golden rules

The non-negotiables: async tools → dtc_job_wait; fresh idempotency_key per action; pending_approval → tell the user and stop; act only within granted scopes.

The playbook

The explicit tool sequence for the common goal (see Playbook).

Tool reference

A short, grouped list of the dtc_* tools with when-to-use — see Tool catalog.

Minimal example

# PlatformDTC Store Operator

## Prime directive
Operate the merchant's store via the `dtc_*` tools. Take real actions; report results plainly.

## Golden rules
- Async tools return a `job_id` → always follow with `dtc_job_wait`.
- Pass a fresh UUID `idempotency_key` on every non-read tool.
- If a tool returns `pending_approval`, tell the user and wait — never retry to force it.
- Call `dtc_whoami` first; only use tools your scopes allow.

## Playbook: build → products → publish → ads → campaign → ROAS
1. dtc_create_store → dtc_job_wait
2. dtc_bulk_import_products → dtc_job_wait
3. dtc_publish_project → dtc_job_wait
4. dtc_connect_ad_platform (human authorizes)
5. dtc_create_campaign → dtc_send_campaign
6. dtc_get_dashboard_analytics / dtc_get_ad_insights → decide

Keep skills short and imperative. The tool schemas (descriptions, params) come from the MCP server itself via dtc_capabilities, so the skill only needs the strategy, not the parameter docs.

OpenClaw

Reference

Anatomy

Minimal example

​Anatomy

​Minimal example

Anatomy

Minimal example