azurewithdanidu/agentz-publisher

Analyse what someone wants to publish to the agentz marketplace and capture it as an intent brief before anything is built. Use when someone says "I want to publish an agent", "I have an idea for a skill", "can we share this prompt with other teams", or starts the agentz publishing flow. This is phase 1 of 4 (Analyse, Research, Build, Validate). Do not use to build or edit files, or for plugins that already exist.

Build a new agentz marketplace plugin from a confirmed intent brief, scaffolding the Agent Plugins 1.0 layout and authoring its skill, using HVE Core's hve-builder when it's installed. Use when the user says "create a plugin", "new plugin", "scaffold a skill for the marketplace", or after research-catalog returns a "new" verdict. This is phase 3 of 4 (Analyse, Research, Build, Validate). Do not use to edit an existing plugin's logic or to install plugins.

Search the agentz marketplace catalog for plugins, skills, agents and commands that already do what a new one would, and return a reuse, extend or new verdict. Use when someone asks "does agentz already have", "is there a skill for", or plans a new agent, skill or plugin. Use during research, including with rpi-research, and before hve-builder creates an artifact for agentz. This is phase 2 of 4 (Analyse, Research, Build, Validate). Do not use to build anything or to review an open pull request.

Validate a new or changed agentz plugin before publishing by writing its Vally evals, running them, running the marketplace gate locally, and producing a publish-readiness report. Use when the user says "validate my plugin", "write evals for this skill", "is my plugin ready to publish", or after build-plugin finishes. This is phase 4 of 4 (Analyse, Research, Build, Validate). Do not use to review someone else's pull request.