yxtay · yxtay · Jul 16, 2026 · Jul 16, 2026
@@ -24,12 +24,14 @@ if command -v rtk >/dev/null; then
 fi
 
 agents=(opencode)
+if command -v claude >/dev/null; then
+  agents+=(claude-code)
+fi
 
 repo_skills=(
   mattpocock/skills=wayfinder,grill-with-docs,to-spec,to-tickets,triage,handoff,implement
   mattpocock/skills=grilling,domain-modeling,research,prototype,codebase-design,tdd,diagnosing-bugs
-  mattpocock/skills=resolving-merge-conflicts,improve-codebase-architecture
-  mattpocock/skills=ask-matt,setup-matt-pocock-skills,writing-great-skills,teach,grill-me
+  mattpocock/skills=setup-matt-pocock-skills,improve-codebase-architecture,writing-great-skills
   philschmid/mcp-cli=mcp-cli
 )
 for entry in "${repo_skills[@]}"; do

@@ -10,7 +10,6 @@ fi
 marketplaces=(
   anthropics/claude-plugins-official
   JuliusBrussee/caveman
-  mattpocock/skills
   MemPalace/mempalace
   zilliztech/memsearch
 )
@@ -25,7 +24,6 @@ plugins=(
   pyright-lsp@claude-plugins-official
   typescript-lsp@claude-plugins-official
   caveman@caveman
-  mattpocock-skills@mattpocock
   mempalace@mempalace
   memsearch@memsearch-plugins
 )

@@ -2,10 +2,9 @@
 name: okf
 description: >-
   Create and maintain knowledge bundles in Open Knowledge Format (OKF) —
-  markdown + YAML-frontmatter concept files for durable knowledge. Use when
-  the user wants to write, structure, or validate an OKF bundle, add a
-  "concept" document, build an `index.md`/`log.md`, cross-link concepts, or
-  asks "is this OKF-conformant".
+  markdown + YAML-frontmatter concept files for durable knowledge. Invoke to
+  write, structure, or validate an OKF bundle; add concept documents; build
+  `index.md`/`log.md`; cross-link concepts; or check OKF conformance.
 user-invocable: true
 argument-hint: "[produce|maintain|consume] [bundle-path]"
 ---
@@ -39,7 +38,7 @@ missing optional fields, unknown types, and broken links.
 Templates: [concept](templates/concept.md), [index](templates/index.md),
 [log](templates/log.md).
 
-## Modes
+## Task types
 
 ### produce — create or extend a bundle
 
@@ -51,8 +50,7 @@ Templates: [concept](templates/concept.md), [index](templates/index.md),
 4. Write each concept from [templates/concept.md](templates/concept.md): set a
    descriptive `type`, fill recommended fields, cross-link related concepts.
 5. Add/refresh `index.md` per directory (`okf_version: "0.1"` in root index)
-   and append to `log.md`. Done when every new or changed concept has an
-   `index.md` entry.
+   and append to `log.md`.
 
 ### maintain — sync a bundle with reality
 
@@ -70,6 +68,5 @@ Templates: [concept](templates/concept.md), [index](templates/index.md),
 
 ## Before declaring done
 
-- Every concept written or touched: parseable frontmatter, non-empty `type`.
 - `index.md` updated for any new concepts.
 - `log.md` entry appended if the bundle has one.
@@ -1,7 +1,8 @@
 #!/usr/bin/env bash
-# SessionEnd hook: periodically distill memsearch memories into the ~/wiki OKF bundle.
-# Independent of the memsearch plugin's own SessionEnd hook — reads its memory output
-# as a data source only, no changes to memsearch itself.
+# SessionStart/SessionEnd hook: once per calendar day, distill memsearch memories into
+# the ~/wiki OKF bundle. Runs on both events so it fires whether a session starts fresh
+# or ends normally. Independent of the memsearch plugin — reads its memory output as a
+# data source only, no changes to memsearch itself.
 set -euo pipefail
 
 # Avoid recursing into our own hooks when the nested `claude -p` below exits.

@@ -0,0 +1,31 @@
+You are maintaining a personal OKF (Open Knowledge Format) wiki.
+
+You will receive recently-changed memsearch memory files (markdown logs of past coding sessions)
+and, when listed, memsearch-synthesized PROJECT.md (project review) and USER.md (user profile) as
+additional context. Treat synthesized summaries as primary; use raw memory files for detail not
+captured there.
+
+Step 1 — invoke the `okf` skill. It defines the bundle layout, frontmatter rules, and the exact
+steps for adding, updating, and linking concepts. Follow it exactly for any edits you make.
+
+Step 2 — read `<wiki>/index.md` to understand the bundle's current structure.
+
+Step 3 — read the files listed under "Recent memory:" in the user message, plus any user profile and project review files listed.
+
+Step 4 — decide: is there anything worth adding or updating in the wiki?
+Lean toward capturing. Capture any of:
+- How something works — tools, systems, integrations, flags, invocation patterns
+- How something was set up or configured — steps, sequences, decisions made
+- Why something was done — rationale, tradeoffs, constraints
+- What was found — investigation results, things ruled out, gotchas
+- What worked or didn't — patterns, failure modes, workarounds
+
+Only skip if the knowledge is already fully covered by an existing concept, or if it is truly
+ephemeral (e.g. a one-line typo fix with no transferable lesson). When in doubt, add it.
+Prefer amending an existing concept over creating a new one for incremental additions.
+
+Step 5 — if there is durable knowledge, apply the skill's **maintain** mode.
+
+Constraints:
+- Do not touch memsearch-owned files (PROJECT.md, USER.md, memory .md files) — read-only to you.
+- Do not ask questions. This runs unattended.
@@ -2,9 +2,9 @@
 type: CONCEPT_TYPE
 title: DISPLAY_NAME
 description: Single sentence summarizing the concept.
-resource: CANONICAL_URI_omit_for_abstract_concepts
+# resource: URI  # omit for abstract concepts
 tags: [TAG]
-timestamp: 2026-01-01T00:00:00Z
+timestamp: 2026-07-16T09:30:00Z
 ---
 
 ## Overview

@@ -2,6 +2,6 @@
 
 ## YYYY-MM-DD
 
-- **Creation**: what was created — [concept](bundle-relative-path).
-- **Update**: what changed — [concept](bundle-relative-path).
-- **Deprecation**: what was retired — [concept](bundle-relative-path).
+- **Creation**: what was created — [concept](bundle-relative-path)
+- **Update**: what changed — [concept](bundle-relative-path)
+- **Deprecation**: what was retired — [concept](bundle-relative-path)