Docmost is a team wiki that rewards good structure: spaces for each team, nested pages, real-time co-editing. On your OpenSysLab server it ships with a vibe-code agent inside the Open WebUI chat — an assistant that can read Docmost’s files, query its database, run commands, and restart services. Here are ten everyday jobs you can hand to it, from first-day setup to weekly upkeep.

1. Build your space structure on day one

Most wikis die in the first week because nobody builds the skeleton. Describe your teams and the agent creates the spaces — Engineering, Sales, Operations — with a sensible nested page tree under each: an Onboarding section, a Runbooks section, a place for meeting notes. It drafts placeholder pages so nothing is empty, orders the sidebar, and flags which space permissions you should review before people join. Try: “Create spaces for Engineering, Sales, and Operations, each with Onboarding, Runbooks, and Meeting notes sections and two starter pages in each.”

2. Turn a spoken process into a runbook page

You know how refunds work; writing it down is the part that never happens. Describe the process out loud in chat and the agent drafts a structured page: numbered steps, a callout on the step people always get wrong, a toggle block hiding the edge cases. You review the text, correct two sentences, publish. What was tribal knowledge becomes a page a new hire can actually find. Try: “Write a runbook for processing refunds: five normal steps, a warning callout about the 30-day limit, and a toggle block for the edge cases.”

3. Get the diagram you’d never draw yourself

Every team has that architecture page that is just a wall of text. Docmost renders Mermaid, draw.io, and Excalidraw diagrams inline, but nobody wants to fight diagram tools after lunch. Describe the flow and the agent writes the Mermaid code, checks the syntax, and tells you exactly where to paste it. The page goes from unreadable to the one people link in interviews. Try: “Add a Mermaid flowchart to the Deployments page showing how a change moves from pull request to production, including the rollback path.”

4. Move your old notes in

You are not starting from zero: there are Notion exports, a folder of Markdown files, maybe an old Confluence dump. The agent inspects the export, fixes broken image links and heading levels, splits monster files into separate pages, and prepares a ZIP that Docmost’s importer accepts — or walks you through the built-in Notion and Confluence import if page-by-page structure matters. Big imports take a while; the agent runs them and checks the result instead of you babysitting a progress bar. Try: “I exported our Notion workspace as a ZIP — clean it up and get it into the Engineering space without breaking the images.”

5. Rescue a page someone broke

With real-time editing, accidents happen: someone selects all, pastes, and the pricing page is gone. Ask the agent to open the page history and it diffs the versions, shows you exactly what changed since Friday, and restores the last good one — or copies Friday’s version into a new page so you can salvage pieces. Nothing is lost as long as history exists, but most owners never click that history icon until it is too late. Try: “The pricing page got mangled this morning — show me what changed since Friday and restore the last good version.”

6. Tidy a page tree that grew wild

After six months, every wiki has “Untitled” pages, three near-duplicate onboarding docs, and a sidebar nobody can navigate. The agent audits the tree: it proposes better names for vague titles, merges duplicates while keeping their history, and moves strays into the right sections. It shows you the plan before touching anything, so the merge you disagree with never happens. Try: “Find all pages called ‘Untitled’ or ‘New doc’, propose better titles, and merge the duplicate onboarding pages into one.”

7. Answer “where do we keep X?”

Half of a wiki’s value is retrieval. Ask where the API-key rotation procedure lives and the agent runs a full-text search across your spaces — the same index the search box uses — and answers with the page link, or tells you honestly that it does not exist. When it doesn’t, it can draft the missing page right there so the next person finds it instead of asking you. Try: “Where do we document how to rotate API keys? If it isn’t written down, start a page for it.”

8. Turn raw meeting notes into a page worth reading

Paste the notes you scribbled during standup and the agent turns them into a proper page: decisions up top, action items in a table with owners and due dates, discussion points collapsed under toggle blocks. It files the page under the right space, dates the title, and links any related pages you mention. Your raw notes stay yours; the readable version is what the team searches three months later. Try: “Turn these standup notes into a page — Decisions section up top, then a table of action items with owners and due dates.”

9. Make invitation and mention emails actually arrive

Docmost sends invitations and mention notifications by email, but only if SMTP is configured — and most self-hosted installs skip this on day one. The agent sets the SMTP variables in your environment file, restarts the app, sends a test invitation, and reads the mail server logs when a provider rejects the message. It is ten minutes of work that makes “@mention someone” actually notify them. Try: “Set up SMTP with our mail server so invites and mention emails arrive, then send me a test invitation.”

10. Open a public help center from existing pages

Some of your pages are already customer-ready. Docmost can publicly share any page by link, no login needed. The agent helps you pick the candidates, moves them into a Public space, turns on sharing for each, and produces the list of links to embed in your website or app. One caution it should repeat back to you: anyone with the link can read it, so public means public. Try: “Pick the ten pages that belong in our customer help center, move them to a Public space, and turn on public sharing for each.”

Start with the one job that nags you every week. The agent does the work, shows its steps, and everything stays on your server. See Docmost on OpenSysLab.