session-librarian

Organizes agent session libraries by finding, renaming, archiving, and pruning sessions.

Updated Aug 21, 2026
One-click install
npx skills add https://github.com/TylerSimons1127/vibe --skill session-librarian-tylersimons1127
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-librarian
Source: https://github.com/TylerSimons1127/vibe/tree/main/skills/productivity/session-librarian
Command: npx skills add https://github.com/TylerSimons1127/vibe --skill session-librarian-tylersimons1127

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long-running agent usage accumulates dozens of untitled, stale, or duplicate sessions, making it hard to find past decisions or keep the session library manageable. ## Core Features & Use Cases - Topic-Based Discovery: Search past sessions by keyword using full-text search over the message store, then summarize each session's goal and outcome. - Safe Cleanup Workflow: Rename sessions meaningfully, archive stale ones reversibly, and propose deletions with a mandatory plan table and dry-run confirmation before any destructive action. - Parallel Workstreams: Split work into one delegated task per ticket, with each subagent running in its own searchable session. - Use Case: Ask to find all sessions about Q3 pricing, keep the useful ones, rename them clearly, and archive the duplicates — the agent presents a plan first, then executes only after approval. ## Quick Start Ask the agent to find your sessions about a specific topic, summarize what was decided, and clean up the duplicates.

Frequently Asked Questions about session-librarian

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

FAQPage Schema
How do I find past agent sessions about a specific topic?▼

Use the session_search tool with topic keywords and a limit of 5-10 results, varying phrasing such as feature names or project names. Each result includes the session goal, match window, and resolution for quick summarization.

How to clean up old or duplicate agent sessions safely?▼

Present a plan table listing which sessions get renamed, archived, or deleted, then wait for user approval. Prefer reversible archive over delete, and always run destructive commands with --dry-run first before confirming with --yes.

What is the difference between archiving and deleting sessions?▼

Archiving is a reversible soft-hide that removes sessions from default listings while keeping them in the database, viewable with --include-archived. Deleting via prune or delete is destructive and permanent, so export valuable sessions to markdown first.

Can I filter sessions by age, source, or cost instead of content?▼

Yes, use the hermes sessions list CLI with filters like --source telegram or --limit 50 for metadata-based sweeps. The session_search tool only searches message content, so combine both approaches for mixed requests like old sessions about pricing.

How do I split work into one session per ticket?▼

Use delegate_task with one task per workstream rather than driving other live sessions directly. Each subagent runs in its own session automatically, and every delegation transcript remains searchable later via session_search.