keeper-save

Insert and append structured notes into an Obsidian vault via vault-librarian.

Updated Feb 19, 2026
One-click install
npx skills add https://github.com/nhangen/claude-obsidian-plugin --skill keeper-save
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: keeper-save
Source: https://github.com/nhangen/claude-obsidian-plugin/tree/main/skills/keeper-save
Command: npx skills add https://github.com/nhangen/claude-obsidian-plugin --skill keeper-save

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the insertion and appending of structured notes into an Obsidian vault, eliminating the need for manual entry and back-and-forth interactions.

Core Features & Use Cases

  • Agent-Facing Entry Point: Provides a structured interface for agents and sub-skills to file or append notes to the vault.
  • Vault Operations: Handles INSERT and APPEND operations, validating structured payloads and dispatching vault-librarian tasks.
  • Use Case: Ideal for scenarios where multiple agents or sub-skills need to contribute to the vault, such as daily logs, research findings, and decision documentation.

Quick Start

Dispatch the vault-librarian with a payload file for note insertion using the keeper-save skill.

Frequently Asked Questions about keeper-save

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

FAQPage Schema
How do I automate note insertion into an Obsidian vault from an agent?

You can automate Obsidian vault note insertion by dispatching a structured payload to the vault-librarian, which validates the content and handles the filing. This eliminates manual entry and enables seamless agent-generated documentation.

What's the best way to append structured notes to an Obsidian vault?

The best way to append structured notes is using a structured payload framework that supports APPEND operations. The system validates the payload and routes it through the vault-librarian for deduplication and proper placement within the vault.

Can multiple agents contribute to the same Obsidian vault without duplicate entries?

Yes, multiple agents can contribute to the same Obsidian vault. The system leverages a vault-librarian for routing and deduplication, ensuring that structured payloads from different sub-skills do not create duplicate notes.

Does keeper-save support both creating new notes and appending to existing ones?

Yes, it supports both INSERT and APPEND operations. INSERT handles creating new notes, while APPEND adds content to existing files, providing a standardized interface for all agent-generated content filing needs.

When do I need a structured payload for vault automation?

You need a structured payload for vault automation when multiple agents or sub-skills require a standardized interface to file daily logs, research findings, or decision documentation without manual back-and-forth interactions.

Why use a vault-librarian for routing agent-generated notes?

Using a vault-librarian for routing agent-generated notes ensures proper deduplication and structured placement within the Obsidian vault. It acts as an agent-facing entry point that validates payloads before committing them.