diary

Store session notes and decisions in a local SQLite diary with Markdown export.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/jtucker9/mystuff --skill diary-jtucker9
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diary
Source: https://github.com/jtucker9/mystuff/tree/main/skills/diary
Command: npx skills add https://github.com/jtucker9/mystuff --skill diary-jtucker9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Logging sessions and decisions to preserve context for future reference, post-mortems, and knowledge transfer.

Core Features & Use Cases

  • Session logging: captures accomplishments, blockers, decisions, and next steps at session end.
  • Context preservation: stores a retrievable diary linked to projects and commits.
  • Exportability: provides human-readable markdown export for backups and reporting.

Quick Start

Tell the agent to save the diary at the end of a session to record a concise log.

Frequently Asked Questions about diary

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

FAQPage Schema
How do I log session notes and decisions for future recall?

You log session notes by telling the agent to save the diary at the end of a session, which records accomplishments, decisions, problems, and next steps into a persistent store.

What is the best way to preserve work session context for post-mortems?

The best way to preserve work session context is to use a persistent diary that stores retrievable entries linked to your projects and commits for reliable recall later.

Does session logging with SQLite support markdown export for backups?

Yes, session logging with SQLite supports markdown export, providing a human-readable backup file containing fields for accomplishments, files changed, commits, decisions, problems, and next steps.

Can I use a local SQLite diary store to record code and planning session history?

Yes, you can use a local SQLite diary store to record code, design, or planning session history, capturing concise logs of files changed and commits made during your productive work periods.

When do I need to start session logging for my workflow?

You need session logging at the end of any code, design, or planning session where a persistent diary is desired, ensuring your decisions and work context are automatically captured for future recall.

What are the limitations of using a local SQLite diary store for session memory?

A limitation of using a local SQLite diary store for session memory is that entries are stored locally, meaning recall is restricted to the device where the persistent diary database resides.