Verify an Agent Plugin package

Verify each boundary that a package consumer depends on. A successful build plan proves file selection, while installed inspection proves the final artifact and document access.

1. Inspect file selection

uv run --with agent-plugins agent-plugins plan packages/python --json

Check the authored plugin root and every target path. The plan should contain plugin.json, the intended Agent Skills, optional mcp.json, and selected client extension files.

2. Validate authored documents

Construct a direct Plugin handle and access the fields your consumers use:

import agent_plugins as ap

plugin = ap.Plugin(".")
print(plugin.manifest.name)
print(plugin.manifest.issues)

for skill in plugin.skills:
    print(skill.frontmatter)

if plugin.mcp is not None:
    print(plugin.mcp.servers)
    print(plugin.mcp.issues)

This validates the supported Agent Plugins JSON fields and the SKILL.md text structure. Use an Agent Skills validator to check YAML fields and other Agent Skills rules.

3. Build both artifacts

uv build packages/python --out-dir dist

The output should contain one wheel and one .tar.gz source distribution.

4. Rebuild from the source distribution

Build a wheel from the sdist into a separate directory:

uv build \
  --wheel dist/my_project-0.1.0.tar.gz \
  --out-dir dist/from-sdist

The rebuilt wheel should expose the same Agent Plugin target paths as the direct wheel.

5. Inspect a clean installation

Install the direct wheel in an isolated temporary environment and inspect it:

uv run --no-project --isolated --no-cache \
  --with agent-plugins \
  --with dist/my_project-0.1.0-py3-none-any.whl \
  agent-plugins locate my-project

uv run --no-project --isolated --no-cache \
  --with agent-plugins \
  --with dist/my_project-0.1.0-py3-none-any.whl \
  agent-plugins list --json

Repeat the commands with dist/from-sdist/my_project-0.1.0-py3-none-any.whl. Then access plugin.manifest.name, each skill document, and plugin.mcp.servers from Python. File location and document validation are separate checks.

6. Inspect an editable installation

uv run --no-project --isolated --no-cache \
  --with agent-plugins \
  --with-editable packages/python \
  agent-plugins locate my-project

Confirm that the root points to the authored directory. In a persistent editable environment, add a file, reinstall the editable distribution, and confirm that a new handle includes the new path.

Package-specific projects can automate these checks around their own build command. This repository's contributor workflow is documented in development_docs/testing-and-release.md.