> ## Documentation Index
> Fetch the complete documentation index at: https://docs.datazone.co/llms.txt
> Use this file to discover all available pages before exploring further.

# AI Skills

> Install the official Datazone agent skills so your AI coding assistant can build pipelines, endpoints, flows, and apps correctly

# AI Skills

Datazone publishes a set of **public agent skills** that teach AI coding assistants how to work with Datazone. Install them once, and your agent knows the YAML schemas, the `config.yml` registration rules, the deploy loop, and the mistakes that produce a project which validates and then fails at runtime.

Without them, an assistant guesses at Datazone's conventions. With them, it writes a `@transform` that deploys, an endpoint YAML that resolves, and a Studio App that does not 404 on its own assets.

<Card title="Browse the collection on skills.sh" icon="sparkles" href="https://www.skills.sh/datazoneco/datazone-skills/">
  Eight skills covering pipelines, endpoints, flows, objects, apps, and the API
</Card>

## Install

Run this in the root of your Datazone project repository:

```bash theme={null}
npx skills add datazoneco/datazone-skills
```

The CLI detects which assistant you use and installs the skills where it expects to find them. Supported clients include **Claude Code**, **Cursor**, **Codex**, **GitHub Copilot**, **Windsurf**, **Gemini**, **Cline**, **AMP**, and **Antigravity**.

To install a single skill instead of the whole collection, pass `--skill`:

```bash theme={null}
npx skills add datazoneco/datazone-skills --skill datazone-pipeline
```

<Note>
  Skills are instructions, not credentials. They tell your agent how Datazone works — they do not grant it access. Your agent still authenticates with your own [API key](/reference/development/api-key) or `datazone` CLI [profile](/reference/development/command-line), under your existing [policies](/reference/development/policy).
</Note>

## What's included

| Skill                       | Use it for                                                                                 | Reference                                                  |
| --------------------------- | ------------------------------------------------------------------------------------------ | ---------------------------------------------------------- |
| `datazone-project-setup`    | Installing the CLI, creating profiles, cloning a project, and the edit-deploy-verify loop  | [Command line](/reference/development/command-line)        |
| `datazone-pipeline`         | Python `@transform` functions, `input_mapping`, `output_mapping`, materialization          | [Pipelines](/reference/development/pipeline)               |
| `datazone-knowledge-object` | Versioned business entities in YAML — fields, primary keys, relationships, action handlers | [Knowledge Objects](/reference/knowledge-objects/overview) |
| `datazone-endpoint`         | Exposing a query, action, or vector search as an authenticated REST API                    | [Endpoints](/reference/integration/endpoints)              |
| `datazone-flow`             | Declarative orchestration — `llm_call`, `rest_call`, `for_each`, Python nodes, connections | [Flows](/reference/flows/overview)                         |
| `datazone-intelligent-app`  | YAML dashboards — charts, filters, tabs, widgets                                           | [Intelligent Apps](/reference/intelligent-apps/overview)   |
| `datazone-studio-app`       | Vite + React SPAs served behind your organisation's session                                | [Studio Apps](/reference/studio-apps/overview)             |
| `datazone-api`              | Calling the REST API — `x-api-key` auth, filtering, sorting, pagination, linked documents  | [API reference](/api-reference/introduction)               |

Each skill loads only when it is relevant. Ask your agent to "add a chart to the sales app" and it reads `datazone-intelligent-app`; ask it to "expose this query as an API" and it reads `datazone-endpoint`. You do not choose between them by hand.

## Using them

Once installed, work in plain language. The skill supplies the schema and the conventions.

```text theme={null}
Add a pipeline that reads the orders dataset, aggregates revenue by
region, and materializes the result.
```

The agent writes `pipelines/revenue_by_region.py`, registers it in `config.yml` under `pipelines:` with a unique alias, commits, and pushes — because pushing is what deploys. It then checks the deploy result, since validation is server-side and asynchronous.

Some further examples that map cleanly onto a single skill:

* *"Create a Knowledge Object for Contract with a relationship to Customer."*
* *"This flow fails validation — the `for_each` node isn't receiving its input."*
* *"Expose the unpaid-invoices query as an endpoint and show me how to call it."*
* *"My Studio App builds but shows a blank page."*

<Tip>
  Skills are most useful inside your project repository, where the agent can read your actual `config.yml`, datasets, and existing definitions. Several skills begin by confirming they are in a Datazone project — one with a `config.yml` at the root — and will stop and ask if they are not.
</Tip>

## Keeping them current

Datazone's YAML schemas and CLI evolve. Re-run the install command to pull the latest published versions:

```bash theme={null}
npx skills add datazoneco/datazone-skills
```

The collection is versioned alongside the platform, so refreshing after a [release](/changelog) keeps your agent's knowledge aligned with what your deployment actually accepts.

## Related resources

<CardGroup cols={2}>
  <Card title="Command Line" icon="terminal" href="/reference/development/command-line">
    Install the `datazone` CLI and manage profiles
  </Card>

  <Card title="Projects" icon="folder" href="/reference/development/project">
    How a project repository is structured and deployed
  </Card>

  <Card title="Orion AI" icon="sparkles" href="/reference/intelligent-apps/orion-ai">
    Datazone's built-in assistant for queries and apps
  </Card>

  <Card title="API Reference" icon="code" href="/api-reference/introduction">
    The REST API your agents and scripts call
  </Card>
</CardGroup>