Menu
TIL capture for explicit requests to save learned material from a session into an engaging Obsidian note. Use when the user runs /til or asks to save, document, or write up what they learned.
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 | til |
| description | TIL capture for explicit requests to save learned material from a session into an engaging Obsidian note. Use when the user runs /til or asks to save, document, or write up what they learned. |
| user-invocable | true |
| argument-hint | [project or topic name — omit to infer from context] |
Turn a session into a durable, engaging knowledge note. The goal is a note future-you will actually want to read — not a dry changelog. This skill is the single source of truth for TIL note format.
Use $ARGUMENTS if provided. Otherwise infer from:
pwd)git remote get-url origin)Complete when the topic/project name is explicit or the inferred topic is shown to the user.
obsidian read path="3 - Resources/TIL/til-$(date +%Y-%m-%d).md" 2>/dev/null
If a note exists, append a session entry. Never overwrite — today may have multiple sessions.
Analyze the full conversation and pull out only evidence-backed material:
Completion: every listed learning category has either extracted evidence from the conversation or is intentionally omitted as not applicable. Do not pad empty categories.
Write like telling a story to a friend, not filing a report.
Use:
Required frontmatter tags: 3–5 tags using the til/ prefix.
| Category | Examples |
|---|---|
| Technology | til/react, til/typescript, til/nextjs, til/python |
| Patterns | til/architecture, til/testing, til/debugging, til/performance |
| Libraries | til/tanstack-query, til/zod, til/prisma |
| Concepts | til/accessibility, til/security, til/composition |
---
tags: [til/typescript, til/architecture]
date: YYYY-MM-DD
project: <topic or project name>
---
# TIL: <engaging title that captures the insight>
## What We Covered
<brief context — one sentence>
## The Story
<narrative with anecdotes, analogies, code snippets>
## Key Insight
<the one thing to remember>
## What I'd Do Differently
<honest retrospective — omit if nothing stands out>
Append only a session section. Do not repeat frontmatter or the top-level # TIL title.
## Session N — <engaging title>
### What We Covered
<brief context>
### The Story
<narrative>
### Key Insight
<the one thing to remember>
### What I'd Do Differently
<omit if nothing stands out>
# New note
obsidian create path="3 - Resources/TIL/til-$(date +%Y-%m-%d).md" \
content="<full note content>"
# Existing note — append a session entry only
obsidian append path="3 - Resources/TIL/til-$(date +%Y-%m-%d).md" \
content="\n## Session N — <title>\n\n<session content>"
After saving, confirm the note title, location, and categories included.
Audit existing React Hook Form code for correctness, accessibility, validation, data ownership, submission, dirty-state, field-array, wizard, controlled-widget, and performance problems. Use when reviewing RHF forms, investigating form bugs or rerenders, or checking an RHF-heavy change. Read-only; use react-hook-form for implementation.
Build and modify React Hook Form forms. Use when React Hook Form is mentioned, imported, installed, or established by project conventions, including controlled widget integration, schema validation, fetched edit forms, conditional fields, multi-step wizards, field arrays, submission errors, and dirty-state handling. Use the react-hook-form-audit skill when the job is review rather than implementation.
Capture a concrete work or learning receipt in today's Obsidian note, then optionally hand it to tweet-today or blog. Use when the user says "save this for sharing", "capture this receipt", "tweet this now", or when close-day promotes an Idea Worth Sharing.
End-of-day Obsidian ritual: close the active focus loop, triage Ideas Worth Sharing, and confirm tomorrow's carry-forward. Use for "close my day", "end of day", "wrap up today", or /close-day.
Daily startup ritual for the Obsidian vault: create today's workday note, surface exact context, and require the user to choose one daily outcome and next action. Use for "start my day", "daily startup", "today's focus", or /daily.
Obsidian goals review for quarterly, monthly, or weekly goal notes. Use when the user asks to review goals, run an OKR check-in, update goals, set monthly goals, check whether goals are on track, or runs /goals.