vault-synthesis_skill

This skill synthesizes notes across the vault to create cohesive histories, frontmatter summaries, and topic hubs while preserving links.
  • TypeScript

0

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill nweii/agent-stuff --skill vault-synthesis

  • changelog.md765 B
  • SKILL.md3.2 KB

Overview

This skill synthesizes and organizes content across a vault of notes, producing history rollups, frontmatter summaries, periodic rollups, and topic hub notes. It streamlines cross-note aggregation so you can find high-value insights without manual copying or scattered context loss.

How this skill works

The skill scans selected notes and extracts salient lines, metadata, and timestamps, preserving wikilinks back to original sources for provenance. It then generates targeted outputs: a consolidated history note, a concise YAML frontmatter description, a parent periodic-summary from child descriptions, or a topic note that groups related items with backlinks. Outputs respect vault hierarchy and metadata conventions to remain navigable and token-efficient.

When to use it

  • Compile mentions of a project or domain into a single History note
  • Generate or update the description frontmatter for an individual note
  • Roll up daily note summaries into weekly or quarterly parent notes
  • Create a focused topic hub that groups related notes and backlinks
  • Any time you need traceable, low-overhead aggregation across many notes

Best practices

  • Always keep wikilinks to source notes in the synthesized output for traceability
  • Choose an abstraction level appropriate to the destination note (detailed for working notes, high-level for indexes)
  • Prefer frontmatter description fields for short navigational summaries to save tokens
  • Respect existing metadata (tags, categories, types) and update related properties bidirectionally
  • Run periodic rollups on a cadence (weekly/quarterly) to avoid large one-off syntheses

Example use cases

  • Roll up daily standup notes into a weekly summary that links to each day
  • Auto-generate a note's description frontmatter after significant edits
  • Aggregate mentions of a client across months into a single project history
  • Create a Topic note that groups all research notes on a given method with backlinks
  • Synthesize quarterly progress from weekly summaries for reporting

FAQ

Yes. Every synthesis preserves wikilinks back to source notes so provenance is clear.

How does the skill decide abstraction level for rollups?

It matches the target: periodic rollups prioritize concise summaries of child descriptions, while history notes retain more context and representative excerpts.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational