vault-mirror
SolidUse when you need to populate the Meta-Vault with machine-generated notes derived from session-orchestrator JSONL records. Converts entries from `.orchestrator/metrics/sessions.jsonl` and `.orchestrator/metrics/learnings.jsonl` into vault-conformant Markdown under `50-sessions/` and `40-learnings/`. Called automatically at session-end Phase 3.7 and after evolve Phase 3.5 — only when `vault-integration.enabled=true` and `vault-integration.mode != "off"`. Idempotent: re-runs safely; skips hand-authored notes. Triggers: "mirror to vault", "sync session notes to vault", "write learning notes to vault", "vault-mirror failed at session close". <example>Context: session-end is finalizing, vault-integration.mode is "warn". user: "/close" assistant: "Running vault-mirror to write 50-sessions/session-2026-05-17.md from the closing session record — 1 created, 0 skipped."</example>
Install
Quality Score: 82/100
Skill Content
Details
- Author
- Kanevry
- Repository
- Kanevry/session-orchestrator
- Created
- 5 months ago
- Last Updated
- today
- Language
- JavaScript
- License
- MIT
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
vault-sync
Use when you need to validate the Meta-Vault's Markdown frontmatter and wiki-link integrity before closing a session or after vault edits. Runs as a hard gate at session-end Phase 1 — blocks close if any `.md` file fails the Zod frontmatter schema or has dangling `[[wiki-links]]`. Supports three modes: `hard` (blocks on errors), `warn` (reports without blocking), `off` (skip). Reads `vault-sync.*` from Session Config; respects per-vault exclude globs from `CLAUDE.md`. Triggers: "vault validation failed at session close", "fix vault frontmatter errors", "check vault wiki-links", "why is session-end blocked by vault-sync". <example>Context: session-end Phase 1 quality gate, vault-sync.enabled=true, vault-sync.mode="hard". user: "/close" assistant: "vault-sync found 2 frontmatter errors in vault/40-learnings/ml-notes.md — missing required `id` field. Fixing before close."</example>
vault-skill
Persistent project memory in a local Obsidian vault (.claudevault). Use PROACTIVELY — do not wait to be asked — whenever any of these happen: an architecture/design decision is made ("we decided", trade-offs weighed, alternatives chosen); a work session ends or is being wrapped up; project context/goals/stack change; reference knowledge worth keeping again surfaces (research, specs, findings hard to re-derive); the user wants to init the vault, read context at the start of a session, process the raw/ intake folder, or generate a report/briefing into outputs/. Creates interlinked markdown notes (decisions, logs, knowledge) that reference each other with [[wikilinks]] and all link back to context.md.
reflect
Close a working session by turning what it taught into durable memory: atomic facts with evidence, each routed to its single owner — an Obsidian vault core with its folder of fact notes, the project's agent memory, the always-loaded global rules, or a pending list for rules seen once — and applied as ADD, UPDATE, LINK, SUPERSEDE or NOOP without writing what is already written. Also opens a session by reading the project's core back. Use when the user closes or wraps up a session, asks for a reflection or retrospective, asks what the vault knows about the current project, or when a hook reports a compacted session. Triggers: close the session, wrap up, reflect, retrospective, what do we know about this project, start the session, закрываем сессию, проведи рефлексию, подведём итоги, что мы знаем про этот проект, начинаем сессию, рефлексия в фоне