til
Captures learnings from any session — coding, research, or a /learn conversation — into an engaging TIL note in the Obsidian vault. Make sure to use this skill whenever the user runs /til, says "save what I learned", "create a TIL", "document this session", "write up what we built", or reaches the end of any learning or coding session where new things were learned. Also triggers at the end of a /learn session when the user says "done". Writes like telling a story to a friend — not a dry report.
What this skill does
# TIL (Today I Learned) Capture 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. ## Step 1 — Identify the Topic Use `$ARGUMENTS` if provided. Otherwise infer from: 1. Current working directory (`pwd`) 2. Git repo name (`git remote get-url origin`) 3. Dominant topic from the conversation ## Step 2 — Check for an Existing TIL Today ```bash obsidian read path="3 - Resources/TIL/til-$(date +%Y-%m-%d).md" 2>/dev/null ``` If a note exists: append a new section. Never overwrite — today may have multiple sessions. ## Step 3 — Extract Learnings from the Conversation Analyze the full conversation and pull out: - **What was built, learned, or designed** — the artifact or insight - **Key decisions and trade-offs** — why this approach over alternatives - **Bugs or blockers encountered and fixed** — symptom, root cause, fix - **"Aha moments"** — insights that reframe how you think about something - **What would be done differently** — honest retrospective ## Step 4 — Write with an Engaging Voice Write like telling a story to a friend, not filing a report. **Use:** - Analogies: "it's like a cache, but for..." - Anecdotes: "We tried X first — it broke because..." - Before/after code for bug fixes and pattern changes - Mermaid diagrams for architecture or data flow when they clarify structure **Required frontmatter tags (3–5 using `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` | **Note structure:** ```markdown --- 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 — skip if nothing stands out> ``` ## Step 5 — Save the Note ```bash # New note obsidian create path="3 - Resources/TIL/til-$(date +%Y-%m-%d).md" \ content="<full note content>" # Existing note — append new section obsidian append path="3 - Resources/TIL/til-$(date +%Y-%m-%d).md" \ content="\n## Session 2 — <title>\n\n<content>" ``` ## Hard Rules - Never mention Claude or AI assistance in the note — write in first person - Never overwrite an existing TIL — always append a new section - Write for future-you in 6 months, not for the PR description - If Obsidian CLI fails: tell the user "Obsidian CLI isn't working — update Obsidian with CLI enabled"
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.