Chronological tracker for how a specific topic has developed within your personal notes.

Install

mkdir -p .claude/skills/trace-kingjinsight && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13244" && unzip -o skill.zip -d .claude/skills/trace-kingjinsight && rm skill.zip

Installs to .claude/skills/trace-kingjinsight

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Use when the user runs /trace [topic] or wants to see how an idea evolved over time across the vault. Tracks the arc of thinking on a specific topic.
149 chars✓ has a “when” trigger
Beginner

Key capabilities

  • Search for a topic across vault files
  • Extract topic mentions from markdown files
  • Sort matches chronologically
  • Identify the first mention of an idea
  • Trace the evolution of an idea over time

How it works

The skill searches markdown files for the given topic, extracts relevant paragraphs and creation dates, then sorts them chronologically to reconstruct the idea's evolution.

Inputs & outputs

You give it
A topic to trace
You get back
A chronological report detailing the evolution of the topic across notes

When to use trace

  • Tracing idea evolution
  • Finding related notes
  • Summarizing topic history

About this skill

Trace — Idea Evolution Tracker

Show how a specific idea or topic has evolved across King's vault over time.

Input

The user provides a topic after the command: /trace [topic] If no topic given, ask: "What idea do you want to trace?"

Process

  1. Search broadly — grep all .md files in the vault for the topic (and synonyms/related terms)

    grep -ril "[topic]" ~/Documents/Obsidian/personalOS/ --include="*.md"
    
  2. Collect matches — read each matching file, extract:

    • The file path and folder (tells you context: daily note vs knowledge vs project)
    • The frontmatter date or created field
    • The surrounding paragraph(s) where the topic appears
  3. Sort chronologically — by date/created frontmatter, or by filename for daily notes (YYYY-MM-DD.md)

  4. Trace the arc — look for:

    • First mention: what was the original framing?
    • How did the language/framing shift over time?
    • What other concepts got linked to it?
    • Where does it sit now — active project, knowledge note, daily thought?

Output Format


Tracing: [topic] Found in [N] notes across [date range]

First appearance — [date], [file]

[quote or paraphrase]

Evolution

  • [date] — [file type] — [how the idea shifted]
  • [date] — [file type] — [new angle or connection]
  • ...

Current state — [where it lives now, how it's framed]

Connected to

  • [[note]] — [why it's connected]

Observation — [one insight about how this idea has grown or changed]


Rules

  • Pull direct quotes where possible — King's own words, not summaries
  • Chinese content in daily notes: include it, translate inline
  • If topic appears in only 1-2 notes, say so — the trace may be short
  • Don't force connections that aren't there

When not to use it

  • When not tracing the evolution of an idea
  • When not searching for a topic across the vault
  • When not needing to see how an idea evolved over time

Limitations

  • If topic appears in only 1-2 notes, the trace may be short
  • Does not force connections that are not present in the notes
  • Requires markdown files with date or created frontmatter for accurate sorting

How it compares

This skill provides a structured chronological trace of an idea's development across a knowledge vault, unlike a simple keyword search.

Compared to similar skills

trace side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
trace (this skill)03moReviewBeginner
qmd262moReviewIntermediate
deep-reading-analyst19moNo flagsBeginner
knowledge-base16moReviewBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

qmd

tobi

Search personal markdown knowledge bases, notes, meeting transcripts, and documentation using QMD - a local hybrid search engine. Combines BM25 keyword search, vector semantic search, and LLM re-ranking. Use when users ask to search notes, find documents, look up information in their knowledge base, retrieve meeting notes, or search documentation. Triggers on "search markdown files", "search my notes", "find in docs", "look up", "what did I write about", "meeting notes about".

2669

deep-reading-analyst

ginobefun

Comprehensive framework for deep analysis of articles, papers, and long-form content using 10+ thinking models (SCQA, 5W2H, critical thinking, inversion, mental models, first principles, systems thinking, six thinking hats). Use when users want to: (1) deeply understand complex articles/content, (2) analyze arguments and identify logical flaws, (3) extract actionable insights from reading materials, (4) create study notes or learning summaries, (5) compare multiple sources, (6) transform knowledge into practical applications, or (7) apply specific thinking frameworks. Triggered by phrases like 'analyze this article,' 'help me understand,' 'deep dive into,' 'extract insights from,' 'use [framework name],' or when users provide URLs/long-form content for analysis.

13

knowledge-base

incidentfox

Search runbooks, documentation, and knowledge base articles from Confluence. Use when looking for incident response procedures, service documentation, post-mortems, or troubleshooting guides.

12

ask

Lambenthan

对 wiki 提问,综合检索相关页面后回答,好的回答可 crystallize 回 wiki

00

search

V1CeVersaa

>-

00

notebooklm-management

bg-szy

NotebookLM MCP server management - query notebooks, add from share links, handle auth, reset sessions. Use when working with Google NotebookLM notebooks for conversational research tasks.

00

Search skills

Search the agent skills registry