Standardize how an AI-collaboration project turns work into reusable knowledge. Use when initializing or retrofitting Project Cairn in a project, recording progress after meaningful work, maintaining AGENTS/CLAUDE/cairn docs, auditing project knowledge for drift or missing records, pulling and citing external knowledge, or graduating validated project experience into a reusable knowledge base.
npx skills add https://github.com/iBlinkQ/project-cairn --skill project-cairn
Project Cairn gives AI-collaboration projects a durable way to keep and reuse what they learn while doing real work. The Skill supplies the method, AGENTS.md carries always-read project rules, and .cairn/config.yaml stores machine-readable configuration.
This Skill is documentation-first. It provides instructions, templates, references, and provider adapters. It has no CLI, MCP server, background hook, chat-end trigger, automatic provider write, or automatic history migration. Routine maintenance happens during normal work because AGENTS.md carries the rules. Provider writes require human confirmation.
Load exactly the reference you need:
references/init.md — initialize, retrofit, bootstrap, or set up Project Cairn in a project.references/consume.md — pull, cite, reuse, or apply external knowledge from the configured knowledge base.references/maintenance.md — record progress, update LOG, update ROADMAP, maintain topic notes, or apply Cairn rules after work.references/audit.md — inspect, audit, validate, clean up, or find missing project knowledge records.references/upgrade.md — upgrade an initialized project instance to the current skill spec, or check how far it has drifted (instance drift after the skill itself evolved).references/graduation.md — graduate knowledge, move reusable experience to a knowledge base, or judge graduation-readiness; a provider write additionally reads only the selected references/graduation/<provider>.md.references/frontmatter.md — create or review Cairn topic notes or knowledge-base notes.references/branch-closure.md — review, close, abandon, or roll back an exploration branch and salvage its cairn/ knowledge before it disappears.references/zh-glossary.md — writing project docs in Chinese (or resolving what a Chinese term should be); fixed English↔Chinese terminology mapping for Project Cairn's own vocabulary.The description frontmatter describes triggering situations, not the workflow in detail.
assets/templates/ holds templates used by init and by later triggered actions: AGENTS.md, CLAUDE.md, config.yaml, LOG.md, ROADMAP.md, topic.md, Cited.md. init only scaffolds the core set (AGENTS.md, CLAUDE.md, .cairn/config.yaml, cairn/LOG.md, and optionally cairn/ROADMAP.md); topic.md, Cited.md, and Reference/ are created on first trigger, not pre-stamped. Templates use {{PLACEHOLDER}} tokens; never hardcode a specific provider or knowledge path into a template.
AGENTS.md is read as project rules.scripts/*.sh are bash — verified on macOS/Linux; Windows users need WSL or Git Bash. scripts/*.py scripts only need a Python 3 interpreter, no shell required.This skill should be used when the user asks about "plugin settings", "store plugin configuration", "user-configurable plugin", ".local.md files", "plugin state files", "read YAML frontmatter", "per-project plugin settings", or wants to make plugin behavior configurable. Documents the .claude/plugin-name.local.md pattern for storing plugin-specific configuration with YAML frontmatter and markdown content.
-Automatically convert documentation websites, GitHub repositories, and PDFs into Claude AI skills in minutes.
This skill should be used when the user asks about "plugin settings", "store plugin configuration", "user-configurable plugin", ".local.md files", "plugin state files", "read YAML frontmatter", "per-project plugin settings", or wants to make plugin behavior configurable. Documents the .claude/plugin-name.local.md pattern for storing plugin-specific configuration with YAML frontmatter and markdown content.
Persistent memory and context management for AI agents using OpenContext. Keep context across sessions/repos/dates, store conclusions, and provide document search workflows.
> PARA method knowledge management for Obsidian vaults. Use this skill whenever the user wants to organize notes using PARA (Projects, Areas, Resources, Archive), classify a note into a PARA category, route a note to the right vault folder, normalize frontmatter fields, run a PARA hygiene review, suggest archiving, audit vault structure, or process new knowledge inputs into an existing PARA-based vault. Also trigger when the user mentions inbox processing, vault cleanup, note classification, PARA review, or asks "where does this note belong?". Works with existing Obsidian skills (obsidian-markdown, obsidian-cli) — never replaces them.
Keeps implementation and specs in sync. Use when working on a feature that has a spec in .agents/specs/, when the user says /spec, or when starting implementation of a documented feature. Also use when the user asks to verify implementation against a spec or update a spec after changes.
Build and query AI-powered knowledge bases from claude-mem observations. Use when users want to create focused "brains" from their observation history, ask questions about past work patterns, or compile expertise on specific topics.
(builtin) Initialize hierarchical AGENTS.md knowledge base
Take iblinkq/project-cairn from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.