Internal Knowledge Base Kit

A wiki is not a library, it is a switchboard — every page answers a question a real person asked, or it is deleted.

What it is

The internal wiki rebuilt as an operating instrument instead of a filing project. Decides what belongs in it and what belongs in an SOP, a decision log or nowhere; structures it around the task a reader is doing rather than the org chart; imposes one page shape with an owner and a review date; and installs the review bands, stale signal, deletion ritual and four usage numbers that keep it true. For founders, operations leads and anyone asked twice this week a question already written down somewhere nobody can find.

What you receive

an internal knowledge base people actually use — the scope decision that sorts reference knowledge from SOPs, decision logs and news, a structure and naming built on how people search rather than how the company is organised, the answer-first page standard, an ownership model putting a named owner and a review date on every page, and the pruning discipline, usage measures and deletion ritual that stop it becoming an archive of lies

Delivered as a single, complete .md skill file — open it, paste it into any capable chat model, and work. No installation, no account with anyone but us.

Supported models

• Claude (Opus/Sonnet)
• ChatGPT (GPT-4o/5)
• Gemini
• any capable chat model

People reach for it when

• “how to set up an internal wiki people will actually use”
• “our notion is a mess and nobody can find anything”
• “what goes in the wiki versus the sop”
• “internal documentation standard for a small company”
• “how do we stop our knowledge base going out of date”

Record

In the collection. The sale room is being fitted; this work goes on sale when it opens.

License

Free-shelf works ship under the DolceDrago House License — use the outputs freely, personal or commercial; the work file itself stays with the house.