From digital-brain
Capture a short, time-bound note in the wiki vault under `wiki/notes/`. Notes carry a kind (`task` or `reminder`) and a due time. They auto-expire 7 days after creation — expired notes never resurface in `/sync` or `/sup`. `/note` writes the note file, updates `wiki/notes/_index.md`, optionally touches `wiki/hot.md` if the due is in the next 24h, wikilinks any `@Person` mentions, and appends to `wiki/log.md`. Triggers on: "/note", "/digital-brain:note", "remind me to …", "note to self". Subcommands: add (default), list, done, clear.
How this skill is triggered — by the user, by Claude, or both
Slash command
/digital-brain:noteThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Notes are the lightweight, ephemeral cousin of full wiki pages. Use them for "ping Carol about the demo tomorrow", "review red-team PR by Friday", "buy a new charger". They live for **7 days**, then auto-expire.
Notes are the lightweight, ephemeral cousin of full wiki pages. Use them for "ping Carol about the demo tomorrow", "review red-team PR by Friday", "buy a new charger". They live for 7 days, then auto-expire.
User identity: [email protected]. Vault root: ~/digital-brain/.
wiki/notes/ (create if missing)wiki/notes/_index.md (create if missing — table of active notes only)wiki/index.md — has a ## Meta section; add [[notes/_index|Active Notes]] there oncewiki/log.md — append a note entry at the TOP after every add/donewiki/hot.md — touch ONLY if the note's due is within 24h| Form | Action |
|---|---|
/note <free-text> | add (default kind = reminder) |
/note task <free-text> | add with note_kind: task |
/note reminder <free-text> | add with note_kind: reminder (explicit) |
/note list | show active (non-expired, open) notes |
/note done <id-or-slug> | mark a note as done |
/note clear | manually sweep expired notes (auto on every invocation) |
If $ARGUMENTS is empty, show the forms and ask which one.
/note [kind] <tail>task or reminder, consume it and set note_kind. Otherwise default note_kind: reminder.by <when> / tomorrow / today HH:MM / <weekday> / in <N>h|d).
by 18:00 or by 6pm → today at that time (or tomorrow if already past)tomorrow [HH:MM] → tomorrow at the given time or 09:00next <weekday> → next occurrence of that weekday at 09:00in 3h / in 2d → relative from nowdue = today 18:00 (or tomorrow 09:00 if it's already past 18:00).@<Person>). Default assignee: me. If @Name appears, resolve via wiki/entities/people/_index.md:
assignee: "<Full Name>" and wikilink [[Full Name]] in the body.ppl skill with best-guess role, then link.by … / @Name is the title. Trim to ≤ 80 chars; full text stays in the body.add Workflowwiki/notes/*.md.created = now (ISO YYYY-MM-DD HH:MM, local time)expires = created date + 7 days (date only, YYYY-MM-DD)slug = lowercase title, non-alphanum → -, trimmed to 40 charsnote_id = <YYYY-MM-DD>-<HHMM>-<slug>wiki/notes/ and wiki/notes/_index.md from the template below if missing.wiki/notes/<note_id>.md from the Note Page Template._index.md: add a row to the matching section (Active Tasks / Active Reminders). Notes with status: expired or done are NEVER in _index.md — the index is the working set.wiki/index.md once: under ## Meta, ensure a bullet - [[notes/_index|Active Notes]] - active tasks and reminders (7-day TTL) exists. If already present, skip.due is within the next 24h (compute against now), append a one-liner under ## Active Threads in wiki/hot.md. Format: - ⏰ <due time> — <title> — [[notes/<note_id>]].wiki/log.md (under the header):
## [YYYY-MM-DD HH:MM] note add | <note_id>
- Kind: <task|reminder>
- Due: <YYYY-MM-DD HH:MM>
- Expires: <YYYY-MM-DD>
- Assignee: <name>
- Location: wiki/notes/<note_id>.md
Filed <kind> [[notes/<note_id>]] — due <due>, expires <expires>.list Workflowwiki/notes/_index.md. Render the two tables (Active Tasks, Active Reminders).due ascending. Mark rows with due ≤ now + 4h as 🔥.due.done <id-or-slug> Workflowwiki/notes/ and slug portions. If ambiguous, list candidates and ask.status: done, append a ## Closed section with timestamp._index.md.## [YYYY-MM-DD HH:MM] note done | <note_id>.clear Workflowexpired and which.Every invocation of /note, /sync, and /sup runs this sweep BEFORE doing anything else:
for each wiki/notes/*.md where status == "open":
if today > expires:
set status: expired
bump updated to today
remove the row from _index.md
(do NOT delete the file — keep for history)
Expired notes are invisible to /sync and /sup. They stay on disk for retrospection but never resurface in dashboards. If the user wants something back after 7 days, they re-create it — that's the design.
The sweep is idempotent and cheap; never skip it.
---
type: note
note_kind: <task|reminder>
title: "<title>"
created: <YYYY-MM-DD HH:MM>
due: <YYYY-MM-DD HH:MM>
expires: <YYYY-MM-DD>
status: open
assignee: "<Full Name or me>"
linear: ""
tags:
- note
- <note_kind>
related:
- "[[notes/_index|Active Notes]]"
---
# <title>
<full free-text body from the /note input, with any [[Person]] wikilinks resolved>
## Source
- /note invocation at <YYYY-MM-DD HH:MM>
_index.md Template---
type: meta
title: "Active Notes"
updated: <YYYY-MM-DD>
tags: [meta, index, notes]
status: evergreen
related:
- "[[index]]"
- "[[hot]]"
---
# Active Notes
7-day TTL. Expired notes drop off this index automatically; they remain on disk under `wiki/notes/` for history.
Add via `/note <text>` or `/note task <text>`. Mark done via `/note done <id>`.
---
## Active Tasks
| ID | Title | Assignee | Due | Linear |
| --- | ----- | -------- | --- | ------ |
## Active Reminders
| ID | Title | Due |
| --- | ----- | --- |
If the input mentions a person (either as @Name or in free text matching an existing alias in wiki/entities/people/_index.md), wikilink them in the note body. If the name doesn't resolve, apply the flywheel: file them via ppl with best-guess role and a > [!todo] Confirm role callout, THEN link. Never emit a phantom [[Name]] to a non-existent page.
/note review red-team PR by friday @AliceAlice Smith (resolved from alias Alice)review red-team PRwiki/notes/2026-05-13-1430-review-red-team-pr.md/note task ship BigCustomer retro by tomorrow 12:00wiki/notes/2026-05-13-1430-ship-bigcustomer-retro.md/note list_index.md, sorted by due, 🔥 on anything due in next 4h./note done 2026-05-13-1430-review-red-team-pr_index.md. Logs.status. History matters.due — always default to today 18:00 / tomorrow 09:00.wiki/hot.md unless due is within 24h._index.md — the index is the working set only.npx claudepluginhub eliransu/digital-brainFetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Applies a firm's KYC/AML rules grid to parsed onboarding records: assigns risk rating, checks required documents, outputs rule outcomes with citations, and routes for escalation.
Generates daily or weekly digests of activity from connected sources (chat, email, docs, tasks, CRM), highlighting action items, decisions, mentions, and project updates.