borghei/Claude-Skills / personal-productivity/learning-workspace
learning-workspace
VerifiedSet up and run a multi-session study workspace with mission, curriculum, lessons and spaced review. Use when learning a topic over weeks, resuming study after a gap, checking real understanding, or planning reviews.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.4 KB |
| assets/learning-record-entry-template.md | markdown | 1.1 KB |
| assets/lesson-template.md | markdown | 1.6 KB |
| assets/sample_learning_record.json | config | 4.3 KB |
| assets/sample_learning_record_clean.json | config | 3.3 KB |
| assets/sample_workspace_spec.json | config | 2.0 KB |
| assets/sample_workspace_spec_flawed.json | config | 525 B |
| references/learning-science.md | markdown | 10.5 KB |
| references/session-playbook.md | markdown | 7.2 KB |
| references/workspace-formats.md | markdown | 8.6 KB |
| scripts/review_scheduler.py | script | 10.9 KB |
| scripts/workspace_scaffolder.py | script | 11.8 KB |
assets/lesson-template.md
View on GitHub# Lesson NNNN: <core idea in a few words>
Module: <M#> | Planned: <minutes> min | Date: <YYYY-MM-DD>
## Win for this lesson
<One thing the learner will be able to do at the end, phrased so you can watch it happen.>
Mission link: <which success criterion in MISSION.md this moves toward>
## Warm-up (retrieval, no notes, 3-4 min)
<Paste the scheduler's warm_up items as production questions. Learner answers, then grades
recalled / partial / failed against the correct answer.>
1. <item id> — <question>
2.
3.
## Core idea (5-7 min)
<The minimum knowledge needed for the win. One idea. Use GLOSSARY.md terms exactly.>
Source: <primary resource from RESOURCES.md, section or timestamp>
Prediction prompt before revealing: <question>
## Worked example (3-5 min)
| Step | What | Why (learner states this) |
|---|---|---|
| 1 | | |
| 2 | | |
| 3 | | |
## Practice with feedback (7-9 min)
1. <same type, last step blank>
2. <same type, last two steps blank>
3. <new surface, all steps blank>
4. <optional: mixed with an earlier technique>
## Exit check (3 min)
- Explain-back: <"Explain to someone who missed this lesson why...">
- Transfer: <same idea, different context>
- Result: <demonstrated / partial / not yet>
## Read or watch next
<One primary source, with what to look for in it.>
Questions are welcome at any point — an unasked question is the most common hidden gap.
## Record after the lesson
- Session entry added: [ ]
- Warm-up results appended to items: [ ]
- New items (id, concept, state, evidence):
- Misconceptions surfaced (belief, correction, recheck date):
- Glossary terms added:
- Module status change:
- Scheduler re-run, gate passes: [ ]
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |