handwritten-exam-notes
Turn lecture slides (PDF/PPTX) and the student's exam tips into handwriting-style exam notes - spiral notebook on graph paper, highlighters, underlines, arrows, click-to-reveal fill-in-the-blank, small interactive tools - published as one HTML artifact plus a one-page-per-section PDF. Use when the user uploads slides and asks for exam notes, revision notes, a cheat sheet or "notes like the last ones".
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Badge for your README
Markdown
[](/listings/ian-chin--notes-skill)HTML
<a href="/listings/ian-chin--notes-skill"><img src="/api/listings/ian-chin--notes-skill/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
1. Copy this folder to your skills directory, keeping the folder name, for example `~/.claude/skills/handwritten-exam-notes/` (Claude Code), or zip it and upload it under Settings > Skills (claude.ai). 2. `SKILL.md` at the top level is what Claude reads. Everything else is loaded on demand.
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
SKILL.md · Manifest · 51 lines
- ---
- name: handwritten-exam-notes
- description: Turn lecture slides (PDF/PPTX) and the student's exam tips into handwriting-style exam notes - spiral notebook on graph paper, highlighters, underlines, arrows, click-to-reveal fill-in-the-blank, small interactive tools - published as one HTML artifact plus a one-page-per-section PDF. Use when the user uploads slides and asks for exam notes, revision notes, a cheat sheet or "notes like the last ones".
- ---
- # Handwritten exam notes
- Builds a notebook-style study page from the user's own slides, shaped by **their exam structure and tips**.
- Output: one self-contained HTML (published as an artifact) + a PDF with exactly one page per section.
- Everything the notes need is in this folder:
- | Path | Use |
- |---|---|
- | `assets/notes.css`, `assets/core.js`, `assets/defs.svg.html` | the design system (do not rewrite, build on it) |
- | `templates/starter/` | a working 4-page project that shows every component. Copy it to start |
- | `references/components.md` | copy-paste HTML for every component + when to use each |
- | `references/workflow.md` | the step-by-step method, exam-tip mapping, coverage check |
- | `references/lessons.md` | mistakes already made once. Read before building |
- | `scripts/build.py` | pages/*.html -> one index.html |
- | `scripts/check.py` | lint (duplicate nav, bad ids, unclosed tags, bare blanks) |
- | `scripts/export_pdf.py` | one PDF page per section, blanks revealed in red, optional PNG per page |
- | `examples/` | three finished sets (CCP, DSTR, CSLLT) to imitate for density and tone |
- ## Inputs to collect (ask only for what is missing)
- 1. The slides (PDF/PPTX). Read **all** of them, not a sample.
- 2. The exam structure and tips: sections, question counts, marks, "topics to focus", exam date.
- 3. Optional but valuable: past papers / mock exams. They routinely test things the slides never teach (see lessons).
- If the user gave tips, do not ask again. If they gave none, ask once for the exam structure, then proceed.
- ## Method (details in references/workflow.md)
- 1. **Extract** slide text per week/chapter (`pdftotext -layout`, or python-pptx). Keep slide numbers.
- 2. **Map** every exam tip / section to the slide content that answers it. Write the map down. Anything in a tip with no slide behind it is flagged, not invented.
- 3. **Plan pages**: one `<section class="page">` per topic (usually one per week or per tip), a cover with the exam-part -> pages table, and a night-before sheet last.
- 4. **Write pages** from `references/components.md`. Match the exam style: MCQ -> definitions + traps; fill-in-the-blank -> code with `.b[data-a]` blanks; theory -> tables, steps and "explain" cards; coding -> full programs the student can rewrite; calculation -> worked examples + a small tool.
- 5. **Verify facts**: run code you show (Java/Python/C), recompute every worked number, and check each slide example against the slide. Slide errors go in a red `.card.warn` on the cover, never silently "fixed".
- 6. **Build + lint**: `python3 scripts/build.py proj/` then `python3 scripts/check.py proj/index.html`.
- 7. **Look at it**: `python3 scripts/export_pdf.py proj/index.html out.pdf --png-dir shots/` and open the PNGs. Fix overlaps, clipped text, empty cells.
- 8. **Publish** the HTML with the artifact tool (`publish_files`, `index.html`), send the PDF, then give a short summary.
- ## Style rules
- - Mark semantics are fixed (state them on the cover): yellow = memorise, pink = exam trap, green = answer/result, blue = definition, red squiggle = key word, grey dashed `.mine` tag = content **not** on the slides.
- - Every claim traces to a slide or carries a `.mine` tag. Never present your own addition as lecturer content.
- - Star the likely-examined items (`★`, `★★`, `★★★`) using the user's tips as the ranking.
- - Add a "Study order if short on time" list on the cover and a "Close the notes and try these" list at the end.
- - Handwriting tone: short sentences, arrows for cause -> effect, no filler. Text fits on the page: if a section would exceed roughly 3500px, split it.
- - Tools (`.tool`) only for things the student can compute in the exam (scheduler, converter, tracer). Put their JS in `extra.js`, scoped by `if(!$('id'))return;`.
- ## Final reply
- Say what the notes cover and what they do not, list slide mistakes found, state which answers are your own reading (not an official key), link nothing twice (the artifact card carries the link), and name one next step. Keep the user's tone preferences.
README.md · README · 68 lines
- # notes-skill: handwritten exam notes from your slides
- A Claude skill that turns lecture slides and your exam tips into **spiral-notebook, graph-paper study notes**: highlighters, wavy underlines, hand-drawn arrows, sticky notes, click-to-reveal fill-in-the-blank, and small interactive tools. You get a published HTML page and a PDF with **one page per section**.
- 
- ## What you get
- - **HTML artifact**: one self-contained page, works on phone and laptop, with a tab bar for each topic.
- - **PDF**: one PDF page per section, exactly as tall as the content, blanks printed in red.
- - **Tailored to your exam**: the cover maps each exam part (MCQ, fill-in-the-blank, theory, coding) to the pages that cover it, with a "study order if you are short on time" list.
- - **Honest content**: anything not on the slides is tagged `my answer`, and slide mistakes are listed in a red box.
- | Components | Tools and slide mistakes |
- |---|---|
- |  |  |
- 
- Real sets made with it (full pages in `examples/`):
- | CCP (threads, Java) | DSTR (trees) |
- |---|---|
- |  |  |
- ## Install as a Claude skill
- 1. Copy this folder to your skills directory, keeping the folder name, for example `~/.claude/skills/handwritten-exam-notes/` (Claude Code), or zip it and upload it under Settings > Skills (claude.ai).
- 2. `SKILL.md` at the top level is what Claude reads. Everything else is loaded on demand.
- ## How to use it
- Give Claude the slides and your exam tips, and name the skill if it does not trigger on its own:
- > Use the handwritten-exam-notes skill. Here are my slides for CT074 (weeks 2 to 13). Exam: Section A 20 MCQ, Section B 10 fill in the blank, Section C theory + coding. Tips: deadlock, monitors, semaphores. Exam is 24 Nov.
- Claude will: extract the slides, map your tips to pages, write the notes, run the code it shows, lint, render every page to PNG and look at it, publish the artifact, and send the PDF.
- **Add your mock exams or past papers if you have them.** They often test things the slides never teach. For the CCP set, the slides had no `ReentrantLock`, `Semaphore` or `join()`, and the mocks asked for all three.
- Good follow-ups: "add a self-test with an answer key from the mocks", "make the code blocks shorter", "add a tool that steps through the trace".
- ## Build it yourself (no Claude needed)
- ```bash
- pip install playwright pypdf && playwright install chromium # once; npm is needed for the fonts
- cp -r templates/starter my-notes # edit meta.json and pages/*.html
- python3 scripts/build.py my-notes # -> my-notes/index.html
- python3 scripts/check.py my-notes/index.html # lint
- python3 scripts/export_pdf.py my-notes/index.html my-notes.pdf --png-dir shots/
- ```
- Add `--embed-fonts` to `build.py` for a fully offline HTML file.
- ## Project layout
- ```
- SKILL.md what Claude reads: method, inputs, style rules
- assets/ notes.css (design), core.js (tabs + blanks), defs.svg.html (arrows, wobble)
- templates/starter/ working 4-page project: cover, components page, tool page, night-before
- references/ components.md (copy-paste HTML), workflow.md, lessons.md
- scripts/ build.py, check.py, export_pdf.py, fonts.py
- examples/ three finished sets (CCP, DSTR, CSLLT)
- docs/screenshots/ the images above
- ```
- ## Mark legend
- `yellow` memorise, `pink` exam trap, `green` answer or result, `blue` definition, red squiggle = key word, grey dashed tag = not on the slides.
- ## Known limits
- - Slide text is read from the PDF/PPTX text layer. Scanned slides need a visual read and can contain mistakes.
- - Answers to mock questions are Claude's own reading unless your lecturer gave a key. The notes say so.
- - Fonts (Patrick Hand, Caveat Brush, Shadows Into Light Two, Courier Prime) come from Google Fonts for the HTML and are embedded for the PDF.
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.