learning-gap-analyzer

Map understanding, identify knowledge gaps, and build targeted learning plans with spaced repetition. Use when assessing knowledge levels, designing study plans, or optimizing learning paths.

31 stars

Best use case

learning-gap-analyzer is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Map understanding, identify knowledge gaps, and build targeted learning plans with spaced repetition. Use when assessing knowledge levels, designing study plans, or optimizing learning paths.

Teams using learning-gap-analyzer should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/learning-gap-analyzer/SKILL.md --create-dirs "https://raw.githubusercontent.com/travisjneuman/.claude/main/skills/learning-gap-analyzer/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/learning-gap-analyzer/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How learning-gap-analyzer Compares

Feature / Agentlearning-gap-analyzerStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Map understanding, identify knowledge gaps, and build targeted learning plans with spaced repetition. Use when assessing knowledge levels, designing study plans, or optimizing learning paths.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Learning Gap Analyzer

Frameworks for diagnosing knowledge gaps, creating targeted remediation plans, and designing effective learning strategies using evidence-based techniques.

## Knowledge Mapping

### Self-Assessment Matrix

```
KNOWLEDGE MAP: [Subject/Domain]

Topic                    | Awareness | Understanding | Application | Mastery
                         | (1)       | (2)           | (3)         | (4)
-------------------------|-----------|---------------|-------------|--------
[Subtopic 1]             | [ ]       | [ ]           | [ ]         | [ ]
[Subtopic 2]             | [ ]       | [ ]           | [ ]         | [ ]
[Subtopic 3]             | [ ]       | [ ]           | [ ]         | [ ]
[Subtopic 4]             | [ ]       | [ ]           | [ ]         | [ ]
[Subtopic 5]             | [ ]       | [ ]           | [ ]         | [ ]

LEVELS:
  1 - Awareness:     I've heard of it, can recognize the term
  2 - Understanding: I can explain the concept in my own words
  3 - Application:   I can use it to solve problems independently
  4 - Mastery:       I can teach it, adapt it, and combine with other concepts

SCORING GUIDE:
  Mark your honest current level for each topic.
  Gaps = Topics where your level is below the target level.
  Priority = High target importance + large gap size.
```

### Concept Dependency Map

```
PREREQUISITE CHAIN: [Domain]

Build knowledge in this order (each level requires prior levels):

Level 1 (Foundations):
  □ [Concept A] → Required for everything else
  □ [Concept B] → Required for everything else

Level 2 (Core):
  □ [Concept C] ← Requires: A
  □ [Concept D] ← Requires: A, B
  □ [Concept E] ← Requires: B

Level 3 (Intermediate):
  □ [Concept F] ← Requires: C, D
  □ [Concept G] ← Requires: D, E

Level 4 (Advanced):
  □ [Concept H] ← Requires: F, G
  □ [Concept I] ← Requires: G

DIAGNOSTIC APPROACH:
  1. Test understanding at Level 3+
  2. If gaps found, trace back to prerequisites
  3. Start remediation at the earliest gap in the chain
  4. Don't skip ahead — build foundations first
```

## Gap Identification Methods

### Diagnostic Assessment Design

```
DIAGNOSTIC ASSESSMENT TEMPLATE:

PURPOSE: Identify specific knowledge gaps before starting learning plan

STRUCTURE:
  Section 1: Foundational concepts (5 questions)
    - If <60% correct: Start at Level 1
    - Tests: Definitions, basic recall, simple recognition

  Section 2: Core understanding (5 questions)
    - If <60% correct: Start at Level 2
    - Tests: Explanation, comparison, basic application

  Section 3: Application (5 questions)
    - If <60% correct: Start at Level 3
    - Tests: Problem-solving, scenario analysis, transfer

  Section 4: Advanced (5 questions)
    - If <60% correct: Start at Level 4
    - Tests: Synthesis, evaluation, novel situations

QUESTION TYPES:
  - Explain in your own words: [concept]
  - Given [scenario], what would happen if [variable changed]?
  - Compare and contrast: [concept A] vs [concept B]
  - Solve: [problem requiring application]
  - What's wrong with this: [flawed example]
```

### The Feynman Technique for Gap Detection

```
FEYNMAN TECHNIQUE:

STEP 1: Choose a concept you think you understand
STEP 2: Explain it as if teaching a 12-year-old
  - Use simple language
  - No jargon
  - Include examples

STEP 3: Identify where you get stuck
  - Where do you reach for jargon?
  - Where does your explanation get vague?
  - Where can't you provide a clear example?

  → THESE ARE YOUR GAPS

STEP 4: Go back to source material
  - Study specifically the areas where you struggled
  - Don't re-read everything — target the gaps

STEP 5: Simplify and retry
  - Re-explain using analogies
  - If you can explain it simply, you understand it
  - If you can't, repeat steps 3-4

TRACKING FORMAT:
  Concept: _______________
  Explanation attempt: [Your explanation]
  Stuck points: [Where it broke down]
  Gap identified: [What you need to learn]
  Source to study: [Specific chapter, video, article]
  Re-explanation: [After studying]
  Confidence: [ ] Low  [ ] Medium  [ ] High
```

