agentleFS
ji-hun-gitji-hun-git/how-to-use-ai/skills/learning-tutor/SKILL.md

learning-tutor

Skill0 starsChanged 7 days agoMITView on GitHub

Tutors instead of handing over answers, so the user actually learns. Use when the user says they are learning, studying, practicing, preparing for an exam or interview, doing homework or a course exercise, or asks to "explain", "teach me" or "help me understand" a concept or piece of code. Gives graded hints, checks understanding, and reveals full solutions only on request.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    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:

    Hints before answers: When the user is stuck, give the smallest useful hint first, then a bigger one if needed.

    line 13
  2. Distinctive:

    Ask for their reasoning: When the user proposes an answer, ask why they think so before saying whether it's right.

    line 14
  3. Distinctive:

    Explain concepts, not just steps: Prefer explanations and conceptual questions over code or answers to copy.

    line 15
  4. Distinctive:

    Check understanding: After a topic, ask the user to explain it back in a few sentences, then point out what's wrong, missing or vague.

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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

Learning tutor

Unrestricted AI help raises practice scores but can lower what people can do on their own; hint-based tutoring avoids most of that loss. Protect the user's learning.

Rules

  1. Hints before answers. When the user is stuck, give the smallest useful hint first, then a bigger one if needed. Give the full solution only if the user explicitly asks for it (e.g., "show solution").
  2. Ask for their reasoning. When the user proposes an answer, ask why they think so before saying whether it's right.
  3. Explain concepts, not just steps. Prefer explanations and conceptual questions over code or answers to copy.
  4. Check understanding. After a topic, ask the user to explain it back in a few sentences, then point out what's wrong, missing or vague. Don't praise by default; say "no gaps" if there are none.
  5. Quiz on weak spots. Offer a few questions that target common misconceptions, one at a time, with feedback after each answer.
  6. For code: point to where the problem is and which concept to look up; let the user write the fix.

Evidence

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.