obsidian-capture

Save session insights, error causes, and library usage into Obsidian vault notes.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/UtakataKyosui/C2Lab --skill obsidian-capture-utakatakyosui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: obsidian-capture
Source: https://github.com/UtakataKyosui/C2Lab/tree/main/plugins/obsidian-knowledge/skills/obsidian-capture
Command: npx skills add https://github.com/UtakataKyosui/C2Lab --skill obsidian-capture-utakatakyosui

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of saving valuable insights, error resolutions, and technical knowledge gained during a session directly into your Obsidian vault, ensuring that important information is organized and easily retrievable.

Core Features & Use Cases

  • Organized Knowledge Storage: Automatically categorizes and saves information into appropriate sections of your Obsidian vault (daily notes, knowledge base, procedures).
  • Flexible Saving Options: Supports both appending to existing notes and creating new notes with specified content and paths.
  • Link Integration: Encourages the creation of links to related notes, enhancing your knowledge graph.
  • Use Case: After successfully debugging a complex issue, use this Skill to save the solution steps and related error messages into your knowledge/ notes, linking it to the relevant library or concept.

Quick Start

Use the obsidian-capture skill to create a new note named 'new-feature-ideas' in the 'knowledge' directory with the content 'Brainstorming session notes...'.

Frequently Asked Questions about obsidian-capture

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

FAQPage Schema
How do I save session insights and error resolutions directly to an Obsidian vault?

You can save session insights to an Obsidian vault by using a capture skill that categorizes episode memories into daily notes, semantic memories into knowledge notes, and procedural memories into procedures.

What is the best way to organize debugging solutions into my personal knowledge base?

Organizing debugging solutions into a personal knowledge base is best handled by automatically categorizing error causes and library usage into dedicated knowledge notes with links to relevant concepts.

Do I need to configure environment variables to capture notes into Obsidian?

Yes, capturing notes into Obsidian requires you to configure environment variables with your specific Obsidian vault name or path so the session insights can be saved to the correct location.

Can I append new technical knowledge to existing daily notes in Obsidian?

Yes, you can append new technical knowledge to existing daily notes in Obsidian, or you can create entirely new notes with specified content and directory paths for flexible knowledge storage.

How does linking related notes work when saving session memories to Obsidian?

Linking related notes works by encouraging the creation of internal links within your saved session memories, which enhances your overall knowledge graph by connecting procedural and semantic memories.