Runbooks and customer documentation live in the same system as your tickets.
Runbooks
Customers
Public Wiki
Customers › Bäckerei Krause › Network
Shared via share linkNetwork
The switch and router are in the storeroom.
In the wiki you maintain runbooks, solutions and the technical documentation of each customer, with tables, code, images and attachments. You reach the documentation of a customer directly from their customer record, and search finds it across all customers.
You share individual pages, such as a network diagram, with a customer via a link, without setting up an account for them, and revoke the link at any time. Guides for all customers are published in the public area of the customer portal.
The wiki is divided into the areas Runbooks, Customers and Public Wiki, and you arrange the pages in the page tree by dragging. In the editor you insert tables, code, callout boxes and checklists you can tick off. Images come from a shared library, and file attachments can be up to 25 MB.
There is no version history, no protection against simultaneous editing and no permissions per page. Skipper only hides deleted pages.
You create the documentation of a customer directly from their customer record, or it is created the first time you use “Document knowledge” on one of their tickets. Every new page in it automatically belongs to that customer.
The area starts with an empty home page; there is no template. The customer does not see their documentation in the portal, and the wiki is not a password vault.
The German full-text search covers the titles and text of all pages and highlights the match. If you wish, Skipper searches by meaning instead of matching words, through an integrated provider: OpenAI, Mistral, Ollama or an OpenAI-compatible endpoint.
Search by meaning is off by default and, once switched on, replaces the full-text search. Page content and search queries then go to the provider.
For any page you create a secret link, with its subpages if you wish, and revoke it at any time. Guides for all customers go into the public area, which the customer portal shows under “Wiki”.
Links have no expiry date and no password. Pages in the public area are on the internet immediately, and anyone in the team can share pages.
Customers › Bäckerei Krause › Network
Shared via share linkNetwork
The switch and router are in the storeroom.
A button opens the page in the AI chat of your provider, such as Claude. The assistant loads the content via the MCP server, through which it can also search, create and correct pages and upload images such as screenshots to the wiki. From a ticket, “Document knowledge” opens the chat with the task of going through the ticket and suggesting an addition or a new page in the customer wiki. By default, Skipper asks about this when you resolve a customer ticket on the ticket page.
The prepared message instructs the assistant to write only after your confirmation and not to copy credentials; Skipper itself does not enforce this. Because the wiki has no version history, whatever an assistant overwrites or deletes cannot be restored in the interface. Skipper only fetches images from public addresses, not from your internal network.
The customer record brings together contacts, tickets, time, projects, contracts and documentation in one place.
Your customers submit requests via a form, see the status of their tickets and reply directly.
Skipper connects to the AI provider of your choice, and AI assistants such as Claude work with tickets, customers, time and wiki via the MCP server.
As of Skipper 1.22.1, October 2026. This page describes this version.
We show you the areas that matter to your business, using your own workflows as the example.