Storing things is the easy half. This is the field guide to using them — each item type, in plain English, with the laziest workflow that works.
Live connection (MCP) — the agent reaches into your library on demand. Always your latest version. Set up once per tool on the Connect page.
Pulled files — npx -y @aistoragedepot/mcp pull writes your skills and prompts into each tool’s commands folder as typed /commands. Frozen copies: they work offline, and you re-run pull to refresh them.
See the same prompt twice in a slash menu? Both channels installed a button for it — (user) is the pulled copy, (MCP) is live. Pick the (MCP) one when both exist: it’s always current.
Free accounts include 25 pulls a month across both channels — plenty to try everything. Plus, Team, Group, and Company plans are unlimited.
A reusable message with [fields] — “Draft a cold outreach email from [Sender] to [Recipient] about [Topic].”
In the app: open it, click each field, fill, hit Copy result — or Send to ChatGPT/Claude to open your AI with it prefilled.
As a slash command: type the command, then just brain-dump in plain English on the same line — don’t try to remember the fields. The AI maps your words onto them and asks you for anything you missed. Typing the command with nothing after it works too: the AI interviews you, one question at a time.
A method the AI follows — “how to do a proper code review”, “how to write a conventional commit”. No blanks to fill; it’s knowledge, not a form.
Over MCP, don’t type a command — just ask: “review this diff the way my code-review skill says” and the agent goes and reads the skill mid-conversation.
As a pulled slash command: pressing it pastes the instructions into chat and the AI follows them on whatever you’re doing. (Skills only get slash commands from pull — over MCP they’re documents the agent reads, which is why they never show an (MCP) menu entry.)
Instructions a coding agent should always follow — TypeScript standards, review etiquette, “never use any”.
Main move: Download. The file comes out with the exact name and path your tool expects — AGENTS.md, .cursor/rules/*.mdc — drop it into the repo and every agent session obeys it automatically.
Over MCP: “follow my team’s TypeScript rules” — the agent fetches and applies them without the file ever landing in the repo.
Anything the AI should be able to look up — architecture notes, API conventions, onboarding guides, cheatsheets.
Over MCP: “check my deployment doc before answering” — the agent reads the current version on demand. No copy-paste, never stale.
Ready-to-use mcp.json snippets — which MCP servers a project should have. Download drops the file where it belongs; your whole team pulls the same tool setup from the shared library.
Prompt → slash command + brain-dump (or fill fields in-app) · Skill → ask for it by name, or press its pulled command · Rule → download into the repo (or let MCP apply it) · Doc → tell the agent to read it · Config → download into place.
And everything, of every type, can be copied, downloaded as a real file, shared with a link, or published to your team.