New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Diary

by sickn33 in sickn33/agentic-awesome-skills

Unified Diary System: A context-preserving automated logger for multi-project development.

MITAuto-check: warningsKnowledge Management

Install Diary

The automated check flagged lines worth reading first. See the safety section below.

skills CLI
$ npx skills add sickn33/agentic-awesome-skills --skill diary -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install sickn33/agentic-awesome-skills diary --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/diary .claude/skills/diary && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
diary
GitHub stars
47k
Used in
2 other repos
Token cost
~2.3k tokens
SKILL.md length
985 words
Files
12 (incl. scripts)
Skills in repo
1,394
Repo updated
First seen
Licence
MIT

At a glance

Unified Diary System: A context-preserving automated logger for multi-project development.

  • Works in 5 steps: Local Project Archiving (AI Generation) → 5: Refresh Project Context (Automation… → Extract Global & Project Material… → …
  • Tasks that involve Journaling and reflection
  • SKILL.md covers When to Use This Skill, Step 1: Local Project…, Step 1.5: Refresh Project… and Step 2: Extract Global &…, plus 4 more sections
  • Runs Python scripts from its folder; calls python

What it does

Diary is an agent skill from sickn33/agentic-awesome-skills. Unified Diary System: A context-preserving automated logger for multi-project development.

Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 13 other files, including scripts (for example `README.md`, `scripts/fetch_diaries.py` and `scripts/master_diary_sync.py`).

It sits in Knowledge Management, covering Journaling and reflection. The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.

When your agent uses it

  • Tasks that involve Journaling and reflection

Example prompts

  • “/diary”

Requirements

  • Python 3

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Local Project Archiving (AI Generation)
  2. 5: Refresh Project Context (Automation Script)
  3. Extract Global & Project Material (Script Execution)
  4. AI Smart Fusion & Global Archiving (AI Execution) 🧠
  5. Cloud Sync & Experience Extraction (Script + Human) 🛑

What it can do on your machine

Read from SKILL.md and the folder at commit 1e53ce2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 4 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Diary loads about 2.3k tokens when it runs. Until then it costs about 24 tokens; SKILL.md has 985 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~24
When it runs · the whole SKILL.md, loaded when a task matches
~2.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: warnings

The automated check found patterns that need a careful read before installing.

  • WarningTells the agent its actions are pre-authorized / not to stop for confirmationSKILL.md:42
    Completion**: Force continue to Step 2; do not wait for user confirmation.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from sickn33/agentic-awesome-skills at commit 1e53ce2, republished under its MIT licence (© sickn33). 985 words, ~2,297 tokens.

Download SKILL.mdSave it as .claude/skills/diary/SKILL.md (or your agent's skills folder). This skill also uses 11 other files; get the full folder from GitHub.
name
diary
description
Unified Diary System: A context-preserving automated logger for multi-project development.
risk
safe
source
self
date_added
2026-09-04

📔 Unified Diary System

When to Use This Skill

Use this skill when you want to summarize progress, write a daily dev log, or perform a daily review while keeping project contexts isolated and synced to Notion/Obsidian.

🚨 Agent One-Shot Integrity Constraint (Highest Priority): Steps 1-4 are an indivisible atomic workflow. The AI MUST use Continuous Tool Calling to complete all actions in one breath.

  • ABSOLUTELY FORBIDDEN to output conversational text and wait for the user after completing Step 1, 2, or 3.
  • Example: Immediately after saving the file in Step 1, you must automatically and instantly call the terminal tool to execute the script in Step 2. Stopping to chat or asking "Should I continue?" is considered a critical error. Only inform the user explicitly if you are stuck due to a technical error.

⚠️ Ironclad Rule 1: The local project diary in Step 1 must NEVER be polluted with global data. It only records the current project. ⚠️ Ironclad Rule 2: When using tools like run_command to execute predefined python scripts (Step 2, Step 4), you must set them to SafeToAutoRun: true to avoid getting stuck waiting for user authorization. ⚠️ Ironclad Rule 3: Never guess the project name. The AI must confirm the current directory name as the project identifier using a terminal command BEFORE taking any action in Step 1.

Step 1: Local Project Archiving (AI Generation)

  • Action 0 (Identify): Call the terminal pwd (Linux/Mac) or (Get-Item .).Name (Windows) to confirm the current folder name.
  • Action 1 (Write): Summarize the achievements from the current conversation (Git Commits, file changes, task progress), and write them into the current project folder at diary/YYYY/MM/YYYY-MM-DD-ProjectName.md.
  • Isolation and Naming Rules (Ironclad Rules):
    • 📄 Mandatory Filename Suffix: The local diary MUST include the project name detected just now. It is absolutely forbidden to use a global-level filename (like 2026-02-23.md) locally.
    • ✅ Pure Content: Only record content exclusive to the current project. Do not mix in other projects.
    • 📝 Append Mode: If the project diary already exists, update it using "append", never overwrite the original content.
    • 📁 Auto-Creation: Create subfolders diary/YYYY/MM/ based on the year and month.
    • ⚡ Force Continue: Once writing is complete, do not interrupt the conversation; immediately call the terminal tool and proceed to Step 2.

Step 1.5: Refresh Project Context (Automation Script)

  • Prerequisite: You have confirmed the current project directory path (from Action 0's pwd result).
  • Action: Call the terminal to execute the following command to automatically scan the project state and generate/update AGENT_CONTEXT.md:
    powershell
    python {diary_system_path}/scripts/prepare_context.py "<Project_Root_Path>"
  • SafeToAutoRun: true (Safe operation; purely reading and writing local files).
  • Result: AGENT_CONTEXT.md in the project directory is refreshed to the latest state.
  • After Completion: Force continue to Step 2; do not wait for user confirmation.

Step 2: Extract Global & Project Material (Script Execution)

  • Action: Call the extraction script, passing in the absolute path of the project diary just written in Step 1. The script will precisely print "Today's Global Progress" and "Current Project Progress".
  • Execution Command:
    powershell
    python {diary_system_path}/scripts/fetch_diaries.py "<Absolute_Path_to_Step1_Project_Diary>"
  • Result: The terminal will print two sets of material side-by-side. The AI must read the terminal output directly and prepare for mental fusion.
Show full SKILL.md (485 more words)Show less

Step 3: AI Smart Fusion & Global Archiving (AI Execution) 🧠

  • Action: Based on the two materials printed by the terminal in Step 2, complete a seamless fusion mentally, then write it to the global diary: {diary_system_path}/diary/YYYY/MM/YYYY-MM-DD.md.
  • Context Firewall (Core Mechanism):
    1. No Tag Drift: When reading "Global Progress Material", there may be progress from other projects. It is strictly forbidden to categorize today's conversation achievements under existing project headings belonging to other projects.
    2. Priority Definition: The content marked as 📁 [Current Project Latest Progress] in Step 2 is the protagonist of today's diary.
  • Rewrite Rules:
    1. Safety First: If the global diary "already exists," preserve the original content and append/fuse the new project progress. Do not overwrite.
    2. Precise Zoning: Ensure there is a dedicated ### 📁 ProjectName zone for this project. Do not mix content into other project zones.
    3. Lessons Learned: Merge and deduplicate; attach action items to every entry.
    4. Cleanup: After writing or fusing globally, you must force-delete any temporary files created to avoid encoding issues (e.g., temp_diary.txt, fetched_diary.txt) to keep the workspace clean.

Step 4: Cloud Sync & Experience Extraction (Script + Human) 🛑

  • Action 1 (Sync): Call the master script to push the global diary to Notion and Obsidian.
  • Execution Command:
    powershell
    python {diary_system_path}/scripts/master_diary_sync.py --sync-only
  • Action 2 (Extraction & Forced Pause):
    1. The AI extracts "Improvements & Learning" from the global diary.
    2. Confirm if it contains entirely new key points lacking in the past (📌 New Rules), or better approaches (🔄 Evolved Rules).
    3. List the results and WAIT FOR USER CONFIRMATION (user says "execute" or "agree").
    4. After user confirmation, update the .md file in {Knowledge_Base_Path}/ and execute qmd embed (if applicable).

🎯 Task Acceptance Criteria:

  1. ✅ Project local diary generated (no pollution).
  2. ✅ fetch_diaries.py called with absolute path and successfully printed materials.
  3. ✅ AI executed high-quality rewrite and precisely wrote to global diary (appended successfully if file existed).
  4. ✅ --sync-only successfully pushed to Notion + Obsidian.
  5. ✅ Experience extraction presented to the user and authorized.

📝 Templates and Writing Guidelines

Strictly apply the following Markdown templates to ensure clarity during Step 1 (Local) and Step 3 (Global Fusion).

💡 Writing Guidelines (For AI)
  1. Dynamic Replacement: The {Project Name} in the template MUST strictly use the folder name grabbed by pwd in Step 1.
  2. Concise Deduplication: When writing the global diary in Step 3, the AI must condense the "🛠️ Execution Details" from the local diary. The global diary focuses only on "General Direction and Output Results."
  3. Mandatory Checkboxes: All "Next Steps" and "Action Items" must use the Markdown * [ ] format so they can be checked off in Obsidian/Notion later.
📝 Template 1: Project Local Diary (Step 1 Exclusive)
markdown
# Project DevLog: {Project Name}
* **📅 Date**: YYYY-MM-DD
* **🏷️ Tags**: `#Project` `#DevLog`

---

> 🎯 **Progress Summary**
> (Briefly state the core task completed, e.g., "Finished Google Colab environment testing for auto-video-editor")

### 🛠️ Execution Details & Changes
* **Git Commits**: (List if any)
* **Core File Modifications**:
  * 📄 `path/filename`: Explanation of changes.
* **Technical Implementation**:
  * (Record key logic or architecture structural changes)

### 🚨 Troubleshooting
> 🐛 **Problem Encountered**: (e.g., API error, package conflict)
> 💡 **Solution**: (Final fix, leave key commands)

### ⏭️ Next Steps
- [ ] (Specific task 1)
- [ ] (Specific task 2)
🌍 Template 2: Global Diary (Step 3 Exclusive)
markdown
# 📔 YYYY-MM-DD Global Progress Overview

> 🌟 **Daily Highlight**
> (1-2 sentences summarizing all project progress for the day, synthesized by AI)

---

## 📁 Project Tracking
(⚠️ AI Rule: If file exists, find the corresponding project title and append; NEVER overwrite, keep it clean.)

### 🔵 {Project A, e.g., auto-video-editor}
* **Today's Progress**: (Condense Step 2 local materials into key points)
* **Action Items**: (Extract next steps)

### 🟢 {Project B, e.g., GSS}
* **Today's Progress**: (Condense key points)
* **Action Items**: (Extract next steps)

---

## 🧠 Improvements & Learnings
(⚠️ Dedicated to Experience Extraction)

📌 **New Rules / Discoveries**
(e.g., Found hidden API limit, or a more efficient python syntax)

🔄 **Optimizations & Reflections**
(Improvements from past methods)

---

## ✅ Global Action Items
- [ ] (Tasks unrelated to specific projects)
- [ ] (System environment maintenance, etc.)

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

© sickn33, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 11 other files (scripts) in skills/diary of sickn33/agentic-awesome-skills.

  • SKILL.md
  • .env.example
  • .gitignore
  • LICENSE
  • README.md
  • requirements.txt
  • scripts/fetch_diaries.py
  • scripts/master_diary_sync.py
  • scripts/prepare_context.py
  • scripts/sync_to_notion.py
  • templates/global-diary-template.md
  • templates/local-diary-template.md

Open the folder on GitHubat commit 1e53ce2

Used in 2 other repositories

We found 3 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Diary next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Diary compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Diary this skillsickn33/agentic-awesome-skills47k2 repos~2.3kAutomated safety check: WarnMIT
LLM Wikilewislulu/llm-wiki-skill655—~3.7kAutomated safety check: PassNone
Munger Perspectivealchaincyf/munger-skill3771 repos~3.7kAutomated safety check: PassMIT
Daily Journalhuytieu/COG-second-brain1.3k—~1.3kAutomated safety check: PassMIT
Letterboxd Diaryjoe-bell/skills211—~4.2kAutomated safety check: PassMIT
Em Grid Scorermanager-dot-dev/manager-skills114—~5.8kAutomated safety check: PassMIT

Similar skills

  • LLM Wiki

    lewislulu/llm-wiki-skill

    Build and maintain a Karpathy-style LLM knowledge base — a self-compiling Obsidian markdown wiki where an Agent ingests raw sources, compiles cross-linked concept/entity/summary pages, answers…

    655 GitHub stars~3.7k tokensUpdated 5 mo ago
    Knowledge ManagementAuto-check passed

  • Munger Perspective

    alchaincyf/munger-skill

    查理·芒格的思维框架与表达方式。基于《穷查理宝典》、伯克希尔/Daily Journal股东会、 USC/哈佛演讲、访谈记录、外部批评等50+来源的深度调研， 提炼5个核心心智模型、8条决策启发式和完整的表达DNA。

    377 GitHub starsUsed in 1 repo~3.7k tokens
    Knowledge ManagementAuto-check passed

  • Daily Journal

    huytieu/COG-second-brain

    A passive daily work journal that Claude keeps FOR you so you never have to write it yourself.

    1.3k GitHub stars~1.3k tokensUpdated 5 days ago
    Knowledge ManagementAuto-check passed

  • Letterboxd Diary

    joe-bell/skills

    Fetch recently watched films from a Letterboxd member's diary RSS feed and render them as a compact markdown list, with first-run setup for the username.

    211 GitHub stars~4.2k tokensUpdated 3 days ago
    Knowledge ManagementAuto-check passed

  • Em Grid Scorer

    manager-dot-dev/manager-skills

    Score an Engineering Manager's coverage across all 12 cells of the EM Grid based on their calendar and Slack.

    114 GitHub stars~5.8k tokensUpdated 5 mo ago
    Knowledge ManagementAuto-check passed

  • Digital Brain

    foryourhealth111-pixel/Vibe-Skills

    This skill should be used when the user asks to "write a post", "check my voice", "look up contact", "prepare for meeting", "weekly review", "track goals", or mentions personal brand, content…

    3.6k GitHub stars~1.7k tokensUpdated 1 mo ago
    Knowledge ManagementAuto-check passed

More from sickn33/agentic-awesome-skills

All 1,394 skills in this repo

  • Liuguang Banlan UI

    sickn33/agentic-awesome-skills

    Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed

  • User Thoughts Memory

    sickn33/agentic-awesome-skills

    Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed

  • Using LWC Memory and Graphs

    sickn33/agentic-awesome-skills

    Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.

    47k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed

  • Find Complementary Founders

    sickn33/agentic-awesome-skills

    Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.

    47k GitHub starsUsed in 1 repo~4.8k tokens
    Auto-check passed

  • Whatsapp Cloud API

    sickn33/agentic-awesome-skills

    Integracao com WhatsApp Business Cloud API (Meta). An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 2 repos~4.5k tokens
    Auto-check passed

  • Cline Pilot

    sickn33/agentic-awesome-skills

    Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.

    47k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed

Categories

Questions about Diary

What does Diary do?

Unified Diary System: A context-preserving automated logger for multi-project development. Diary is an agent skill from sickn33/agentic-awesome-skills. Unified Diary System: A context-preserving automated logger for multi-project development.

When should I use Diary?

Diary fits situations like: tasks that involve Journaling and reflection.

How do I install Diary in Claude Code?

Run `npx skills add sickn33/agentic-awesome-skills --skill diary -a claude-code`. Or copy the skill folder (skills/diary in sickn33/agentic-awesome-skills) into .claude/skills/diary in your project. Claude Code loads it when a task matches its description.

How do I install Diary in Codex?

Run `npx skills add sickn33/agentic-awesome-skills --skill diary -a codex`. Or copy the skill folder (skills/diary in sickn33/agentic-awesome-skills) into .agents/skills/diary in your project. Codex loads it when a task matches its description.

Can I use Diary in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sickn33/agentic-awesome-skills --skill diary -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/diary, .gemini/skills/diary, .github/skills/diary and .opencode/skills/diary in your project.

What does Diary need to run?

Going by SKILL.md and its folder, Diary needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.

Does Diary access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Diary safe to install?

Our automated static check of SKILL.md flagged 1 warning(s): tells the agent its actions are pre-authorized / not to stop for confirmation. Read the flagged lines before installing; the check is not a guarantee either way. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Diary use?

Diary is published under the MIT licence (from the LICENSE file in the skill folder). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Diary use?

About 2.3k tokens (SKILL.md is roughly 9.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Diary?

Skills that share tags, products or a category with Diary: LLM Wiki (lewislulu/llm-wiki-skill, 655 stars), Munger Perspective (alchaincyf/munger-skill, 377 stars), Daily Journal (huytieu/COG-second-brain, 1.3k stars) and Letterboxd Diary (joe-bell/skills, 211 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Diary?

sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,304 GitHub stars. The repository holds 1,394 skills in this directory. The repository was last updated on October 6, 2026.

Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.