Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

kb-session

Estrellas0

Forks0

Actualizado6 de julio de 2026 a las 11:52

Orient the session in the Ecosystem KB (prograph-vault) at start. Called automatically via a SessionStart hook. Read-only — detects the current project, surfaces applicable cross-cutting rules and the latest project journal entries, and points to /kb-load, /kb-save, /kb-search. Never writes to the KB.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

andrei-shtanakov

andrei-shtanakov/prograph-vault

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Otras ocupaciones informáticasOcupaciones informáticas y matemáticas·SOC 15-1299

SKILL.md

readonly

name	kb-session
description	Orient the session in the Ecosystem KB (prograph-vault) at start. Called automatically via a SessionStart hook. Read-only — detects the current project, surfaces applicable cross-cutting rules and the latest project journal entries, and points to /kb-load, /kb-save, /kb-search. Never writes to the KB.
allowed-tools	Bash, Read, Grep, Glob
user-invocable	false

kb-session — orient in the Ecosystem KB

Lightweight, read-only orientation for the current project against the shared KB (prograph-vault). Loads nothing heavy — just enough to know what the KB already holds. For a full context warm-up use /kb-load; to record work use /kb-save; for a targeted lookup use /kb-search.

Step 0 — Locate the KB

_kb() { local d; d="$(pwd -P)"; while [ "$d" != "/" ]; do
    [ -d "$d/prograph-vault/authored" ] && { printf '%s\n' "$d/prograph-vault"; return 0; }
    [ -d "$d/authored" ] && [ -f "$d/CLAUDE.md" ] && [ "$(basename "$d")" = prograph-vault ] && { printf '%s\n' "$d"; return 0; }
    d="$(dirname "$d")"; done; return 1; }
KB_ROOT="${KB_ROOT:-$(_kb)}"
[ -z "$KB_ROOT" ] && { echo "ℹ️  prograph-vault not found — continuing without the KB."; exit 0; }
source "$KB_ROOT/authored/skills/kb-utils/kb-env.sh"
PROJECT="$(kb_project || true)"
echo "KB: $KB_ROOT | project: ${PROJECT:-<unknown>}"

If the KB is not found, print the notice and continue the session silently — do not block startup.

Step 1 — Show what the KB has for this project

# Cross-cutting rules that apply everywhere
ls "$KB_ROOT/authored/rules/" 2>/dev/null

# This project's auto-facts (written by prograph)
ls "$KB_ROOT/derived/projects/${PROJECT}"* 2>/dev/null

# Latest journal entries for this project (written by kb-save)
tail -n 30 "$KB_ROOT/derived/journal/${PROJECT}/journal.md" 2>/dev/null

Step 2 — Brief recap (2–3 lines)

Print to the user, concisely:

Which project the session is in, and whether the KB has facts/journal for it.
The 2–3 most recent journal entries (date + one-line summary), if any.
A pointer: /kb-load <topic> to warm up context, /kb-save to record significant actions, /kb-search <query> to look something up.

Do not dump file contents. Keep it to a few lines; the KB is not loaded wholesale here. Write nothing to the KB.

Más de este repositorio

mismo repositorio

onboarding

andrei-shtanakov/prograph-vault

Guide a new contributor into the AI-Orchestrators ecosystem — walk a role checklist step by step, answer every question grounded in the KB with a citation, mark progress in the runtime store, and capture questions the KB cannot answer as KB-gap signal. Robin's first paid duty (ROBIN-SPEC §6.3; robin/duties.md

2026-07-070

kb-curator

andrei-shtanakov/prograph-vault

Curator of the Ecosystem KB (prograph-vault). Keeps the knowledge base in order: freshness audit of the registry and authored docs, archiving of the obsolete (with date+reason, no deletion), fixing broken links, knowledge search, graduation of canon from _cowork_output into the KB, and pruning/archiving the derived/journal. Run when the user asks: "tidy up the KB / knowledge base", "check the registry's freshness", "archive the obsolete", "fix the links in the vault", "find … in the KB", "move this from _cowork_output into the KB", "clean up authored", as well as on a scheduled (e.g. weekly) run. Works ONLY in the KB; other repos are read-only. Filesystem-only, no Obsidian.

2026-07-060

kb-load

andrei-shtanakov/prograph-vault

Proactively warm up context from the Ecosystem KB (prograph-vault) when starting work on a known area — interfaces, cross-cutting rules, contracts, or established patterns for the current project. Loads the relevant bundle at once (applicable rules + this project's facts/interfaces + related contracts + recent journal). Use at the start of a work area; for a single targeted question use kb-search instead.

2026-07-060

kb-save

andrei-shtanakov/prograph-vault

Record a significant action on the CURRENT project into the Ecosystem KB (prograph-vault) journal. Use after any notable project event — a decision, an interface/contract change, a new component, a migration, a status change, or a noteworthy result. Not just hard problems: log all significant project actions. Scoped to the current project only; appends to derived/journal/<project>/journal.md. Does not auto-commit.

2026-07-060

kb-search

andrei-shtanakov/prograph-vault

Answer a targeted question against the Ecosystem KB (prograph-vault) — standards, cross-cutting rules, templates, contracts, project facts, recent changes, or past activity. Use for ad-hoc lookups like "what's the rule for X", "which template for Y", "what changed in Z lately", "did we decide about W". Read-only, unrestricted across the whole KB. For proactively loading a work area up front, use kb-load instead.

2026-07-060

name	kb-session
description	Orient the session in the Ecosystem KB (prograph-vault) at start. Called automatically via a SessionStart hook. Read-only — detects the current project, surfaces applicable cross-cutting rules and the latest project journal entries, and points to /kb-load, /kb-save, /kb-search. Never writes to the KB.
allowed-tools	Bash, Read, Grep, Glob
user-invocable	false

kb-session — orient in the Ecosystem KB

Step 0 — Locate the KB

_kb() { local d; d="$(pwd -P)"; while [ "$d" != "/" ]; do
    [ -d "$d/prograph-vault/authored" ] && { printf '%s\n' "$d/prograph-vault"; return 0; }
    [ -d "$d/authored" ] && [ -f "$d/CLAUDE.md" ] && [ "$(basename "$d")" = prograph-vault ] && { printf '%s\n' "$d"; return 0; }
    d="$(dirname "$d")"; done; return 1; }
KB_ROOT="${KB_ROOT:-$(_kb)}"
[ -z "$KB_ROOT" ] && { echo "ℹ️  prograph-vault not found — continuing without the KB."; exit 0; }
source "$KB_ROOT/authored/skills/kb-utils/kb-env.sh"
PROJECT="$(kb_project || true)"
echo "KB: $KB_ROOT | project: ${PROJECT:-<unknown>}"

If the KB is not found, print the notice and continue the session silently — do not block startup.

Step 1 — Show what the KB has for this project

# Cross-cutting rules that apply everywhere
ls "$KB_ROOT/authored/rules/" 2>/dev/null

# This project's auto-facts (written by prograph)
ls "$KB_ROOT/derived/projects/${PROJECT}"* 2>/dev/null

# Latest journal entries for this project (written by kb-save)
tail -n 30 "$KB_ROOT/derived/journal/${PROJECT}/journal.md" 2>/dev/null

Step 2 — Brief recap (2–3 lines)

Print to the user, concisely:

Which project the session is in, and whether the KB has facts/journal for it.
The 2–3 most recent journal entries (date + one-line summary), if any.
A pointer: /kb-load <topic> to warm up context, /kb-save to record significant actions, /kb-search <query> to look something up.

Do not dump file contents. Keep it to a few lines; the KB is not loaded wholesale here. Write nothing to the KB.