obsidian-additions

Organize Obsidian notes with a two-level attachment system for supplementary materials.

4|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/flowing-abyss/obsidian-vault-skills --skill obsidian-additions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: obsidian-additions
Source: https://github.com/flowing-abyss/obsidian-vault-skills/tree/main/skills/obsidian-additions
Command: npx skills add https://github.com/flowing-abyss/obsidian-vault-skills --skill obsidian-additions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Obsidian Additions provide a two-level system to attach supplementary materials to existing notes: an aggregator space that groups by type and concrete additions that live under the aggregator, enabling structured context, better reference management, and scalable note enrichment.

Core Features & Use Cases

  • Aggregator space: create a central base/additions/ folder that groups related additions by type (practice, attachments, conspectuses, etc.) and keeps parent notes uncluttered.
  • Concrete additions: inside each aggregator, create concrete items (experiments, meetings, reports, conspectuses, annotations, links) that point back to the parent note.
  • Flexible linking: automatically update the parent note to reference new additions via wikilinks, preserving existing content.
  • Use Case: attach meeting notes to a project note, and within the aggregator collect all related experiments, logs, and references for quick access.

Quick Start

Create a new aggregator under base/additions and then add a concrete addition to attach it to an existing note.

Frequently Asked Questions about obsidian-additions

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

FAQPage Schema
How do I attach supplementary materials to Obsidian notes without clutter?

To attach supplementary materials to Obsidian notes without clutter, use a two-level attachment system with an aggregator space to group additions by type, keeping parent notes clean while linking concrete additions back via wikilinks.

What is the best way to organize meeting notes and references for a project in Obsidian?

The best way to organize meeting notes and references in Obsidian is creating an aggregator space under a base folder to group related experiments, logs, and conspectuses, automatically linking them to the parent project note.

Can I automatically update parent notes when adding new attachments in Obsidian?

Yes, you can automatically update parent notes when adding new attachments by leveraging a frontmatter-driven structure that preserves existing content and automatically inserts wikilinks pointing to the new additions.

Does the Obsidian additions workflow require specific dependencies or scripts?

The Obsidian additions workflow requires no external dependencies, utilizing an internal frontmatter-driven structure with optional scripts, references, and assets to support extended reuse within your note-taking environment.

When should I use an aggregator space versus direct attachments for note-taking?

You should use an aggregator space over direct attachments when you need scalable note enrichment and structured context, allowing you to group multiple concrete additions like experiments or annotations under a single typed category.