knowledge · thoreinstein — Claude Code skill: what it does, how to install
This skill finds ideas repeated across project notes and drafts a shared note in Engineering/. Use it to turn recurring project knowledge into a linked concept.
ISC ★ 102 updated 2026-10-25
npx skills add thoreinstein/gemini-obsidian --skill knowledge -a claude-codeWhat knowledge does
The skill scans working/*/knowledge/*.md, then uses obsidian_rag_query to find semantically related notes. A note becomes a candidate when matching results come from at least two projects. The agent reads the candidates and drafts Engineering/<ConceptName>.md with a concept type, creation date, rewritten content, and links to the source notes.
You see the draft and its path before anything is created. After your approval, the skill calls obsidian_create_note, then lists project notes that should link back to the new concept. When search returns no results, it suggests running /obsidian:index; if no idea recurs across projects, it recommends manual promotion. The workflow depends on Obsidian tools being available to the agent.
What it helps with
- spot ideas that recur in notes from different projects
- turn shared definitions into a single concept note
- retain links to the original notes with
[[wikilinks]] - identify project notes that should link to a shared concept
Example prompts for the agent
- Find ideas repeated across project knowledge notes and draft a shared concept.
- Synthesize the authentication patterns in my project notes into a draft for
Engineering/. - Review the source notes and show me which ones should link to the new concept.
How to install knowledge
1Skills CLI (Vercel)
npx skills add thoreinstein/gemini-obsidian --skill knowledge -a claude-code2Manually: put the files in place
~/.claude/skills/knowledge/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/knowledge/
1Skills CLI (Vercel)
npx skills add thoreinstein/gemini-obsidian --skill knowledge -a codex2Manually: put the files in place
.agents/skills/knowledge/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add thoreinstein/gemini-obsidian --skill knowledge -a cursor2Manually: put the files in place
.cursor/skills/knowledge/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install thoreinstein/gemini-obsidian skills/knowledge2Manually: put the files in place
.github/skills/knowledge/SKILL.md1Skills CLI (Vercel)
npx skills add thoreinstein/gemini-obsidian --skill knowledge -a gemini-cli2Platform CLI
gemini skills install https://github.com/thoreinstein/gemini-obsidian --path skills/knowledgeManually: put the files in place
.devin/skills/knowledge/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about knowledge
How do I install knowledge in Claude Code?
Run npx skills add thoreinstein/gemini-obsidian --skill knowledge -a claude-code. The skill file is at ~/.claude/skills/knowledge/SKILL.md.
What does knowledge do?
It finds ideas recurring in knowledge notes from multiple projects and drafts a shared note under Engineering/. The draft needs your approval before the skill creates it.
What happens when the search finds no notes?
The skill suggests running /obsidian:index. If no knowledge appears across multiple projects, it recommends promoting it manually.
Source text
SKILL.md · ISC
--- name: knowledge description: >- Use when the user wants to promote cross-project knowledge to the global Engineering/ folder, or says "promote knowledge", "compound notes", "knowledge synthesis", or "find repeated ideas across projects". --- # Compound Knowledge Promotion Identify knowledge that has crystallized across multiple projects and promote it to a global Engineering/ note. ## Workflow 1. **Scan project knowledge dirs** — Call `obsidian_list_notes` with `subfolder: "working"`. Filter results to paths matching `working/*/knowledge/*.md`. 2. **Semantic clustering** — For each knowledge note path, call `obsidian_rag_query` with the note filename (without extension) as query, `limit: 8`. Track which notes appear in results from 2+ different projects — these are candidates. 3. **Read candidates** — Call `obsidian_read_note` on shortlisted files. Look for shared definitions, patterns, or insights worth generalizing. 4. **Draft global note** — Compose a new `Engineering/<ConceptName>.md` with: - Frontmatter: `type: concept`, `created: <today>` - Synthesized body (not copy-paste — rewrite for clarity) - `## Source Notes` section with `[[wikilinks]]` back to originating notes 5. **Show draft to user** — Present the proposed note content and path before creating. Ask for confirmation. 6. **Create on approval** — Call `obsidian_create_note` with the approved content. 7. **Report cross-links** — List which project knowledge notes should now add `[[ConceptName]]` to avoid re-discovering this knowledge next time. ## Arguments Optional topic hint: `/compound authentication patterns` ## Tips - If `obsidian_rag_query` returns no results, suggest running `/obsidian:index` first - If no notes appear in 2+ projects, report that and suggest manual promotion
© thoreinstein · ISC · thoreinstein/gemini-obsidian
Similar skills
All skills for Notes, tasks and projects →knowledge by other authors comes first.