Open Source · MIT · Eleventy

Your agents know the answers.
Cairns makes sure the team does too.

Your team's knowledge is scattered across repos, Notion pages, Slack threads, and people's heads. Cairns gives an AI agent access to all of it — and produces a living knowledge base that anyone on the team can actually read.

Get Started View on GitHub →
$ git clone https://github.com/gorewood/cairns $ cd cairns && npm install $ npm run build # Eleventy builds articles → Pagefind indexes them → static site ready

The Problem

Knowledge is everywhere. Except where you need it.

Scattered across systems

Decision in a Slack thread. Context in a Notion doc. Implementation detail in a repo README. Getting the full picture means hunting through five tools.

Written once, then abandoned

Someone writes a wiki page. It drifts from reality within weeks. Nobody owns the update cycle. Stale docs are worse than no docs.

Locked in people's heads

Tribal knowledge is bottlenecked through whoever was in the room. New hires, adjacent teams, and future-you all start from zero.

The Solution

One agent. Every source. One place to read.

Give your agent access to repos, docs, Notion, Slack — whatever your team uses. It synthesizes what it finds into well-structured articles anyone can read, with links back to the source of truth for deeper dives.

src/articles/2026-04-02-api-versioning.md
--- title: "API Versioning Without the Grief" subtitle: "Three strategies, one clear winner for your stack" date: 2026-04-02 tags: [api, architecture, patterns] submitter: Agent duration: 14 status: published lead: > URL-path versioning feels natural until you have thirty endpoints and a mobile client on v2... --- # Agent researches, writes markdown, builds the site. # Articles auto-appear in trailhead, library, archives, and tag pages.

cairn

A single knowledge article. Self-contained, well-researched.

trail

A multi-part series. Linked with prev/next navigation.

trailhead

The homepage. Trails, featured articles, recent entries.

Features

Built for reading. Designed for agents.

The output is a polished static site your team will actually want to read. The input is markdown your agent already knows how to write.

Trails

Multi-part series with automatic prev/next navigation. Group deep dives into coherent learning paths.

Rich callouts

Key takeaways, tips, warnings, and definitions. Color-coded containers your agent writes in markdown.

Pagefind search

Full-text static search built at compile time. No server needed. Find any concept across all articles instantly.

Dark & light mode

System preference detection with manual override. Smooth transitions. Persisted in localStorage.

Auto-organized tags

Tag your articles in frontmatter. Library view, tag index pages, and archive pages generate automatically.

Scroll animations

Sections fade in as you scroll. Progress bar tracks reading position. Respects reduced-motion preferences.

Philosophy

A first stop for everything your team knows.

Without Cairns

  • ● Context scattered across Slack, Notion, repos, wikis
  • ● Understanding requires access to every system
  • ● Onboarding means shadowing whoever was in the room
  • ● Nobody has time to synthesize it, so nobody does

With Cairns

  • ● Agent pulls from every source into one readable hub
  • ● Written for learning — not reference dumps
  • ● Links back to source systems for deeper dives
  • ● Readers give feedback, agent makes corrections

The knowledge hub that ties together everywhere your team works.

Integrations

Works with any agent.

The OpenClaw skill teaches your agent the content format, publication workflow, and maintenance routines. Ask it to write about something new and it researches, drafts, and publishes. Tell it something's wrong and it corrects. Other agent frameworks are an exercise left to the reader.

OpenClaw Claude Code Gemini CLI Cursor any CLI agent
skill/cairns/SKILL.md
# The skill file teaches your agent: 1. Research — web search, source code, internal docs 2. Write — markdown with callouts, scenarios, diagrams 3. Publish — build, verify, commit, push 4. Maintain — freshness checks, broken links, tag cleanup # Drop skill/cairns/ into your agent's skill directory. # It handles the rest.

Get Started

Three steps to your first cairn.

1

Clone and install

$ git clone https://github.com/gorewood/cairns $ cd cairns && npm install
2

Customize for your team

Edit the guide page, site config, and tag vocabulary to match your team's domain.

# Your team's identity $ $EDITOR src/_data/site.json # title, description, url $ $EDITOR src/guide.md # how your team uses Cairns
3

Teach your agent

Point your agent at the skill directory. It learns the format and starts writing.

# The skill/ directory contains everything the agent needs. # Copy it into your agent's skill path, or reference it directly. $ ls skill/cairns/ SKILL.md references/
Read the guide →