---
title: Agent Skills
description: Install the Notiflows agent skills to teach any compatible AI assistant the notiflow and template schemas, the CLI, and where authoritative docs live — grounded in the real product.
---

Agent **skills** are installable, self-contained packets of context that teach a compatible AI coding agent (Claude Code, Cursor, and others) how to create and manage notiflows **as code** — without you pasting in docs or examples. They're grounded in the real Notiflows schemas and the [`@notiflows/cli`](/docs/cli).

The skills are open source and published at [github.com/notiflows/skills](https://github.com/notiflows/skills).

## What is a skill?

A skill is a `SKILL.md` file with YAML frontmatter (`name` + `description`) and a **progressive-disclosure** body: a start-here overview the agent reads first, then deeper references it pulls in only when the task needs them. The agent loads a skill when the task matches its `description`, keeping its context lean until the knowledge is actually required. Each skill follows the [agentskills.io](https://agentskills.io) spec.

## Install

There are two ways to install, depending on your agent.

### Cursor and other agents

Add the skills with the `skills` CLI:

```bash
npx skills add notiflows/skills
```

### Claude Code

Install the Notiflows plugin from the marketplace:

```bash
/plugin marketplace add notiflows/skills
/plugin install notiflows@notiflows-skills
```

Or clone the repo and point Claude Code at it directly:

```bash
git clone https://github.com/notiflows/skills
claude --plugin-dir ./skills
```

The Claude Code plugin bundles the skills **and** the hosted [MCP server](/docs/ai/mcp), wiring it up for you. On first use it prompts once for your [account token](/docs/cli/account-tokens) and stores it in the OS keychain.

## The skills

| Skill | What it covers |
|---|---|
| **notiflows-schema** | The `notiflow.json` flat-steps format — step types (trigger/end/channel/wait/digest/throttle/condition), positions and ordering, branching, condition steps and branches, per-step gate conditions, and per-type settings. |
| **notiflows-template-schema** | Channel templates — the `{ channel_type, data }` shape, the per-channel fields, `content_type` enums, and the `@`-suffix convention that extracts a body into its own file. |
| **notiflows-cli** | The [`@notiflows/cli`](/docs/cli) — install, account-token auth, the `pull` / `push` / `publish` / `validate` / `diff` commands, and `notiflow run` to trigger a notiflow. |
| **notiflows-docs-support** | Where to find authoritative answers — the docs, `llms.txt`, which API and auth to reach for, and when to use the CLI versus the MCP server. |

Every skill is grounded in the real Notiflows product. They describe only fields, commands, and behavior that actually exist; when a detail is uncertain at runtime, they direct the agent to validate against the Management API rather than guess.

## Related

- [CLI](/docs/cli) — the commands the `notiflows-cli` skill describes.
- [MCP server](/docs/ai/mcp) — connect an agent directly to the Management API.
- [Agent toolkit](/docs/ai/agent-toolkit) — expose notiflows as typed tools for your own agents.
- [llms.txt & docs for agents](/docs/ai/llms-txt) — the machine-readable docs the skills point to.