Emerge
Twenty Obsidian knowledge-work skills for Claude Code: connect, contradict, emerge, trace, ghost, weekly-learnings.
npx -y skills add slogsdon/skills-vault-knowledge --skill emergeAssembled 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
Use when asked to surface hidden patterns or implicit ideas in the vault, or when /emerge is invoked. Do NOT use to find connections between two specific concepts — use /connect for that.
SKILL.md
2.1 KB, as published. Nobody here has run it
Skill: /emerge [argument]
Surface what Shane is circling in the vault without stating directly — the implicit beliefs, unspoken assumptions, and ideas approached from multiple angles but never synthesized.
Don't: surface obvious or labeled themes — the value is in what's implicit. Don't use this for cross-concept bridging — that's /connect.
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). Search the vault for implicit patterns, unspoken assumptions, and emergent ideas around '[argument]' (or across the full vault if no argument given). Surface what Shane is circling without stating directly."skill: "emerge"
- Review Qwen's result, synthesize if needed, and present to Shane.
Fallback
If Qwen is unavailable:
- If
[argument]is provided, runobsidian search query='[argument]' limit=15via bash; otherwise run broad searches via bash:obsidian search query='goals' limit=10,obsidian search query='beliefs' limit=10,obsidian search query='habits' limit=10,obsidian search query='work' limit=10 - Read 10–15 notes spanning different topics and time periods by running
obsidian read file='[note name]'via bash for each - Look for what's implicit — not stated conclusions, but:
- Topics that recur without being labeled as important
- Assumptions embedded in how questions are framed
- Ideas approached from multiple angles but never synthesized
- Things written around but never directly about
- Surface 3–5 emergent patterns, each framed as: "You keep circling [X] without naming it directly — the implicit belief seems to be [Y]"
- Present the findings to Shane with specific note evidence for each pattern