Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

open-knowledge-pack-plain-notes

Sterne1.810

Forks87

Aktualisiert26. Juni 2026 um 20:33

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. 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.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

inkeep

inkeep/open-knowledge

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

SKILL.md

readonly

name	open-knowledge-pack-plain-notes
version	0.18.0
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. 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	Claude Code, Claude Desktop, Claude Cowork, Claude.ai web. Requires OpenKnowledge MCP server. Installed project-local by `ok seed --pack plain-notes`.
metadata	{"pack":"plain-notes","author":"Inkeep","repository":"https://github.com/inkeep/open-knowledge"}

Plain Notes pack — how to work here

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

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 (YYYY-MM-DD-1.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.

Mehr aus diesem Repository

gleiches Repository

open-knowledge-discovery

inkeep/open-knowledge

Read when the user asks what OpenKnowledge is, wants to install it on a repository, wants to share an OpenKnowledge project with collaborators, 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 at `.claude/skills/open-knowledge/` whenever `ok init` runs. If the user appears to be editing markdown inside a `.ok/` project and this is the only OK skill loaded, advise them to re-run `ok init` to install the project-local skill.

2026-07-021.8k

open-knowledge

inkeep/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, or editing any `.md` or `.mdx` file in the project, and before any `mcp__open-knowledge__*` tool call (`exec`, `search`, `write`, `edit`, 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.

2026-07-021.8k

open-knowledge-write-skill

inkeep/open-knowledge

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), the SKILL.md frontmatter contract, progressive-disclosure structure, evaluating the skill, and installing it into the user's editors.

2026-07-021.8k

open-knowledge-pack-codebase-wiki

inkeep/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`. Carries the per-folder rules and freshness + log discipline, summarizes the audience/depth knobs and source-reference convention, and points to the `workflow({ kind: 'wiki' })` guide for the full generate/refresh procedure. Complements the platform `open-knowledge` skill; does not replace it.

2026-06-271.8k

open-knowledge-pack-entity-vault

inkeep/open-knowledge

How to work in an Entity vault 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. Carries the dossier convention and entity-extraction behaviors so that guidance does not live inside template bodies or folder descriptions. Complements the platform `open-knowledge` skill; does not replace it.

2026-06-271.8k

open-knowledge-pack-knowledge-base

inkeep/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/` — wired to the `workflow` MCP tool's ingest / research / consolidate kinds. Carries the pack's workflow, per-folder rules, status flows, and log discipline so this guidance does NOT live inside template bodies or log.md. Complements the platform `open-knowledge` skill; does not replace it.

2026-06-261.8k

name	open-knowledge-pack-plain-notes
version	0.18.0
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. 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	Claude Code, Claude Desktop, Claude Cowork, Claude.ai web. Requires OpenKnowledge MCP server. Installed project-local by `ok seed --pack plain-notes`.
metadata	{"pack":"plain-notes","author":"Inkeep","repository":"https://github.com/inkeep/open-knowledge"}

Plain Notes pack — how to work here

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

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 (YYYY-MM-DD-1.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.