Skills

Two installable skill files, what each teaches an agent, and why the URL is the upgrade path.

Two files

A skill is a markdown file an agent reads once and keeps. Miles publishes two, at stable URLs:

Skill	URL	Teaches the agent
ask-miles	https://askmiles.ai/skills/ask-miles.md	How to ask Miles a question through the Chat API: when to pass a question through verbatim and when to compose one, client-side threading for follow-ups, what a denial or an outage does and does not mean, how to read provenance
miles-wallet	https://askmiles.ai/skills/miles-wallet.md	How to work the wallet tools over MCP: which tool answers which question, how to read a capped or conditional rate, what a refusal code means

Both carry frontmatter a skill installer reads, and both interpolate the same constants the docs do, so a rate limit or a URL cannot be stale in one place and current in another.

Installing

Paste this to an agent that can fetch a URL:

Fetch https://askmiles.ai/skills/ask-miles.md and install it as a skill named ask-miles. Then tell me what one-time authorization step I need to complete.

The agent installs the file and then tells you the one-time authorization step it needs: a personal API key for ask-miles, an MCP approval for miles-wallet. OpenClaw users can install ask-miles from ClawHub instead; see OpenClaw.

Upgrading

Re-fetch the URL. Each file carries a last-updated date in its frontmatter; the registry copy on ClawHub is pinned to a version, so when the two disagree the URL is the one that is current.