Awesome-claude-skills update-mirror
Update the Mirror (second brain) in Obsidian after a conversation or on demand. Proposes what to create/update, waits for confirmation, then executes.
install
source · Clone the upstream repo
git clone https://github.com/Anna-Pinewood/awesome-claude-skills
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/Anna-Pinewood/awesome-claude-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/update-mirror" ~/.claude/skills/anna-pinewood-awesome-claude-skills-update-mirror && rm -rf "$T"
manifest:
skills/update-mirror/SKILL.mdsource content
/update-mirror — Update Mirror in Obsidian
Update Mirror based on the current conversation or a user-specified topic.
How
- Read
— follow all rules from there0-claude-mirror/mirror-rules.md - Read
— understand current state0-claude-mirror/map.md - Analyze the conversation: what should be captured?
- Read any existing Mirror files that would be affected
- Search for connections (see rules below)
- Propose an update plan to the user (what to create/update/link and why)
- Wait for confirmation
- Execute, update map.md
- Output list of updated files
Connection search rules
When proposing a new or updated note, you MUST search for meaningful connections before presenting the plan:
- Search Knowledge Pages and Graph Nodes, not just Mirror notes. Use vault search with relevant keywords for the topic.
- Don't list trivial or universal connections. If a note connects to everything (e.g.
), it's not a meaningful connection — omit it.about-me - Show what you searched when proposing. If you found no vault connections, say so explicitly — don't silently skip.
- Connections should be specific and informative: explain how the notes relate, not just that they exist.
Access
Obsidian MCP tools (
mcp__obsidian__vault, mcp__obsidian__view).
Load via ToolSearch with query +obsidian if not yet available.
Vault path for direct file access:
/Users/olgalipina/Yandex.Disk.localized/obsidian-vault/cloud-base/