Our review
This skill tracks the evolution of an idea or topic across an Obsidian vault by searching for mentions, sorting them chronologically, and analyzing shifts in perspective.
Strengths
- Provides a visual timeline of how a thought developed over time
- Uses direct quotes to stay faithful to the original wording
- Handles Chinese notes with inline translation
- Identifies connections between notes and changes in conceptual framing
Limitations
- Depends on reliable dates in frontmatter or filenames
- May miss subtle conceptual shifts that don't change vocabulary
- Limited to .md files, does not cover other formats
Use this skill when you need to understand how an idea has grown, evolved, or changed meaning within your knowledge base.
Do not use it for simple fact-finding or if your vault is too small for meaningful evolution to occur.
Security analysis
SafeThe skill only reads local markdown files using a simple grep command. It does not perform any destructive actions, exfiltrate data, or interact with external systems. No sensitive operations are involved.
No concerns found
Examples
/trace machine learning/trace productivity system/trace mindfulnessname: trace description: 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.
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
-
Search broadly — grep all
.mdfiles in the vault for the topic (and synonyms/related terms)grep -ril "[topic]" ~/Documents/Obsidian/personalOS/ --include="*.md" -
Collect matches — read each matching file, extract:
- The file path and folder (tells you context: daily note vs knowledge vs project)
- The frontmatter
dateorcreatedfield - The surrounding paragraph(s) where the topic appears
-
Sort chronologically — by
date/createdfrontmatter, or by filename for daily notes (YYYY-MM-DD.md) -
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
API Documentation Generator
Documentation
Automatically generates OpenAPI/Swagger API documentation.
Technical Writer
Documentation
Writes clear technical documentation following top style guides.
Hono Documentation Search
Documentation
Use the hono CLI to search and view Hono framework documentation. It provides commands like hono search and hono docs to quickly find and browse documentation directly from the terminal. This is useful when developing with Hono and needing instant access to API references or guides.