From bridge
This skill should be used when the user types "/lc-collect", asks to "capture to vault", "collect a note", "save to lifecycle vault", "send to collect", "save this to Obsidian", "capture this idea", "jot this down in my vault", "save what we discussed to the vault", "capture this conversation to vault", or wants to create a new note in their Obsidian Lifecycle System vault's Collect folder.
How this skill is triggered — by the user, by Claude, or both
Slash command
/bridge:lc-collect [--from-chat] <what to capture — an idea, meeting summary, decision, etc.>[--from-chat] <what to capture — an idea, meeting summary, decision, etc.>This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Capture information into an Obsidian Lifecycle System vault's Collect folder. Validate configuration, parse arguments, and spawn the collector agent to write the note.
Capture information into an Obsidian Lifecycle System vault's Collect folder. Validate configuration, parse arguments, and spawn the collector agent to write the note.
Parse the input provided after /lc-collect:
--from-chat flag detection:
Description text:
Examples:
/lc-collect meeting notes about the auth refactor — freeform description, no conversation context/lc-collect --from-chat key decisions from this debugging session — include summarized conversation context/lc-collect — no arguments, ask the user what to captureUse the Agent tool to spawn the collector agent. Build the prompt with this structure:
Vault: !`echo "${LIFECYCLE_VAULT:?LIFECYCLE_VAULT is not set in your settings.json}"`
Task: Create a new note in the vault's Collect/ folder.
What to capture:
<user's description text>
If --from-chat was used, append a clearly delimited section:
---
Conversation context:
<summarized conversation context relevant to the description>
The collector agent reads vault conventions (CLAUDE.md and Style Guide), chooses a title, writes the note, and searches the Catalog for relevant MOCs to suggest as wikilinks.
Display the note title and full file path created. Summarize what was captured in one sentence. Remind the user the note is in Collect/ and will be processed during weekly review.
Daily log prompt: After reporting the captured note, check whether the user's original input mentioned the daily log, daily note, or journal entry. If they did NOT mention it, ask:
Would you also like me to add an entry to today's daily log referencing this note?
If the user says yes, append a bullet to today's daily log linking to the new Collect note via the obsidian CLI:
obsidian vault=$LIFECYCLE_VAULT daily:append content="- [[<Note Title>]]"
The CLI handles file creation, date format, and journal location automatically — no manual path manipulation needed.
If the user already asked for a daily log entry as part of their original capture request, handle it automatically without prompting.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub alexmarnell/obsidian-lifecycle-plugins --plugin bridge