Propose and publish a library change
Propose a change to a skill, agent or rule in your org's library, get it reviewed, and publish it to every session.
The library holds your org's kit: skills, agents, instructions, rules, standards, knowledge docs, workflows, MCP entries, guides, templates and brand kits. Each one is an asset with versions. A new session gets the published versions, built for its harness. Nothing reaches a session until someone publishes it.
The library is a module: with it off, your org has no Library. Guests can read what they're given but can't add to it.
How scopes stack
Every asset has a scope: The whole org, A teamspace, A product or Just me. A session gets them in that order, from the org down to you. Instructions, rules, standards, guides and knowledge add up. A skill, agent, workflow, MCP entry or template with the same name replaces the outer one, unless the outer one is mandatory.
Find what's there
Open Library. The views help you find your part: Needs my review, Used in my sessions, My changes, Past review date and Unused for 60 days. Filter by kind, scope or tag. An asset with a pending edit shows Change open.
Add a new asset
Press New asset
Admins also see Import, which starts the same flow from a file. See Bring your existing kit.
Answer three questions
- What are you adding? A skill, agent, instruction, knowledge doc, standard, workflow, MCP entry, rule, guide, template or brand kit.
- Who is it for? Pick the scope, and the teamspace or product when you choose one.
- Start from: Blank, a starter, Generate (describe it and an assistant drafts it; desktop app only) or Import (paste text, upload a file, a GitHub URL, a file in a repo, or the MCP registry).
Write it
Fill in the properties and the text. Checks run as you go. Then Submit for review.
- Just me needs no review: only you see it, and it publishes at once.
- If you approve changes at that scope yourself, it publishes as the first version.
Change an existing asset
Open the asset and press Request change: "Opens a change from the current text for an admin to review and publish." Say what should change, then edit the draft. On an asset of your own, the button is Edit, and your asset is published again as soon as you save.
From a session you can propose too. Ask the assistant to draft the change; it uses the library_propose
and library_draft_edit tools after you approve. These never publish: the change waits for review like
any other.
To share one of your own assets, use Promote to the teamspace or Promote to the org. It opens a change, and nothing is shared until it is published.
Review a change
A change page holds everything a reviewer needs:
- The diff against the published version, block by block.
- Checks: the Agent Skills validator, each harness's budget, links and mentions, and a secret scan. "No findings" means there's nothing to fix.
- Output per harness: what a new session on each harness gets from this asset. Built means the harness loads it natively; Pointer means the instructions name the file to read; Not supported means that harness can't take it.
- Comments on the change and its lines.
The author can Submit for review again after an edit, or Withdraw the change. A reviewer has:
- Approve and publish, with a Version bump of Patch, Minor or Major.
- Request changes, with what to change, so the author knows.
- Reject, with a reason.
Some changes need an org admin
A change that touches a power field, an MCP server or a mandatory asset is published by an org admin: "This change is held for an org admin, who publishes or rejects it."
After you publish
Sessions that start from now on get the new version. A running session keeps the version it started with. The chip in a session shows which library version it launched with.
Two actions undo a publish:
- Yank a version: its files are deleted, and sessions that loaded it are told. Give a reason.
- Retire the asset, so new sessions stop getting it.
Your org admin can stop all publishing with the library_publish switch; your own Just me
assets still save.
Related
- Bring your existing kit
- Start a session: what a session gets from the library
- Roles and access
Something wrong or missing? Suggest a change
Pick up a teammate's session
Hand off a session: pick up a teammate's work as your own fork, or continue your session in another harness without losing context.
Bring your existing kit
Bring your AGENTS.md, CLAUDE.md, skills and agents into EasyCode, and see how each harness gets them in every session.