What a Tool is

A Tool is a ready-made way of working that somebody on this server has packaged up: a board with its lists, folders, tags, wiki pages and rules already in place, the skills that tell your AI assistant how to use that board, and the docs that explain it. Job Search, an automated job search, is one.

You'll find the Tools you can use under Tools in the menu: your own, the ones shared with you, and the ones listed for everyone here.

Installing one

Open a Tool and pick the assistant you use — Claude on the website or app, Claude Code, or ChatGPT — and follow its steps. They come to the same thing: connect your assistant to Slipdock, add the Tool's skills to it, and then start a chat and say “Set up … for me.”

The assistant then asks Slipdock to build the Tool's board, which it does the same way for everybody, and talks you through filling it in. You can also build the board yourself with Make the board on the Tool's page. Either way you get one board per Tool: asking again finds the board you already have.

Before you install

A Tool's skills are instructions your assistant follows with your access to your boards. So the Tool's page shows everything before you install it: the board it will build, the files it adds, and every skill file in full. Read them as you would anything you let act for you.

  • Installing touches only the new board it makes, never your other boards.
  • A published version never changes. A new version has a new number.
  • A Tool listed for everyone has had that version approved by an admin; a newer version isn't shown to you until it has been approved too.

New versions

When a Tool you've installed has a newer version, its page offers Upgrade the board. Upgrading adds what your board is missing — new lists, folders, tags, pages, rules and files — and leaves everything you've changed exactly as it is. A page you've edited is never overwritten. Update the skills the same way you added them.

How your board plans: Principles and Playbook

The built-in handbook Tool gives a board two pages that say how its work is decided and planned. Principles are the tie-breakers: where a change could go two right ways, which one this project takes. Each is a short paragraph and a matching PRIN rule, which agents keep to and a verifier checks. It starts with three that suit most projects (one place for each concern, the obvious reading of an ambiguous ask, extend before adding and split what has grown).

The Playbook is what an agent follows when you ask it to plan ("I want to build…", "break this into cards"): it sizes the ask as a card, a feature or a system, then runs the stages that size takes (grill, decide, principles, spec, cards), each writing to a handbook page or to cards. A one-sentence ask stays one card. Its Defaults line can name a page of your own stack and hosting choices; those are proposed and asked about, never imposed.

Editing these two pages is how a board changes its process: an agent reads them as they are now. A new principle is a rule, so an agent proposes it and you decide. Installing the Tool again replaces a page that still holds the first, empty version with this baseline, and never touches one you've edited.

Publishing your own

Put the Tool in a folder (see the next part) and publish it with the CLI:

slipdock tools publish ./my-tool

Or, without the CLI, pack the folder as a .tar.gz (tar czf my-tool.tgz my-tool) and upload it under Publish a Tool on the Tools page. The name in its tool.json decides whether it is a new Tool or the next version of one of yours; your Tool's own page takes its next version too.

Its page then appears under Tools for you alone. Publish again with a higher version for each change; the same version twice is refused.

To start from a Tool that is already published, yours or one you can see, take the whole package — every file at its path — with Download the package on its page, or:

slipdock tools download my-tool

Unpack it, change what you need, raise the version in tool.json, and publish it again, with the CLI or by uploading it. Somebody else's Tool keeps its name, so publish a copy under a new name.

The package

  • tool.json: name (lowercase, unique on this server), version (like 1.0.0), summary, and optionally title, author, requires and files.
  • README.md: the docs, shown as the Tool's page.
  • board.json: the board — lists (each with a role: ready, backlog, doing, done or dropped), folders, tags, pages (skeletons, which may use {{board.name}} and {{today}}) and automations (ready-made rules by preset name; a rule that sends cards to a runner can carry the prompt its jobs are given).
  • skills/<name>/SKILL.md, with front matter naming the skill and saying when to use it, and anything else the skill needs beside it.
  • files/: each listed in tool.json as going on the board (into a Tool folder in its wiki) or local (beside a skill, on the installer's machine).

Slipdock checks all of it when you publish and says exactly what is wrong — a list meant to be the ready list that wouldn't be read as one, a rule on a list that doesn't exist, a file not listed in tool.json.

A skill can fetch any file of its Tool while it runs, by its path in the package (/api/tools/<name>/files/skills/<skill>/SKILL.md, or list_tools with file), from the newest version you can see. So a short skill can read its steps from the server and follow a new version without being installed again. A Tool's board files are read from the board's Tool folder with /api/boards/<board>/files/Tool/….

Sharing and listing

On your Tool's page, share it with people by email; they can read it and install it. To offer it to everyone on this server, ask an admin to list it. Admins approve one version at a time, under Tool listings, so each new version is approved before it reaches anyone you haven't shared it with.

Skills from elsewhere

Skills are also published outside Slipdock, often as a GitHub repository of SKILL.md files. Under Skills in the menu, add one by its URL: a repository, a folder or one file in one, or a SKILL.md at any https address. Slipdock fetches each skill in it (or the README, when there are none) and keeps it with its name, description, version, licence and when it was fetched. Open a skill to read the whole file before anything follows it.

  • Only public addresses are fetched, redirects aren't followed, and a file over the size limit is left out. What was left out, and why, shows under the source.
  • Refresh fetches the source again and says which skills were added, changed or removed; Remove deletes it and its skills.
  • Your sources are yours alone. The ones listed under On this server are there for everyone, and only an admin changes them.
  • A new server starts with one, mattpocock/skills, enabled on no board. An admin adds another by ticking For everyone on this server when adding it.

To give a skill to a board's agents, open it and Enable this text on a board you can write to. The board keeps the text you read: a refresh that changes the skill shows Changed upstream with the lines that differ, and the board's agents keep the old text until somebody who can write to the board reads the change and re-pins it. A stage of a board's Playbook asks for a skill with a skill: <name> line; the Skills page lists those stages and flags one whose skill nothing provides.