kb-orient
Skill1 starsChanged 32 days agoMITView on GitHub
Use at the start of every session in this knowledge repo to learn where we are and what's next, before any other work. Reads STATE and the index map, never the whole repo.
In this repository11 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- kb-captureSkill
- kb-dashboardSkill
- kb-elicitSkill
- kb-evolveSkill
- kb-goalSkill
- kb-planSkill
- kb-recallSkill
- kb-recapSkill
- kb-sanitizeSkill
- kb-visualizeSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 1 is distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Read kb.config.yml. Note mode and language.
- Very specific: line 17
Read STATE.md — current focus + next step (intent ONLY.
- Very specific: line 18
Read index/MAP.md — domains and note counts.
- Very specific: line 20
If index/health.md exists, read it for open questions/risks.
- Very specific: line 21
Run npm run plan -- show — the operational plan (в розробці / черга / backlog + recent done).
- Very specific: line 34
Never read the whole knowledge/ tree here.
- Distinctive: line 35
Do not modify any file in this skill.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
kb-orient — session bootstrap
Goal: in seconds, know the current phase, what's done, what's next, and open questions — without loading the whole knowledge base.
Steps
- The SessionStart hook already put a
[kb] session snapshotin context (focus, plan, attention counts) — start from it; the steps below expand it. - Read
kb.config.yml. Notemodeandlanguage. Respond inlanguage.debug: report what you read and the full picture.autonomous: give only a short human summary of where things stand.
- Read
STATE.md— current focus + next step (intent ONLY; it does not hold counts/progress). - Read
index/MAP.md— domains and note counts. Do NOT open individual notes yet. This is the AUTHORITATIVE source for counts/progress; ifSTATE.mdever disagrees, MAP/health win. - If
index/health.mdexists, read it for open questions/risks. - Run
npm run plan -- show— the operational plan (в розробці / черга / backlog + recent done). This is the delivery half of "where we are"; STATE holds only strategic intent. Goals/timeline:index/roadmap.index.mdif needed. - Produce an orientation summary:
- Current phase and the single recommended next step.
- Plan snapshot: what's in work, what's next in the queue.
- Per-domain note counts (from MAP).
- Any open questions/risks you saw.
- Offer the live dashboard for visuals (
kb-dashboard→ http://localhost:4321).
- Hand off: if the next step is knowledge capture, suggest running
kb-elicitor proceed withkb-capturefor a specific insight.
Rules
- Never read the whole
knowledge/tree here. Orientation is index-only. - Do not modify any file in this skill.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

