otto-pluginlisted

# Otto plugins Build or manage the requested plugin directly. Use the current public docs to catch contract changes, but keep working from this skill if the network is unavailable. **User's request:** $ARGUMENTS ## Check current documentation Fetch [https://otto-code.me/llms.txt](https://otto-code.me/llms.txt) first. Select and fetch the current plugin Markdown pages from that index before changing a plugin: - [Plugin quickstart](https://otto-code.me/docs/plugins/v0.8/index.md) ([browser page](https://otto-code.me/docs/plugins/v0.8)) - [Plugin reference](https://otto-code.me/docs/plugins/v0.8/reference.md) ([browser page](https://otto-code.me/docs/plugins/v0.8/reference)) Use the deployed docs when they disagree with this skill. Do not send the user away to read them instead of completing the work. In the Otto repository, use `public-docs/plugins/v0.8/reference.md` for the checkout's API, including unreleased changes. Use `docs/plugins.md` for maintainer guidance. Complete contracts belong in the public docs; this skill indexes the references and examples. ## What a plugin can contribute Pick the contribution that matches the request. Each row names the registration, when it fits, and where the full contract lives. Most plugins combine several: a slash command that calls an RPC, which appends a timeline row, which a renderer draws. | Contribution | Registration | Use it when