Save Diary

Community

faizkhairi

save-diary

MUST use when user says 'save diary', 'write diary', 'diary entry', 'update diary', or 'document session'. Also auto-trigger at the end of any significant session (feature shipped, major bug fixed, architecture decision, new project started).

Overview

Publisher	faizkhairi
Repository	`claude-code-blueprint`
Skill name	`save-diary`
Stars	73
Forks	22
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by faizkhairi on GitHub. Read the source before you install it.

Installation

Install the Save Diary AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/faizkhairi/claude-code-blueprint/tree/main/skills/save-diary
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/faizkhairi/claude-code-blueprint.git /tmp/claude-code-blueprint
mkdir -p .claude/skills
cp -r /tmp/claude-code-blueprint/skills/save-diary .claude/skills/save-diary

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Save Diary in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Save Diary on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Save Diary is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Prerequisite check (run first): if ./memory/diary/current/ does not exist OR ~/.claude/.memory-disabled marker file is present, this skill is a no-op. Output: "Memory persistence is disabled. Run ./setup.sh and choose to enable memory if you want diary entries to be saved."

Dev Diary: Session Documentation Skill

Today's story takes shape.

Activation

When this skill activates, output: "Dev Diary: documenting today's session."

Context Guard

Context	Status
User says "save diary" / "write diary" / "diary entry"	ACTIVE, full diary write
End of significant session	ACTIVE, auto-document
User says "review diary"	ACTIVE, read recent entries
Mid-conversation (no save request)	DORMANT, no diary action

Protocol

Step 1: Monthly Archive Check

Scan ./memory/diary/current/ for files from previous months
For each file where month != current month:
- Create ./memory/diary/archived/YYYY-MM/ folder if not exists
- Move the file from current/ to archived/YYYY-MM/
Continue with diary write

Step 2: Find or Create Today's File

Check if ./memory/diary/current/YYYY-MM-DD.md exists
If exists: use it (will append new entry)
If not: create new file with header:


# YYYY-MM-DD, Session N: Brief Description

Step 3: Compose and Append Diary Entry

Get current date via bash: date +"%B %d, %Y" or PowerShell Get-Date -Format "MMMM dd, yyyy"
Analyze current session for key content
Write structured entry using our actual diary format:
- Title: # YYYY-MM-DD, Session N: Brief Description
- What Happened: Concise summary of the session context and goals
- Fixes Applied / Key Changes: Specific technical work done (commits, code changes)
- Key Insight: Lessons learned or important observations
- Pending / Next Steps: What's left to do
Session numbering: Read the existing file first. Find the highest Session N number in today's entries and increment by 1. If this is the first entry of the day, check the previous day's file for the last session number and continue from there. If no previous entries exist, start at Session 1.
APPEND to today's file (never overwrite existing content)
Multiple entries per day are separated by ---

Step 4: Update Session Memory

Update ./memory/core/session.md with:
- Session recap and key achievements
- Current working state for continuity
- Next steps identified
Confirm diary entry saved

Mandatory Rules

Always APPEND: never overwrite existing diary entries
One file per day: multiple entries separated by ---
Use real timestamps: get current date via system command
Archive first: run monthly archive check before every write
Evidence-based: document actual session content, not generic summaries
Use our format: concise technical summaries (What Happened, Key Changes, Key Insight, Pending)

Edge Cases

Situation	Behavior
First entry of the day	Create new file with header + first entry
Second+ entry same day	Append with `---` separator
No significant content	Create brief entry noting session type
"review diary" command	Read and present recent entries from current/

Frequently asked questions

What does the Save Diary AI skill do?

Why use Save Diary on TypingMind?

Because you install it once and use it with any model. Save Diary is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Save Diary in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/faizkhairi/claude-code-blueprint/tree/main/skills/save-diary. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Save Diary?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Save Diary?

As many as you like. As long as a model supports skills, you can use Save Diary with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Save Diary AI skill free?

Yes. It is published on GitHub by faizkhairi under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Auto Qa

openclaw

OrganizationPopular

Run OpenClaw-wide autonomous QA and live/stress campaigns across independent subsystem lanes, with verified fixes and a resumable evidence report.

Autoreview

Structured code review when explicitly requested, preferring OpenAI/Codex before Claude.

Claw Score

Audit or refresh OpenClaw maturity scorecard docs from root taxonomy, maturity scores, and QA evidence artifacts without using maintainer discrawl data or committed inventory reports.

Clawsweeper

Use for all ClawSweeper work: OpenClaw issue/PR sweep reports, repair jobs, cloud fix PRs, @clawsweeper maintainer mention commands, trusted ClawSweeper-reviewed autofix/automerge, GitHub Actions…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Dev Diary: Session Documentation Skill

Activation

Context Guard

Protocol

Step 1: Monthly Archive Check

Step 2: Find or Create Today's File

Step 3: Compose and Append Diary Entry

Step 4: Update Session Memory

Mandatory Rules

Edge Cases

Frequently asked questions

Related AI Skills

Set up your own AI workspace now