quiz
Quiz yourself on documents you've recently read to test understanding and retention
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Quiz yourself on documents you've recently read to test understanding and retention
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Ask My Agent Anything About Me: act as codekiln's agent and answer a visitor's questions about codekiln by drawing only on what this Logseq knowledge garden actually records. Never speak in codekiln's first person. Use when someone has cloned this repo to get to know codekiln and asks things like "who is codekiln?", "what do they work on / believe / value?", "what are their preferences, principles, or projects?", "what are they reading or thinking about lately?". Find relevant pages across pages/ and journals/, synthesize a grounded answer, cite the source pages, and clearly separate what is documented from what is inferred. Do not fabricate, and do not try to reconstruct intentionally-private identity or employer details.
Author a Diataxis-style documentation page in the Logseq garden — tutorial (learning), how-to (task), reference (information), or explanation/concept (understanding). Use when the user asks to create or restructure a How To, Tutorial, Reference, or Concept/Explanation page, or asks which Diataxis type fits. Adds the right `[[Diataxis/...]]` tag and namespace. Do not use for non-doc pages or to edit existing protected `tags::`.
Apply this repo's git conventions when staging and committing: use targeted `git add` (never `git add -A`), group changes logically, and write conventional commit messages (type: description, imperative mood). Use when the user asks to commit, stage, or write a commit message in this repo. Do not use for branch/PR review workflows.
Complete an end-of-session checkout for this repo: file issues for remaining work, run quality gates if code changed, sync and push to remote, clean up git state, and hand off context. Use when the user says "land the plane", "wrap up", "finish the session", or asks to make sure everything is committed and pushed. Work is not done until `git push` succeeds.
Reference or document AI models in the garden using provider namespaces and singular naming. Use when mentioning a model in passing/changelogs, creating a model stub, or authoring a detailed model page with features, benchmarks, tiers, access, and specs. Covers OpenAI/Anthropic/Google/DeepSeek/xAI model link formats and model-code aliases. Do not use for general entity creation (logseq-entity) or non-model pages.
Construct Logseq asset links: convert a macOS/absolute file path or a Logseq namespaced page name into a relative Markdown link (or file:/// link) into the graph's assets/ directory. Use when the user gives a file path or [[Namespace/Page]] and wants the asset/image/PDF link, an asset filename, or an asset folder path. Do not use for ordinary page wikilinks (logseq-core / logseq-link-hygiene).
| name | quiz |
| description | Quiz yourself on documents you've recently read to test understanding and retention |
| targets | ["*"] |
You are quizzing the user on documents they've recently read in Readwise Reader. Follow this process carefully.
Check if Readwise MCP tools are available (e.g. mcp__readwise__reader_list_documents). If they are, use them throughout. If not, use the equivalent readwise CLI commands instead (e.g. readwise list, readwise read <id>, readwise search <query>). The instructions below reference MCP tool names — translate to CLI equivalents as needed.
Check for persona file. Read reader_persona.md in the current working directory if it exists. Use it to personalize question framing, application questions, and grading commentary throughout the quiz. If no persona file exists, proceed without personalization — questions will be more generic.
Welcome the user. Open with a brief, friendly introduction:
Quiz · Readwise Reader
I'll find something you've recently read and quiz you on it — one question at a time, graded like a smart colleague who also read the piece.
(You can also name a specific article, book, or document and I'll quiz you on that instead.)
Find a document to quiz on. The user may provide a document in one of these ways:
If they give a specific document (title, URL, or ID) — use mcp__readwise__reader_search_documents or mcp__readwise__reader_list_documents with id to find it.
If they say "quiz me" with no specific document — find recently read material:
mcp__readwise__reader_list_documents with location="archive", limit=10, response_fields=["title", "author", "category", "word_count", "summary", "url", "saved_at"]. Do NOT paginate or fetch additional pages — 10 results is enough to pick from.reading_progress and look for documents with progress > 50%. That's it — two calls maximum.| # | Title | Author | Length |
|---|---|---|---|
| 1 | ... | ... | ... |
Or if there's a clear best pick, confirm: "Want me to quiz you on [title]?"
Fetch the full document. Use mcp__readwise__reader_get_document_details with the document's ID to get the full content. Also fetch any highlights with mcp__readwise__reader_get_document_highlights — these tell you what the user found important.
Read the document. Understand its core arguments, key claims, structure, and nuances. Note what the user highlighted — these are the parts they engaged with most.
Present questions one at a time. Wait for the user's answer before moving on.
Tell the user what you're quizzing them on:
Quiz: [Title] by [Author] [Category] · [word count or read time]
[1-2 sentence description of what the piece argues/covers]
I'll ask [3-5] questions. Ready?
Mix these types based on the document. Not every quiz needs all types.
If the persona file exists, frame questions around their world:
After each answer:
Quiz like a smart colleague, not a teacher — challenging but collaborative. Be direct, no fluff. Be honest about what they got right and what they missed. Quote the source material when it sharpens the point.
After all questions, provide: