travisjneuman/.claude

learning-gap-analyzer

Map understanding, identify knowledge gaps, and build targeted learning plans with spaced repetition.

Ver código-fonte

Como usar

  1. Copie o comando e verifique o pacote antes de instalar no seu ambiente de agente.
  2. Consulte no original as ferramentas, credenciais e ambientes necessários.
  3. Descreva os dados de entrada e a entrega esperada; confira a saída com as fontes.
npx skills add https://github.com/travisjneuman/.claude --skill learning-gap-analyzer

Antes de começar

  • A instalação não inclui assinatura de modelo, franquia API ou acesso aos seus arquivos.
  • Estrelas e instalações indicam atividade, não um teste independente de qualidade ou segurança.
Documento original do Skill

Renderizado do repositório de origem, preservando títulos, exemplos, código, tabelas, links e imagens.

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

TechniqueHow It WorksBest ForEffort Level
FlashcardsQuestion → attempt recall → checkFacts, definitions, formulasLow-Medium
Practice problemsSolve without looking at solutionApplication, proceduresMedium
Free recallClose book, write everything you knowComprehensive reviewMedium-High
InterleavingMix topics in practice (don't block)Discrimination, transferMedium
Elaborative interrogationAsk "why?" and "how?" for each factDeep understandingMedium
Self-testingCreate and take your own quizzesAll types of knowledgeMedium
Teaching othersExplain concept to someone elseDeep mastery verificationHigh

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

LevelEvidence RequiredAssessment Method
AwarenessCan define term and recognize it in contextMultiple choice, matching
UnderstandingCan explain concept in own words with examplesShort answer, Feynman test
ApplicationCan solve novel problems using the conceptPractice problems, case studies
MasteryCan teach others and combine with other conceptsTeaching 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

Relacionados por tarefa

do mesmo repositório

Mais Skills

Todos os Skills
travisjneuman
Comunidade

tech-debt-analyzer

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.

instalações
1
GitHub Stars
105
Atualizado
19 de out.
travisjneuman
Comunidade

agent-desktop-developer

Specialist subagent: Expert desktop application developer for Electron, Tauri, and native desktop development

instalações
1
GitHub Stars
105
Atualizado
19 de out.
travisjneuman
Comunidade

agent-technical-writer

Specialist subagent: Architecture Decision Records, API documentation, migration guides, runbooks, and technical documentation specialist. Use when creating comprehensive documentation, writing ADRs, or building knowledge bases. Trigger phrases: ADR, documentation, runbook, migration guide, technical writing, API docs, changelog, architecture decision, knowledge base, onboarding docs.

instalações
1
GitHub Stars
105
Atualizado
19 de out.
travisjneuman
Comunidade

agent-test-generator

Specialist subagent: Generates comprehensive test suites using TDD patterns. Use only when the user explicitly asks for tests, improved coverage, or test-first development.

instalações
1
GitHub Stars
105
Atualizado
19 de out.