SkillAtlasSkill 详情

tutor-setup

Two Claude Code skills that turn any knowledge source into an Obsidian StudyVault and then quiz...

审核状态:已审核Quality 72Security 70

复制安装命令

用 Codex 或 Claude 安装复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它先审查 Skill 页面再帮你安装。

复制前请先查看来源、License 和安全提示。

项目 README

来源文件:README.md

抓取于 2026年8月21日

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

Repository Structure

tutor-skill/
├── skills/
│   ├── tutor-setup/              # Vault generation skill
│   │   ├── SKILL.md
│   │   └── references/
│   │       ├── templates.md
│   │       ├── codebase-workflow.md
│   │       ├── quality-checklist.md
│   │       └── codebase-templates.md
│   └── tutor/                    # Interactive quiz skill
│       ├── SKILL.md
│       └── references/
│           └── quiz-rules.md
├── examples/
├── install.sh
├── uninstall.sh
├── README.md
└── LICENSE

Uninstall

./uninstall.sh

Or manually:

rm -rf ~/.claude/skills/tutor-setup
rm -rf ~/.claude/skills/tutor

License

MIT

其他

中风险

  • 来源需自行核对维护者身份。
  • 包含脚本或命令调用,安装前请复核。
  • 可能需要外部 token、网络权限或第三方服务。
  • 未检测到高风险命令。
  • 扫描发现:2 条。

Codex — Git Clone 安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 克隆仓库:git clone https://github.com/bevibing/tutor-skills.git
  3. 将 "skills/tutor-setup" 文件夹复制到 Codex 的 skills 目录中。
  4. 重启 Codex 让新的 skill 生效。

Codex — 手动复制安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 从源仓库下载 SKILL.md 及相关文件。
  3. 在 Codex 的 skills 目录中创建新文件夹。
  4. 将所有 skill 文件复制到新文件夹中。
  5. 重启 Codex 让新的 skill 生效。

Claude Code — Git Clone 安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 克隆仓库:git clone https://github.com/bevibing/tutor-skills.git
  3. 将 "skills/tutor-setup" 文件夹复制到 Claude Code 的 skills 目录中。
  4. 重启 Claude Code 让新的 skill 生效。

Claude Code — 手动复制安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 从源仓库下载 SKILL.md 及相关文件。
  3. 在 Claude Code 的 skills 目录中创建新文件夹。
  4. 将所有 skill 文件复制到新文件夹中。
  5. 重启 Claude Code 让新的 skill 生效。

Cursor — Git Clone 安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 克隆仓库:git clone https://github.com/bevibing/tutor-skills.git
  3. 将 "skills/tutor-setup" 文件夹复制到 Cursor 的 skills 目录中。
  4. 重启 Cursor 让新的 skill 生效。

Cursor — 手动复制安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 从源仓库下载 SKILL.md 及相关文件。
  3. 在 Cursor 的 skills 目录中创建新文件夹。
  4. 将所有 skill 文件复制到新文件夹中。
  5. 重启 Cursor 让新的 skill 生效。

GitHub Copilot — Git Clone 安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 克隆仓库:git clone https://github.com/bevibing/tutor-skills.git
  3. 将 "skills/tutor-setup" 文件夹复制到 GitHub Copilot 的 skills 目录中。
  4. 重启 GitHub Copilot 让新的 skill 生效。

GitHub Copilot — 手动复制安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 从源仓库下载 SKILL.md 及相关文件。
  3. 在 GitHub Copilot 的 skills 目录中创建新文件夹。
  4. 将所有 skill 文件复制到新文件夹中。
  5. 重启 GitHub Copilot 让新的 skill 生效。

Windsurf — Git Clone 安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 克隆仓库:git clone https://github.com/bevibing/tutor-skills.git
  3. 将 "skills/tutor-setup" 文件夹复制到 Windsurf 的 skills 目录中。
  4. 重启 Windsurf 让新的 skill 生效。

Windsurf — 手动复制安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 从源仓库下载 SKILL.md 及相关文件。
  3. 在 Windsurf 的 skills 目录中创建新文件夹。
  4. 将所有 skill 文件复制到新文件夹中。
  5. 重启 Windsurf 让新的 skill 生效。
查看 SKILL.md 原文
name: tutor-setup
description: >
  Transforms knowledge sources into an Obsidian StudyVault. Two modes:
  (1) Document Mode — PDF/text/web sources → study notes with practice questions.
  (2) Codebase Mode — source code project → onboarding vault for new developers.
  Mode is auto-detected based on project markers in CWD.
argument-hint: "[source-path-or-url]"
allowed-tools: Read, Write, Edit, Glob, Grep, Bash, WebFetch

Tutor Setup — Knowledge to Obsidian StudyVault

CWD Boundary Rule (ALL MODES)

NEVER access files outside the current working directory (CWD). All source scanning, reading, and vault output MUST stay within CWD and its subdirectories. If the user provides an external path, ask them to copy the files into CWD first.

Mode Detection

On invocation, detect mode automatically:

  1. Check for project markers in CWD:
    • package.json, pom.xml, build.gradle, Cargo.toml, go.mod, Makefile, *.sln, pyproject.toml, setup.py, Gemfile
  2. If any marker found → Codebase Mode
  3. If no marker found → Document Mode
  4. Tie-break: If .git/ is the sole indicator and no source code files (*.ts, *.py, *.java, *.go, *.rs, etc.) exist, default to Document Mode.
  5. Announce detected mode and ask user to confirm or override.

Document Mode

Transforms knowledge sources (PDF, text, web, epub) into study notes. Templates: templates.md

