kg-history

Writes dated changelog entries for knowledge graph batches into weekly Markdown history files.

1.6k|143|Updated Sep 9, 2019
One-click install
npx skills add https://github.com/frutik/awesome-search --skill kg-history
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kg-history
Source: https://github.com/frutik/awesome-search/tree/main/claude-skills/kg-history
Command: npx skills add https://github.com/frutik/awesome-search --skill kg-history

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintaining a consistent, readable changelog for a growing Obsidian knowledge graph is tedious and error-prone; this Skill enforces a fixed entry format so every batch of note edits produces a uniform, subscriber-friendly history entry.

Core Features & Use Cases

  • Fixed Entry Format: Generates entries with a dated heading, per-entry new/updated counts, one 60-120 word prose paragraph, optional corrections bullets, and typed New/Updated wikilink lines.
  • Weekly File Management: Creates and prepends to ISO-week files (History/<year>.<week>.md) while keeping History.md as a pure index of links with refreshed entry counts.
  • Style Enforcement: Applies 14 hard rules banning deliberation, running totals, graph-centric language, and unresolved wikilinks.
  • Use Case: After a batch that adds notes on multi-tenancy in search engines, invoke this Skill to write a dated entry announcing what the material covers, link the new notes, and update the weekly index before review.

Quick Start

Write the history entry for the batch of notes just added to the Awesome Search knowledge graph.

Frequently Asked Questions about kg-history

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

FAQPage Schema
How do I write a changelog entry for knowledge base edits?

Invoke this Skill at the end of each editing batch. It splits the work into coherent units, computes new and updated note counts, drafts a 60-120 word paragraph per unit, and prepends entries to the current ISO week file.

How are weekly history files organized in Obsidian?

Entries live in History/<year>.<week>.md files named by ISO week, newest first, separated by horizontal rules. History.md is only an index of links to those week files with entry counts, never the entries themselves.

Can one session produce multiple history entries?

Yes. Unrelated work in one session, such as processing an article plus fixing an unrelated stub, gets separate entries, each with its own heading, counts, and paragraph. Merging unrelated work into one entry is prohibited.

What content is banned from history entries?

Entries cannot contain deliberation about rejected options, running totals, words like vault or graph, subheadings, tables, or paragraphs over 120 words. Corrections are limited to three bullets stating what changed and where.

When should the history entry be written in the workflow?

Write it at the end of every batch, after the note-writing work completes and before the review step. The entry is written from session context or the writer subagent's report, never reconstructed from diffs.