agentleFS
ozgureyilmazozgureyilmaz/skills/socratic-tutor/SKILL.md

socratic-tutor

Skill2 starsChanged 6 days agoNo licenceView on GitHub

Structured Socratic tutoring when the user explicitly asks to be taught, quizzed, or drilled to mastery on a topic: diagnostic placement, a skill map with levels 0-5, spaced review, and a final assessment. Trigger phrases: 'teach me', 'tutor me', 'quiz me', 'drill me', 'help me master'. Not for one-off 'explain X' or 'what is X' questions.

15 other projects use a version of this, 1 of them edited; 1 of 1 edited versions we compared changed its rules; 3 new projects in the last 4 weeks, against 0 the 4 before.

How people change it

1 of 1 edited versions changed its rules.

Of the 1 edited version we compared: 1 made changes of their own.

Rules people drop

  1. Run a short diagnostic: 3-5 probing questions spanning easy to hard, to place the user's starting level per subskill. Do not teach anything until the diagnostic is done.dropped by 1 of 1
  2. Use solid/light block characters (U+2588 / U+2591) for the bars when rendering.dropped by 1 of 1
  3. Ask ONE question at a time. End the message immediately after the question and wait for the answer; do not add hints, example answers, or teaching content after it.dropped by 1 of 1
  4. Prefer questions that make the user: predict an outcome, explain why, find the flaw in a plausible-but-wrong claim, apply an idea to a new case, or connect two ideas.dropped by 1 of 1
  5. When the user is wrong, do not give the answer. Ask a narrower question that exposes the contradiction in their reasoning. Only explain directly after 2-3 failed attempts, and then immediately re-test the same idea from a different angle.dropped by 1 of 1
  6. When the user is right, occasionally play devil's advocate ("are you sure? what about X?") — they should be able to defend correct answers under pressure.dropped by 1 of 1
  7. If the user fails a review, lower the level and revisit.dropped by 1 of 1

We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.

Adopted by

Surging: 3 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 1 new projectWeek of Nov 1: 0 new projectsWeek of Nov 8: 2 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 3 in all, so this is a hint, not a trend.

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 8

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 10 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.

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.