PandaOSPandaOS
Enterprise

Library

Add, update, restore or archive the items you give your members: skills, agents, rules, starters, MCP servers and design systems. Set what members may share.

How-to guide Updated 19 Nov 2026

Who can do this

Owners and admins.

What you get

A published item reaches the members you chose within about 5 minutes, marked as coming from your organization. Every publish is a new numbered version. Change an item later, or go back to an older one.

Create and publish an item

You need: an owner or admin role in your organization's console.

Skills, agents and rules are made on one page. Starters use a stepped editor: fill in each step and click Next to reach the following one. Apps cannot be created here. They arrive from members, see What the Library is.

  1. In the console, click Library, then the tab for the kind of item, for example Skills.
    Your own MCP servers are on the MCP tab.
  2. Click New skill.
    The button names the kind: New agent, New rule and so on.
  3. Enter a Name and a Description.
    The description is one sentence members see next to the name, up to 500 characters. Skills and agents need one; for the other kinds it is optional.
  4. Write the Instructions, or the Rule for a rule.
    To start from a Markdown file, click Import from file. One file can hold up to 256 KB.
  5. Under Who gets it, choose Everyone or Selected teams.
    With Selected teams, tick at least one team.
  6. Under How members get it, choose Available, On by default or Required.
    Only the levels the kind offers are listed. Agents and starters have none.
  7. Click Publish.

What you see when it worked

The page confirms it, for example "Code review: published as v1. Members receive it within five minutes." The item appears on its kind's page, in the group of who gets it. When you open it again, the editor reads "Published, version 1".

Choose how members get an item

In the editor, How members get it sets the level:

  • Available: members find it and choose it themselves.
  • On by default: it is on for every member who gets it, and each member can turn it off.
  • Required: it is on for everyone, and members cannot turn it off or remove it.

Not every kind offers every level. Skills, rules, apps and plugins offer all three, MCP servers offer On by default and Required, and design systems offer Available and On by default. What each level means for each kind is in What the Library is.

The setting is hidden while Who gets it is Only specific people, because those people always get the item as Available.

Update an item

  1. In the console, click Library, then the tab for the item's kind.
  2. Click the item, then click Edit.
    Starters have Edit on their row.
  3. Change the content, the description, Who gets it or How members get it.
  4. Click Publish.
    This publishes the next version. If another admin published the item while you were editing, the publish is refused. Click Discard draft and reload and make your change again.

View history and restore a version

  1. On the item's kind page, click the item to preview it.
    Starters have History on their row.
  2. Click History.
    Every version is listed with who published it and when. The live one is marked "Current".
  3. Click View on a version to read its content.
  4. Click Restore, then Restore revision.
    The old content is published as a new version. The item's current title, teams and Required setting are kept.

Archive and republish

Archiving takes an item away from members without deleting it. What happens to copies they already have depends on the kind, see What the Library is.

Archive an item

  1. Click the item, then click Edit.
    Starters have Edit on their row.
  2. Click Archive.
  3. Confirm with the button named after the kind, for example Archive skill.
    The item moves to the Archived group. A starter stays in the table, marked Archived.

Republish an archived item

  1. In the Archived group, click the item, then click Republish.
    Starters have Republish on their row.
  2. Check the content and Who gets it.
  3. Click Publish.

When publishing fails

The editor shows the reason over its buttons. Find the message among these.

It says the content changed since the page was opened

The full message is "This content changed since the page was opened. Reload to see the latest version, then publish again." It has two causes.

  • Another admin published the item while you were editing. Click Discard draft and reload, then make your change again.
  • You are creating a new item whose short name is already taken by an item of the same kind, archived items included. The short name is made from the name and shows under Advanced. Give the new item another name, or republish the archived item instead.

It says to choose at least one team

Selected teams is chosen but no team is ticked. Tick a team, or choose Everyone. If your organization has no teams yet, create one under Teams first.

