til

Extract technical learnings from AI chat sessions into Obsidian daily notes.

1|Updated Jun 8, 2025
One-click install
npx skills add https://github.com/ryosukesuto/dotfiles --skill til-ryosukesuto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: til
Source: https://github.com/ryosukesuto/dotfiles/tree/main/config/claude/skills/til
Command: npx skills add https://github.com/ryosukesuto/dotfiles --skill til-ryosukesuto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you capture valuable technical learnings and system insights from your current AI chat session, ensuring that knowledge isn't lost and is easily retrievable in your Obsidian notes.

Core Features & Use Cases

  • Knowledge Extraction: Identifies and extracts key technical learnings, service specifications, domain knowledge, troubleshooting steps, and system structures from conversations.
  • Obsidian Integration: Formats extracted information into Markdown suitable for Obsidian, including proper headings, tags (e.g., #til/category), and internal links ([[link]]).
  • Daily Note Appending: Appends the formatted knowledge to your Obsidian daily notes, creating a searchable and organized knowledge base.
  • Use Case: After a debugging session that uncovered a specific configuration detail for a service, use /til [service-name] to automatically record the finding, its context, and the solution in your daily Obsidian note.

Quick Start

Use the til skill to extract knowledge from the current session, focusing on Fastly configurations.

Frequently Asked Questions about til

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract technical learnings from an AI chat session into Obsidian notes?

You can extract technical learnings into Obsidian notes by running the command to identify key specifications and troubleshooting information, format it with Markdown headings and tags, and append it directly to your daily note.

Can I save specific troubleshooting steps from a chat to my Obsidian daily notes?

Yes, you can save specific troubleshooting steps by specifying a topic, which filters the chat session extraction to isolate relevant context and solutions before appending the formatted Markdown to your Obsidian daily note.

How does this append Markdown formatted knowledge to Obsidian daily notes?

It appends Markdown knowledge by applying Obsidian-specific formatting, including proper headings, tags like #til/category, and internal links using [[link]] syntax, then writes the content using the Obsidian CLI.

Do I need the Obsidian CLI to record session knowledge into my notes?

Yes, the Obsidian CLI is required because the skill uses it to append the extracted and Markdown-formatted technical knowledge directly into your existing Obsidian daily notes.

What is the best way to capture service specifications from an AI conversation into a knowledge base?

The best way to capture service specifications is to extract the domain knowledge from your session, optimize it with internal links and tags, and append it to a daily note to create a searchable knowledge base.

Can I focus knowledge extraction on a specific service configuration discussed in the session?

Yes, you can focus extraction on a specific service configuration by providing the service name as an argument, ensuring only the relevant technical details and system structures are recorded.