$ show bevibing/tutor-skills
This repository is a content-based Claude Code skill package rather than a conventional software service. It contains two agent skills — /tutor-setup and /tutor — that an LLM coding assistant executes using filesystem and WebFetch tools. tutor-setup scans a working directory, auto-detects whether it contains source code or documents, and generates an Obsidian StudyVault: concept notes, dashboards, exam-traps, and practice questions, with strict rules for source traceability, tag registries, wiki-linking, and folder conventions. tutor-setup operates through detailed phase models (D1-D9 for documents, C1-C9 for codebases), and codebase mode produces architecture maps, module notes, API surfaces, and onboarding exercises. tutor then reads that vault and runs interactive 4-question quiz rounds, updating concept-level progress files and a compact dashboard; it supports diagnostic, weak-area drill, section review, and hard-mode sessions, all governed by a zero-hint quiz design rule in references/quiz-rules.md. The implementation is almost entirely Markdown instructions plus two small Bash install/uninstall scripts; there is no compiled code, test suite, CI pipeline, or dependency manifest. The operational logic is prompt/instruction engineering that Claude Code interprets. External dependencies are Claude Code (or a compatible npx-skills-aware assistant), Obsidian for reviewing generated vaults, pdftotext/poppler for PDF extraction, and the assistant's built-in Read, Write, Edit, Glob, Grep, Bash, WebFetch, and AskUserQuestion tools. The data flow is unidirectional: source files in the CWD are scanned and extracted, transformed into StudyVault markdown, then quiz answers update concept files and dashboard aggregate stats. The skill enforces a CWD boundary to avoid accessing files outside the working directory. The strong point is unusually detailed and internally consistent procedural specification: mandatory source-content verification, per-topic coverage rules, tag registries, active-recall fold callouts, interlinking requirements, and self-review quality checklists. Weaknesses are the absence of automated tests/CI and versioned dependency pins, and behavior ultimately depends on the host LLM following prompt rules correctly. The README also references a different GitHub owner (RoundTable02) than the repository path (bevibing/tutor-skills), indicating a fork or repackage whose provenance should be verified before use. Overall, it fulfills its stated purpose well, and several Markdown modules are genuinely reusable as templates for other agent skills, study-vault generators, or adaptive quiz systems.
The LLM identified 4 files worth highlighting for reuse:
Defines a complete context-aware vault-generation process: mode auto-detection, nine-phase execution, mandated tool choices (pdftotext only for PDFs), a CWD security boundary, verified source-mapping, and mandatory self-review gates. It is self-contained and could be extracted as a template for any deterministic document-to-structured-knowledge agent skill.
Implements a self-correcting quiz loop that persists concept-level proficiency (attempts, correct count, last tested date, unresolved error notes) and derives next-session options from dashboard state. The dashboard/concept-file split is an isolated, reusable architecture for any adaptive practice system running in a tool-calling assistant.
A compact, transferable set of constraints for generating fair multiple-choice questions with LLMs: no implicit hints, plausible distractors, randomized correct-answer positions, difficulty balancing, and rephrasing missed concepts in new contexts. It could be extracted into any quiz or assessment product independent of Claude Code.
A mode-specific verification checklist covering source traceability, coverage completeness, tag discipline, wiki-linking, and question-type diversity. It demonstrates an operational pattern for enforcing quality in generative markdown workflows and is reusable as a generic acceptance rubric for knowledge-generation tasks.