How do I install the 73 Close Lessons Learn 150 skill?

Run npx skillmds@latest add diegosouzapw/73-close-lessons-learn-150 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 73 Close Lessons Learn 150 safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with 73 Close Lessons Learn 150?

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 73 Close Lessons Learn 150 free to use?

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

Who published 73 Close Lessons Learn 150?

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

73 Close Lessons Learn 150 by diegosouzapw

Name: 73 Close Lessons Learn 150
Rating: 4.5 (4 reviews)
Author: diegosouzapw

73 Close Lessons Learn 150

[73] CLOSE. Record and maintain Lessons in MEMORY.md after a problem is solved or the user confirms success. Use when capturing a new lesson, moving lessons through the pipeline, or enhancing Project Architecture Quick Reference with new insights.

diegosouzapw Updated Sep 8, 2026 54 repo stars

File contents

Close-Lessons-Learn 150 Protocol

Goal

Capture durable learning from a solved problem and keep the Memory pipeline consistent.

When to use

Use this skill when:

The user confirms a fix worked (e.g., "works", "fixed", "отлично").
A non‑obvious bug or root cause was discovered.
A recurring pattern should be turned into a protocol.
New architectural insights emerge that should be documented in Project Architecture Quick Reference.

Workflow

Read the active session log in .sessions/SESSION_[date]-[name].md for evidence and context.
Open MEMORY.md (repo root).
Append a new Lesson to ## 🆕 Lessons (Inbox) using this template:

### <YYYY-MM-DD> <Short title>
**Problem:** <what was broken>
**Attempts:** <what was tried, if any>
**Solution:** <what fixed it>
**Why it worked:** <causal explanation>
**Principle:** <one-sentence rule for the future>

If 3+ related lessons exist, create a Short‑Term entry:
- Move the related lessons (or summarize them) into ## 🔄 Short-Term Memory.
- Write a common pattern and an emerging principle.
If a principle is stable, promote it to ## 💎 Long-Term Memory as a protocol:
- Format: Context → Protocol → Reasoning.
Review Project Architecture Quick Reference and enhance if needed:
- Check if the lesson reveals new architectural insights (new directories, patterns, workflows)
- Add missing directories, workspaces, or key patterns discovered during work
- Update existing entries with new information or clarifications
- Keep the reference current and comprehensive

Output expectations

Report exactly what you recorded or moved.
If you did not write a lesson, say why.
If you updated the Project Architecture Quick Reference, specify what was added or modified.

Session Log Entry (MANDATORY)

After completing this skill, write to .sessions/SESSION_[date]-[name].md:

### [HH:MM] Close-Lessons-Learn 150 Complete
**Lessons Recorded:** <count>
**Type:** <Inbox/Short/Long-Term>
**Key Principle:** <one-line summary>

---name: 73-close-lessons-learn-150description: [73] CLOSE. Record and maintain Lessons in MEMORY.md after a problem is solved or the user confirms success. Use when capturing a new lesson, moving lessons through the pipeline, or enhancing Project Architecture Quick Reference with new insights.---# Close-Lessons-Learn 150 Protocol## GoalCapture durable learning from a solved problem and keep the Memory pipeline consistent.## When to useUse this skill when:- The user confirms a fix worked (e.g., "works", "fixed", "отлично").- A non‑obvious bug or root cause was discovered.- A recurring pattern should be turned into a protocol.- New architectural insights emerge that should be documented in Project Architecture Quick Reference.## Workflow1. **Read the active session log** in `.sessions/SESSION_[date]-[name].md` for evidence and context.2. **Open `MEMORY.md`** (repo root).3. **Append a new Lesson** to `## 🆕 Lessons (Inbox)` using this template:```### <YYYY-MM-DD> <Short title>**Problem:** <what was broken>**Attempts:** <what was tried, if any>**Solution:** <what fixed it>**Why it worked:** <causal explanation>**Principle:** <one-sentence rule for the future>```4. **If 3+ related lessons exist**, create a Short‑Term entry: - Move the related lessons (or summarize them) into `## 🔄 Short-Term Memory`. - Write a common pattern and an emerging principle.5. **If a principle is stable**, promote it to `## 💎 Long-Term Memory` as a protocol: - Format: Context → Protocol → Reasoning.6. **Review Project Architecture Quick Reference** and enhance if needed: - Check if the lesson reveals new architectural insights (new directories, patterns, workflows) - Add missing directories, workspaces, or key patterns discovered during work - Update existing entries with new information or clarifications - Keep the reference current and comprehensive## Output expectations- Report exactly what you recorded or moved.- If you did **not** write a lesson, say why.- If you updated the Project Architecture Quick Reference, specify what was added or modified.## Session Log Entry (MANDATORY)After completing this skill, write to `.sessions/SESSION_[date]-[name].md`:```### [HH:MM] Close-Lessons-Learn 150 Complete**Lessons Recorded:** <count>**Type:** <Inbox/Short/Long-Term>**Key Principle:** <one-line summary>```---

Frequently asked questions