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

# Publish a Community Plugin

> Ask an agent to prepare and open a Webcmd repository pull request for a reusable community plugin.

# Publish a Community Plugin

## Before You Publish

Publish a plugin only when its workflows, examples, and verification are useful to people beyond your team. The pull request is the review and publishing boundary.

## Ask an Agent to Prepare the Contribution

```text theme={null}
Prepare my `webcmd-acme` plugin for contribution to the AgentR Webcmd repository. Place it under `plugins/acme/`, make the manifest name match the directory, include version, description, Webcmd compatibility, and my author name and GitHub handle, improve the README and examples, run the repository plugin checks, and open a pull request summarizing the workflows and verification evidence.
```

## Repository Requirements

Community plugins live under `plugins/<name>/`. Their `webcmd-plugin.json` must use the directory name, and include non-empty `version`, `description`, and `webcmd` compatibility fields. Author metadata needs both a display name and valid GitHub handle.

Repository plugins are catalog source, not npm package contents. Users install
an approved plugin explicitly; Webcmd core does not bundle it.

The root `webcmd-plugin.json` and the README community table are generated by repository tooling; do not edit them by hand.

## Authoring Through Webcmd

To fork an installed command into a private copy you can edit, run `webcmd adapter override <site>/<command>` in either mode. Locally that copies the file into `~/.webcmd/clis` and records provenance, and `webcmd adapter path <site>/<command>` prints the file to edit. In hosted mode it forks the command into a tenant-private package, and `webcmd adapter source get|put <site>/<command>` reads and writes that source. Use `webcmd browser init <site>/<command>` to scaffold, `webcmd browser verify <site>/<command>` to validate, and `webcmd site memory` commands to retain sanitized discovery evidence.

## Validation and Pull Request

The agent runs `npm run check-community-plugins`, improves the plugin README and examples, and opens a pull request with the workflows and verification evidence. The pull request is the review/publishing boundary.

## What Happens After Merge

Repository tooling adds the approved plugin to the generated root catalog and README community table, making it discoverable through `webcmd plugin search`. Users install the returned `installSource`.