version unknown

tutor

bevibing@bevibing⭐ 1.4k stars· last commit 8mo ago· 7 open issues

>

Choose how to use this skill

You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.

1. Native installer

This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.

Do not guess an installer command or replace an existing version without reviewing the diff.

2. Complete package recommended

Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.

No complete ProSkills package is published for this listing yet.

3. Prompt-only

Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.

Need only the instruction file?

Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.

No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.

7.3/10
Verified
Oct 12, 2026

// RATINGS

⭐GitHub Stars
⭐⭐⭐⭐⭐ 1.4k on GitHubGitHub ↗

Very popular

🟢ProSkills ScoreAI Verified
7.3/10
📍

Not yet listed on ClawHub or SkillsMP

// README

tutor-skill

License: MIT Claude Code Install with npx skills

Two Claude Code skills that turn any knowledge source into an Obsidian StudyVault and then quiz you on it — closing the loop from content to comprehension.

How It Works

  Documents / Code                    Obsidian                    Quiz Session
 ┌──────────────────┐           ┌──────────────────┐          ┌──────────────────┐
 │  PDF, MD, HTML,  │  /tutor   │   StudyVault/    │  /tutor  │  4 questions per  │
 │  EPUB, source    │──setup──▶ │   structured     │────────▶ │  round, graded,   │
 │  code projects   │           │   interlinked    │          │  concept tracking  │
 └──────────────────┘           │   notes + MOC    │          └────────┬─────────┘
                                └──────────────────┘                   │
                                         ▲                             │
                                         └─────── progress updates ────┘

Skills Overview

SkillCommandPurposeInputOutput
tutor-setup/tutor-setupGenerate a StudyVaultDocuments or source codeObsidian vault with notes, dashboards, practice questions
tutor/tutorInteractive quiz tutorAn existing StudyVaultQuiz sessions with concept-level progress tracking

Quick Start

One-line install (recommended)

npx skills add RoundTable02/tutor-skills

Requires npx skills — works with Claude Code, Cursor, Windsurf, and more.

Manual install

git clone https://github.com/RoundTable02/tutor-skills.git
cd tutor-skills
./install.sh

Step 1: Generate a StudyVault

cd ~/study-materials/          # or any source code project
claude
> /tutor-setup

Step 2: Start Quizzing

claude
> /tutor

tutor-setup

Transforms knowledge sources into a structured Obsidian StudyVault. Mode is auto-detected:

Marker FoundMode
package.json, pom.xml, build.gradle, Cargo.toml, go.mod, etc.Codebase Mode
No project markersDocument Mode

Document Mode

Turns PDFs, text files, web pages, and other sources into comprehensive study notes.

  • Auto-scans working directory for source files (PDF, TXT, MD, HTML, EPUB)
  • Extracts and analyzes content with verified source mapping
  • Generates concept notes with comparison tables, ASCII diagrams, and exam patterns
  • Creates practice questions with hidden answers (active recall via fold callouts)
  • Builds a dashboard with Map of Content (MOC), Quick Reference, and Exam Traps
  • Full interlinking with [[wiki-links]] across all notes

Phases

PhaseNameDescription
D1Source DiscoveryScan, extract, and verify source content mapping
D2Content AnalysisBuild topic hierarchy and dependency map
D3Tag StandardDefine English kebab-case tag registry
D4Vault StructureCreate numbered folders per topic
D5DashboardMOC, Quick Reference, Exam Traps
D6Concept NotesStructured notes with tables, diagrams, callouts
D7Practice QuestionsActive recall with fold callouts (8+ per topic)
D8InterlinkingCross-reference all notes with wiki-links
D9Self-ReviewVerify against quality checklist

Generated structure

StudyVault/
  00-Dashboard/          # MOC + Quick Reference + Exam Traps
  01-<Topic1>/           # Concept notes + practice questions
  02-<Topic2>/
  ...

Codebase Mode

