From vaultkit
Archive the latest /export output into the active Obsidian project's Conversations folder. Use after the user runs /export session from the workspace root.
How this skill is triggered — by the user, by Claude, or both
Slash command
/vaultkit:archive-exportThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Picks up the latest conversation export and files it into the active Obsidian project's `Conversations/` folder.
Picks up the latest conversation export and files it into the active Obsidian project's Conversations/ folder.
The user always runs /export session from the current working directory. This produces a consistent file:
./session.txt
This skill creates two copies in the project's Conversations/ folder: a .txt file (plain text, well-formatted when viewed natively) and a .md file (Obsidian-renderable, searchable) that embeds the .txt as an attachment and includes the session ID for resuming the conversation.
ls -lh ./session.txt
If missing, remind the user to run /export session from this directory first.
Use conversation context. If unclear, run:
obsidian vault=Personal files folder="Projects"
and ask the user which project to file it under.
Follow the get-session-id sub-skill to resolve the current session ID. Save the result as SESSION_ID.
mkdir -p "$VAULT/Projects/ProjectName/Conversations"
Where VAULT is the path to your Personal vault.
Base name format: YYYY-MM-DD-HHMM-<slug> (no extension yet)
This is the canonical filename format for conversation archives.
2026-04-03-2314-backtest-snapshot-playbook-fixBASENAME=$(date '+%Y-%m-%d-%H%M')-your-slug-here
This base name is used for both files:
YYYY-MM-DD-HHMM-slug.txt — plain text copyYYYY-MM-DD-HHMM-slug.md — Obsidian markdown copycp ./session.txt "$VAULT/Projects/ProjectName/Conversations/$BASENAME.txt"
Follow the vaultkit:file-edit sub-skill's new-file guidance to stamp the birth time on the copied .txt.
The .md file has three parts:
plaintext fenced code blockUse the Bash tool to build and write the file in one step:
{
echo "session-id: $SESSION_ID"
echo "resume: claude --resume $SESSION_ID"
echo ''
echo "![[${BASENAME}.txt]]"
echo ''
echo '```plaintext'
cat ./session.txt
echo '```'
} > "$VAULT/Projects/ProjectName/Conversations/$BASENAME.md"
Then stamp its birth time per the vaultkit:file-edit sub-skill's new-file guidance.
rm ./session.txt
Report both destination paths and the session ID to the user.
.txt file is the source of truth for content; the .md file embeds it as an attachment and also inlines the full text in a plaintext block for Obsidian search indexingget-session-id sub-skillclaude --resume SESSION_ID/export from the wrong directory, locate the file with:
find . -name "session.txt" 2>/dev/null | head -5
npx claudepluginhub smallorbit/smallorbit-plugins --plugin vaultkitProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.