Publish a setup to the setup library

Publishing a setup places a full copy of it in the setup library, the shared catalogue of agent setups that projects have published. An agent setup is a named bundle of what your AI coding tools work with: skills, agents, rules, MCP servers and setup files. The copy is a library entry, which other Athenode users can add to their projects or merge into their own setups.

One setup has one entry. The entry is separate from the setup it came from: editing or deleting the setup changes nothing in the library until you publish a new version.

Detail of an entry	Limit
Name	Up to 200 characters, unique across the whole library
Description	Up to 25,000 characters
Tags	Up to 10, each up to 30 characters of lowercase letters, digits and hyphens
Note on a new version	Up to 2,000 characters

Prepare a setup for publishing

Everything in the setup is published: every skill with its bundle files, every agent, the rules, every MCP server and every setup file, including the settings files under settings/ as they are. Prepare the setup before you open the publish page.

You need the owner or editor role in the project, and the project must be on the Solo, Team or Business plan. On the Free plan the publish page shows "Publishing to the library needs a paid plan."

1. Open Setups and select the setup.
2. In each MCP server, replace every value typed directly into an environment variable or a header with a ${VAR} reference.
3. Read the rules, the setup files and the skills for anything that should stay inside your team, such as internal addresses, names of people or credentials inside command arguments.

Athenode refuses to publish while an MCP server holds a literal value in an environment variable or a header. The publish page then shows "This setup cannot be published yet" and names the servers and the variables or headers concerned. Athenode checks nothing else for you, so command arguments, URLs, rules, files and the texts of skills and agents are yours to review.

Publish a setup

Publish a setup when it is ready for people outside your project to read and use.

1. On the Setups page, open the setup's menu and select Publish to library.
2. Check Name and Description, which start as the setup's own, and change them if you want the entry to read differently.
3. Optional: add Tags, which people use to search and filter the library.
4. Under What will be published, select each item to see exactly what will be published.
5. Select the checkbox I have reviewed this content, I am responsible for everything it makes public, and I agree to it being shown on the public Athenode website.
6. Select Publish.

Athenode confirms that the setup is in the library, and the setup shows the badge Published v1. Select the badge to open the entry. Signed-in users find the entry in the library at once, and the catalogue on the Athenode website is updated within a day.

Publish a new version

Publish a new version when you changed the setup and want the library to carry the change. The same role and plan are required as for the first publication.

1. On the Setups page, open the setup's menu and select Publish new version. The page states the number, such as "This will be version 2."
2. Optional: in What changed (optional), describe the change for the people who use your setup.
3. Review the items under What will be published and select the confirmation checkbox.
4. Select the publish button, which names the version, such as Publish version 2.

Versions are numbered 1, 2, 3 and so on. The library holds the content of the latest version, and that is what everyone reads, adds and merges. Projects that added your entry as a new setup see Update available on that setup, and your note under Show what changed.

Each new version turns public display on again. If you turned it off after an earlier publication, the Athenode website can show the entry again, with the new version's content.

Edit a library entry

Edit an entry to change its name, its description or its tags, or to take it off the Athenode website while it stays in the library. Editing doesn't create a new version. You need the owner or editor role in the project, on any plan.

1. On the Setups page, open the setup's menu and select Edit library entry. On the entry's own page in the library, select Edit.
2. Change Name, Description or Tags.
3. Select or clear the checkbox Also show this entry on the public Athenode website.
4. Select Save.

Athenode confirms with "Library entry updated." After you clear the checkbox, the entry leaves the Athenode website within a day and stays in the library for signed-in users.

Unpublish an entry

Unpublish an entry to remove it from the library for everyone. You need the owner or editor role in the project, on any plan.

1. On the Setups page, open the setup's menu and select Unpublish. On the entry's own page, the same button is next to Edit.
2. In the dialog "Unpublish this entry?", select Unpublish.

The entry leaves the library at once and the Athenode website within a day. Your setup stays in your project and loses its Published badge. Setups that other projects added from the entry keep working and receive no further updates.

Manage an entry after its project or setup changes

An entry outlives the setup and the project it was published from:

• If the project moves to the Free plan, its entries stay in the library. You can edit and unpublish them, and you publish new entries and new versions again once the project is on a paid plan.
• If you delete the setup or the project, the entry stays in the library and gets no further versions. The person who published it can edit and unpublish it in the web app, from the entry's page.
• If the publisher's account is deleted, the entry stays in the library and leaves the Athenode website.

Publish from your AI tool or the terminal

From your AI tool, ask /atn-manage to publish a setup or a new version, change an entry's name, description, tags or public display, or unpublish it. The skill shows you what would be published and asks before it publishes and before it turns public display on.

From the terminal, use the library commands of the Athenode CLI. library publish without --confirm-public publishes nothing and prints what would be published:

npx @athenode/cli library publish --setup "Web shop review" --tag code-review

Add --confirm-public to publish. The flag is your confirmation that the content becomes visible to signed-in users and on the open web:

npx @athenode/cli library publish --setup "Web shop review" --tag code-review --confirm-public

On the Free plan the command ends with exit code 3. athenode library edit changes an entry's name, description, tags and public display, and athenode library unpublish removes the entry at once, without asking for confirmation.

Your AI coding agent reaches the same actions through the tools library_publish, library_edit and library_unpublish of the Athenode MCP server. library_publish publishes only when it is called with confirmPublic.