read

Name: read
Author: yha9806

24stars3forks

How to install read?

yha9806/academic-writing-toolkit/read

$npx -y skills add yha9806/academic-writing-toolkit --skill read

Installs into the current project.

Summary

Read PDF page by page with structured output — key arguments, terms glossary, thesis connections. Use when reading academic papers, books, or articles.

Files · 1

View on GitHub

SKILL.md

1	# /read — Academic PDF Reading Skill
2
3	## Core Principle
4
5	Display first, restrain expansion. Show the page content, provide a terms glossary, give a brief summary and thesis connections. Do not auto-expand, auto-search, or auto-record unless the user explicitly asks. The reader controls the pace and direction.
6
7	## Trigger Words
8
9	This skill activates on: `read`, `next page`, `continue`, `skip to p.N`, `read p.N`, `/read`.
10
11	## PDF Limits
12
13	- Maximum 15 pages per invocation.
14	- Maximum 90 pages per conversation.
15	- Track cumulative pages read in the conversation. When the count reaches 75, display:
16	`[Limit reminder: {N}/90 pages read this conversation. 15 remaining.]`
17	- If a request would exceed the limit, warn the user and suggest starting a new conversation.
18
19	## Workflow
20
21	1. Identify the PDF. If the user provides a path, use it directly. If the user names an author or title, search the project's `literature/` directory using Glob to locate the file.
22	2. Read the specified page(s) using the Read tool with the `pages` parameter. Default to the next unread page if the user says "next page" or "continue".
23	3. Display structured output following the format below.
24	4. Wait for user instruction. Do not proceed to the next page, take notes, or search for related material unless explicitly asked.
25
26	## Output Format
27
28	For each page read, produce the following:
29
30	```
31	## p.{N} -- {Topic Summary}
32
33	### Content
34
35	{Paragraph topic}
36
37	> "{direct quote}" (p.{N})
38
39	- {key point}
40	- {key point}
41
42	{Next paragraph topic}
43
44	> "{direct quote}" (p.{N})
45
46	- {key point}
47
48	### Key Terms
49
50	\| Term \| Translation \| Context \|
51	\|------\|-------------\|---------\|
52	\| {term} \| {if non-English, provide translation} \| {how it is used on this page} \|
53
54	### Summary
55
56	{3-5 sentence summary of the page content. Focus on the argument structure and evidence presented.}
57
58	### Connections
59
60	- Thesis link: {one sentence connecting to the user's research}
61	- Previous page: {one sentence on continuity with previous page, or "First page" if N=1}
62	- Open question: {if any unresolved point or tension is raised}
63
64	---
65	Next page? Take notes? Expand a connection?
66	```
67
68	## Handling Multiple Pages
69
70	When reading a range (e.g., "read p.10-15"):
71	- Produce the structured output for each page individually.
72	- At the end, add a range summary section:
73	```
74	## Pages {start}--{end} Summary
75	{5-8 sentence summary of the range as a whole}
76	```
77
78	## Constraints
79
80	1. Never auto-record notes. The user must explicitly say "take notes", "record this", or invoke `/note`.
81	2. Never auto-search for related literature, web sources, or definitions unless the user asks.
82	3. Never launch agents or parallel tasks.
83	4. All extensions require explicit user request -- expanding a connection, comparing with another source, verifying a claim.
84	5. Literature directory is determined from project configuration. Do not hardcode paths.
85	6. Keep connections to 1-2 sentences max. Do not elaborate. The user will ask if they want more.
86	7. Preserve original language for key terms. If the source is in a non-English language, show the original term alongside the translation.
87	8. Quote accurately. Use the exact text from the PDF. If a quote spans pages, note both page numbers.

People who liked this also viewed

6 picks

Type

read

24stars3forks

View on GitHub

How to install read?

yha9806/academic-writing-toolkit/read

$npx -y skills add yha9806/academic-writing-toolkit --skill read

Installs into the current project.

Summary

Read PDF page by page with structured output — key arguments, terms glossary, thesis connections. Use when reading academic papers, books, or articles.

Files · 1

View on GitHub

SKILL.md

1	# /read — Academic PDF Reading Skill
2
3	## Core Principle
4
5	Display first, restrain expansion. Show the page content, provide a terms glossary, give a brief summary and thesis connections. Do not auto-expand, auto-search, or auto-record unless the user explicitly asks. The reader controls the pace and direction.
6
7	## Trigger Words
8
9	This skill activates on: `read`, `next page`, `continue`, `skip to p.N`, `read p.N`, `/read`.
10
11	## PDF Limits
12
13	- Maximum 15 pages per invocation.
14	- Maximum 90 pages per conversation.
15	- Track cumulative pages read in the conversation. When the count reaches 75, display:
16	`[Limit reminder: {N}/90 pages read this conversation. 15 remaining.]`
17	- If a request would exceed the limit, warn the user and suggest starting a new conversation.
18
19	## Workflow
20
21	1. Identify the PDF. If the user provides a path, use it directly. If the user names an author or title, search the project's `literature/` directory using Glob to locate the file.
22	2. Read the specified page(s) using the Read tool with the `pages` parameter. Default to the next unread page if the user says "next page" or "continue".
23	3. Display structured output following the format below.
24	4. Wait for user instruction. Do not proceed to the next page, take notes, or search for related material unless explicitly asked.
25
26	## Output Format
27
28	For each page read, produce the following:
29
30	```
31	## p.{N} -- {Topic Summary}
32
33	### Content
34
35	{Paragraph topic}
36
37	> "{direct quote}" (p.{N})
38
39	- {key point}
40	- {key point}
41
42	{Next paragraph topic}
43
44	> "{direct quote}" (p.{N})
45
46	- {key point}
47
48	### Key Terms
49
50	\| Term \| Translation \| Context \|
51	\|------\|-------------\|---------\|
52	\| {term} \| {if non-English, provide translation} \| {how it is used on this page} \|
53
54	### Summary
55
56	{3-5 sentence summary of the page content. Focus on the argument structure and evidence presented.}
57
58	### Connections
59
60	- Thesis link: {one sentence connecting to the user's research}
61	- Previous page: {one sentence on continuity with previous page, or "First page" if N=1}
62	- Open question: {if any unresolved point or tension is raised}
63
64	---
65	Next page? Take notes? Expand a connection?
66	```
67
68	## Handling Multiple Pages
69
70	When reading a range (e.g., "read p.10-15"):
71	- Produce the structured output for each page individually.
72	- At the end, add a range summary section:
73	```
74	## Pages {start}--{end} Summary
75	{5-8 sentence summary of the range as a whole}
76	```
77
78	## Constraints
79
80	1. Never auto-record notes. The user must explicitly say "take notes", "record this", or invoke `/note`.
81	2. Never auto-search for related literature, web sources, or definitions unless the user asks.
82	3. Never launch agents or parallel tasks.
83	4. All extensions require explicit user request -- expanding a connection, comparing with another source, verifying a claim.
84	5. Literature directory is determined from project configuration. Do not hardcode paths.
85	6. Keep connections to 1-2 sentences max. Do not elaborate. The user will ask if they want more.
86	7. Preserve original language for key terms. If the source is in a non-English language, show the original term alongside the translation.
87	8. Quote accurately. Use the exact text from the PDF. If a quote spans pages, note both page numbers.

People who liked this also viewed

6 picks

Type