Help us improve
Share bugs, ideas, or general feedback.
From skills
Captures ideas and brain dumps into an Obsidian Inbox, surfaces buried ideas from the vault, and promotes daily note ideas to permanent notes.
npx claudepluginhub kriscard/skillsHow this skill is triggered — by the user, by Claude, or both
Slash command
/skills:ideasThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Get ideas out of your head and into the vault immediately. Low friction is the whole point — capture
Synthesizes Obsidian inbox items into structured wiki notes after discussing key ideas with the user. Saves conversation answers as permanent reference pages.
Integrates Claude Code with an Obsidian vault for capturing thoughts, managing tasks, morning planning, and querying linked notes via a dual-zone architecture.
Captures ideas mid-conversation and stores them in the vault for later processing. Supports listing, processing, editing, and prioritizing banked ideas.
Share bugs, ideas, or general feedback.
Get ideas out of your head and into the vault immediately. Low friction is the whole point — capture first, organize later. The Inbox is the landing zone.
Write to inbox immediately, no questions:
obsidian create path="0 - Inbox/idea-$(date +%Y%m%d-%H%M).md" content="..."
Frontmatter to add:
---
type: idea
captured: YYYY-MM-DD HH:MM
context: <project name or topic, if obvious>
tags: [idea]
---
After capturing, ask ONE optional follow-up:
"This looks like a [project / area / resource] idea — want a full project note now, or just inbox for later?"
Only ask if the answer isn't already obvious. If they say "just capture it", stop there.
When the conversation contains multiple ideas scattered through the discussion:
# One note per distinct cluster
obsidian create path="0 - Inbox/idea-$(date +%Y%m%d-%H%M)-<slug>.md" content="..."
Present the clusters to the user before writing, in case grouping is wrong.
If the idea clearly has:
...ask: "This sounds like more than an idea — want me to set up a project note in 1 - Projects/?"
Then hand off to the project skill if yes.
idea-YYYYMMDD-HHMM.mdidea-YYYYMMDD-HHMM-<short-slug>.mdidea-YYYYMMDD-HHMM-<topic>.mdKeep slugs short (2–3 words max). The timestamp is the primary identifier.
When the user wants to promote ideas from daily notes to permanent notes:
obsidian read path="2 - Areas/Daily Ops/YYYY/YYYY-MM-DD.md" # repeat for each day
Explicit signals: #idea, #expand, "I should write about", named concepts, unresolved
[[links]]
Implicit signals: high-energy paragraphs (longer, stronger language), original frameworks, recurring themes across 3+ days, questions that keep reappearing
Not candidates: tasks, meeting logistics, things with existing standalone notes
For each candidate:
obsidian search query="<candidate concept>" format=json
Categorize: New concept (no note exists) / Underdeveloped (thin note) / Already covered (skip) /
Recurring unresolved [[link]] (high priority)
| # | Idea | Source | Days Mentioned | Status | Recommendation |
|---|
Include for each: 1–2 sentence summary, exact quote from daily note, what it connects to in vault.
Always ask before creating or modifying files.
For new notes: place in 3 - Resources/ (concept), 1 - Projects/ (actionable + deadline),
2 - Areas/ (ongoing interest). Write as mini-essay (3–8 paragraphs) with core claim, context from
daily notes, [[backlinks]], open questions. Go back and add [[links]] in source daily notes.
For enriching existing: read note, add dated section, add backlinks, update source daily note links.