Agent Skills
Learn how to use Novu Agent Skills to help AI agents build multi-channel notification systems.
What are Agent Skills?
Agent Skills are an open standard that gives AI agents (Claude Code, Cursor, Copilot, etc.) the context they need to work with specific tools and platforms. Novu's skills provide AI agents with everything required to build multi-channel notification systems — triggering workflows, managing subscribers, integrating the in-app inbox, and configuring preferences.
Prerequisites
- A Novu account
- Secret key from dashboard.novu.co/settings/api-keys
Setup
Install the Novu skills into your project using the skills CLI:
This pulls the skills from the novuhq/skills GitHub repository and makes them available to your AI agent (Claude Code, Cursor, Copilot, etc.).
Available Skills
| Skill | Description |
|---|---|
| trigger-notification | Send single, bulk, broadcast, and topic-based notifications |
| manage-subscribers | CRUD operations on subscribers and topics |
| inbox-integration | Integrate the in-app notification inbox into React, Next.js, or vanilla JS |
| manage-preferences | Configure workflow and subscriber notification preferences |
Quick Routing
Use this guide to pick the right skill for your task:
- "Send a welcome notification" →
trigger-notification - "Create subscriber" →
manage-subscribers - "Add a bell icon to my app" →
inbox-integration - "Let users opt out of emails" →
manage-preferences
Common Combinations
- Full notification system:
trigger-notification+manage-subscribers - In-app notifications:
trigger-notification+inbox-integration - Complete stack: all four skills together
SDK Overview
| Package | Side | Purpose |
|---|---|---|
@novu/api | Server | Trigger notifications, manage subscribers/topics/workflows via REST |
@novu/react | Client | React Inbox component, Notifications, Preferences, Bell |
@novu/nextjs | Client | Next.js-optimized Inbox integration |
@novu/react-native | Client | React Native hooks-based Inbox integration |
@novu/js | Client | Vanilla JavaScript client for non-React apps |
Skill Reference
Trigger Notification
Send notifications by triggering Novu workflows. Supports single, bulk, broadcast, and topic-based delivery.
Key trigger parameters:
| Parameter | Required | Description |
|---|---|---|
workflowId | Yes | The workflow identifier (not the display name) |
to | Yes | Subscriber ID string, subscriber object, or topic target |
payload | No | Data passed to the workflow, validated against payloadSchema |
overrides | No | Provider-specific overrides per channel |
transactionId | No | Unique ID for idempotency and cancellation |
actor | No | Subscriber representing who triggered the action |
context | No | Key-value pairs for multi-tenancy / organizational context |
Manage Subscribers
Subscribers are the recipients of your notifications. Each subscriber has a unique subscriberId — typically your application's user ID.
Topics are named groups of subscribers for group-based notification targeting:
Inbox Integration
Add an in-app notification center to your web application. The Inbox provides a bell icon, notification feed, read/archive management, and real-time WebSocket updates.
HMAC Authentication is required in production to prevent subscriber impersonation. Generate the hash server-side:
Manage Preferences
Novu uses a two-level preference system: workflow defaults and subscriber overrides (set by end users).
Workflow-level defaults: Workflow level defaults can be configured in the Novu Dashboard. To do so, click on the workflow you want to configure and then click on the Manage Preferences option.
Subscriber-level overrides:
Preference resolution order (most specific wins):
- Subscriber workflow preference
- Subscriber global preference
- Workflow default
- System default (all channels enabled)
The Inbox component includes a built-in Preferences panel accessible via the settings icon, or use <Preferences /> as a standalone component.
For additional help, check the Novu documentation or contact us at [email protected].