tutor-setup
by RoundTable02tutor-setup transforms learning materials or a codebase into an Obsidian StudyVault. It auto-detects Document Mode or Codebase Mode, follows a strict CWD boundary, and helps you create structured study notes, practice questions, or a developer onboarding vault with less guesswork.
This skill scores 68/100, which means it is list-worthy for directory users, but it should be installed with moderate expectations. The repository provides a real, non-placeholder workflow for converting sources into an Obsidian StudyVault, with automatic mode detection that helps agents trigger it without much guesswork. However, the listing decision should note that the repository lacks supporting files and install guidance, so users will need to infer some usage details from the SKILL.md itself.
- Clear two-mode workflow: Document Mode for PDFs/text/web sources and Codebase Mode for source code onboarding vaults.
- Auto-detection logic and CWD boundary rule give agents a concrete trigger path and execution constraints.
- Substantial SKILL.md content with headings and phase structure, including repo/file references and code examples, supports operational use.
- No support files, references, or resources are included, so users have limited auxiliary guidance beyond SKILL.md.
- No install command or quick-start example is provided, which may slow adoption for first-time users.
Overview of tutor-setup skill
What tutor-setup does
tutor-setup turns either learning materials or a codebase into an Obsidian StudyVault. It is designed for people who want a structured study workspace, not just a raw summary: the skill can build notes, extract source material, and add practice-oriented organization.
Who it fits best
Use the tutor-setup skill if you need a repeatable way to turn PDFs, web pages, text files, or a source repository into a usable vault for study or onboarding. It is especially relevant for self-learners, instructors, and teams that want a lightweight knowledge base instead of a one-off answer.
Why it is different
The main value is mode-aware setup. tutor-setup auto-detects whether the current folder is a document source or a code project, then adjusts its workflow. That makes tutor-setup for Skill Scaffolding useful when you want one skill to handle two common input types without manually rewriting the process each time.
How to Use tutor-setup skill
Install and place the files correctly
Run the install command from your skill environment, then work inside the current working directory because tutor-setup enforces a strict CWD boundary. The tutor-setup install flow depends on source files being copied into the working folder first; it will not reach outside that boundary to fetch them.
Give it the right kind of input
The tutor-setup usage pattern is simple: provide a local source path or URL, then let the skill determine the mode. For best results, make your request explicit about the outcome you want, for example: “Create an Obsidian StudyVault from these lecture notes with chapter summaries and practice questions,” or “Build an onboarding vault from this repo for a new developer.”
Read these files first
Start with SKILL.md, because it defines the mode detection rules, CWD boundary, and the two workflows. If your copy includes them, inspect references/templates.md and any supporting notes linked from the skill so you understand the expected vault structure before prompting for output. In a repository context, also scan README.md, AGENTS.md, and any rules/, resources/, references/, or scripts/ folders if present.
Prompting tips that change output quality
State the source type, target audience, and depth up front. A weak prompt like “use tutor-setup on this folder” leaves too much to guess; a stronger prompt says what the vault should optimize for, such as exam prep, onboarding, or quick review. If you are using tutor-setup for Skill Scaffolding, include the desired output shape, note granularity, and any constraints on terminology, tone, or file naming.
tutor-setup skill FAQ
Is tutor-setup better than a normal prompt?
Yes, when you want a repeatable workflow with clearer boundaries and mode selection. A normal prompt can summarize content, but tutor-setup adds a more explicit process for document discovery, source handling, and vault creation.
When should I not use tutor-setup?
Do not use it if your source files are outside the current working directory and you cannot copy them in first. It is also a poor fit if you only want a short answer, because the skill is meant to produce a structured StudyVault rather than a quick explanation.
Is tutor-setup beginner-friendly?
Yes, if you can point it at a folder and describe the desired study outcome. The main beginner risk is vague input; the skill works best when you specify whether you want study notes, practice questions, or a developer onboarding vault.
Does tutor-setup work for both docs and code?
Yes. That is one of its core strengths: tutor-setup automatically detects Document Mode or Codebase Mode from the contents of CWD. If the folder is ambiguous, confirm the mode in your prompt so the workflow stays aligned with your intent.
How to Improve tutor-setup skill
Give it cleaner source material
The strongest tutor-setup outputs come from well-scoped inputs: a single folder, a clear source set, and files that are easy to classify. If the material is messy, mixed, or duplicated, the vault will usually inherit that confusion.
Specify the end use, not just the source
Tell tutor-setup what the vault is for: exam revision, concept retention, team onboarding, or project ramp-up. That choice affects what gets emphasized in the notes, which sections deserve more detail, and how practice questions should be framed.
Review the first vault for mode mistakes
The most common failure mode is incorrect mode selection or overly generic structuring. If the first pass feels off, tighten the prompt by naming the source type, confirming the mode, and pointing to the most important folders or documents before asking for a revision.
Iterate with targeted constraints
For better tutor-setup usage, ask for specific revisions instead of rerunning everything. For example: “reduce note depth,” “add more practice questions,” “focus on onboarding terminology,” or “split dense topics into smaller study notes.” This keeps the output aligned without losing the structure the skill already created.