Skip to content
Skills Library
Personal productivity · Analysis

trace

/trace

Map the chronological evolution of an idea across vault notes. Use when /trace is invoked or when Shane asks "how has my thinking on X changed", "when did I first write about X", "trace the evolution of X". Do NOT use to find connections between two separate ideas — that's /connect.

Licence
MIT
Last repository change
20.09.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 20.09.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Map the chronological evolution of an idea across vault notes. Use when /trace is invoked or when Shane asks "how has my thinking on X changed", "when did I first write about X", "trace the evolution of X". Do NOT use to find connections between two separate ideas — that's /connect.

Triggers from the description

how has my thinking on X changedwhen did I first write about Xtrace the evolution of X
Original author description

Map the chronological evolution of an idea across vault notes. Use when /trace is invoked or when Shane asks "how has my thinking on X changed", "when did I first write about X", "trace the evolution of X". Do NOT use to find connections between two separate ideas — that's /connect.

How it works

  1. Steps
  2. Fallback
Original SKILL.md headings · 25 lines, 195 words
SKILL.md preview
---
name: trace
description: Map the chronological evolution of an idea across vault notes. Use when /trace is invoked or when Shane asks "how has my thinking on X changed", "when did I first write about X", "trace the evolution of X". Do NOT use to find connections between two separate ideas — that's /connect.
---

# Skill: /trace [argument]

Map the arc of how Shane's thinking on a topic evolved — not the current position, but the path that led there and the inflection points along the way.

**Don't:** use this for cross-concept bridging — that's `/connect`. Don't present a settled position without showing the inflection points that led there.

## Steps

1. Parse the argument/topic from Shane's request.
2. Follow [Qwen Protocol](../_lib/qwen-protocol.md) with:
   - `task`: "Vault access (bash only, no MCP tools): `obsidian search query='TERM' limit=10`, `obsidian read file='Note Name'` (no .md). Map the chronological evolution of Shane's thinking about '[argument]'. What was the earliest framing? What shifted, and what triggered each shift? What's the current settled position (if any), or what remains unresolved? Highlight inflection points — moments where thinking meaningfully changed direction."
   - `skill`: "trace"
3. Review Qwen's result, synthesize if needed, and present to Shane.
4. Follow [Concept Save Protocol](../_lib/concept-save.md).

## Fallback

If Qwen is unavailable:

1. Run `obsidian search query='[argument]' limit=10` via bash; read notes paying attention to dates.
2. Sort chronologically. Identify: earliest framing, inflection points, current position.
3. Present a chronological narrative with specific note references and dates.
4. Follow [Concept Save Protocol](../_lib/concept-save.md).

Versions

RepositoryScoreLicence
This page · slogsdon/skills-vault-knowledge90MIT
jeremylongshore/tons-of-skills-marketplace100MIT
r3dlex/oh-my-auggie100Apache-2.0
zereight/gitlab-mcp100MIT
proxify-dev/agentic-kit100MIT
biliboss/skills100MIT
oliver-kriska/claude-elixir-phoenix100MIT
moonklabs/aiwf100MIT
Soul-Brews-Studio/arra-oracle-skills-cli100MIT

Database snapshot: 13.11.2026 · package version e23857b0e60e (SHA-256 digest of the entire package)

Downloads in the last 30 days: 1 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100explore
    Chronological timeline of an idea across notes. Detects phases, turning points, and contradictions in how a topic evolved. Use when the user asks "how did X evolve", "trace the history of Y", "timeline of Z", "when did we start thinking about", "show how this idea changed", or…
  • 100vault-retrieve
    Answer a question from the vault — generate the query fan-out, read every match, and return the relevant content verbatim with its paths. Use when Shane says "what do my notes say about X", "search the vault for X", "pull everything on X", "check my notes before we start", or…
  • 90migrate
    Bring notes from another notes system (a folder of markdown, an Obsidian or Logseq vault, exported notes) into this vault, one batch at a time. Use when the user asks to migrate or import existing notes.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.