agentleFS
TakaGotoTakaGoto/rag-learning-academy/.claude/skills/recap/SKILL.md

recap

Skill24 starsChanged 19 days agoMITView on GitHub

Quick summary of what you covered last session

45 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use orchestrate, brainstorm and 4 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • varun29ankuSSkill

    orchestrate

    This skill should be used when the user asks to 'orchestrate a task', 'break down work into parallel agents', 'coordinate subtasks', 'run agents in parallel', or mentions 'multi-agent'. Decomposes complex tasks into tracked subtasks, dispatches parallel subagents, and coordinates until completion.

    Also in 4 projects that use this

  • nicolasestremSkill

    brainstorm

    Structured idea generation and solution exploration with systematic analysis.

    Also in 3 projects that use this

  • BlockSkill

    plan

    Draft a TDD, PRD, or lightweight plan in the conversation without committing it.

    Also in 3 projects that use this

  • SentrySkill

    commit

    Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.

    Also in 3 projects that use this

  • SentrySkill

    review

    Fixture review skill.

    Also in 3 projects that use this

  • MicrosoftSkill

    handoff

    Compact the current conversation into a handoff document for another agent to pick up.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 4 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 39 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the following files to reconstruct the last session:

    line 12
  2. Very specific:

    If no progress data exists, say: "No previous session found.

    line 19
  3. Distinctive:

    Keep it to 5-8 lines max. Cover:

    line 23
  4. Very specific:

    If mid-module: /lesson to continue

    line 46
  5. Very specific:

    If they just finished a module: /quiz to test understanding

    line 47
  6. Very specific:

    If quiz scores were low: /explain [weak topic] to review

    line 48
  7. Distinctive:

    If they wrote journal notes with questions: address the question briefly

    line 49
  8. Distinctive:

    Keep it short. The whole recap should fit in one screen.

    line 51

“Common” is measured: kept by at least 6 in 10 of the 39 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Recap: What You Learned Last Time

Give the learner a fast, useful summary of their most recent session so they can pick up where they left off.

Step 1: Load Session History

Read the following files to reconstruct the last session:

  • progress/module-tracker.md — find the most recently completed lessons (by date)
  • progress/quiz-results.md — any quizzes taken recently
  • progress/journal.md — any notes the learner wrote
  • progress/learner-profile.md — current module and track

If no progress data exists, say: "No previous session found. Run /start to begin your journey."

Step 2: Summarize Last Session

Keep it to 5-8 lines max. Cover:

  1. What you worked on — which lesson(s), quiz, or challenge
  2. Key concepts — the 2-3 main ideas from that session, in plain language
  3. Where you stopped — what's next in the track

Format:

Last Session Recap
==================
You worked on: [lesson/quiz/challenge name]
Key concepts:
  - [concept 1 in one sentence]
  - [concept 2 in one sentence]
  - [concept 3 in one sentence]
Next up: [next incomplete lesson or suggested action]

Step 3: Suggest Next Action

Based on where they left off, suggest one clear next step:

  • If mid-module: /lesson to continue
  • If they just finished a module: /quiz to test understanding
  • If quiz scores were low: /explain [weak topic] to review
  • If they wrote journal notes with questions: address the question briefly

Keep it short. The whole recap should fit in one screen.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.