## Learning Plan Design

### Targeted Remediation Plan

```
LEARNING PLAN: [Goal]

CURRENT STATE: [Assessment results summary]
TARGET STATE: [Desired competency level]
TIMELINE: [Weeks/months]
WEEKLY TIME BUDGET: [Hours]

PHASE 1: FOUNDATIONS (Weeks 1-N)
  Gap: [Specific knowledge gap]
  Resources:
    - [Resource 1] — Estimated time: [X hours]
    - [Resource 2] — Estimated time: [X hours]
  Practice:
    - [Exercise or application activity]
  Milestone: [How you'll know you've closed this gap]

PHASE 2: CORE SKILLS (Weeks N-M)
  Gap: [Specific knowledge gap]
  Resources:
    - [Resource 1] — Estimated time: [X hours]
    - [Resource 2] — Estimated time: [X hours]
  Practice:
    - [Exercise or application activity]
  Milestone: [How you'll know you've closed this gap]

PHASE 3: APPLICATION (Weeks M-P)
  Gap: [Specific knowledge gap]
  Resources:
    - [Resource 1] — Estimated time: [X hours]
  Practice:
    - [Project or real-world application]
  Milestone: [Demonstrable competency]

WEEKLY SCHEDULE:
  Day       | Activity                    | Duration
  Monday    | New material (reading/video) | 1 hour
  Tuesday   | Practice problems            | 45 min
  Wednesday | Spaced review (flashcards)   | 30 min
  Thursday  | New material                 | 1 hour
  Friday    | Application project          | 1 hour
  Weekend   | Weekly review + assessment   | 30 min
```

## Spaced Repetition System

### Optimal Review Schedule

```
SPACED REPETITION INTERVALS:

First learning:     Day 0
First review:       Day 1   (24 hours later)
Second review:      Day 3   (2 days after first review)
Third review:       Day 7   (4 days after second review)
Fourth review:      Day 14  (7 days after third review)
Fifth review:       Day 30  (16 days after fourth review)
Sixth review:       Day 60  (30 days after fifth review)
Maintenance:        Every 90 days thereafter

ADJUSTMENT RULES:
  If you recalled easily:     Move to next interval
  If you recalled with effort: Repeat at current interval
  If you failed to recall:    Reset to Day 1 interval

CARD DESIGN PRINCIPLES:
  - One concept per card (atomic)
  - Question on front, answer on back
  - Include context/example on back
  - Use images where possible
  - Avoid yes/no questions — require recall
```

### Active Recall Techniques

