# Skills & AI

## Working from these pages in an AI chat

Almost everything here is **Markdown-based** or has a **Markdown export**, so you can reuse it in assistants (Cursor, ChatGPT, Claude, internal bots, etc.):

- **Guides** (this section of the site) are authored as Markdown. In the browser you can **select and copy** the body of any guide page, open the same files from the published docs repository, or **open the live page next to a chatbot** (for example Cursor’s browser + side chat) and work from the URL plus copied excerpts—whatever fits your assistant.
- **API reference** pages are generated from the OpenAPI spec. When the docs site is built with the Markdown export step, each operation also has a **`.md` sibling** next to its HTML page (same path with a `.md` suffix)—handy to drop whole operations into a chatbot or RAG index. See the **platform-docs** `README` for how `generate:api-md` fits into `yarn dev` / `yarn build`.

That workflow helps an AI answer “how do I call validate cart?” or “what fields does pricing return?” with the same text humans read on the site.

## Fleet Platform API skills (Skills CLI)

Fleet publishes **Agent Skills** for the Platform API—compact instruction packs an AI agent can load when integrating with `/platform/v1`.

Install them with the [Skills](https://skills.sh) ecosystem CLI (see also [vercel-labs/skills](https://github.com/vercel-labs/skills)):

```bash
npx skills add fleet.co/platform-api-skills
```

That command pulls the skill bundle from the **`fleet.co/platform-api-skills`** coordinate once that repository is available; until then, use the skills shipped alongside your integration package or monorepo if your team provides them another way.

After installation, your agent gets structured guidance (auth, rate limits, catalog, carts, devices, users) in addition to this site’s guides and OpenAPI reference.

## Practical combo

1. Install skills for **high-level** workflows and naming.
2. Paste a **guide** section or an **operation `.md`** file when you need **verbatim** API detail in a long context window.
3. Use **API reference** in the sidebar for interactive browsing and schema drill-down.