mistake-notebook

Record and retrieve mistakes in project-local and universal Mistake.md files.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/justcyl/my-skills --skill mistake-notebook
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mistake-notebook
Source: https://github.com/justcyl/my-skills/tree/main/mistake-notebook
Command: npx skills add https://github.com/justcyl/my-skills --skill mistake-notebook

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Mistake notebook helps teams and assistants memorize and reuse mistakes by recording them in Mistake Notebooks, enabling quick lookup and continuous improvement.

Core Features & Use Cases

  • Memory: Persist and retrieve mistakes with a structured entry including problem, insights, and solution.
  • Automation: Append new entries after solving a problem, updating the Mistake Notebook.
  • Use Case: When solving a complex issue, log the problem, steps taken, and final solution to avoid repeating it.

Quick Start

Log a new mistake after resolving a problem by describing the issue and the successful solution.

Frequently Asked Questions about mistake-notebook

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

FAQPage Schema
How do I record and reuse problem-solving mistakes across different projects?

You can record and reuse problem-solving mistakes by maintaining a universal ~/MISTAKE.md for generic issues and project-local Mistake.md files for specific contexts. This structured notebook approach appends solutions after resolving problems to enable accurate lookup and continuous learning.

What is the best way to log a mistake after resolving a complex issue?

The best way to log a mistake is to append a new entry to your Mistake Notebook after resolving the issue. You describe the problem, the steps taken, and the successful solution, ensuring the entry enforces the Mistake Solution Format and metadata capture for accurate future retrieval.

Can I maintain separate mistake notebooks for project-specific and generic problems?

Yes, you can maintain both project-local Mistake.md files for project-specific issues and a universal ~/MISTAKE.md for generic problems. This dual-notebook approach allows you to apply recorded solutions across different projects and contexts effectively.

Does the mistake notebook format require specific metadata for entries?

Yes, the mistake notebook enforces the Mistake Solution Format and metadata capture for every entry. Capturing structured metadata alongside the problem, insights, and solution enables accurate lookup, review, and learning from past errors.

Why should I use a structured notebook for recording errors instead of plain notes?

Using a structured notebook for recording errors enforces the Mistake Solution Format and metadata capture, enabling accurate lookup and review. This prevents repeating past mistakes by persisting problem-solving insights and solutions in a retrievable format.

When do I need to update my mistake notebook with a new entry?

You need to update your mistake notebook with a new entry immediately after solving a complex issue. Appending the problem description, steps taken, and final solution at this point ensures the problem-solving memory is accurate and readily available for future lookup.