Build, improve, validate, evaluate, and package agent capabilities without tying their portable core to one runtime.
This distribution provides four guided creators for Agent Skills, custom agents, hooks, and complete Agent Plugins. Its portable outputs follow open Agent Skills and Agent Plugins specifications and are runtime-agnostic by format. Runtime-specific outputs are isolated and labeled explicitly. The integration suite is tested with Goose, an open-source Agentic AI Foundation project. Compatibility with another host depends on that host implementing the relevant specification and has not been verified by this repository unless stated.
| Status | Value |
|---|---|
| Distribution | 0.5.0 |
| Portable plugin target | Agent Plugins 1.0.0 |
| Portable skill target | Agent Skills |
| Verified host integration | Goose 1.47.0 |
| Creator runtime | Node.js 22+ |
| License | CeCILL-C |
Turn a concrete need into an agent capability, then prove whether it helps:
- Create portable Agent Skills and complete plugins from guided requirements instead of hand-writing fragile package structures.
- Apply good practices for concise instructions, progressive disclosure, safe paths, portable manifests, and explicit host adapters.
- Validate schemas, structure, references, packaging, and host-specific behavior before distribution.
- Evaluate performance with paired A/B runs: compare
with_skillagainst anold_skillorwithout_skillbaseline on the same scenarios. - Inspect a visual report that combines outputs, grading evidence, timing, benchmark summaries, regressions, and reviewer feedback.
- Improve from evidence: revise weak instructions, rerun the same cases, and compare iterations without claiming gains that were not measured.
The goal is not merely to generate files. It is to produce maintainable capabilities with traceable evidence from idea to release.
Use
agent-plugins:skill-creatorto create.agents/skills/api-review. It should review an OpenAPI diff for breaking changes and produce a concise Markdown report. Keep the Skill portable, apply progressive disclosure, add realistic evaluation cases, validate every reference, and show the resulting files.
Expected outcome: a valid SKILL.md, only the supporting resources the workflow needs, and explicit validation or evaluation gaps.
Use
agent-plugins:plugin-creatorto create./release-assistantwith a portable Skill for drafting release notes. Keep the portable core compliant with Agent Plugins 1.0.0, isolate any host-specific behavior, validate in portable-load and strict-authoring modes, and show the package before writing a release archive.
Expected outcome: a valid plugin.json, portable components in fixed locations, separate host adapters when required, and a reviewable validation result before packaging.
Use
agent-plugins:skill-creatorto evaluate.agents/skills/api-reviewagainst its previous version. Run the same realistic scenarios with the current Skill and the old Skill, grade both variants using explicit evidence, aggregate the benchmark, generate the static HTML review, identify regressions and trade-offs, and recommend only evidence-backed improvements.
The evaluation workspace preserves paired with_skill and old_skill/without_skill outputs. It produces benchmark.json, benchmark.md, and an HTML review such as review.html. Open the HTML file in a browser to inspect outputs and grading side by side. The analysis should explain:
- which assertions improved, regressed, or remained inconclusive;
- whether quality gains trade off against time or token use;
- which instruction or example likely caused each difference;
- what to change next and which unchanged scenarios must be rerun.
A complete report does not guarantee improvement: results remain pass, fail, blocked, or na, and missing evidence never becomes a positive claim.
- What you can do
- See it in action
- Choose your path
- Choose the right creator
- Quick start
- How-to guides
- Installation and updates
- Validation and evaluation
- Troubleshooting
- Formats, portability, and security
- Component reference
- Contributing
- Project information
- Create a portable Skill: start with Create a Skill with good practices, then install
skill-creatorthrough a compatible host or as a standalone Skill. - Measure whether a Skill helps: use A/B test a Skill to compare paired outputs and inspect the visual report.
- Build or migrate a plugin: use
plugin-creatorfor manifests, MCP, packaging, integration evaluation, and release decisions. - Create host-specific behavior: use
agent-creatororhook-creator; these outputs are explicitly labeled as Goose-specific today. - Contribute to this repository: follow Contributing.
| I want to… | Creator | Output portability |
|---|---|---|
| Create, improve, or A/B evaluate one Agent Skill | agent-plugins:skill-creator |
Open Agent Skills format |
| Create or evaluate a custom agent | agent-plugins:agent-creator |
Goose custom-agent format |
| Create or validate a lifecycle hook | agent-plugins:hook-creator |
Goose extension in a plugin |
| Create, migrate, validate, evaluate, or release a plugin | agent-plugins:plugin-creator |
Portable core plus explicit host adapters |
Use the unqualified names—such as skill-creator—when a creator is installed standalone. A productive request names one deliverable, its destination, user outcome, constraints, and success criteria.
The creator utilities require Node.js 22 or later. To load them through an agent, use a host that implements the relevant Agent Skills or Agent Plugins specification. The distribution includes compiled scripts and vendored runtime dependencies; consumers must not run npm install inside an installed release.
Host discovery and installation commands differ. This repository verifies the complete integration with Goose. Other hosts may load the portable outputs when they implement the corresponding specification, but this repository does not claim untested host compatibility.
goose plugin install --auto-update https://github.com/servierhub/agent-plugins.gitOmit --auto-update if you want to approve updates manually.
Start a new Goose session and ask:
Use
agent-plugins:skill-creatorto explain, without modifying files, what you need from me to create an Agent Skill.
Success means Goose resolves the qualified creator and asks for or explains the target behavior, activation conditions, workflow, and evaluation needs. If it cannot resolve the creator, see Troubleshooting.
Use
agent-plugins:skill-creatorto create.agents/skills/markdown-summary. It should summarize one Markdown file into key decisions and open questions. Keep the Skill portable, validate it, and show me the files created and any evidence still required.
A successful run creates at least .agents/skills/markdown-summary/SKILL.md, validates its format, and reports either completed evaluation evidence or an explicit evaluation: blocked state. Additional references, scripts, or evaluations are created only when the behavior needs them.
Each guide identifies the request and the evidence of success. Exact supporting files depend on the requested behavior.
Use when: you want repeatable instructions that compatible agents can discover through the Agent Skills format.
Prompt:
Use
agent-plugins:skill-creatorto create.agents/skills/api-review. It should review an OpenAPI diff for breaking changes and produce a concise Markdown report. Include realistic evaluations, validate the result, and report any blocked evidence.
Success: SKILL.md has valid frontmatter and focused instructions; its directory name matches the Skill name; any referenced files exist; validation passes; behavioral evidence is reported separately.
Use when: a Goose custom agent already exists under .agents/agents/ and needs evidence-backed improvement.
Prompt:
Use
agent-plugins:agent-creatorto evaluate.agents/agents/security-reviewer.mdagainst its current baseline, improve only evidence-backed weaknesses, and report the benchmark delta.
Success: the custom-agent definition validates, paired evidence remains traceable, and the report distinguishes measured improvement from unavailable or blocked evidence.
Use when: a plugin needs Goose lifecycle behavior. Hooks execute commands and are not part of the portable core.
Prompt:
Use
agent-plugins:hook-creatorto add a safePostToolUsehook to./my-plugin. Invoke a plugin-relative script, keep persistent writes inside plugin data, validate the hook, and explain its side effects.
Success: the plugin already has a valid plugin.json; the hook uses the canonical namespaced extension; referenced scripts exist and remain inside the plugin; executable behavior has been reviewed.
Use when: you need a conformance decision, migration, package, or release—not just one component.
Prompt:
Use
agent-plugins:plugin-creatorto validate./my-pluginin strict-authoring mode, fix actionable errors, run applicable evaluations, and prepare a release only if every required gate has evidence.
Success: portable and host-specific resources are classified separately; strict validation passes; requested behavioral evidence and archive checks exist; missing evidence blocks rather than weakens a release gate.
From a source checkout of this repository, direct validation is also available:
node skills/plugin-creator/dist/scripts/cli.js validate <plugin-directory> --mode portable-load --format json
node skills/plugin-creator/dist/scripts/cli.js validate <plugin-directory> --mode strict-authoring --format jsongoose plugin install --auto-update https://github.com/servierhub/agent-plugins.gitFor an installation without automatic updates:
goose plugin install https://github.com/servierhub/agent-plugins.git
goose plugin update agent-pluginsGoose 1.47.0 provides plugin install and plugin update, but no plugin uninstall subcommand. Use the removal procedure documented by your installed host version rather than deleting unknown runtime state manually.
Use the host's documented Agent Skills or Agent Plugins installation mechanism. There is intentionally no invented universal command: the file formats are open, while discovery and lifecycle management belong to each host. A host respecting a specification can consume the corresponding portable surface, but support must be verified per host and per component. Qualified creator names are a host presentation detail and may differ.
Clone the ServierHub distribution, then copy the self-contained creator directory:
git clone https://github.com/servierhub/agent-plugins.git
cd agent-plugins
mkdir -p ~/.agents/skills
cp -R skills/skill-creator ~/.agents/skills/skill-creator
test -f ~/.agents/skills/skill-creator/SKILL.mdThe .agents/skills location is an emerging interoperability convention used by Goose and other compatible agents; confirm discovery rules in your host.
Validation answers “does the artifact conform?” Evaluation answers “does it improve behavior?”
portable-load: models what an Agent Plugins 1.0.0 loader accepts, ignores, or isolates.strict-authoring: adds semantic, operational, migration, and safety policy; this is the authoring default.- Release: additionally requires applicable tests, behavioral receipts, archive identity, and human review.
JSON commands return a stable envelope. Exit codes are 0 for success, 1 for failure, 2 for invalid usage, and 3 when required execution or evidence is blocked. A blocked evaluation is not a passed evaluation and is not necessarily a format failure.
scenarios → paired isolated runs → grading → benchmark → review → release gates
| Symptom | What to check |
|---|---|
| A creator is not found | Start a new host session after installation; try the qualified name for a plugin install and the plain name for a standalone install. |
| Goose cannot start a creator | Confirm Goose has a configured model provider and the plugin installation completed without errors. |
| Node.js errors appear | Run node --version; creator scripts require Node.js 22 or later. |
| An installed release reports a missing dependency | Treat it as an incomplete package; do not repair it with npm install. Reinstall a complete release and report the defect. |
| Validation fails | Read the structured diagnostics and correct the referenced path or field; do not bypass strict-authoring errors. |
Evaluation reports blocked |
Supply the requested model run, grading, timing, test, or human-review evidence, then resume the workflow. |
| Portable and Goose behavior seem inconsistent | Check whether the resource is portable core, a Goose-specific adapter, or a legacy migration input. |
Report reproducible defects in the upstream issue tracker; the ServierHub fork does not maintain a separate issue queue.
The active target is the published Agent Plugins 1.0.0 format:
my-plugin/
├── plugin.json # required
├── skills/review/ # optional Agent Skills
│ └── SKILL.md
└── mcp.json # optional portable MCP configuration
plugin.json, direct children of skills/, and root mcp.json form the portable package surface. The vendored Agent Plugins 1.1.0 snapshot is an inactive Working Draft for analysis, not a supported target.
Custom-agent definitions and hooks currently target Goose contracts. New hooks live under plugin.json.extensions["io.github.bioinfornatics.agent-plugins.goose"] and point to extensions/io.github.bioinfornatics.agent-plugins.goose/hooks.json. Root hooks/hooks.json, root .mcp.json, and inline plugin.json.mcpServers are legacy migration inputs, not portable alternatives.
Hooks are executable behavior. Review generated commands, paths, credentials, blocking semantics, and side effects before enabling them. Never package secrets.
See portable conformance and the Goose adapter reference for normative detail.
- Shared capability contracts—portable capability, evaluation, result, and host execution adapter protocols.
- Skill Creator—portable Agent Skills authoring and evaluation.
- Plugin Creator—portable package boundaries, validation, migration, and release.
- Agent Creator—Goose custom-agent definitions.
- Hook Creator—Goose lifecycle hooks and executable safety.
Contributor dependency installation is separate from end-user installation. From the repository root, these copy/paste-safe subshell commands preserve the working directory:
(cd contracts/capability-contract && npm install && npm run build && npm test) # capability, evaluation-plan, result-state, and host-adapter contracts
(cd skills/agent-creator && npm install && npm run build && npm test)
(cd skills/hook-creator && npm install && npm run build && npm test)
(cd skills/plugin-creator && npm install && npm run build && npm test)
(cd skills/skill-creator && npm install && npm run build && npm test)Verify the complete offline distribution from the repository root:
npm run prepare:offline
npm test
npm run test:offline- Servier Open Source Hub distribution: https://github.com/servierhub/agent-plugins
- Upstream source repository: https://github.com/bioinfornatics/agent-plugins
- Agent Skills open specification: https://agentskills.io/specification
- Agent Plugins open specification: https://agent-plugins.org/
- Agentic AI Foundation: https://aaif.io/
- Goose documentation: https://goose-docs.ai/
- Distribution manifest:
plugin.json - License: CeCILL-C
Install this Servier distribution from servierhub/agent-plugins. It is a public fork of the upstream source repository and may carry Servier-specific presentation or release commits.