Docusaurus
for LuumenAI
Turn Docusaurus SOPs and runbooks into skills LuumenAI can follow.
Turn what your team wrote down in Docusaurus into something that runs. LuumenAI searches SOPs and runbooks, follows them step by step, and can package a page into a shared skill — with updates written back only after review.
The Docusaurus toolbox
15 tools: 10 read, 5 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadSearch pagesFind SOPs, runbooks, and post-mortems relevant to the current work.
- ReadRead page contentBring the procedure into the thread so it can become a skill.
- ReadTurn a page into a skillConvert a runbook into a reviewed, reusable LuumenAI skill.
- ReadList spacesSpaces, wikis, or folders you can read.
- ReadGet page historyWho changed a page and when.
- ReadList attachmentsFiles attached to a page.
- ReadGet page linksPages that link here or are linked from here.
- ReadSearch by labelPages tagged for a system or team.
- ReadGet recently updatedWhat changed in a space this week.
- ReadCompare versionsDiff two versions of a page.
- WriteCreate or update pageWrite back what changed, with the run linked. Approval by default
- WriteAdd commentLeave a note on a page for its owner. Approval by default
- WriteMove pageReparent a page as an approved edit. Approval by default
- WriteAdd labelTag a page for discovery. Approval by default
- WriteArchive pageRetire a page with a redirect note. Approval by default
One prompt, start to finish
What a governed Docusaurus run looks like inside Luumen.
Questions
Authorize once with OAuth 2.0. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — create or update page, add comment, move page, add label, and more — is shown as a plan and requires approval by default. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Docusaurus — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
ConfluenceSOPs and runbooks that become skills the whole team can run.
NotionRunbooks in Notion, followed and turned into skills.
SharePointRead SharePoint sites for context, then change files and permissions on approval.
Google DriveSearch Drive for the file you need, then write the change back as an approved stepPut Docusaurus to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.