Build plugins
An Agent Plugins 1.0 package is a directory with root plugin.json and Skills, MCP configuration, or both. Start with the smallest component that solves your users' task. A Skill supplies instructions; MCP supplies a connection to tools.
Availability
The current native installer release, CLI, can validate and install standard packages. Package-manager channels can lag; check agentplugins version for the installed version. It does not include agentplugins author. The authoring commands in this Build journey describe current source builds with authoring enabled. Historical 0.1.65 authoring release evidence remains version-specific and does not describe today's installer.
You can write the files by hand and use the released installer, or build the source tools below for scaffolding, static checks and an explicit MCP runtime loop. A passing static check does not prove native client activation or a working service connection.
Make a small package by hand
Create this structure:
review-helper/
plugin.json
skills/
review-docs/
SKILL.mdPut package identity in plugin.json:
{
"$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
"name": "review-helper",
"version": "0.1.0",
"description": "Review documentation changes for clarity and evidence"
}Start skills/review-docs/SKILL.md with:
---
name: review-docs
description: Use when reviewing documentation for clarity and evidence.
---
# Review documentation
Identify the intended reader and task. Check each command's input and effect.
Separate verified behavior from prerequisites and untested claims. Return
findings with file locations and a suggested correction.Install the released manager, then validate and preview the package:
npm install -g universal-agent-plugins
agentplugins validate ./review-helper
agentplugins add ./review-helper --target codex --dry-runReview the plan and use Use plugins when ready to apply it. See package layout for the responsibility of each file.
Build from source
The following commands build the current CLI from source with authoring enabled. They require Git and the Go toolchain declared by the repository (currently Go 1.26.11). Record the checked-out commit when sharing results.
git clone https://github.com/777genius/universal-agent-plugins.git
cd universal-agent-plugins/cli
mkdir -p ../bin
authoring_module=$(go list -f '{{.Module.Path}}' ./cmd/agentplugins)
authoring_revision=$(git rev-parse HEAD)
go build -ldflags "-X ${authoring_module}/internal/authoring/commands.Enabled=release-cli-contract-v1 -X ${authoring_module}/internal/authoring/commands.Revision=${authoring_revision}" \
-o ../bin/agentplugins ./cmd/agentplugins
export PATH="$(cd ../bin && pwd):$PATH"
agentplugins author --helpUse a separate working directory for the tutorial packages. This source binary is a development build. Its existence is not a qualified public authoring release. Check your executable path if the installed manager still reports an unknown author command.
Choose a package to scaffold
| Need | Journey | Required template inputs |
|---|---|---|
| Instructions an agent can follow | Standalone Skill | --template skill |
| Connect to an existing service | Remote MCP | --template mcp-remote --url <endpoint> |
| Provide a local Node MCP process | Stdio MCP | --template mcp-stdio --runtime node |
| Instructions together with tools | Hybrid | --template hybrid --mcp-template <choice> and that MCP template's inputs |
A standalone Skill package still has root plugin.json. Installing standalone Skills from another repository is a separate installer operation.
Follow the authoring loop
- Create a package in an absent destination, then edit the generated files.
- Run validate, inspect and static test on the exact package root.
- Check the intended clients with
compatand inspectdoctorevidence. - For MCP, evaluate runtime separately with explicit source-build execution.
- Share the package and its evidence through the installer handoff.
Current source also provides lockfile-based bootstrap, continuous dev, JSON normalize and explicit Claude MCP import native. See checks and stdio MCP. Client projection, bundle export and package publication are outside this current authoring command surface. Client-specific hooks remain separate from the portable Skill and MCP components.