archive-export

Archive the latest /export session into an Obsidian project's Conversations folder.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/smallorbit/smallorbit-plugins --skill archive-export
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: archive-export
Source: https://github.com/smallorbit/smallorbit-plugins/tree/main/plugins/vaultkit/skills/archive-export
Command: npx skills add https://github.com/smallorbit/smallorbit-plugins --skill archive-export

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive the latest /export output into the active Obsidian project's Conversations folder. Use after the user runs /export session from the workspace root.

Core Features & Use Cases

  • Picks up the latest conversation export and files it into the active Obsidian project's Conversations/ folder.
  • Creates two copies in the project's Conversations folder: a .txt file (plain text) and a .md file (Obsidian-renderable) that embeds the .txt as an attachment and includes the session ID for resuming the conversation.
  • Use case: After running /export session, archive and organize the conversation for future retrieval and resume.

Quick Start

Run this skill after exporting to archive the latest session into your vault's Conversations folder.

Frequently Asked Questions about archive-export

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I archive exported conversations into an Obsidian vault?

To archive exported conversations into an Obsidian vault, this skill automates filing the latest exported session into a designated Conversations folder, creating both plain-text and markdown copies with timestamps and session IDs for future retrieval and resume.

What is the best way to save session exports as markdown files in Obsidian?

Saving session exports as markdown files in Obsidian is handled by generating an Obsidian-renderable .md file that embeds the plain-text export as an attachment, complete with a timestamp and session ID for resuming the conversation.

Do I need to configure a specific vault path to export session data to Obsidian?

Yes, exporting session data requires a configured Obsidian vault path and a Conversations directory to correctly place the generated .txt and .md files into the active project's folder structure.

Can I resume a conversation from an archived Obsidian markdown file?

Yes, resuming a conversation from an archived Obsidian markdown file is possible because the skill embeds the original session ID into the markdown attachment, providing the reference needed to resume the session.

When should I run the archiving process after exporting a session?

You should run the archiving process immediately after executing a session export from the workspace root, ensuring the skill picks up the latest conversation data and organizes it correctly into the vault.