ExamPass-Assistant's quick start installs packages and stops, because the entry point is a slash command
Turns classroom handouts into exam-ready tools: converts PPT, Word and PDF course materials into structured knowledge summaries and interactive quizzes to make review more efficient. For college students, teachers at any level, and anyone cramming for short-term exams.
At a glance
- What is it?
- ExamPass-Assistant turns lecture PPT, Word and PDF files into notes and self-grading quizzes through five sub-agents running inside a coding agent session. Its dependency list contains no model client, its four commands are chat input rather than shell input, and v2.0 folded two of them away.
- Who is it for?
- ExamPass-Assistant fits a student or teacher who already works inside a coding agent and wants a printable study file rather than a hosted study app. Three things to check before relying on it.
- Can I use it commercially?
- Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
- Is it still maintained?
- Yes. The repository last received commits 139 days ago.
- What is it written in?
- Mainly Python, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- WUBING2023/ExamPass-Assistant808 ★ · +38
| Repository | 2026-09-21 | 2026-11-15 |
|---|---|---|
| WUBING2023/ExamPass-Assistant | 770 | 808 |
38 Stars in the last 55 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The quick start installs dependencies and stops, because the entry point is a slash command
The quick start is three commands, and they get you as far as a working checkout and no further:
git clone https://github.com/WUBING2023/ExamPass-Assistant.git
cd ExamPass-Assistant
pip install -r requirements.txtThere is no step after that, and no console script in the tree to run. The entry point is `SKILL.md`, described in the project structure as the /exampass entry point for command routing, and the four commands are slash commands typed into a coding agent session rather than things you type in a shell. So after the clone you open a session and give it `/exampass <dir>`.
That is a sensible design for a tool whose whole job is orchestration, but it leaves the quick start and the commands table answering two different questions. The first is about Python packages, the second is about chat input, and nothing on the page joins them. Nothing documented gives you a shell command to drive it either, since the first phase of the pipeline is `run_exampass.py` run by the agent rather than invoked by you.
requirements.txt has no model client, because Claude arrives through the agent session
The dependency list is eight lines, and not one of them is a model SDK:
python-pptx
python-docx
pdfplumber
pymupdf
pytest
pytest-mock
Pillow
reportlabThat fits how the pipeline is described. Course material is read with Claude, key concepts are extracted with logical narratives, and the sub-agents produce the content from cards in `agents/`. The model is the host agent session, not a library the project imports, which is also why nothing on the page mentions an API key.
What the eight entries buy is document handling, and PDF twice over: `python-pptx` for the slides, `python-docx` for Word handouts, `pdfplumber` and `pymupdf` as two separate PDF libraries, `Pillow` for images and `reportlab` for writing output files. The last two are test tooling, `pytest` and `pytest-mock`, sitting in the runtime requirements file rather than in a dev extras group, next to a `tests/` directory in the tree.
The supported input formats are PPTX, DOCX and PDF, and image recognition is described as coming from multimodal analysis rather than from a separate OCR package, which is consistent with there being no OCR dependency in the list.
Five agents, named artifacts, and an orchestrator that only schedules
The default pipeline is a table of five phases, and it names the file each one leaves behind:
| Phase | Agent | Output |
|-------|-------|--------|
| 0. Extract | `run_exampass.py` | per-chapter `_extraction_bundle.json` + `chapter_manifest.json` |
| 1. Skeleton | `skeleton-agent` | `knowledge_skeleton.json` (chapter → KC DAG) + per-chapter slices |
| 2. Create | `notes-agent` + `item-agent` (parallel per chapter) | `notes/chN.html` + `questions/chN.json` |
| 3. Review/Revise | `reviewer-agent` + `solver-agent` (streaming per chapter) | diagnostics → targeted revision |
| 4. Render | `template_engine` | combined page (notes + quiz) per chapter |The table is also the only place the parallelism shows. Notes and questions are produced in parallel per chapter, and review and revision stream per chapter rather than waiting for the whole set. Two claims attach to that third phase: streaming replaced waiting for every chapter, and unchanged chapters are skipped from cache.
The division of labour is stated plainly. The orchestrator, described as the main Claude instance, only schedules, and the content is produced by sub-agents working from the cards. Every intermediate artifact lands in `.epa_work/`, which is also where the render path writes slide images. So one scratch directory holds the extraction bundles, the skeleton, the notes, the questions and the rendered pages, and the finished output is whatever `template_engine` writes outside it. The cards carry the methodology: skeleton builds the chapter to knowledge concept DAG, notes follows the Hook to TL;DR to Why to What to How to self-check arc, item writes subject-aware questions, reviewer checks correctness and completeness, solver does two-pass verification.
The slide rail went from an opt-in flag to on by default, with the pages embedded as base64
The headline v2.0 feature is the original-PPT cross-reference rail, and the page is explicit that it was previously an opt-in flag and is now on by default. The mechanism sits in `slide_renderer.py`: it renders whole PDF pages with `get_pixmap` and pins them beside each note, together with their original text in a collapsible block. Headings automatically get a `[页N]` chip, and clicking it scrolls the rail to the matching slide. Density is selectable between `full`, `key` and `none`, which is the only way to turn the volume back down.
The reason for embedding rather than linking is given as keeping the HTML a single shareable file, so the images are base64. That is what makes a note page portable: one file you can mail, print or drop on a drive, with the source slides inside it. The same reasoning produced the combined page in the same release, where `save_combined_html` puts the knowledge list and the interactive quiz into one file behind top tabs.
The cost falls out of the same choice. A chapter's notes now carry the rendered pages of the slides behind them at the selected density, so a full-density chapter is a large file, and the Ctrl+P output contains those pages as well. The other new feature in the same area is self-test answers: every in-note checkpoint now carries a collapsible reference answer, an ask-then-reveal pattern rather than a question left open.
v2.0 folded two commands away while adding features
Two of the four commands are not what they were a release ago, and the page says so directly: `fast` is gone because the default is already fast, and `mock` folded into `final --ref`. What is left is `/exampass <dir>` for the default per-chapter pipeline, `/exampass graph <dir>` for the knowledge graph, `/exampass final <dir>` with optional `--ref <past exam>` and `--chapter <ch>`, and `/exampass update` to pull the latest features, fixes and dependencies from GitHub.
The exam generator carries the design decision worth noticing. It picks question types by analysing the course rather than from a fixed template, with nine types including calculation and code chosen automatically by subject, and `--ref` makes it analyse a past paper's style and write brand-new questions in the same shape. Scoring is described as blueprint scoring that lands on exactly 100 points.
For anyone with an existing habit or script, this is the sharp edge in the release. Nothing aliases the old names, so `fast` and `mock` stop working on upgrade, and because `/exampass update` is the documented way to move, the version described in the documentation is not necessarily the version running in a session that was set up earlier.
The output is one HTML file with MathJax, and Ctrl+P is the export path
The delivery format is worth separating from the content, because it is what makes the result shareable. Everything opens in any browser, prints to PDF with Ctrl+P, renders formulas with MathJax, and is responsive down to mobile. The knowledge guides carry MathJax formulas, dual colour highlighting with key points in bold black and explanations in lighter gray, priority tags across must-know, key, frequent and info, an automatic table of contents, and collapsible self-test answers.
None of that needs a server, which is the point. A student can be handed a file. The knowledge graph is the same idea with more interaction: an interactive left-root, right-leaf tree with dependency edges, hub concept stars, hover tooltips, persistent inline note cards that take text and pasted images, a draggable column split, search and zoom. A graph fallback that does not go through an agent is described as existing so that Codex users get a real graph rather than cards.
The single-file constraint shows up in the programmatic surface. `save_knowledge_html` is handed an HTML body and the engine adds the H1 and the table of contents, `save_combined_html` is the two-tab variant, and `build_chapter_slides` is the entry that renders the PDF pages for the rail. That is four exported functions, and the listing on the page stops partway through the slide call rather than at the end of the signature.
The structure tree calls the root EPA, and the licence field is unasserted
The project structure block names its root `EPA/` while the repository is called ExamPass-Assistant, a small drift between the documentation and the clone URL. The cards inside it are named for their job, and the listing stops partway through the `scripts/` directory. The repository root also carries four loose Markdown files, `exampass-final.md`, `exampass-graph.md`, `exampass-writing.md` and `prompt-exampass.md`, alongside `docs/`, `templates/`, `tests/` and a Chinese `README_CN.md` linked from the English page.
Two pieces of metadata are worth reading before you build on this. The last commit is dated 2026-06-29 and the repository has no published releases, so the v2.0 heading at the top of the page is the only version marker there is; there is no tag to pin and no changelog outside the page itself. And the licence field recorded for the repository is unasserted while a `LICENSE` file sits at the root, with nothing on the page saying which of the two applies.
The audience is stated in the repository description rather than in the page body: university students, teachers at various stages, and anyone else facing a short-term exam. The formats and the pipeline match that: a per-chapter combined page for reading, a quiz for self-grading, and a full mock built to 100 points for the run-up.
Editorial conclusion
ExamPass-Assistant fits a student or teacher who already works inside a coding agent and wants a printable study file rather than a hosted study app. Three things to check before relying on it. The tool is not standalone: there is no console script, the entry point is a slash command, and nothing on the page gives you a terminal workflow, so it is not a candidate for an unattended run. Command names are not stable, since v2.0 removed `fast` and folded `mock` into `final --ref` with no alias, and `/exampass update` is how you move between versions. And v2.0 turned the slide cross-reference rail on by default with pages base64-embedded, so per-chapter files are now much larger than they were; set the density to `key` or `none` if that matters. The last commit is 2026-06-29 and there are no published releases, and the licence field is unasserted next to a LICENSE file at the root.
Frequently asked questions
How do I run ExamPass-Assistant after cloning the repository?
The quick start is `git clone`, `cd ExamPass-Assistant` and `pip install -r requirements.txt`, and it ends there. There is no console script: the entry point is `SKILL.md` and the commands are slash commands, so you open a coding agent session and use `/exampass <dir>`, `/exampass graph <dir>`, `/exampass final <dir>` or `/exampass update`.
Does ExamPass-Assistant need an API key or a model SDK installed?
No model SDK appears in `requirements.txt`, which lists python-pptx, python-docx, pdfplumber, pymupdf, pytest, pytest-mock, Pillow and reportlab. The model is the host agent session itself, since the material is read with Claude and the sub-agents produce content from the cards in `agents/`.
What does `/exampass final --ref` do in ExamPass-Assistant?
It makes the exam generator analyse a real past paper's style and write brand-new questions in the same shape. The generator otherwise picks question types by analysing the course rather than from a fixed template, with nine types including calculation and code chosen by subject, and scores on a blueprint that comes to exactly 100 points.
Which input formats does ExamPass-Assistant read, and how is the output shared?
PPTX, DOCX and PDF, with image recognition through multimodal analysis. Output is a single HTML file per chapter, or one combined page holding notes and quiz behind top tabs, with slide pages base64-embedded so the file stays shareable. It opens in any browser, renders formulas with MathJax, and prints to PDF with Ctrl+P.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/wubing2023-exampass-assistant)Star history chart for your README
[](https://hysenlabs.com/projects/wubing2023-exampass-assistant)Was this useful?