Phase D1: Source Discovery & Extraction

  1. Auto-scan CWD for **/*.pdf, **/*.txt, **/*.md, **/*.html, **/*.epub (exclude node_modules/, .git/, dist/, build/, StudyVault/). Present for user confirmation.
  2. Extract text (MANDATORY tools):
    • PDF → pdftotext CLI ONLY (run via Bash tool). NEVER use the Read tool directly on PDF files — it renders pages as images and wastes 10-50x more tokens. Convert to .txt first, then Read the .txt file.
      pdftotext "source.pdf" "/tmp/source.txt"
      
    • If pdftotext is not installed, install it first: brew install poppler (macOS) or apt-get install poppler-utils (Linux).
    • URL → WebFetch
    • Other formats (.md, .txt, .html) → Read directly.
  3. Read extracted .txt files — understand scope, structure, depth. Work exclusively from the converted text, never from the raw PDF.
  4. Source Content Mapping (MANDATORY for multi-file sources):
    • Read cover page + TOC + 3+ sample pages from middle/end for EVERY source file
    • NEVER assume content from filename — file numbering often ≠ chapter numbering
    • Build verified mapping: { source_file → actual_topics → page_ranges }
    • Flag non-academic files and missing sources
    • Present mapping to user for verification before proceeding

Phase D2: Content Analysis

  1. Identify topic hierarchy — sections, chapters, domain divisions.
  2. Separate concept content vs practice questions.
  3. Map dependencies between topics.
  4. Identify key patterns — comparisons, decision trees, formulas.
  5. Full topic checklist (MANDATORY) — every topic/subtopic listed. Drives all subsequent phases.

Equal Depth Rule: Even a briefly mentioned subtopic MUST get a full dedicated note supplemented with textbook-level knowledge.

  1. Classification completeness: When source enumerates categories ("3 types of X"), every member gets a dedicated note. Scan for: "types of", "N가지", "categories", "there are N".
  2. Source-to-note cross-verification (MANDATORY): Record which source file(s) and page range(s) cover each topic. Flag untraceable topics as "source not available".

Phase D3: Tag Standard

Define tag vocabulary before creating notes:

  • Format: English, lowercase, kebab-case (e.g., #data-hazard)
  • Hierarchy: top-level → domain → detail → technique → note-type
  • Registry: Only registered tags allowed. Detail tags co-attach parent domain tag.

Phase D4: Vault Structure

Create StudyVault/ with numbered folders per templates.md. Group 3-5 related concepts per file.

Phase D5: Dashboard Creation

Create 00-Dashboard/: MOC, Quick Reference, Exam Traps. See templates.md.

  • MOC: Topic Map + Practice Notes + Study Tools + Tag Index (with rules) + Weak Areas (with links) + Non-core Topic Policy
  • Quick Reference: every heading includes → [[Concept Note]] link; all key formulas
  • Exam Traps: per-topic trap points in fold callouts, linked to concept notes

Phase D6: Concept Notes

Per templates.md. Key rules:

  • YAML frontmatter: source_pdf, part, keywords (MANDATORY)
  • source_pdf MUST match verified Phase D1 mapping — never guess from filename
  • If unavailable: source_pdf: 원문 미보유
  • [[wiki-links]], callouts ([!tip], [!important], [!warning]), comparison tables > prose
  • ASCII diagrams for processes/flows/sequences
  • Simplification-with-exceptions: general statements must note edge cases

Phase D7: Practice Questions

Per templates.md. Key rules:

  • Every topic folder MUST have a practice file (8+ questions)
  • Active recall: answers use > [!answer]- 정답 보기 fold callout
  • Patterns use > [!hint]- / > [!summary]- fold callouts
  • Question type diversity: ≥60% recall, ≥20% application, ≥2 analysis per file
  • ## Related Concepts with [[wiki-links]]

Phase D8: Interlinking

  1. ## Related Notes on every concept note
  2. MOC links to every concept + practice note
  3. Cross-link concept ↔ practice; siblings reference each other
  4. Quick Reference sections → [[Concept Note]] links
  5. Weak Areas → relevant note + Exam Traps; Exam Traps → concept notes

Phase D9: Self-Review (MANDATORY)

Verify against quality-checklist.md Document Mode section. Fix and re-verify until all checks pass.


Codebase Mode

Generates a new-developer onboarding StudyVault from a source code project. Full workflow: codebase-workflow.md Templates: codebase-templates.md

Phase Summary

PhaseNameKey Action
C1Project ExplorationScan files, detect tech stack, read entry points, map directory layout
C2Architecture AnalysisIdentify patterns, trace request flow, map module boundaries and data flow
C3Tag StandardDefine #arch-*, #module-*, #pattern-*, #api-* tag registry
C4Vault StructureCreate StudyVault/ with Dashboard, Architecture, per-module, DevOps, Exercises folders
C5DashboardMOC (Module Map + API Surface + Getting Started + Onboarding Path) + Quick Reference
C6Module NotesPer-module notes: Purpose, Key Files, Public Interface, Internal Flow, Dependencies
C7Onboarding ExercisesCode reading, configuration, debugging, extension exercises (5+ per major module)
C8InterlinkingCross-link modules, architecture ↔ implementations, exercises ↔ modules
C9Self-ReviewVerify against quality-checklist.md Codebase Mode section

See codebase-workflow.md for detailed per-phase instructions.


Language

  • Match source material language (Korean → Korean notes, etc.)
  • Tags/keywords: ALWAYS English

发现问题?提交给管理员复核

评分:

评论 (0)

暂无评论,成为第一个评论者吧!