Generates a new-developer onboarding vault from a source code project.

  • Auto-detects tech stack, architecture patterns, and module boundaries
  • Traces request flows and data flows end-to-end
  • Creates per-module notes with key files, public interfaces, and dependency maps
  • Generates onboarding exercises (code reading, configuration, debugging, extension)
  • Builds a dashboard with architecture overview, module map, API surface, and getting started guide

Phases

PhaseNameDescription
C1Project ExplorationScan files, detect tech stack, map layout
C2Architecture AnalysisIdentify patterns, trace flows, map modules
C3Tag StandardDefine #arch-*, #module-*, #pattern-* registry
C4Vault StructureCreate dashboard + per-module folders
C5DashboardMOC with module map, API surface, getting started
C6Module NotesPurpose, key files, interface, flow, dependencies
C7ExercisesCode reading, config, debugging, extension tasks
C8InterlinkingCross-link all modules and exercises
C9Self-ReviewVerify against quality checklist

Generated structure

StudyVault/
  00-Dashboard/          # MOC + Quick Reference + Getting Started
  01-Architecture/       # System overview, request flow, data flow
  02-<Module1>/          # Per-module notes
  03-<Module2>/
  ...
  NN-DevOps/             # Build, deploy, CI/CD
  NN+1-Exercises/        # Onboarding exercises

tutor

Interactive quiz tutor that tracks what you know and don't know at the concept level. Works with any StudyVault generated by tutor-setup.

Session Types

TypeWhen AvailableFocus
DiagnosticUnmeasured areas (⬜) existBroad assessment of new areas
Drill weak areasWeak areas (🟥/🟨) existTargeted practice on struggles
Choose a sectionAlwaysStudy any area on demand
Hard-mode reviewAll areas 🟩/🟦Challenge mastered material

Quiz Flow

  1. Detects your StudyVault and reads the learning dashboard
  2. Presents session options based on your current proficiency
  3. Delivers 4 questions per round (4 options each, zero hints)
  4. Grades answers and explains mistakes
  5. Updates concept files and dashboard automatically

Progress Tracking

Proficiency is tracked per area with emoji badges:

BadgeLevelRate
🟥Weak0–39%
🟨Fair40–69%
🟩Good70–89%
🟦Mastered90–100%
⬜UnmeasuredNo data

Concept-level tracking stores attempts, correct count, last tested date, and error notes for wrong answers — so drill sessions rephrase missed concepts in new contexts.


The Learning Cycle

           ┌────────────────────────────┐
           │   /tutor-setup             │
           │   Generate StudyVault      │
           └──────────┬─────────────────┘
                      │
                      ▼
           ┌────────────────────────────┐
           │   Read & review notes      │
           │   in Obsidian              │
           └──────────┬─────────────────┘
                      │
                      ▼
           ┌────────────────────────────┐
           │   /tutor                   │
           │   Take diagnostic quiz     │◀──────────┐
           └──────────┬─────────────────┘           │
                      │                              │
                      ▼                              │
           ┌────────────────────────────┐           │
           │   Review weak areas        │           │
           │   in Obsidian              │           │
           └──────────┬─────────────────┘           │
                      │                              │
                      ▼                              │
           ┌────────────────────────────┐           │
           │   /tutor                   │           │
           │   Drill weak concepts      │───────────┘
           └────────────────────────────┘

