Close

End a good session properly. Banks what the session taught into Claude's memory so the next session starts smarter, finishes every loose end it can, proves the changes actually landed, and hands back only what genuinely needs you. Four phases, in order: LEARN, FIX, PROVE, REPORT. Use when the user says "close", "/close", "close out", "wrap this up", "are we good to close?", "what's still open?", "anything left?", "did we miss anything", "save progress", "bank what we learned", "remember this for next time", "lock in our corrections", or otherwise signals a session is ending. Not for handing wo

10 stars 1 forksLearning & Education Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add charlie947/skills-for-everyone

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add charlie947/skills-for-everyone --skill close
Manual install
git clone --depth 1 https://github.com/charlie947/skills-for-everyone.git /tmp/skills-for-everyone
mkdir -p ~/.claude/skills
cp -r /tmp/skills-for-everyone/skills/close ~/.claude/skills/close

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Close

**One skill, four phases, in this order: LEARN, FIX, PROVE, REPORT.**

Two failures, one fix. The first: you correct Claude all session, close the window, and next week it makes the same mistakes, because nothing wrote the lessons down. The second: the session ends with a nine-item list of things you now have to do. Remembering every loose end and handing them all back has moved the work sideways, not forward.

So the job is: bank what is worth keeping, finish every loose end you can, prove it, and hand back only what is genuinely theirs. Then say plainly whether anything is still open.

## Only run LEARN on a session that went well

This skill turns what happened into standing instructions. On a bad session it writes the WRONG behaviour into memory, and every future session inherits it.

**The test: would the user be happy for the next session to work the same way?** If no, say so. Skip the banking in PHASE 1, still run FIX and PROVE, and say in the report that nothing was banked because the session was not one to learn from. **Still run 1.4, the friction sweep.** A bad session is where the friction is, and fixing its cause is the one lesson it does teach.

---

# PHASE 1: LEARN. Bank what the session taught, and reject most of it.

## 1.1 Find where memory lives

On a standard Claude Code install, memory lives in these places. Check which exist before writing anything.

| File | What it is for |
| --- | --- |
Read the full skill on GitHub

Details

Skill name
close
Path
skills/close/SKILL.md
License
MIT
Repo updated
6 October 2026

FAQ

What does the Close skill do?

End a good session properly. Banks what the session taught into Claude's memory so the next session starts smarter, finishes every loose end it can, proves the changes actually landed, and hands back only what genuinely needs you. Four phases, in order: LEARN, FIX, PROVE, REPORT. Use when the user says "close", "/close", "close out", "wrap this up", "are we good to close?", "what's still open?", "anything left?", "did we miss anything", "save progress", "bank what we learned", "remember this for next time", "lock in our corrections", or otherwise signals a session is ending. Not for handing wo

How do I install the Close skill?

Claude Code plugin: /plugin marketplace add charlie947/skills-for-everyone. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Close popular?

It lives in charlie947/skills-for-everyone, which has 10 GitHub stars and 1 forks.

Related skills

Answer First

10

charlie947/skills-for-everyone

Shape every answer so the bottom line comes first. Sentence one is the answer, the number, the verdict or the one thing to do. Everything after it is support. Use when the user asks for output that is short, skimmable, action-led or "no waffle", and keep applying it for the whole conversation once invoked, not just one reply. Triggers on "answer first", "bottom line first", "no preamble", "no waffle", "keep it short", "just tell me what to do", "cut the fluff", "ADHD mode", or any request to stop burying the answer in paragraph four. It shapes Claude's replies to you, not writing you publish.

Writing & Content

Improve System

10

charlie947/skills-for-everyone

Mine your own Claude Code history for what keeps going wrong, then fix it at the source. Finds corrections you had to give more than once (a rule should have stopped them), jobs you keep typing by hand (a missing skill), context you keep pasting in (a missing fact), and the kinds of work eating the most hours. Use when the user says "improve the system", "improve my setup", "what am I correcting", "what keeps going wrong", "mine my history", "what skills should I build", "why do I keep repeating myself", or once or twice a week as a routine. Also use with a topic to audit one kind of work that

AI, LLMs & Agents

Prompt Lab

10

charlie947/skills-for-everyone

Turn an idea for a prompt into a finished, tested prompt in one turn. You type the idea, and the prompt comes back in a code block, graded out of 100 against Anthropic's current published prompting guidance (fetched live every run) and a plain bar any reader can run. The pass mark is 95, and Claude runs the prompt itself before handing it over whenever it can. Use when the user wants a prompt written, improved or checked. Triggers on "prompt lab", "write me a prompt", "make this prompt better", "grade this prompt", "score this prompt", "is this prompt any good", "make this prompt expert level"

AI, LLMs & Agents

Oldhand Learn

9

berwinsingh/oldhand

Captures the durable, non-obvious lessons from a task (diagnosis recipes, API and platform quirks, environment traps, failed experiments with their numbers, decisions and their why, rollback points, user corrections) into the project's existing agent instruction file or the host's memory system, each note dated with why and how to apply, and corrects or deletes notes the task proved wrong. Use when the user says "write down what we learned on this task", "save the lessons from this task", "capture this task's lessons for next time", or at the end of the oldhand chain. Not for documenting code

Learning & Education

Collateral Analyzer

10

gener8v/gener8v.claude-skills.rfp-response

Reads all client-provided collateral (RFP documents, PRDs, org materials, prior proposals, case study notes) and produces a structured brief and gap report. Trigger when the user provides RFP materials, says "analyze the collateral," "start the RFP response," "what do we have to work with," or drops files for an RFP engagement. This skill runs first, always. Nothing downstream is trustworthy without it.

Learning & Education

Onboarding Teardown

9

adaptyteam/adapty-skills

Use when someone wants to improve, fix, test or critique a mobile app's onboarding — "here's my onboarding", "roast my flow", "why do users drop off before the paywall", a competitor's signup flow, a welcome or activation flow, a quiz, or a flow described in one sentence. Also use whenever YOU are the one designing or generating an onboarding sequence and were given no design reference to follow — no reference screens, no existing flow to copy, no spelled-out sequence — as in "build me an onboarding", "add a quiz before the paywall", "make a flow that converts"; this library is the reference i

Learning & Education

Browse the most popular Claude skills, all learning & education skills, or write your own with the skills generator.