| Technique | How It Works | Best For | Effort Level |
|-----------|-------------|----------|-------------|
| **Flashcards** | Question → attempt recall → check | Facts, definitions, formulas | Low-Medium |
| **Practice problems** | Solve without looking at solution | Application, procedures | Medium |
| **Free recall** | Close book, write everything you know | Comprehensive review | Medium-High |
| **Interleaving** | Mix topics in practice (don't block) | Discrimination, transfer | Medium |
| **Elaborative interrogation** | Ask "why?" and "how?" for each fact | Deep understanding | Medium |
| **Self-testing** | Create and take your own quizzes | All types of knowledge | Medium |
| **Teaching others** | Explain concept to someone else | Deep mastery verification | High |

## Progress Tracking

### Weekly Progress Template

```
WEEKLY LEARNING REVIEW

Week: ___ of ___
Date: __________

HOURS INVESTED:
  Planned: ___ hours
  Actual: ___ hours

TOPICS COVERED:
  □ [Topic 1] — Confidence: [ ] Low [ ] Med [ ] High
  □ [Topic 2] — Confidence: [ ] Low [ ] Med [ ] High
  □ [Topic 3] — Confidence: [ ] Low [ ] Med [ ] High

ASSESSMENT RESULTS:
  Quiz/test score: ___/___
  Practice problem accuracy: ___%
  Concepts recalled via free recall: ___/___

WHAT WENT WELL:
  - [Insight or breakthrough]

WHAT WAS DIFFICULT:
  - [Struggle point]
  - Gap identified: [Specific concept]

ADJUSTMENTS FOR NEXT WEEK:
  - [Change to plan based on this week's learning]

SPACED REVIEW DUE:
  □ [Topic from Week N-1] — Review due: [Date]
  □ [Topic from Week N-3] — Review due: [Date]
```

### Mastery Criteria

| Level | Evidence Required | Assessment Method |
|-------|------------------|-------------------|
| **Awareness** | Can define term and recognize it in context | Multiple choice, matching |
| **Understanding** | Can explain concept in own words with examples | Short answer, Feynman test |
| **Application** | Can solve novel problems using the concept | Practice problems, case studies |
| **Mastery** | Can teach others and combine with other concepts | Teaching exercise, project |

## Learning Science Principles

### Evidence-Based Strategies

```
HIGH-IMPACT LEARNING STRATEGIES:

1. RETRIEVAL PRACTICE (Effect: +0.7 SD)
   Don't just re-read — test yourself
   Implementation: Flashcards, practice quizzes, free recall

2. SPACED PRACTICE (Effect: +0.6 SD)
   Distribute learning over time, don't cram
   Implementation: Review schedule, interleaved practice

3. ELABORATION (Effect: +0.5 SD)
   Connect new info to existing knowledge
   Implementation: "How does this relate to...?" questions

4. INTERLEAVING (Effect: +0.4 SD)
   Mix different topics/problem types in practice
   Implementation: Shuffle practice problems from multiple chapters

5. CONCRETE EXAMPLES (Effect: +0.4 SD)
   Connect abstract concepts to specific instances
   Implementation: Generate 2-3 real examples for each concept

6. DUAL CODING (Effect: +0.3 SD)
   Combine verbal and visual representations
   Implementation: Draw diagrams, create concept maps

LOW-IMPACT STRATEGIES (AVOID):
  ✗ Re-reading (passive, creates illusion of learning)
  ✗ Highlighting (passive, doesn't require processing)
  ✗ Summarizing without retrieval (only slightly better)
  ✗ Massed practice / cramming (poor long-term retention)
```

## See Also

- [Course Material Creator](../course-material-creator/SKILL.md)
- [Career Path Planner](../career-path-planner/SKILL.md)
- [Literature Review Planner](../literature-review-planner/SKILL.md)

Related Skills

tech-debt-analyzer

31
from travisjneuman/.claude

This skill should be used when analyzing technical debt in a codebase, documenting code quality issues, creating technical debt registers, or assessing code maintainability. Use this for identifying code smells, architectural issues, dependency problems, missing documentation, security vulnerabilities, and creating comprehensive technical debt documentation.

real-estate-analyzer

31
from travisjneuman/.claude

Property valuation, market analysis, investment ROI calculations, comparable analysis, and rental yield assessment. Use when evaluating real estate investments, analyzing property markets, or calculating returns.

fundraising-analyzer

31
from travisjneuman/.claude

Nonprofit fundraising performance analysis with donor segmentation, campaign ROI, retention metrics, and trend analysis. Use when evaluating fundraising effectiveness, analyzing donor data, or planning campaigns.

example-skill

31
from travisjneuman/.claude

Example skill - replace with your skill's description and activation keywords

websockets-realtime

31
from travisjneuman/.claude

Real-time communication with WebSockets, Server-Sent Events, and related technologies. Use when building chat, live updates, collaborative features, or any real-time functionality.

video-production

31
from travisjneuman/.claude

Professional video production from planning to delivery. Use when creating video content, editing workflows, motion graphics, or optimizing video for different platforms.

ui-research

31
from travisjneuman/.claude

Research-first UI/UX design workflow. Use BEFORE any frontend visual work to research modern patterns, gather inspiration from real products, and avoid generic AI-generated looks. Mandatory prerequisite for quality UI work.

ui-animation

31
from travisjneuman/.claude

Motion design and animation for user interfaces. Use when creating micro-interactions, page transitions, loading states, or any UI animation across web and mobile platforms.

travel-planner

31
from travisjneuman/.claude

Travel destination research and daily itinerary creation with logistics planning, budget tracking, and experience optimization. Use when planning trips, creating travel itineraries, comparing destinations, or organizing travel logistics.

test-specialist

31
from travisjneuman/.claude

This skill should be used when writing test cases, fixing bugs, analyzing code for potential issues, or improving test coverage for JavaScript/TypeScript applications. Use this for unit tests, integration tests, end-to-end tests, debugging runtime errors, logic bugs, performance issues, security vulnerabilities, and systematic code analysis.

tdd-workflow

31
from travisjneuman/.claude

Test-Driven Development workflow enforcement with RED-GREEN-REFACTOR cycle. Use when implementing features test-first or improving test coverage.

tauri-desktop

31
from travisjneuman/.claude

Tauri 2.0 project setup, Rust backend + web frontend, plugin system, IPC commands, security model, auto-update, and mobile support. Use when building lightweight cross-platform desktop or mobile apps with Tauri.