session-librarian

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Over time an agent accumulates dozens of untitled, duplicated, or stale sessions, making it hard to find past decisions or keep the library tidy. This Skill turns plain-language requests into a safe, plan-first workflow for searching, renaming, archiving, and deleting sessions. ## Core Features & Use Cases - Topic-based discovery: Uses FTS5 session search plus CLI metadata filters (age, source, cost, workspace) to locate relevant past sessions and summarize their goals and outcomes. - Safe cleanup with mandatory planning: Presents a plan table of renames, archives, and proposed deletions before mutating anything, prefers reversible archive over delete, and requires dry-run plus explicit confirmation for destructive commands. - Parallel workstreams: Delegates one task per workstream via subagents so work like "one session per ticket" runs in isolated sessions whose transcripts remain searchable. - Use Case: Ask "find my sessions about Q3 pricing, keep the useful ones, and clean up the duplicates" and receive a summarized plan, reversible archives, and exported backups before anything is deleted. ## Quick Start Ask the agent to find all sessions about a topic, summarize what was decided, and propose stale duplicates for archiving.

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 session_search with topic keywords and a limit of 5-10, varying phrasing such as feature names or project names. Results include the session goal, match window, and resolution, which usually suffice for a one-line summary per session.

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

Present a plan table of proposed renames, archives, and deletions first, then act only after user approval. Prefer the reversible archive command, run destructive delete or prune commands with --dry-run first, and export valuable sessions to markdown before deleting.

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 delete or prune is destructive and permanent, so it requires dry-run output and explicit confirmation.

Can session_search filter sessions by age or source?▼

No, session_search finds content via full-text search, not metadata. Age, cost, source, and workspace filters live in the hermes sessions list CLI, so combine both tools when a request mixes content and metadata criteria.

How do I split one investigation into multiple parallel sessions?▼

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