How do I install the Problem Log skill?

Run npx skillmds@latest add naticorrea-03/problem-log in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Problem Log safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Problem Log?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Problem Log free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Problem Log?

naticorrea-03 (@naticorrea-03) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Problem Log by naticorrea-03 — Agent Skill

Name: Problem Log
Author: naticorrea-03

Problem Log

A hands-off daily log of how you actually solve problems. Once a day it reads your Claude Code sessions and writes a short entry per real problem-solving arc (the problem, how you worked it, the outcome) to a local markdown file. Great for standups, reviews, interviews, or just remembering what you figured out.

naticorrea-03 a8ce743 5 files · 8.9 KB Updated Sep 17, 2026

File contents

problem-log

You solve real problems in Claude Code every day and forget them by next week. This logs them automatically.

Once a day a cron reads that day's Claude Code sessions, finds the genuine problem-solving arcs (a bug you chased down, a design decision with tradeoffs, a diagnosis that overturned your first guess), and appends a short entry for each to a markdown file. No manual step. Routine chatter and simple lookups are skipped.

What you get, per arc

Problem — the friction in one line
Approach & iteration — how you worked it, including dead ends and pivots
Outcome — what actually resolved it
Tools — what you used
Date + source session id

Setup (2 minutes)

Requires the claude CLI on your PATH and Python 3.
Pick where the log lives (default ~/problem-log.md).

Install the daily cron:

cp com.example.problem-log-daily.plist ~/Library/LaunchAgents/
# edit the path inside to point at this folder, then:
launchctl load ~/Library/LaunchAgents/com.example.problem-log-daily.plist

(On Linux, use the crontab line in daily-sweep.sh's header instead.)

Run it by hand

./daily-sweep.sh          # log yesterday's arcs now
./daily-sweep.sh dry      # print what it would log, write nothing

How it works

build_digest.py (pure local, no LLM) reads your session transcripts from ~/.claude/projects, keeps only the human/assistant text, and drops trivial sessions. Then a headless claude pass reads that digest per SWEEP_PROMPT.md and appends the arcs to your log file. Nothing leaves your machine except the model call you already use.

---name: problem-logdescription: A hands-off daily log of how you actually solve problems. Once a day it reads your Claude Code sessions and writes a short entry per real problem-solving arc (the problem, how you worked it, the outcome) to a local markdown file. Great for standups, reviews, interviews, or just remembering what you figured out.---# problem-logYou solve real problems in Claude Code every day and forget them by next week. This logs them automatically.Once a day a cron reads that day's Claude Code sessions, finds the genuine problem-solving arcs (a bug you chased down, a design decision with tradeoffs, a diagnosis that overturned your first guess), and appends a short entry for each to a markdown file. No manual step. Routine chatter and simple lookups are skipped.## What you get, per arc- **Problem** — the friction in one line- **Approach & iteration** — how you worked it, including dead ends and pivots- **Outcome** — what actually resolved it- **Tools** — what you used- Date + source session id## Setup (2 minutes)1. Requires the `claude` CLI on your PATH and Python 3.2. Pick where the log lives (default `~/problem-log.md`).3. Install the daily cron: ``` cp com.example.problem-log-daily.plist ~/Library/LaunchAgents/ # edit the path inside to point at this folder, then: launchctl load ~/Library/LaunchAgents/com.example.problem-log-daily.plist ``` (On Linux, use the `crontab` line in `daily-sweep.sh`'s header instead.)## Run it by hand```./daily-sweep.sh # log yesterday's arcs now./daily-sweep.sh dry # print what it would log, write nothing```## How it works`build_digest.py` (pure local, no LLM) reads your session transcripts from `~/.claude/projects`, keeps only the human/assistant text, and drops trivial sessions. Then a headless `claude` pass reads that digest per `SWEEP_PROMPT.md` and appends the arcs to your log file. Nothing leaves your machine except the model call you already use.

Frequently asked questions