research-assistant
The research-assistant skill systematically searches a note vault for information on a given topic, then synthesizes findings into a structured summary highlighting key themes, contradictions, knowledge gaps, and connections between ideas. Use this skill when a user requests comprehensive research across existing notes, wants to understand what the vault collectively knows about a subject, or needs to identify gaps and contradictions in existing knowledge to guide further investigation.
git clone --depth 1 https://github.com/heyitsnoah/claudesidian /tmp/research-assistant && cp -r /tmp/research-assistant/.agents/skills/research-assistant ~/.claude/skills/research-assistantSKILL.md
# Research Assistant Conduct thorough research on topics by searching the vault and synthesizing findings. ## Process 1. **Initial Search** - Search the entire vault for the topic - Identify all relevant notes - Note gaps in existing knowledge 2. **Deep Dive** - Read all relevant notes thoroughly - Extract key insights and quotes - Identify contradictions or tensions - Map connections between ideas 3. **Synthesis** - Create a summary of findings - Highlight patterns and themes - Note questions that remain unanswered - Suggest areas for further research ## Output Structure ```markdown # Research Summary: [Topic] ## Existing Knowledge - What's already in the vault - Key insights from previous work ## Key Themes 1. Theme 1 - Supporting notes: [[note1]], [[note2]] - Key insight: ... 2. Theme 2 - Supporting notes: [[note3]], [[note4]] - Key insight: ... ## Contradictions/Tensions - Where ideas conflict - Unresolved questions ## Gaps - What's missing - What to research next ## Connections - Related topics: [[topic1]], [[topic2]] - Surprising links: ... ## Recommended Next Steps 1. Specific research needed 2. Questions to explore 3. Experiments to try ``` ## Tips - Cast a wide net initially, then focus - Look for surprising connections - Don't ignore contradictions - they're often where insights live - Always suggest concrete next actions
Add or update YAML frontmatter properties to enhance Obsidian note organization. Use when the user asks to add, fix, normalize, or improve frontmatter, properties, metadata, tags, or YAML on a note or folder of notes.
Conduct an end-of-day review to capture progress and set up tomorrow. Use when the user asks for a daily review, end of day wrap-up, EOD note, what they did today, or wants to reflect on the day and plan tomorrow.
Remove AI-generated jargon and restore human voice to text. Use when the user asks to de-AI-ify, humanize, remove AI tone, or make text sound less machine-generated.
Download files from URLs to the Obsidian attachments folder and organize them with descriptive names. Use when the user provides URLs to download, asks to save files from the web, or wants to add web content as attachments.
Work with git worktrees for isolated parallel development. Use when starting feature work in isolation, when need separate workspace without branch switching, or when cleaning up worktrees after PR merge.
Help organize and process items in the 00_Inbox folder according to the PARA method. Use when the user asks to process, clear, sort, triage, or organize their inbox.
Interactive setup wizard that helps new users create a personalized CLAUDE.md file based on their Obsidian workflow preferences. Use when the user wants to set up claudesidian, onboard a new vault, or run the bootstrap/init/setup wizard.
Install claudesidian shell command to launch Claude Code from anywhere. Use when the user wants to install a shell alias/launcher for their vault, or asks to set up the claudesidian command.