Menu
Capture a reusable piece of knowledge — populates the Knowledge atlas
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
Log a work achievement as a linked note in the vault — for performance reviews
End-of-day check-in — pulls GitHub activity, compares to existing logs, and creates missing entries
Log a concrete task with an optional deadline — surfaces in daily briefings
Morning planning session - reads recent vault activity, flags urgent items, plans the day
Initialise claudia for a new user — walks through prerequisites, then uses the Obsidian CLI to set up the vault
Weekly review - flags forgotten ideas/tasks, summarises the week
| name | til |
| description | Capture a reusable piece of knowledge — populates the Knowledge atlas |
| argument-hint | <what you learned> |
Capture a piece of knowledge. Today: !date +%Y-%m-%d.
Input: $ARGUMENTS
If $ARGUMENTS is empty, ask: "What did you learn?"
Generate a short slug from the insight (lowercase, hyphens, 4-6 words max).
Pick the most fitting Knowledge section — don't ask, just pick:
Create the note:
obsidian create name="[date]-[slug]" path="Notes/" content="---
date: [date]
type: knowledge
tags: [knowledge/SECTION]
---
# [Insight title]
[The knowledge as described — keep it concise and reusable]
"
Tags use the section name lowercase: knowledge/engineering, knowledge/process, knowledge/personal, knowledge/reference.
Insert into the correct section of Knowledge.md:
obsidian read file="Atlas/Knowledge"## [Section] heading- [[date-slug]] | [date] after any existing entries under that headingCheck if the knowledge relates to recent work:
obsidian search query="tag:status/done" --output paths
If a recent work note or project is clearly related, mention the link: "Related to [[note-name]]."
Confirm: "Saved as [[date-slug]]. Knowledge atlas now has [N] entries."
Do not over-elaborate. Just capture it.