quiz

Name: quiz
Author: readwiseio

511installs7forks

How to install quiz?

readwiseio/readwise-skills/quiz

$npx -y skills add readwiseio/readwise-skills --skill quiz

Installs into the current project.

Summary

Quiz yourself on documents you've recently read to test understanding and retention

Files · 1

View on GitHub

SKILL.md

1	You are quizzing the user on documents they've recently read in Readwise Reader. Follow this process carefully.
2
3	## Readwise Access
4
5	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.
6
7	## Setup
8
9	1. 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.
10
11	2. Welcome the user. Open with a brief, friendly introduction:
12
13	> Quiz · Readwise Reader
14	>
15	> 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.
16	>
17	> (You can also name a specific article, book, or document and I'll quiz you on that instead.)
18
19	3. Find a document to quiz on. The user may provide a document in one of these ways:
20
21	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.
22
23	If they say "quiz me" with no specific document — find recently read material:
24	- Make ONE call: `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.
25	- If the first 10 archive results are all very short tweets/RSS items with no substance, make ONE more call to "later" with `reading_progress` and look for documents with progress > 50%. That's it — two calls maximum.
26	- Present 3-5 candidates as a table, then ask the user to pick:
27
28	\| # \| Title \| Author \| Length \|
29	\|---\|-------\|--------\|--------\|
30	\| 1 \| ... \| ... \| ... \|
31
32	Or if there's a clear best pick, confirm: "Want me to quiz you on [title]?"
33
34	3. 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.
35
36	4. 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.
37
38	## Quiz Flow
39
40	Present questions one at a time. Wait for the user's answer before moving on.
41
42	### Opening
43
44	Tell the user what you're quizzing them on:
45
46	> Quiz: [Title] by [Author]
47	> [Category] · [word count or read time]
48	>
49	> [1-2 sentence description of what the piece argues/covers]
50	>
51	> I'll ask [3-5] questions. Ready?
52
53	### Question Types
54
55	Mix these types based on the document. Not every quiz needs all types.
56
57	- "What's the core argument?" — Tests if they got the main point
58	- "How would you apply this to [their domain]?" — Tests practical application (use persona)
59	- "What's the tradeoff/cost of this approach?" — Tests critical thinking
60	- "What did the author miss or hand-wave?" — Tests deep reading
61	- "If you had to bet on [prediction], would you? Why?" — Tests synthesis
62	- "How does this connect to [another thing they've read]?" — Tests cross-referencing (search their highlights for related material)
63
64	### Personalization
65
66	If the persona file exists, frame questions around their world:
67
68	- Reference their job, company, current projects, and interests
69	- Connect the document's ideas to problems they're actually working on
70	- If they read fantasy novels, reference their taste when discussing narrative or craft
71	- Make application questions specific: "How would you apply this at [company]?" not "How would you apply this?"
72
73	### Question Count
74
75	- Short articles (< 2,000 words): 3 questions
76	- Standard articles (2,000-5,000 words): 4 questions
77	- Long articles / essays (5,000+ words): 5 questions
78	- Books: 5 questions (focus on the chapters they highlighted most)
79
80	## Grading
81
82	After each answer:
83
84	1. State the grade clearly: Grade: B+
85	2. Acknowledge what they got right — be specific
86	3. Fill in what they missed or could go deeper on
87	4. Quote the document if relevant to reinforce the point
88	5. Transition to next question
89
90	### Grading Scale
91
92	- A — Nailed it, demonstrated real understanding and application
93	- A- — Got it right, maybe missing one nuance
94	- B+ — Correct direction, but surface-level or incomplete
95	- B — Partially correct, missing key insight
96	- B- — On the right track but vague or hand-wavy
97	- C — Missed the point

People who liked this also viewed

6 picks

Type

lark-drive飞书云空间（云盘/云存储）：管理 Drive 文件和文件夹，包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、评论/权限/订阅、标题、版本、飞书文档密级标签（secure labels）和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题，或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sSkillsJul 2026382k16k
lark-sharedUse for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handlingSkillsJul 2026382k16k
lark-whiteboard飞书画板：查询和编辑飞书云文档中的画板。支持导出画板为预览图片、导出原始节点结构、使用多种格式更新画板内容。当用户需要查看画板内容、导出画板图片、编辑画板时使用此 skill。不负责：飞书云文档内容编辑（lark-doc）、文档内嵌电子表格/Base（lark-sheets / lark-base）。SkillsJul 2026380k16k
lark-task飞书任务：管理任务、清单和任务智能体。创建待办任务、查看和更新任务状态、拆分子任务、组织任务清单、分配协作成员、上传任务附件、注册或注销任务智能体、更新任务智能体的主页数据、写入智能体任务记录。当用户需要创建待办事项、查看任务列表、跟踪任务进度、管理项目清单或给他人分配任务、为任务上传附件文件、注册注销任务智能体、更新智能体主页数据、写入任务记录时使用。SkillsJul 2026380k16k
lark-attendance飞书考勤打卡：查询自己的考勤打卡记录SkillsJul 2026330k16k
lark-apps妙搭（Spark/Miaoda）应用开发与托管：应用创建、本地全栈开发、云端生成迭代、创意设计（UI mockup / 可交互原型 / 线框图 / 落地页 / 仪表盘 / 幻灯片 deck / 视觉探索）、AI相关能力和飞书平台能力或者其他外部能力集成、日志/Trace/监控指标/PV/UV 查询、环境变量管理、应用角色与成员管理、自动化触发器（定时/记录变更/Webhook/飞书审批）。当用户要SkillsJul 2026227k16k

quiz

511installs7forks

View on GitHub

How to install quiz?

readwiseio/readwise-skills/quiz

$npx -y skills add readwiseio/readwise-skills --skill quiz

Installs into the current project.

Summary

Quiz yourself on documents you've recently read to test understanding and retention

Files · 1

View on GitHub

SKILL.md

1	You are quizzing the user on documents they've recently read in Readwise Reader. Follow this process carefully.
2
3	## Readwise Access
4
5	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.
6
7	## Setup
8
9	1. 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.
10
11	2. Welcome the user. Open with a brief, friendly introduction:
12
13	> Quiz · Readwise Reader
14	>
15	> 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.
16	>
17	> (You can also name a specific article, book, or document and I'll quiz you on that instead.)
18
19	3. Find a document to quiz on. The user may provide a document in one of these ways:
20
21	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.
22
23	If they say "quiz me" with no specific document — find recently read material:
24	- Make ONE call: `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.
25	- If the first 10 archive results are all very short tweets/RSS items with no substance, make ONE more call to "later" with `reading_progress` and look for documents with progress > 50%. That's it — two calls maximum.
26	- Present 3-5 candidates as a table, then ask the user to pick:
27
28	\| # \| Title \| Author \| Length \|
29	\|---\|-------\|--------\|--------\|
30	\| 1 \| ... \| ... \| ... \|
31
32	Or if there's a clear best pick, confirm: "Want me to quiz you on [title]?"
33
34	3. 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.
35
36	4. 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.
37
38	## Quiz Flow
39
40	Present questions one at a time. Wait for the user's answer before moving on.
41
42	### Opening
43
44	Tell the user what you're quizzing them on:
45
46	> Quiz: [Title] by [Author]
47	> [Category] · [word count or read time]
48	>
49	> [1-2 sentence description of what the piece argues/covers]
50	>
51	> I'll ask [3-5] questions. Ready?
52
53	### Question Types
54
55	Mix these types based on the document. Not every quiz needs all types.
56
57	- "What's the core argument?" — Tests if they got the main point
58	- "How would you apply this to [their domain]?" — Tests practical application (use persona)
59	- "What's the tradeoff/cost of this approach?" — Tests critical thinking
60	- "What did the author miss or hand-wave?" — Tests deep reading
61	- "If you had to bet on [prediction], would you? Why?" — Tests synthesis
62	- "How does this connect to [another thing they've read]?" — Tests cross-referencing (search their highlights for related material)
63
64	### Personalization
65
66	If the persona file exists, frame questions around their world:
67
68	- Reference their job, company, current projects, and interests
69	- Connect the document's ideas to problems they're actually working on
70	- If they read fantasy novels, reference their taste when discussing narrative or craft
71	- Make application questions specific: "How would you apply this at [company]?" not "How would you apply this?"
72
73	### Question Count
74
75	- Short articles (< 2,000 words): 3 questions
76	- Standard articles (2,000-5,000 words): 4 questions
77	- Long articles / essays (5,000+ words): 5 questions
78	- Books: 5 questions (focus on the chapters they highlighted most)
79
80	## Grading
81
82	After each answer:
83
84	1. State the grade clearly: Grade: B+
85	2. Acknowledge what they got right — be specific
86	3. Fill in what they missed or could go deeper on
87	4. Quote the document if relevant to reinforce the point
88	5. Transition to next question
89
90	### Grading Scale
91
92	- A — Nailed it, demonstrated real understanding and application
93	- A- — Got it right, maybe missing one nuance
94	- B+ — Correct direction, but surface-level or incomplete
95	- B — Partially correct, missing key insight
96	- B- — On the right track but vague or hand-wavy
97	- C — Missed the point

People who liked this also viewed

6 picks

Type