An MCP server's name is reserved

MCP server names starting with pandaos or pandactions are kept for PandaOS itself. Pick another name.

It says how members get it could not be saved

The item was published, but its level was not. Open the item, choose How members get it again, and publish.

It says the response could not be read

The publish may have gone through. Reload the page and check the item before you publish again.

Set what members can share

Members share what they made from PandaOS with a colleague, a team or everyone. You decide what happens to those shares under Policies, Sharing. Like every policy page, a change takes effect when you publish the policy.

SettingWhat it does
Members can shareOff stops every share a member starts. What was shared before stays.
Review skills that contain scriptsA skill with a scripts folder waits for review, even where skills are shared automatically.
What members can shareFor each kind and each audience (A person, A team, Everyone): Automatic shares at once, Review waits for an admin in the Review queue, Not allowed refuses the share.

Unless you change it, members can share, apps and MCP servers wait for review, and everything else is shared at once. A team can have its own settings, marked Custom. What members share always reaches people as Available: only admins can make an item on by default or required.

Skills: references and scripts

Besides its instructions, a skill can carry two kinds of files:

SectionWhat goes there
ReferencesDocuments the skill can read, like a style guide, in Markdown.
ScriptsCode the skill can run. Allowed types: .sh, .bash, .py, .js, .mjs, .cjs, .ts, .rb, .ps1, or no extension.

Use Add reference or Add script, then New reference (or New script) to write a file, or Upload files to bring files in. Removing a file happens at once, without a confirmation.

A skill holds at most 20 files, 256 KB per file and 1 MB in total. A file's path can be up to 128 characters.

Once a skill has scripts, members on older PandaOS versions get it only after they update. In the preview, a skill with scripts carries the warning "Runs code on members' computers. Its script runs wherever this skill is installed. Read it before approving."

If a member already wrote a skill with the same name, PandaOS does not overwrite it.

Agents: skills and model

An agent has two extra settings in the editor:

SettingWhat it does
SkillsSkills installed along with the agent when a member hires it. Click Add skills and pick from Your Library or PandaOS.
ModelHow strong a model the agent runs on: High, Medium, Low or Utility. Medium unless you pick another. The tiers map to your organization's models, on whichever engine the member uses.

To choose which model stands behind each tier, see Model tiers.

Starters

A starter is one of the PandaOS starters plus your own principles, knowledge, skills and agents. Members find it in New Project under "From Acme", where selecting it shows what it adds. If the starter asks questions, they appear to the member as an extra step named "Acme options".

If a starter refers to an item members can no longer get, PandaOS skips that item and shows a warning. When a member removes the starter from a project, your organization's rules leave the project and the knowledge files stay.

Design systems

A design system carries your brand's colors, fonts and voice. Members build on it in the Design app, read-only, under "From Acme".

Members can also share design systems they made, and you decide in the Review queue. Designs already built on a design system keep their look when you archive it.

MCP servers

On the MCP tab, paste the server's configuration. A server can be remote, reached by a URL, or local, a command that runs on each member's computer.

The configuration cannot contain credentials. Each member signs in with their own account the first time they use the server, with Sign in in Customize, Connectors.

A new server starts On by default: it is on for every member who gets it until they turn it off. Make it Required to keep it on. The tool rules under Policies, Apps and MCP apply to it as to any other server, see Apps and MCP. When you change or archive a server, it leaves chats that are already open.

Apps

You cannot create an app in the console. A member shares an app they built from its page in PandaOS. Unless your Sharing policy says otherwise, it waits in the Review queue. Approving it publishes it read-only, under your organization's badge. See Review queue.

If a member already has an app of their own with the same identity, theirs wins and PandaOS shows them a note.

What members see

A published or updated item reaches every member it is meant for within about 5 minutes. It comes sooner if they restart PandaOS or click Refresh in Settings, Organization. Where each kind shows up is listed in What the Library is.