agentleFS
Edzard9Edzard9/stash/skills/study/study-notes/SKILL.md

study-notes

Skill0 starsChanged 8 days agoMITView on GitHub

Turn lecture material (slides, PDFs, module text) into compact study notes plus question=answer flashcards, one pair per line, ready to paste into a quiz tool. Use when the user wants material summarized for studying, flashcards made, or says "buatkan catatan", "ringkas materi", "flashcard", "buatkan soal latihan", "summarize these slides". Do NOT use to do the assignment itself or to summarize material the user has not provided.

4 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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Keep the lecturer's terms and definitions.

    line 22
  2. Distinctive:

    Ask the way an exam asks: definitions, contrasts ("what is the difference between X and Y"), consequences ("what happens when"), and …

    line 43

≈ “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

Study Notes

Reading slides twice is not studying. This skill converts lecture material into the two artifacts studying actually uses: a compact note that fits the topic on a page or two, and a deck of flashcards that asks the questions the exam will ask, in a format any quiz tool can import.

Input discipline

  • Work only from the material provided: the slides, PDF, module, or pasted text from this session. If a concept is missing from the material, it stays missing; do not complete the topic from general knowledge and present it as the lecturer's material. Additions the user asks for are labeled as additions.
  • Keep the lecturer's terms and definitions. When the material defines something its own way, the note uses that definition, even if textbooks phrase it differently. Exams grade the course's version.

The notes

  • One short section per topic, in the material's order.
  • Each section: the definition in one line, the mechanism in two or three, and one concrete example or number from the material.
  • Tables where the material compares things; the comparison is usually the exam question.
  • Cut ruthlessly: slide furniture, repeated introductions, and examples that illustrate nothing new. A note longer than a fifth of the source is a summary failure.

The flashcards

  • Format: question=answer, exactly one pair per line, nothing else on the line, so the whole block pastes into a quiz tool as-is.
  • One fact per card. A card asking two things is two cards.
  • Ask the way an exam asks: definitions, contrasts ("what is the difference between X and Y"), consequences ("what happens when"), and numbers from the material. Avoid yes/no cards and cards whose question contains the answer.
  • 10-25 cards per topic is the useful range. More than that and the deck stops being reviewed.

Example lines:

Apa fungsi subinterface pada router-on-a-stick?=Membagi satu interface fisik menjadi interface logis per VLAN, masing-masing menjadi gateway VLAN-nya
Berapa hop tracert PC-A ke PC-B pada praktikum inter-VLAN?=2 hop: gateway VLAN asal, lalu PC tujuan

Deliverable

The notes as a document (Markdown or DOCX, as asked), and the flashcard block as plain text in the same delivery, ready to copy in one selection. State the source material used, in one line, so the user knows exactly what the notes cover and what they do not.

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.