remember-me

name

remember-me

description

Capture durable facts the user states about themselves into their personal OKF "about-me" knowledge bundle, then refresh the bundle. Use proactively WHENEVER the user reveals a lasting fact about themselves in first person — their role, employer, location, background, skills, tools, work style, preferences that affect how work should be done, ongoing projects/goals, relationships, health, or hard constraints. Triggers on statements like "I work at…", "I'm a…", "I prefer…", "I live in…", "my team…", "I'm working on…", "remember that I…". Do NOT trigger for transient task context, one-off requests, or facts about other people.

remember-me

You maintain a personal OKF about-me bundle or fit their personal information i nto their current bundlefor the user: a durable, self-describing knowledge base of facts they've stated about themselves. When the user reveals a lasting fact about themselves, capture it as an OKF concept and refresh the bundle. This is the OKF-bundle counterpart to the file-based memory system — use it when the fact belongs in the user's portable knowledge graph.

Follow the OKF authoring rules in the sibling open-knowledge-format skill (${CLAUDE_PLUGIN_ROOT}/skills/open-knowledge-format/SKILL.md, with SPEC.md alongside it) for any normative detail; this skill is the capture playbook.

Paths

• Scripts: ${CLAUDE_PLUGIN_ROOT}/scripts (run with python3).
• Bundle (default): Use the bundle in the current directory, or create a new about-me/ bundle in the current directory if none exists. The bundle root must contain a log.md file and an index.md file (the latter is auto-generated).

What counts as a fact worth capturing

Capture durable, first-person facts about the user:

• Identity & role — job title, employer, team, seniority, field.
• Location / timezone / working hours.
• Background — education, prior roles, notable work, publications.
• Skills, languages, tools, frameworks they use.
• Preferences that shape how work should be done (e.g. "I prefer pytest over unittest", "always use type hints", "I like terse answers").
• Ongoing projects, goals, and constraints.
• Relationships and affiliations they frame as their own.
• Health, accessibility needs, or other lasting personal context.

Do NOT capture: transient task state, one-off requests, speculation, things the user asked you to do (vs. facts about them), or facts about other people unless framed as the user's own relationship. When unsure whether a fact is durable, lean toward not capturing — quality over volume.

Workflow

1. Pick the destination bundle. Default to the about-me bundle above. If the user clearly has another bundle that is about them specifically, enrich that instead. If the default bundle does not exist, create it (a profile/ directory plus the person hub concept).

2. Find or create the right concept. Organize by facet, one concept per file, cross-linked back to the person hub:

   • profile/me.md — the person hub (identity overview).
   • work/<slug>.md — employer, role, team (type: Affiliation / Role).
   • preferences/<slug>.md — work-style and tooling preferences (type: Preference).
   • projects/<slug>.md — ongoing work and goals (type: Project).
   • profile/<slug>.md — background, skills, relationships, etc. Prefer updating an existing concept over creating a near-duplicate: search the bundle for the topic first. Merge the new fact into the existing body; never let two concepts assert the same thing.

3. Author concretely. Frontmatter: always type; add title, a one-sentence description (reused verbatim in index.md), tags, and a timestamp (today, ISO-8601). Body: structural markdown (tables, lists), only facts the user actually stated — never invent details, dates, or URLs. Cross-link new concepts to /profile/me.md (absolute bundle-relative links), and add a backlink from the hub when it's a new facet.

4. If a new fact contradicts an existing one, update the concept to the new truth (don't keep both), refresh its timestamp, and note the change in the bundle's log.md.

5. Append to log.md at the bundle root: under today's ## YYYY-MM-DD heading, add a * **Creation** or * **Update** line linking the concept.

6. Refresh the bundle — regenerate indexes, validate, rebuild the viewer:

   python3 "${CLAUDE_PLUGIN_ROOT}/scripts/okf_sync.py" <bundle> --name "About Me"
   

   (Equivalent to /okf:update <bundle>.) Fix any HARD validation errors; warnings are advisory.

7. Confirm briefly. One line: what you captured and where (e.g. "Saved your pytest preference to preferences/testing.md and refreshed the bundle."). Do not derail the user's current task — capture inline and move on.

Quality bar

• One concept = one coherent facet. Don't sprawl.
• One-sentence descriptions; structural bodies over prose.
• Only what was actually said. No invented employers, dates, or links.
• Update-in-place beats duplicate concepts.