Drift
Twenty Obsidian knowledge-work skills for Claude Code: connect, contradict, emerge, trace, ghost, weekly-learnings.
npx -y skills add slogsdon/skills-vault-knowledge --skill driftAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Analyze gaps between stated priorities (OKRs, focus statements) and actual session behavior to surface drift. Use when /drift is invoked, when the user says "am I doing what I said I would", "where am I off-track", "do my actions match my goals", "am I avoiding something", or during weekly retrospectives. Reads accountability.md, patterns.md, and recent daily notes. Do NOT use for surfacing patterns within a topic — use /emerge for that.
SKILL.md
2.4 KB, as published. Nobody here has run it
Skill: /drift [argument]
Surface the gap between Shane's stated intentions and actual behavior — where he's drifting from his own goals and values, with vault evidence for each.
Don't: use this for topic pattern analysis — that's /emerge. Don't soften drift findings — this is accountability analysis, not cheerleading.
Steps
- Parse the argument/topic from Shane's request.
- Follow Qwen Protocol with:
task: "Vault access (bash only, no MCP tools):obsidian search query='TERM' limit=10,obsidian read file='Note Name'(no .md),obsidian read file='Context/accountability',obsidian read file='Context/patterns'. Analyze the gap between Shane's stated intentions and actual behavior patterns in the vault around '[argument]' (or broadly). Where is he drifting from his own stated values or goals?"skill: "drift"
- Review Qwen's result, synthesize if needed, and present to Shane.
Fallback
If Qwen is unavailable:
- Search for stated intentions via bash:
obsidian search query='want to' limit=10,obsidian search query='goal' limit=10,obsidian search query='intend' limit=10,obsidian search query='commit' limit=10,obsidian search query='value' limit=10 - Also read
Context/accountability.mdandContext/patterns.mdby runningobsidian read file='Context/accountability'andobsidian read file='Context/patterns'via bash - If
[argument]is provided, scope the search to that domain; otherwise cast broadly - Compare stated intentions against observable behavior:
- What does Shane say he values? What does the vault show him actually spending time/attention on?
- What goals appear repeatedly without progress?
- What beliefs does he state vs. what his decisions imply?
- Surface 2–4 specific drift patterns, each framed as: "You say [X], but the evidence shows [Y]"
- Be direct — this is accountability analysis, not cheerleading
- Present findings with vault evidence for each drift identified