Agent Skill
Open Knowledge Write Skill skill
open-knowledge-write-skillinkeep/open-knowledgepackages/server/assets/skills/write-skill/SKILL.md
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 than a one-off prompt. Covers choosing scope (project vs global), authoring inside a plugin or skills-distribution repo (write in the repo's own layout, never install), the SKILL.md frontmatter contract, progressive-disclosure structure, evaluating the skill, and installing it into the user's editors.
always on
152 tokname + description
once used
3,341 tokSKILL.md body
bundled files
24 KB
repo stars
4.7kGitHub
Install the Open Knowledge Write Skill skill
Skills CLI (Claude Code, Codex, Cursor and others)
npx skills add https://github.com/inkeep/open-knowledge --skill open-knowledge-write-skill
Claude Code, by hand (all projects)
git clone --depth 1 https://github.com/inkeep/open-knowledge.git /tmp/open-knowledge mkdir -p ~/.claude/skills cp -R /tmp/open-knowledge/packages/server/assets/skills/write-skill ~/.claude/skills/open-knowledge-write-skill
For one project only, copy the folder into .claude/skills/ in that project instead. The agent picks it up when a task matches its description.
What it costs your context
Agent Skills load in three steps. Tokens counted with the o200k tokenizer; your model's count will differ a little.
| When | What loads | Cost |
|---|---|---|
| Every session | Name and description | 152 tok |
| When the agent uses it | The SKILL.md instructions | 3,341 tok |
| Only if opened | 2 bundled files (4 KB) | varies |
Until it is used, open-knowledge-write-skill costs about 9.0× less than the median MCP server we measured (1,363 tokens on every turn). Installing all 18 skills from inkeep/open-knowledge would load 2,452 tokens of descriptions. Skills vs MCP study
Checks
- The name doesn't match its folder name, as the specification requires.
Checked 2026-10-22 · method
What's inside
The headings of its SKILL.md. Read the full file on GitHub.
- Writing an OpenKnowledge skill
- Stage 1 — Capture intent and classify the skill
- Stage 2 — Resolve scope FIRST (never infer silently)
- Stage 3 — Plan the contents
- Stage 4 — RED baseline (discipline skills only)
- Stage 5 — Draft the skill
- Stage 6 — GREEN eval + refactor
- Stage 7 — Optimize the description (this is what makes the skill fire)
- Stage 8 — Install (choose where it's available)
- Reminders
More skills from inkeep/open-knowledge
- codebase-wikiinkeep/open-knowledge
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 freshness + log discipline, summarizes the audience/depth knobs and source-reference convention, and bundles the full generate/refresh procedure in `references/`. Complements the platform `open-knowledge` skill; does not replace it.
4.7k152 tok idle · 1,529 in use - consolidate-notesinkeep/open-knowledge
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:` chain that keeps the evidence trail intact, and the canonical voice. Does not conduct new research — that is the sibling `research-with-sources` skill.
4.7k118 tok idle · 1,875 in use - frame-a-proposalinkeep/open-knowledge
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 accepted (use record-a-decision), to write an implementation spec (use write-a-spec), to write a postmortem (use write-a-postmortem), or to review or critique an existing design (use review-a-design).
4.7k136 tok idle · 3,100 in use - knowledge-baseinkeep/open-knowledge
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 procedures live elsewhere: ingest in the platform `open-knowledge` skill, research and consolidate as their own sibling skills in this pack. Complements the platform `open-knowledge` skill; does not replace it.
4.7k133 tok idle · 1,740 in use - note-takinginkeep/open-knowledge
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 platform `open-knowledge` skill; does not replace it.
4.7k102 tok idle · 292 in use - okf-knowledge-baseinkeep/open-knowledge
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.
4.7k58 tok idle · 864 in use - open-knowledgeinkeep/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 an OpenKnowledge project and it governs every markdown file here. Covers the read/write tool surface, grounding and linking rules, folder/template conventions, the live browser preview, and the rule that OK's MCP tools — never native file tools — handle in-scope markdown.
4.7k153 tok idle · 4,526 in use - open-knowledge-discoveryinkeep/open-knowledge
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 OpenKnowledge reads/writes — the runtime guidance for editing markdown inside an initialized OK project ships as a separate project-local skill installed into each detected agent's skills dir (for example `.claude/skills/open-knowledge/`) whenever `ok init` runs.
4.7k139 tok idle · 1,751 in use