Claude Code plugin marketplace

Install the AgentFeedback skill through a package manager you already use. This is an alternative to the native adapter, not an extra step after agentfeedback init.

Before you start

Install the binary with the local quickstart and check agentfeedback version. Skip native wiring for the harness you will configure here: two installers must not own the same skill directory.

This route installs the skill without the native hooks. It does not add automatic failure nudges or end-of-turn flushing.

Install

Run this from a terminal where the claude CLI is available:

claude plugin marketplace add AgentFeedback/agentfeedback && claude plugin install agentfeedback@agentfeedback

Verify

Run claude plugin list and confirm that agentfeedback appears.

Start a new harness session, confirm it can load the AgentFeedback skill, and ask it to file a labelled setup report. Run agentfeedback list --open to find the report. agentfeedback doctor --e2e separately checks the inbox connection; it does not prove that the package manager loaded the skill.

Troubleshooting and removal

If the skill runs but the binary cannot be found, check PATH in the harness environment. If a native install already owns the directory, remove that integration with agentfeedback uninstall <harness> before choosing this route; do not overwrite it.

For a server-backed inbox, run agentfeedback flush periodically because this route adds no hooks. Remove the skill or plugin through the package manager that installed it; agentfeedback uninstall does not own these files.

See the client installation playbook for the upstream package-manager procedure.

Source and verification

Documented on 2026-10-09. This is upstream's recorded verification level, not a claim that every setup above was live-tested by this site.

Source: integration registry and operating guide, pinned at c7573e1.