Requirements

  • [Claude Code CLI](h

// HOW IT'S BUILT

// FILES

3 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.

  • skills/tutor/SKILL.md5.6 KBaeec70d84334upstream ↗
    ---
    name: tutor
    description: >
      Interactive quiz tutor for Obsidian StudyVault learning. Use when the user wants to:
      (1) Take a diagnostic assessment of their knowledge,
      (2) Study or review specific sections/topics,
      (3) Drill weak areas identified in previous sessions,
      (4) Check their learning progress or dashboard,
      or says things like "quiz me", "test me", "let's study", "/tutor", "학습", "퀴즈", "평가".
    ---
    
    # Tutor Skill
    
    Quiz-based tutor that tracks what the user knows and doesn't know at the **concept level**. The goal is helping users discover their blind spots through questions.
    
    ## File Structure
    
    ```
    StudyVault/
    ├── *dashboard*              ← Compact overview: proficiency table + stats
    └── concepts/
        ├── {area-name}.md       ← Per-area concept tracking (attempts, status, error notes)
        └── ...
    ```
    
    - **Dashboard**: Only aggregated numbers. Links to concept files. Stays small forever.
    - **Concept files**: One per area. Tracks each concept with attempts, correct count, date, status, and error notes. Grows proportionally to unique concepts tested (bounded).
    
    ## Workflow
    
    ### Phase 0: Detect Language
    
    Detect user's language from their message → `{LANG}`. All output and file content in `{LANG}`.
    
    ### Phase 1: Discover Vault
    
    1. Glob `**/StudyVault/` in project
    2. List section directories
    3. Glob `**/StudyVault/*dashboard*` to find dashboard
    4. If found, read it. Preserve existing file path regardless of language.
    5. If not found, create from template (see Dashboard Template below)
    
    If no StudyVault exists, inform user and stop.
    
    ### Phase 2: Ask Session Type
    
    **MANDATORY**: Use AskUserQuestion to let the user choose what to do. Analyze the dashboard to build context-aware options, then present them.
    
    Read the dashboard proficiency table and build options based on current state:
    
    1. If unmeasured areas (⬜) exist → include "Diagnostic" option targeting those areas
    2. If weak areas (🟥/🟨) exist → include "Drill weak areas" option naming the weakest area(s)
    3. Always include "Choose a section" option so the user can pick any area
    4. If all areas are 🟩/🟦 → include "Hard-mode review" option
    
    Present these as an AskUserQuestion with header "Session" and concise descriptions showing which areas each option targets. The user MUST select before proceeding.
    
    ### Phase 3: Build Questions
    
    1. Read markdown files in target section(s)
    2. If drilling weak area: also read `concepts/{area}.md` to find 🔴 unresolved concepts — rephrase these in new contexts (don't repeat the same question)
    3. Craft exactly 4 questions following `references/quiz-rules.md`
    
    **CRITICAL**: Read `references/quiz-rules.md` before crafting ANY question. Zero hints allowed.
    
    ### Phase 4: Present Quiz
    
    Use AskUserQuestion:
    - 4 questions, 4 options each, single-select
    - Header: "Q1. Topic" (max 12 chars)
    - Descriptions: neutral, no hints
    
    ### Phase 5: Grade & Explain
    
    1. Show results table (question / correct answer / user answer / result)
    2. Wrong answers: concise explanation
    3. Map each question to its area
    
    ### Phase 6: Update Files
    
    #### 1. Update concept file (`concepts/{area}.md`)
    
    For each question answered:
    - **New concept**: Add row to table + if wrong, add error note under `### 오답 메모` (or localized equivalent)
    - **Existing 🔴 concept answered correctly**: Increment attempts & correct, change status to 🟢, keep error note (learning history)
    - **Existing 🟢 concept answered wrong again**: Increment attempts, change status back to 🔴, update error note
    
    Table format:
    ```markdown
    | Concept | Attempts | Correct | Last Tested | Status |
    |---------|----------|---------|-------------|--------|
    | concept name | 2 | 1 | 2026-02-24 | 🔴 |
    ```
    
    Error notes format (only for wrong answers):
    ```markdown
    ### Error Notes
    
    **concept name**
    - Confusion: what the user mixed up
    - Key point: the correct understanding
    ```
    
    #### 2. Update dashboard
    
    - Recalculate per-area stats from concept files (sum attempts/correct across all concepts in that area)
    - Update proficiency badges: 🟥 0-39% · 🟨 40-69% · 🟩 70-89% · 🟦 90-100% · ⬜ no data
    - Update stats: total questions, cumulative rate, unresolved/resolved counts, weakest/strongest
    
    Dashboard stays compact — no session logs, no per-question details.
    
    ## Dashboard Template
    
    Create when no dashboard exists. Filename localized to `{LANG}`. Example in English:
    
    ```markdown
    # Learning Dashboard
    
    > Concept-based metacognition tracking. See linked files for details.
    
    ---
    
    ## Proficiency by Area
    
    | Area | Correct | Wrong | Rate | Level | Details |
    |------|---------|-------|------|-------|---------|
    (one row per section, last column = [[concepts/{area}]] link)
    | **Total** | **0** | **0** | **-** | ⬜ Unmeasured | |
    
    > 🟥 Weak (0-39%) · 🟨 Fair (40-69%) · 🟩 Good (70-89%) · 🟦 Mastered (90-100%) · ⬜ Unmeasured
    
    ---
    
    ## Stats
    
    - **Total Questions**: 0
    - **Cumulative Rate**: -
    - **Unresolved Concepts**: 0
    - **Resolved Concepts**: 0
    - **Weakest Area**: -
    - **Strongest Area**: -
    ```
    
    ## Concept File Template
    
    Create per area when first question is asked. Example:
    
    ```markdown
    # {Area Name} — Concept Tracker
    
    | Concept | Attempts | Correct | Last Tested | Status |
    |---------|----------|---------|-------------|--------|
    
    ### Error Notes
    
    (added as concepts are missed)
    ```
    
    ## Important Reminders
    
    - ALWAYS read `references/quiz-rules.md` before creating questions
    - NEVER include hints in option labels or descriptions
    - NEVER use "(Recommended)" on any option
    - Randomize correct answer position
    - After grading, ALWAYS update both concept file AND dashboard
    - Communicate in user's language
    
  • skills/tutor/references/quiz-rules.md2.1 KB2ef7240c3392upstream ↗
    # Quiz Design Rules
    
    ## Zero-Hint Policy (CRITICAL)
    
    Every question must be answerable ONLY by someone who actually knows the material.
    
    1. **Option descriptions**: NEVER reveal correctness
       - BAD: `label: "stderr"`, `description: "Error output stream used by Cloud Run for error classification"`
       - GOOD: `label: "stderr"`, `description: "Standard error stream"`
    
    2. **No "(Recommended)" tag** on any option
    
    3. **Randomize** correct answer position — never always first or last
    
    4. **Question phrasing**: Ask about behavior/purpose/output, don't hint at the answer
       - BAD: "Which error stream does error() use?"
       - GOOD: "Where does error() method output go?"
    
    5. **Plausible distractors**: Wrong options must be real concepts from the domain, representing common misconceptions
    
    ## Question Types
    
    1. **Factual recall**: "What HTTP status code is returned when...?"
    2. **Conceptual understanding**: "Why does the system use X pattern?"
    3. **Behavioral prediction**: "What happens when X fails?"
    4. **Comparison/distinction**: "What is the difference between X and Y?"
    5. **Debugging scenario**: "Given this error, what is the most likely cause?"
    
    ## Difficulty Balancing
    
    - Diagnostic: easy 40%, medium 40%, hard 20%
    - Weak-area drill: medium 30%, hard 70%
    - Review: all levels evenly
    
    ## Drilling Unresolved Concepts
    
    When targeting 🔴 concepts from concept files:
    - Do NOT repeat the exact same question — rephrase in a new context
    - Test the same underlying knowledge from a different angle
    - E.g., if user confused "400 vs 422", ask a scenario question where they must choose the correct status code for a new situation
    
    ## AskUserQuestion Format
    
    - 4 questions per round, 4 options each, single-select
    - Header: max 12 chars, "Q1. Topic"
    
    ## File Update Protocol
    
    After grading:
    1. Update `concepts/{area}.md` — add/update concept rows + error notes
    2. Update dashboard — recalculate area stats from concept files
    3. Badges: 🟥 0-39% · 🟨 40-69% · 🟩 70-89% · 🟦 90-100% · ⬜ no data
    
    ## Language Rule
    
    All file content and output in the user's detected language. Badge emojis are universal.
    
  • README.mdupstream ↗

    Contents are not inlined in the catalog. Open the upstream file.

Plain-text copy, no login: /skill-bundles/bevibing-tutor-skills-skills-tutor.md

// REPO STATS

1.4k stars
7 open issues
Last commit: 8mo ago