Package an agent template to share

Making a pack is mostly subtraction. Six parts are candidates, and the judgement is which ones.

That subtraction is the same everywhere, and other catalogues learned it the hard way. n8n's export docs tell people to strip auth headers from workflow files before sharing them, and Dify's export deliberately excludes keys, knowledge-base contents and logs (n8n, Dify).

Agent Pack Builder is our own template, and the first thing to install if you intend to publish. It reads a working agent, separates what ships from what stays behind, scrubs what is left, and writes the archive.

Take it from its page, install the skill the way any pack is installed, and point it at the agent you want to publish.

One archive, unpacking to one folder, with a README at the root and a skills directory beside it. That is the same shape What's inside an agent template describes from a reader's side of the page.

Skills have a shape of their own, and it is worth following even where the tool does not insist. The open standard asks for a name, a description that says what the skill does and when to use it, and marks everything else optional (specification).

skills/read-an-invoice/
  SKILL.md          when to use it, and the steps
  references/       the rules it loads only when needed
  scripts/          the parts that should not be improvised

A pack without a licence is a pack most people cannot legally reuse, which is a strange way to publish something you want used. Pick one and put it in the folder as LICENSE.

Those three are the common ones, described from the licence deeds themselves (MIT, Apache-2.0, CC-BY-4.0). If you build on somebody else's pack, their licence sets your floor: keep their notice, add yours, and say what you changed.

Three lines near the top of the README: who wrote it, what it was built from, and the licence it goes out under. Those three lines are what makes a pack answerable to a person.

A pack adapted from somebody else's work is welcome here. The summary you upload with is where you say whose work it started from, and What review checks makes that a rule rather than a courtesy.

The order of the rest of the README is Write a README for an agent template.

• It arrives private, readable by the handles on its audience list and nobody else.
• A reviewer reads the archive against the one-line summary you wrote.
• Approval gives it a page. You make that page visible when you have stopped editing.

Private and published are two separate facts rather than one, and Who can see your agent template is the page that pulls them apart. Who may read it while it waits is Name your collaborators.