symposium plugin
Manage plugin sources.
Usage
symposium plugin <SUBCOMMAND>
Subcommands
symposium plugin sync
symposium plugin sync [PROVIDER]
Fetch or update git-based plugin sources. If a provider name is given, syncs only that provider (ignoring auto-update settings). If omitted, syncs all providers that have auto-update = true. The audits list, when it is on, is synced with them, or alone as symposium-audits.
symposium plugin list
symposium plugin list
List all configured plugin sources and the plugins they provide.
symposium plugin show
symposium plugin show <PLUGIN>
Show a plugin: its id and its effective configuration as TOML, after validation has filled in defaults and promoted inline installations.
symposium plugin digest
symposium plugin digest <TARGET>
Print the payload digest of a crate: the value an audits file matches the crate on. <TARGET> is a crate’s source directory when it names an existing directory (relative to the working directory). A target that looks like a path (it starts with . or contains a path separator) or names something that is not a directory is an error. Anything else is a crate name, resolved the way symposium crate-info resolves it (a workspace member’s own directory, or the source cargo fetches). Write name@version (for example serde@1.0.200) to digest one exact release: the workspace’s own copy when the workspace resolved that release, otherwise the source cargo fetches for =<version>.
On success the command prints the digest and nothing else (sha256: followed by 64 hex characters), so it can be used in a script. It skips the startup auto-update check, so no update notice reaches its output and the binary is never replaced under a script mid-run. When the payload has no digest it prints the reason on stderr, leaving stdout empty, and exits non-zero. With --json it emits a payload_digest event carrying target, digest or ineligible, and, for a crate name, krate (the crate and the version it resolved to).
Use it to check a crate before adding it to an audits file, or from tooling that maintains one, so that the tooling hashes exactly as Symposium does. The digest it prints is computed by the same code the lookup uses.
symposium plugin validate
symposium plugin validate <PATH> [--no-check-crates]
Validate plugins without installing anything. Useful when authoring plugins. Each item is reported with its kind: plugin, agent plugin or skill. <PATH> is one of:
- A crate: a directory whose
Cargo.tomlhas a[package]table, or thatCargo.tomlor the crate’sSymposium.toml. The crate is validated as its users get it:[package.metadata.symposium]andSymposium.tomlmerged, named after the crate, with the defaultskills/group. A malformed[package.metadata.symposium]orSymposium.toml, which loading skips with only a log entry, is an error here, and so is a crate with no plugin content. - A plugin or skill directory, or an Agent Plugins package directory or its
plugin.json, validated as that one entry. - A plugin source directory, such as a checkout of the recommendations repository: every entry in it.
- Any other
.tomlfile, validated as a registry plugin manifest.
| Flag | Description |
|---|---|
<PATH> | Path to a directory or a manifest file |
--no-check-crates | Skip checking that crate names in predicates exist on crates.io |
Besides errors, it warns about a plugin that loads but does not work the same on every agent:
- a plugin name containing
., which Antigravity rejects; - an Agent Plugins package with no
version, which agents that cache plugins by version, such as Codex, may not refresh; - a hook event handled only by agent-format hooks, which fire on that agent alone (see Agent-specific hooks);
- a skill file or folder that is not installed: a link that resolves outside its package, a broken link, or a link back into the skill.
symposium plugin import
symposium plugin import <PATH> [--out <DIR>]
Turn a Claude Code plugin into an Agent Plugins package that Symposium loads, written to <DIR>/<name>/. The command refuses to overwrite an existing folder, and validates the result as plugin validate does.
| Flag | Description |
|---|---|
<PATH> | The Claude Code plugin folder, the one holding .claude-plugin/plugin.json |
--out <DIR> | Where to write the package. Defaults to the current directory |
What each part of the Claude Code plugin becomes:
| Claude Code | Package |
|---|---|
.claude-plugin/plugin.json | plugin.json, keeping name, version, description, author, homepage, repository, license and keywords. The name is rewritten to follow the name rule. Without the file, the folder name is used. |
skills/ | Copied unchanged |
commands/*.md | A skill each, skills/<command>/SKILL.md, named after the command. A command with no description, or whose name an existing skill already has, is left out. |
hooks/hooks.json | [[hooks]] entries with format = "claude" in a Symposium.toml, each running its original command through sh -c |
.mcp.json | [[mcp_servers]] entries in the same Symposium.toml |
| Other files | Copied unchanged, so the scripts a hook runs come along |
A Symposium.toml is written only when there are hooks or MCP servers. It then also declares [[skills]] source.path = "skills", since a Symposium.toml beside plugin.json gets no default skill group.
Symposium runs a format = "claude" hook only in Claude Code, with CLAUDE_PLUGIN_ROOT set to the package folder, so the hook works as it did in the plugin. To run a hook in the other agents, add a format = "symposium" hook next to it.
Everything that is not imported is reported, one line each:
agents/,.lsp.json, andplugin.jsonfields outside the list above, such asuserConfig. The package format has no place for them.- Hooks for an event Symposium does not handle, hooks whose
typeis notcommand, and hooks using a field other thancommandandtimeout, such asiforasync.timeoutitself is dropped. SessionStarthooks whosematcherleaves outstartup, such ascompact: Symposium runsSessionStarthooks on every session start. The matcher of the others is dropped, with a warning.- MCP servers that use
${CLAUDE_PLUGIN_ROOT}, which agents do not expand outside a Claude Code plugin.
A skill that mentions ${CLAUDE_PLUGIN_ROOT} is copied, with a warning: Claude Code only fills that in for the skills of its own plugins.
The imported plugin names no crate, so in a plugin source it stays dormant until enabled with symposium use.
symposium plugin try
symposium plugin try <PATH>
symposium plugin try --remove <PATH or NAME>
Install a plugin you are writing in your agents, the way a user would have it, so you can open an agent and use it. <PATH> is a plugin directory (with a Symposium.toml), an Agent Plugins package directory (with a plugin.json) or a skill directory (with a SKILL.md).
The plugin is linked into ~/.symposium/plugins/ under its name, then the current workspace is synced. A plugin that names no dependency is also enabled in every workspace, as symposium use --global would. Symposium reads your directory in place, so an edit reaches your agents on the next sync: symposium sync, or the automatic one when an agent starts a session. Most agents then need a new session (Claude Code also takes /reload-plugins, Copilot CLI /restart).
A plugin with its own depends-on or predicates is left to them, as it is for its users: it is active only in workspaces where they hold. try names the dependency and warns when the current workspace does not have it.
After syncing, try asks each configured agent what it loaded, using the agent’s own listing command (none of them calls a model), and reports the plugin’s skills it does not list:
| Agent | Command |
|---|---|
| Codex CLI | codex debug prompt-input hi |
| GitHub Copilot | copilot skill list --json |
| Goose | goose skills list |
| OpenCode | opencode debug skill |
Claude Code, Antigravity CLI and Kiro have no such command: start a new session in the project and run /skills. An agent whose command is not on PATH is skipped.
--remove discards the trial: it removes the link and the enablement try added, and syncs, which removes everything installed for the plugin in the current workspace. Other workspaces are cleaned on their next sync. A directory in ~/.symposium/plugins/ that try did not link is left alone.
| Flag | Description |
|---|---|
<PATH> | Path to the plugin or skill directory; with --remove, its path or the plugin name |
--remove | Discard the trial |