Using the Shelf
A shelf for packaging your AI setup (skills, plugins, MCP settings, instruction files and more) so you can hand it over. Members of your organization get it from the shelf; people outside get a link with an expiry date.
What the Shelf is
Hand things over inside and outside your organization
Open it from the book icon next to "…" at the top right of the chat screen (or Business → "Shelf"). Everything on the shelf can be viewed and saved by every member of the same organization. For people outside, create a link with an expiry date.
Who can do what
| Action | Who |
|---|---|
| View and save | Every member of the organization |
| Upload, create links, draft descriptions with AI | Members of organizations on the Starter plan or above (also available during the 7-day trial after signing up for the free plan) |
| Edit descriptions and delete | The uploader, and owners and admins |
| Stop a link | The person who created the link, and owners and admins |
Organizations that go back to the free plan can still view and save what is on the shelf.
What you can share
Seven types
| Type | What you share | What the receiver does |
|---|---|---|
| Skill | Instructions for Claude Code and other AIs (a folder with SKILL.md, zipped) | Put the folder in ~/.claude/skills/ or the project .claude/skills/ |
| Plugin | A bundle of skills, hooks, MCP servers, and commands (with .claude-plugin) | If it has marketplace.json, run /plugin marketplace add then /plugin install. If not, load it with claude --plugin-dir |
| MCP connection | Where and how an AI connects to an outside tool (no keys inside) | Paste it into .mcp.json or register it with claude mcp add. The receiver adds their own key |
| Instruction file | Templates such as CLAUDE.md and AGENTS.md that an AI always reads | Put it at the top of the project and adjust it to their setup |
| Hooks and automation | Things that run automatically before or after the AI runs a command (settings.json hooks and scripts) | Read them first, then add them to the hooks in settings.json |
| Tools and scripts | Tools that run on Python or Node | Follow the README |
| Guides and templates | Documents, prompt collections, and templates | Open, read, or paste |
Letting people use your tools without handing over files
If people connect to the UNIHUB or RUNner MCP, your tools keep running on your side while they use them. Put that connection guide on the shelf as an MCP connection.
Upload
Upload from the web app
- Open the Shelf and choose the organization at the top right
- Under "Add to the shelf", choose the type and title, then drop the file (or "Choose a file")
- When the upload finishes, the description fields open. Fill in "What it does", "How to install", and "License and notes", then press "Save"
Files you can upload
Up to 100 MB per file. Files count toward your organization's plan storage (together with chat attachments). .js, .ts, .html, .exe and similar files cannot be uploaded as is, so zip them.
Draft a description with AI
Press "Edit description" → "Draft with AI" to read the uploaded file and draft "What it does" and "How to install". It reads md, txt, and json files as they are; for a zip, it reads only SKILL.md, README, plugin.json, CLAUDE.md, and AGENTS.md inside. Nothing is shown to others until you save. Up to 30 per organization per month.
Upload from AI
Upload directly from a customer's AI
AIs such as Claude Code and Codex can put files on the shelf directly. The same rules as the web app apply.
- Create an API key with write permission in Settings → API keys
- Add the MCP settings from "Upload from AI" on the Shelf to your AI (replace the key with your own)
- Ask your AI to zip a folder and put it on the shelf
The AI can use five tools: shelf_list (view the shelf), shelf_begin_upload (start an upload), shelf_finish_upload (finish it), shelf_update (write descriptions), and shelf_create_link (create a link). Deleting is only available from the web app.
Handling API keys
An API key acts as the person who created it. Do not give it to others or share it in files. You can stop it on the API keys page when you no longer need it.
Share with a link
Create a link with an expiry date
Press "Create link" on a shelf card and choose an expiry (1 to 30 days). The link is shown only when you create it, so copy it right away. If you lose it, create a new one.
What the receiver sees
Opening the link shows "What it does", "How to install", "License and notes", and a save button, with no sign-in.
Stop a link
You can stop links at any time under "Active links". A stopped link stops working right away. Links also stop working when:
- The expiry date has passed
- The file was deleted
- The person who created the link left the organization
- The organization went back to the free plan
Install with RUNner
Have it installed on your PC with one button
Members who can use RUNner and are on a tier that can send requests to a PC AI see an "Install with RUNner" button on each shelf card. Pressing it creates a goal named "Shelf: install ...", and the AI connected to your PC runner (Claude Code, Codex, and others) downloads the file and installs it following the install steps.
- Press "Install with RUNner"
- When the PC AI finishes, it writes where it installed the file in the goal's notes
- Check it on the goal page and finish the goal (a person confirms the end)
Good to know
- If you have not registered a PC runner or it is paused, a hint is shown instead of the button (connect it from "Connect AI" in RUNner)
- The link the AI uses to download the file is only for the person who pressed the button and is valid for 7 days while the goal is open. It stops working if that person leaves the organization or the file is deleted. If your PC was off for more than 7 days, press the button again
- Pressing it again for the same file reuses the open goal instead of creating a new one
- The goal tells the AI not to overwrite existing folders or settings with the same name, and to stop and ask instead
- It counts toward your RUNner request quota
Good to know
Actions are recorded
Uploads, saves, link creation and stopping, and downloads by people outside are recorded in your organization's audit log (Settings → Audit log).
Do not include keys or passwords
Do not upload MCP settings or scripts that still contain keys, passwords, or tokens. Leave them for the receiver to fill in with their own.