Schema 1.6, all fields optional (D-0014): - F7 review: `review: draft|reviewed|needs_update`, `reviewed_by`, `reviewed_on`; lint check 17 and a review queue; ckb-lint marks reviews - F4 `> CONTRADICTION:` marker, lint check 18; validity dates deferred - F21 `tags` against the new `wiki/tags.md`, lint check 19, retrieve_candidates.py --tag, DRAFT/NEEDS_UPDATE flags - F9 profiles in workload/profiles/, protected `## Rules` on project scope pages, precedence AGENTS.md > Rules > profile - F8 explicit lessons (profile or wiki/lessons.md); new ckb-profile skill Carry-over: `.secrets-allow` `<glob> match:<hash>` entries (also in the bash/PowerShell fallbacks); open threads no longer print twice. ckb-upgrade migrates 1.5 -> 1.6; init/reset know tags.md; Starlight shows review and tags. Smoke test covers a 1.6 KB. Docs in EN and PL. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
107 lines
4.2 KiB
Markdown
107 lines
4.2 KiB
Markdown
---
|
|
name: ckb-profile
|
|
description: Keep a person's profile (role, how to work with them, personal lessons) in workload/profiles/ and record lessons on an explicit request — personal ones in the profile, KB-wide ones in wiki/lessons.md. Use for "set up my profile", "update my profile", "what do you know about me", "remember this", "lesson: …", "from now on always …", "list the lessons", "forget that lesson".
|
|
---
|
|
|
|
# Profile skill
|
|
|
|
## Purpose
|
|
|
|
Two things a session should not have to relearn: who it is working with, and
|
|
what a correction taught it. Both are written only when someone asks, never
|
|
from a guess about tone or preference.
|
|
|
|
## Scopes, and which wins
|
|
|
|
1. **`AGENTS.md`** — the KB's rules. Always win.
|
|
2. **A project scope's `## Rules`** — the team's agreements for that project,
|
|
in `wiki/projects/<name>.md`. Win while working inside that scope.
|
|
3. **A person's profile** — how to work with that person. Applies where
|
|
neither of the above says otherwise.
|
|
|
|
A profile can never relax a rule from 1 or 2. When it conflicts with one,
|
|
follow the rule and say so once.
|
|
|
|
## Profiles
|
|
|
|
One file per person: `workload/profiles/<author-slug>.md`, with the same slug
|
|
as Rule D (`Michał Kopeć` → `michal-kopec`). It sits outside `wiki/`, so
|
|
retrieval never reads it and it needs no `wiki/log.md` entry. The
|
|
session-start brief prints the profile of the session identity, and only
|
|
that one.
|
|
|
|
```markdown
|
|
---
|
|
type: profile
|
|
author: Name
|
|
author_email: name@example.com
|
|
last_updated: YYYY-MM-DD
|
|
---
|
|
|
|
# Name
|
|
|
|
## Role
|
|
<!-- What they do, and what they use this KB for. -->
|
|
|
|
## How to work with me
|
|
<!-- Short bullets: language, level of detail, what to ask before doing. -->
|
|
|
|
## Lessons
|
|
<!-- Personal lessons, newest last, in the lesson format below. -->
|
|
```
|
|
|
|
**Set up** ("set up my profile"): ask at most three questions in one message
|
|
— role, how they want to be worked with, anything to always or never do —
|
|
and write their answers in their words. Never fill a section by guessing.
|
|
**Update**: change only what they named, and set `last_updated`. **"What do
|
|
you know about me"**: show the profile, then say where it lives.
|
|
|
|
**Privacy.** A profile is committed and shared with everyone who clones the
|
|
KB. Say so when creating one. Keep it to working preferences: no health,
|
|
family, contact details beyond the git identity, or anything the person
|
|
would not post in a team channel. Text in `<private>…</private>` is never
|
|
written into a profile.
|
|
|
|
## Lessons
|
|
|
|
Record a lesson only on an explicit trigger: "remember this", "lesson: …",
|
|
"from now on always/never …". A correction on its own is not a trigger; at
|
|
most, offer once: "Want me to keep that as a lesson?"
|
|
|
|
```markdown
|
|
### YYYY-MM-DD — <the rule, one line>
|
|
- **Why:** <what went wrong or what the person said>
|
|
- **Applies when:** <the situations it covers>
|
|
- **Scope:** person | KB
|
|
- **Recorded by:** Name
|
|
```
|
|
|
|
Ask which scope when it is not obvious:
|
|
|
|
- **Person** — how this person likes to work. Append to `## Lessons` in
|
|
their profile.
|
|
- **KB** — true for anyone working in this KB (a naming rule, a source not
|
|
to trust, a step that keeps getting missed). Append to `wiki/lessons.md`.
|
|
Create the page if it is missing (`type: lessons`, a `tldr`, a routing row
|
|
in `wiki/index.md`). Set `review: needs_update`, or `draft` on a new page,
|
|
so a second person checks the lesson before everyone relies on it. Log it
|
|
under Rule B.
|
|
|
|
A lesson that should bind everyone, always, belongs in `AGENTS.md` instead.
|
|
Suggest that once; do not edit `AGENTS.md` from here.
|
|
|
|
The session-start brief lists KB lessons dated after the person's previous
|
|
workload note. Read the ones that bear on the task.
|
|
|
|
**Forgetting**: a lesson is never deleted silently. Strike it through
|
|
(`~~rule~~ — dropped YYYY-MM-DD: why`) so the record survives. A KB lesson
|
|
change is logged under Rule B.
|
|
|
|
## Edge cases
|
|
|
|
- **No git identity** — use the OS-user slug the brief prints, and suggest
|
|
setting `git config user.name` so the profile follows the person.
|
|
- **Two people share one git identity** — one profile per identity. Say so
|
|
and suggest separate identities.
|
|
- **A profile asks for something a skill forbids** (skip the ingest
|
|
check-in, push without asking) — follow the skill and say why once.
|