Advanced usage

Full-power setup

To use Wikilayer at full power, connect your agent, give it repeatable skills, and use the advanced surfaces below when a workflow needs them.

Wikilayer skills

Ready-made skills that audit a Wikilayer wiki against the agent rules, the anti-patterns and the writing style. Each one takes a whole wiki or a single page. An audit pass only reports findings; a skill that writes to the wiki says so below.

Set them up in Claude Code or Codex. Source: github.com/wikilayer/skills.

The .md address

Appending .md to any wiki or page URL of a public wiki returns the whole page as markdown, and the HTML twin advertises it with <link rel="alternate" type="text/markdown">, so an external crawler finds it without being told. On a multilingual wiki the address keeps its language segment, and the closing list of inbound links stays inside that language.

Through MCP, an agent gets the same document with get_page_markdown. Each node is preceded by a comment carrying its id, so the agent can read the page as a whole and then edit the right block. This authenticated route works for private wikis too. Use it before a structural edit to understand the page in context and afterwards to confirm that the result still reads as one document.

A bare .md URL for a private wiki returns 404 because a URL-following agent cannot authenticate there; use the MCP tool instead.

Tags

A node's place in the tree is one axis; a tag is another. Tags are case-insensitive labels you attach to mark a set that cuts across the hierarchy: every block that is required reading, every page still in draft, every entry that needs a source.

Attach them in create_nodes (the tags field) or across existing nodes with tag_nodes. Pull the whole set back with search_nodes passing tag and no query, which returns it in tree order; add a query to search within the tag. list_tags names every label a wiki defines and how many nodes carry it, which is where the name those calls take comes from. update_tag renames or recolours a label, delete_tag removes it.

Wiki rules

Rules tell every connected agent what belongs in a wiki and how it should be written. Open Rules in the wiki and ask your agent to create or change them—for example: Write the rules of this wiki: what belongs here, how pages are named, and which sources count. There is no rules editor in the web UI; the page appears when the agent writes the first rule.

Every agent writing through MCP is served these rules and must confirm that it has read them before it can change the wiki. Use the agent rules as a starting point, then add the conventions specific to your project.