Skip to main content
skill CX Codex

note-taking — Claude Code skill: what it does, how to install

note-taking guides agents working in a plain notes setup with notes/ and daily/ folders. Helps capture ideas quickly and connect pages with cross-links.

MIT 179 installs ★ 17 updated 2026-10-21

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add inkeep/open-knowledge-skills --skill note-taking -a claude-code
Open on GitHub

What note-taking does

This skill establishes a lightweight workflow for the plain-notes starter pack. The project keeps all thematic notes flat inside notes/, while journal entries go into daily/ formatted as YYYY-MM-DD.md. The templates provide minimal structure so you can focus on writing.

The agent links pages aggressively to build a navigable knowledge graph. When an entry mentions a topic worth exploring, the agent creates a link and stubs the missing file. The first daily entry automatically links to yesterday's date, and frontmatter fields like mood, top3, and gratitude track state across days.

Without the OpenKnowledge MCP server configured in your environment, this skill cannot operate. It acts as pack-specific guidance on top of /open-knowledge, so core markdown and grounding rules remain governed by the platform skill.

What it helps with

  • Maintain a flat note archive in notes/ without nested folders
  • Keep a linear journal in daily/ linked to the previous day
  • Capture daily reflections through mood, top3, and gratitude fields
  • Stub missing note files whenever new concepts appear in text

Example prompts for the agent

  • Capture a quick note on database indexing inside notes/
  • Create today's daily log and fill out the top3 goals
  • Add an evening reflection to daily/ and link back to yesterday

How to install note-taking

1Skills CLI (Vercel)

npx skills add inkeep/open-knowledge-skills --skill note-taking -a claude-code

2Manually: put the files in place

~/.claude/skills/note-taking/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/note-taking/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about note-taking

How to install note-taking in Claude Code?

Run npx skills add inkeep/open-knowledge-skills --skill note-taking -a claude-code. The file will be placed in ~/.claude/skills/note-taking/SKILL.md.

What does the note-taking skill do?

It instructs the agent to store topic pages in notes/, maintain chronological logs in daily/, and build links across entries.

What are the requirements for this skill?

It requires the OpenKnowledge MCP server and complements the /open-knowledge platform skill. You can also seed the layout locally with ok seed --pack plain-notes.

Source text

SKILL.md · MIT
---
name: note-taking
description: "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."
compatibility: "Any agent host with the OpenKnowledge MCP server configured. Installed project-local by `ok seed --pack plain-notes` (`ok-beta` for Beta)."
metadata:
  pack: "plain-notes"
  author: "Inkeep"
  repository: "https://github.com/inkeep/open-knowledge-skills"
---
# Plain Notes pack — how to work here

The lightest pack: no posture imposed, just write and link.

> This skill is pack guidance. The platform `/open-knowledge` skill (read/write/preview/linking/grounding rules) still governs every markdown operation — this layers the notes habit on top.

## Folders

- **`notes/`** — one file per topic, flat. Promote a note into a more structured layout later if you outgrow this.
- **`daily/`** — one journal entry per day (`YYYY-MM-DD.md`): morning intentions, capture through the day, evening reflection.

## Agent behaviors

- **Link liberally.** The value of this pack is the graph that emerges from links — when a note or entry mentions something worth its own page, link it (stub the page if it doesn't exist yet). OK's link graph builds itself from those edges.
- **Daily entries:** on the first entry of a day, link to yesterday's entry (its own dated file, e.g. `2026-07-08.md`) and pre-fill the date, so the linear journal is also a navigable graph.
- The `mood`, `top3`, and `gratitude` frontmatter fields on daily entries let you look back across days; fill them when journaling.

## Templates

`note` and `daily` carry only structure; write freely.

© Inkeep · MIT · inkeep/open-knowledge-skills

Similar skills

All skills for Notes, tasks and projects →

From the same set17

The whole set →
review-a-design review-a-design critiques technical proposals, specs, and ADRs for architectural soundness without editing the text. It flags flaws in goals, constraints, and alternatives. CX Codex +1 252installs record-a-decision The record-a-decision skill turns a settled architecture choice into an ADR with its context, alternatives, and consequences. Use it to keep decision history readable. CX Codex +1 252installs frame-a-proposal The frame-a-proposal skill shapes a design request into a reviewable RFC, starting with the problem and beneficiary before moving to options, trade-offs, and open questions. CX Codex +1 248installs write-a-spec write-a-spec turns an accepted proposal into an implementation spec with current-system mapping, decision records, open questions, migration work, and tests. CX Codex +1 247installs software-lifecycle software-lifecycle gives a project a fixed shape for its docs: proposals, decisions, specs, postmortems and guides. The skill carries the status flows and per-folder rules. CX Codex +1 245installs write-a-postmortem write-a-postmortem drafts blameless incident reviews in postmortems/ using the Google SRE framework. Focuses on system affordances and evidence instead of personal fault. CX Codex +1 243installs personal-crm This skill organizes people, company, meeting, and concept notes into a linked Markdown vault. Use it when an agent needs to maintain a personal CRM. CX Codex +1 126installs writing-workflow writing-workflow — a skill for Claude Code and Codex that structures writing into ideas, drafts, and published stages. Triggers when capturing a note, revising prose, or shipping a piece. CX Codex +1 102installs

Project sponsors

Companies that keep this analytics open