agentleFS
Sign inStart free
jurgendnjurgendn/agent-skills/skills/learning-and-metacognition/study-book/SKILL.md

study-book

Skill15 starsChanged 59 days agoNo licenceView on GitHub

Write a story-first study book (compiled to PDF with Typst) whose reader must explain and rebuild the material, not recite it. Three modes chosen at intake: exam revision from a transcript, syllabus or course list (oral exam, APS/DAAD or PhD/MSc admissions interview, qualifying exam); learning a new topic from a source list; or a deep dive into one framework, model or method. Every Part follows story, statement, small checked example, connection, with a spine diagram, concept graph, decision table, seven-stage story flow and questions. Use whenever the user says "make a study book / revision book / study guide", "summarise my courses for the interview", "prepare me for the APS interview from my transcript", "write me notes to really understand X", "a deep dive into how <framework/model> works", or wants a Part added to an existing book of this kind, even without mentioning Typst. Not live explanation in chat (professor-mentor-technical-teaching), not interactive guided mastery (flow-learn-new-topic, flow-deep-understanding: use those when the user wants to be taught or questioned rather than handed a written book), not an exercise set (concept-exercise-generator, which this skill hands off to), not mock interviews (apply-interview-prep), and not an Obsidian notes vault (init-workspace).

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 6 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    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 an estimate: at least 1 in 5 of the 350,495 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.

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.

Check your setup, free