agentleFS
TimCodes04TimCodes04/second-brain/.claude/skills/tutor/SKILL.md

tutor

Skill1 starsChanged 51 days agoMITView on GitHub

Socratic tutoring session grounded in the vault and source PDFs — probes what the user thinks first, gives graduated hints instead of answers, and captures insights back into notes and cards.

26 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use defuddle, obsidian-cli and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • HK-hubSkill

    defuddle

    Extract clean markdown content from web pages using Defuddle CLI, removing clutter and navigation to save tokens. Use instead of WebFetch when the user provides a URL to read or analyze, for online documentation, articles, blog posts, or any standard web page.

    Also in 4 projects that use this

  • jykimSkill

    obsidian-cli

    Interact with Obsidian using the official CLI to read, search, create, and manage notes, daily notes, tasks, properties, and more. Use when the user wants to query or manipulate vault content via the obsidian command.

    Also in 4 projects that use this

  • wangzhuofengSkill

    json-canvas

    Create and edit JSON Canvas files (.canvas) with nodes, edges, groups, and connections. Use when working with .canvas files, creating visual canvases, mind maps, flowcharts, or when the user mentions Canvas files in Obsidian.

    Also in 3 projects that use this

  • MicrosoftSkill

    excalidraw-diagram

    Create Excalidraw diagram JSON files that make visual arguments. Use when the user wants to visualize workflows, architectures, or concepts.

    Also in 3 projects that use this

  • wangzhuofengSkill

    obsidian-bases

    Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.

    Also in 3 projects that use this

  • VercelSkill

    agent-browser

    Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

    Also in 4 projects that use this

  • +1 more from wangzhuofeng

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Probe first: ask what the user currently thinks / how they'd start.

    line 17

“Common” is measured: kept by at least 6 in 10 of the 20 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/tutor [<topic, note, or question>]

Socratic Q&A. Read docs/pedagogy.md first. Vault: <vault>.

Grounding

Before answering anything: find the relevant vault notes (lesson/concept, via filename + grep) and, when they cite a source, read the cited pages of the PDF (sources/ note has the absolute path). Prefer the vault's + sources' treatment and notation over generic knowledge; if the vault contradicts the source or is wrong, say so explicitly and offer to fix the note.

Method — never just answer

  1. Probe first: ask what the user currently thinks / how they'd start. (Exception: a pure lookup question — answer directly with citation, done.)
  2. Graduated hints: guide with questions and minimal hints toward the insight; escalate hint strength only when stuck. Point to the specific concept note or source page at each step.
  3. Close the loop: end by asking the user to summarize the resolved understanding in their own words. Correct the summary if needed.
  4. Capture: offer to (a) append the insight to the relevant concept note's body (elaboration, with updated: bump) and (b) mint 1–2 cards on it via the /card procedure. Do it on a yes.

Tone: precise, warm, zero condescension. If the user's question reveals a misconception, name it explicitly — misconceptions get flagged and become card material.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.