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

> ## Agent Instructions
> For agents: install the OpenWork desktop app with `brew install --cask openwork` (macOS) or from https://openworklabs.com/download. Do not run `npx openwork`; the npm package named `openwork` is a different project.
> Connect an agent to OpenWork with the MCP Gateway: `claude mcp add --transport http openwork https://api.openworklabs.com/mcp/agent`. Teams sign up at https://app.openworklabs.com?mode=sign-up.
> Step-by-step agent guide: https://openworklabs.com/docs/start-here/use-openwork-from-an-ai-agent.md
> Connect Slack (any organization admin): https://openworklabs.com/docs/slack/connect-slack.md. OpenWork in Slack (@openwork bot) is private alpha for approved organizations. Setup guide: https://openworklabs.com/docs/slack/overview.md. Agent skill: https://openworklabs.com/.well-known/agent-skills/set-up-openwork-slack/SKILL.md.

# Agents, commands, and hooks

> What agents, commands and hooks are in an OpenWork plugin, where they come from, and where to see them all.

Besides skills and connectors, a plugin can include **agents**, **commands**,
and **hooks**. Whoever can use the plugin gets all of them; there's nothing
separate to share.

| Part | What it is | Where it comes from |
| - | - | - |
| **Command** | A shortcut like `/follow-up` that runs a set task the same way every time. | Write one when you [create a plugin](https://openworklabs.com/docs/cloud/share-with-your-team/plugins.md#create-a-plugin), or bring it in from GitHub. |
| **Agent** | A helper set up for one kind of task, like reviewing a deal or editing copy. | Claude-compatible plugins in a connected GitHub repository. |
| **Hook** | A step that runs on its own at a set moment, like when a session starts or before a tool is used. | Claude-compatible plugins in a connected GitHub repository. |

You can't write agents or hooks in OpenWork Cloud. They arrive with plugins from
[GitHub Sources](https://openworklabs.com/docs/cloud/share-with-your-team/github-sources.md).

## Commands

A command saves people from typing the same request again and again. Someone
runs `/release-notes`, and the AI does exactly what the command says.

To write one, add a **Command** under **What's inside** when you create a plugin:
give it a name like `/follow-up` and write what should happen when someone runs
it. Commands in a plugin from a connected GitHub repository come in with that
plugin.

## Agents

An agent is a helper with its own instructions for one kind of task, for
example a *Deal reviewer* in a sales plugin or a *Copy editor* in a brand plugin.
Claude-compatible plugins can define agents, and they come in when OpenWork
imports the plugin from a connected repository.

## Hooks

A hook runs by itself at a set moment, without anyone asking. For example, a
hook can load the brand guide when a session starts, run a check before an email
is sent, or save a summary when a session ends. The **Hooks** list shows when
each one runs.

Because hooks run without a prompt, review what a plugin's hooks do before you
share it widely.

## See them all

The plugin directory lists every part across all your plugins, each with the
plugin it came with. It has these tabs:

* **Plugins**
* **Agents**
* **Commands**
* **Hooks**
* **MCPs**: the apps inside your plugins, from your connectors or from remote
  MCP servers in imported plugins.
* **Sources**: your connected GitHub accounts and repositories.

To open it, go to **Manage › Plugins** in OpenWork Cloud and add `?view=agents`
(or `commands`, `hooks`, `mcps`, `sources`) to the address.

## Get agents and hooks into OpenWork

**1. Connect GitHub**

Connect the GitHub account that holds your plugins. See
[GitHub Sources](https://openworklabs.com/docs/cloud/share-with-your-team/github-sources.md#connect-github).

**2. Add the repository**

Add a repository with a Claude-compatible plugin (`.claude-plugin/plugin.json`)
or marketplace (`.claude-plugin/marketplace.json`), and pick the plugins to
import.

**3. Share the plugins**

Choose who can use each plugin on its page, or through a
[Collection](https://openworklabs.com/docs/cloud/share-with-your-team/collections.md). Its agents, commands
and hooks go with it.

When the repository changes, the plugins update on their own.

> [!NOTE]
>
> Importing a single public plugin with **Import from GitHub** brings in its
> skills and MCP servers only. For agents and hooks, connect the repository as a
> source.

## Related

* [Manage plugins](https://openworklabs.com/docs/cloud/share-with-your-team/plugins.md)
* [GitHub Sources](https://openworklabs.com/docs/cloud/share-with-your-team/github-sources.md)
* [Connectors, skills, and plugins](https://openworklabs.com/docs/start-here/do-work-with-it/skills-plugins-and-mcp.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.