Menu
Captures an ad-hoc note, idea or piece of context into the company brain in one step. Use when something worth remembering surfaces mid-task and should not be lost.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | quick-note |
| description | Captures an ad-hoc note, idea or piece of context into the company brain in one step. Use when something worth remembering surfaces mid-task and should not be lost. |
| version | 0.1.0 |
| triggers | ["remember that","note to self","capture this","jot down"] |
| tools | ["Vitrus:remember"] |
Lower the friction of capture to near zero, so context is never lost.
Vitrus:remember with the note content and an optional title. It writes to the markdown source and indexes it.vitrus capture "the note" (or pipe: echo ... | vitrus capture).vitrus ingest inbox <dir> to capture from mobile (iOS Shortcuts/iCloud).Notes are working-tier and decay over time. Promote anything durable into a proper decision or document.
Answers a question from the company brain with cited sources and an honest list of what is not documented yet. Use when someone asks a factual question about the company, its systems, people, decisions or incidents.
Records a decision and its rationale back into the company brain after it is made, with sources, and detects supersede and contradiction effects. Use immediately after an architectural or process decision is reached.
Triages what needs human attention now: stale durable knowledge, unresolved incidents and aging gaps, ranked by severity and age. Use at the start of a work session or on-call shift.
Finds who owns or is responsible for a service, decision or area by traversing the typed knowledge graph and entity index. Use when someone needs to know who to talk to about X.
Helps a newcomer learn an unfamiliar area of the company or codebase by mapping its key entities, owners and decisions from the brain. Use in the first days on a new team, service or domain.
Reviews the company as a system and flags operational risks: unowned services, single-person bus-factor, bottlenecks, broken handoffs and redundant tools, each citing the real nodes behind it. Use for a health check or before reorganizing.