Updated today
by inkeep
open-knowledge
Beautiful, AI-native markdown IDE and LLM wiki
4.6k GitHub stars (4,585)
+256 in 20 days
| Period | New stars |
|---|---|
| Sep 27 | 0 |
| Sep 28 | +8 |
| Sep 29 | +9 |
| Sep 30 | +9 |
| Oct 1 | +1 |
| Oct 2 | +13 |
| Oct 3 | +5 |
| Oct 4 | +2 |
| Oct 5 | +6 |
| Oct 6 | +8 |
| Oct 7 | +12 |
| Oct 8 | +11 |
| Oct 9 | +15 |
| Oct 10 | +44 |
| Oct 11 | +46 |
| Oct 12 | +17 |
| Oct 13 | +17 |
| Oct 14 | +12 |
| Oct 15 | +14 |
| Oct 16 | +7 |
- 18 skills (18 skills found in its SKILL.md files)
- 311 forks (311 forks)
- Today last update (Last updated today)
Install
Skills CLI
npx skills add inkeep/open-knowledge
Asks which skills and agents to install. Just one: npx skills add inkeep/open-knowledge --skill open-knowledge-discovery — add -g for every project.
Claude Code
git clone https://github.com/inkeep/open-knowledgecp -r "open-knowledge/packages/server/assets/skills/discovery" ~/.claude/skills/
Copies the open-knowledge-discovery skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.
Plugin
/plugin marketplace add inkeep/open-knowledge
Run inside Claude Code if the repository ships a plugin marketplace, then pick plugins from /plugin.
Skills can run code on your machine — read the SKILL.md first.
What it does
In the author's own words, from each skill's SKILL.md.
-
open-knowledge-discovery
Read when the user asks what OpenKnowledge is, wants to install it on a repository, wants to open or preview a single markdown file that is not part of an OpenKnowledge project, wants to share an OpenKnowledge project with collaborators, asks whether OpenKnowledge supports a particular capability, or asks how `ok init` / `ok cowork` / OK Desktop set up a project. Do NOT load to perform OpenKnowle…
packages/server/assets/skills/discovery/SKILL.md on GitHub (opens in a new tab) -
open-knowledge
Authoritative agent-runtime contract for working inside an OpenKnowledge project — a markdown-CRDT knowledge base exposed over MCP. Use whenever reading, listing, searching, editing, or linting any `.md` or `.mdx` file in the project, and before any `mcp__open-knowledge__*` tool call (`exec`, `search`, `write`, `edit`, `lint`, and the rest). Installed by `ok init`, so its presence means this is a…
packages/server/assets/skills/project/SKILL.md on GitHub (opens in a new tab) -
open-knowledge-write-skill
Use when the user wants to create, author, write, or design a new Agent Skill (a SKILL.md) — for OpenKnowledge or for their editors — including requests like 'help me write a skill', 'make a skill that…', 'turn this workflow into a skill', or improving an existing skill's triggering and discipline. Also use when capturing reusable agent guidance that should live as an installable skill rather tha…
packages/server/assets/skills/write-skill/SKILL.md on GitHub (opens in a new tab) -
codebase-wiki
How to work in a Codebase Wiki project (the `codebase-wiki` starter pack): an agent-authored, source-grounded wiki of the surrounding codebase. Read when the project has a `wiki/` knowledge base with `architecture/`, `modules/`, `flows/`, `concepts/`, and `guides/` sections plus `wiki/OVERVIEW.md`, or when asked to generate or refresh a wiki of this codebase. Carries the per-folder rules and fres…
packages/server/assets/skills/packs/codebase-wiki/SKILL.md on GitHub (opens in a new tab) -
personal-crm
How to work in a Personal CRM project (the `entity-vault` starter pack, GBrain-compatible): a typed-entity vault of people, companies, meetings, and concepts, each a dossier with a rewritable summary plus an append-only timeline. Read when the project has these folders, OR when asked to capture notes about a person or company, log a meeting, prep for an upcoming meeting, or answer who someone is…
packages/server/assets/skills/packs/entity-vault/SKILL.md on GitHub (opens in a new tab) -
knowledge-base
How to work in a Knowledge Base project (the `knowledge-base` starter pack). Read when the project has the three-layer source-grounded layout — `external-sources/` → `research/` → `articles/` — or when asked how this project is organized. Carries the layer model, per-folder rules, status flows, and log discipline so this guidance does NOT live inside template bodies or log.md. The three procedure…
packages/server/assets/skills/packs/knowledge-base/SKILL.md on GitHub (opens in a new tab) -
okf-knowledge-base
Open Knowledge Format (OKF) v0.2 guidance. Use when creating, reading, reviewing, or maintaining an OKF bundle; responding to OpenKnowledge `okf` plugin warnings; or choosing types, provenance, links, indexes, or logs.
packages/server/assets/skills/packs/okf/SKILL.md on GitHub (opens in a new tab) -
note-taking
How to work in a Plain Notes project (the `plain-notes` starter pack): a flat notes/ folder plus a daily/ journal. The 'I just want to write' layout. Read when the project has these folders, OR when asked to jot a note, capture a quick thought, or write today's journal entry. Carries the linking habit and daily-entry behavior so templates and folder descriptions stay minimal. Complements the plat…
packages/server/assets/skills/packs/plain-notes/SKILL.md on GitHub (opens in a new tab) -
software-lifecycle
How to work in a Software Lifecycle project (the `software-lifecycle` starter pack): proposals → decisions → specs → postmortems, plus guides. Read when the project has these folders, or when asked how this project is organized. Carries the doc lifecycle, status flows, and per-folder agent behaviors so that guidance does not live inside template bodies or folder descriptions. The five workflows —…
packages/server/assets/skills/packs/software-lifecycle/SKILL.md on GitHub (opens in a new tab) -
worldbuilding
How to work in a Worldbuilding project (the `worldbuilding` starter pack): a fiction encyclopedia of characters, settings, themes, factions, and lore. Read when the project has these folders, OR when asked to add a character, setting, faction, or piece of lore, or to check the world for internal consistency. Carries the auto-stub and consistency behaviors so that guidance does not live inside tem…
packages/server/assets/skills/packs/worldbuilding/SKILL.md on GitHub (opens in a new tab) -
writing-workflow
How to work in a Writing Pipeline project (the `writing-pipeline` starter pack): a three-stage drafting flow, ideas → drafts → published. Read when the project has these folders, OR when asked to capture an idea, start or revise a draft, review a piece before it ships, or publish it. Carries the stage flow and review behaviors so that guidance does not live inside template bodies or folder descri…
packages/server/assets/skills/packs/writing-pipeline/SKILL.md on GitHub (opens in a new tab) -
consolidate-notes
Promote existing research into a stable-status canonical article under `articles/` in a Knowledge Base project (the `knowledge-base` starter pack). Read when a decision has actually been made and the team wants the source-of-truth written down, or when asked to consolidate, canonicalize, promote research, or supersede an older article. Carries the decision-confirmation gate, the `supersedes:` cha…
packages/server/assets/skills/packs/knowledge-base/consolidate/SKILL.md on GitHub (opens in a new tab) -
research-with-sources
Investigate a topic against preserved sources and write a draft-status research article under `research/` in a Knowledge Base project (the `knowledge-base` starter pack). Read when asked to research a topic, compare options, synthesize sources, gather evidence, or extend an existing research doc. Carries the full procedure: scan existing coverage, agree a research rubric, capture every source ver…
packages/server/assets/skills/packs/knowledge-base/research/SKILL.md on GitHub (opens in a new tab) -
frame-a-proposal
Frame a new design proposal (RFC-shape) under proposals/ — problem before solution, named beneficiary and observable change, real alternatives, honest drawbacks, and a live open-questions backlog. Read when asked to frame a proposal, write an RFC, propose a design, pitch a change, draft a PRD-style design doc, or open a design proposal for review. Do NOT read to record a decision after it is acce…
packages/server/assets/skills/packs/software-lifecycle/frame-a-proposal/SKILL.md on GitHub (opens in a new tab) -
record-a-decision
Records an architecture decision as a Nygard/MADR-shaped ADR under decisions/ — capturing the context that forced the choice, the options weighed, the decision itself, and its consequences in both directions, plus the supersedes chain that keeps a decision log honest. Read when asked to record an architecture decision, write an ADR, log the decision we made, document why we chose X over Y, captur…
packages/server/assets/skills/packs/software-lifecycle/record-a-decision/SKILL.md on GitHub (opens in a new tab) -
review-a-design
Reviews whether a design is SOUND — solving the right problem, derived from its stated goals and constraints — and emits ranked, evidence-backed findings, not edits. Read when asked to 'review this design', 'is this design sound', 'pressure-test this proposal', 'do a design review', 'does this solve the right problem', 'poke holes in this spec', 'should we build this', or to critique a proposal /…
packages/server/assets/skills/packs/software-lifecycle/review-a-design/SKILL.md on GitHub (opens in a new tab) -
write-a-postmortem
Write a blameless incident postmortem under postmortems/ following the Google SRE shape — evidence-based timeline, trigger vs root cause vs symptom, contributing factors, what went well, and owned+dated+verifiable action items. Read when asked to write a postmortem, do an incident review, run a root cause analysis, write up the outage, retro on the outage, or when the user says we had an incident…
packages/server/assets/skills/packs/software-lifecycle/write-a-postmortem/SKILL.md on GitHub (opens in a new tab) -
write-a-spec
Scope a feature end to end and write an implementation spec under specs/ from an accepted proposal — current-system mapping, goals/non-goals, a Decision Log for one-way-door choices, a live Open Questions backlog, and a real migration + test plan. Read when asked to write a spec, scope this feature, turn this proposal into a spec, plan the implementation, or break this into tasks. Do NOT fire on…
packages/server/assets/skills/packs/software-lifecycle/write-a-spec/SKILL.md on GitHub (opens in a new tab)
No skill matches that filter.
Review before you install
A skill is a set of instructions and scripts your agent will follow, and it can run code on your machine. Read the SKILL.md and any scripts first — this listing is not a security review.