agentsclimarketplace

Kw okf memory

Skill KevinLuo1/kw-okf-memory-skill/skills/kw-okf-memory

Long-term memory for Codex: preserve decisions and context across chats in a local-first Obsidian/Markdown knowledge base with staged writes you approve and index + graph retrieval. Karpathy-style, OKF-inspired.

Install
npx -y skills add KevinLuo1/kw-okf-memory-skill --skill kw-okf-memory

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 27 days oldThe repository was created 27 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Build and maintain a structured Obsidian-friendly Markdown memory wiki for Codex using a Karpathy-style wiki, an opinionated OKF-inspired KW-OKF profile, rebuildable categories.json and graph.json indexes, safe structure evolution, staged AI writes, and optional OKF v0.1 export. Use when Codex should save, update, retrieve, synthesize, search, stage, commit, audit, maintain, or export durable project memory; prevent messy AI-written knowledge bases; check duplicates, conflicts, stale notes, broken links, associations, and vault structure; process memory assets; or open committed notes in Obsidian for human review.

SKILL.md

5.3 KB, as published. Nobody here has run it

KW-OKF Memory

Core Boundary

Use this skill to maintain a long-term Codex memory wiki that stays structured, can evolve safely, supports index-and-graph retrieval, and prevents silent AI writes. Recommend Obsidian for human review, search, backlinks, and navigation after commit, but keep Markdown and the glue script as the write/audit authority. KW-OKF is an opinionated, OKF-inspired memory profile; the internal Vault does not claim direct OKF v0.1 conformance. Use export-okf for an interoperable handoff bundle.

Keep the boundary clear: the Skill stores tools and protocol, the Vault stores long-term knowledge assets, the Python glue layer performs deterministic filesystem/index/audit work, and Codex extracts, judges, previews, and asks for confirmation.

Task Routing

  • For preservation or write intents, including saving experience/rules/cases, distilling knowledge, creating or updating OKF pages, or updating long-term memory, read references/write_workflow.md plus references/okf_schema.md, references/vault_framework.md, and references/association_workflow.md as needed.
  • For lookup intents that need specific existing records, read references/retrieval_workflow.md and references/wiki_lookup_workflow.md, then use search.
  • For synthesis, judgment, planning, conflict-check, comparison, creative expansion, or lesson-extraction intents that need prior memory, read references/retrieval_workflow.md and references/wiki_lookup_workflow.md, then use think.
  • For maintenance intents involving vault health, duplicates, conflicts, stale notes, orphan pages, missing links, or deep organization, read references/maintenance_workflow.md.
  • For memory asset processing intents, preview with process-img --preview, then follow the confirmation and path rules in references/write_workflow.md and references/vault_framework.md.
  • For interoperability or handoff intents, preview and run export-okf; keep the internal KW-OKF Vault unchanged.
  • Use obsidian-open / obsidian-search only for human review. Obsidian is not the write or audit authority.

Load As Needed

  • config.json: read before filesystem actions to locate the Vault and resolve language, image, and Obsidian settings. Structural safety rules are fixed by the Skill and script rather than configurable bypasses.
  • references/write_workflow.md: formal writes, preview, confirmation, commit, and existing-knowledge updates.
  • references/okf_schema.md: KW-OKF node types, frontmatter fields, body template, source refs, and official OKF compatibility boundary.
  • references/vault_framework.md: fixed Vault skeleton, path safety, and directory creation rules.
  • references/retrieval_workflow.md: search / think mode selection, synthesis, gap analysis, and staleness checks.
  • references/association_workflow.md: lightweight write-time associations, relationship labels, and deep association cleanup.
  • references/maintenance_workflow.md: manual maintenance flow, command roles, duplicate/conflict/staleness/orphan checks.
  • references/wiki_lookup_workflow.md: wiki-style lookup, small reads, link following, and error-book rules.

Command Entry

Use the glue script for deterministic filesystem work:

python scripts/okf_glue.py <command> [options]

Common commands are init, build, audit, search, stage, commit, process-img, export-okf, obsidian-open, and obsidian-search; before running a command, read the task-specific workflow reference and confirm arguments with python scripts/okf_glue.py <command> --help.

Language Policy

  • When writing formal notes, use the same language as the current user-Codex conversation unless the user explicitly requests another supported language. When unclear, use the configured fallback language, which defaults to en-US in this public release.

Hard Rules

  • Never write a formal wiki/ page without preview and explicit user confirmation.
  • Formal writes must follow stage -> preview -> user confirmation -> commit -> build/audit.
  • A user may grant batch confirmation for one clearly scoped ordinary cleanup task; batch confirmation does not cover framework changes, schema changes, formal-knowledge deletion, or large merges.
  • Store formal knowledge only in the Vault; do not store business knowledge in the Skill folder.
  • Create runtime business directories or missing Routers only when previewed and confirmed.
  • Do not create asset subdirectories or overwrite existing assets without preview, explicit confirmation, and the matching command flag.
  • Treat new top-level directories and new wiki/ first-level categories as framework changes that require explicit user confirmation and framework doc updates.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.