Knowledge

Wiki and knowledge

Write down your operating rules and criteria, and people and AI agents alike can work by them.

Keep operating procedures, status definitions, the criteria for making articles and task-by-task playbooks in the admin's wiki, written in Markdown. Every page can be handed to AI agents and outside writers by URL, so rules that people read and revise carry straight into the next piece of work.

Prerequisites

Works without any external service. AI agents read and write through MCP.

All features

01Wiki

Keep your procedures in a linked-up wiki

An internal wiki for operating notes, procedures and handovers, written in Markdown. Write [[slug]] in the body to link pages together; a link to a page that doesn't exist yet can be clicked to create it. Set a parent page to build a hierarchy, and filter the tree on the left to find the page you need.

Link pages with [[slug]]-style internal links
Create a new page straight from a link to one that doesn't exist yet
Organize pages into a tree by setting a parent
Every page can be shared by URL as Markdown or HTML

02Wiki page

People and AI agents work by the same rules

For example, put your task status definitions on a single page, with a table of what each status means and who is allowed to set it. Have AI agents read the page through MCP when they start work, and they move tasks forward under the same rules as people. To change a rule, just edit the wiki page.

Spell out each status's meaning and who may set it in a table
AI agents fetch the page through MCP and refer to it
Share boundaries such as “only a person can mark a task done”

03Knowledge base

Your criteria for making articles, one topic per page

A knowledge base that organizes the criteria for making articles and creatives, one topic per page. Record the points writers tend to get stuck on — FAQ headings, approved copy you can use as-is, allowed and banned terms, disclaimer templates for the end of articles — as the reference everyone works from. All pages are also available as a single Markdown file at one URL, so an AI agent can read them in one go.

Part of the wiki, edited and linked like any other page
Child pages are listed and told apart by their slugs
Fetch every page as one Markdown file from a single URL

04Skills

Hand off work with a playbook (skill) URL

Keep a playbook (skill) for each kind of work — writing articles, curating keywords, improving SEO, deploying — one skill per page. When you ask an outside writer or an AI such as ChatGPT or Claude to do the work, just pass along the page's public URL. The Claude Code skills introduced on the Skills page keep their playbooks in this wiki, too.

One skill per page, with procedures kept separate for each task
Pass a skill's public URL as-is when you commission work
Procedures that people revise are used from the next request on

* Screens use sample data, with some details such as article titles and keywords blurred. The admin is shown in Japanese. Click to enlarge.

Explore other features

Questions about adopting or running Autorial? Talk to us.

Back to all features Talk to us