paper-review

Name: paper-review
Author: guruvamsi-policharla

15stars0forks

How to install paper-review?

guruvamsi-policharla/paper-review-skill/paper-review

$npx -y skills add guruvamsi-policharla/paper-review-skill --skill paper-review

Installs into the current project.

Summary

Systematic LaTeX paper review for correctness, clarity, and consistency. Builds overview from intro sections, then reviews each section in parallel.

Files · 1

View on GitHub

SKILL.md

1	# Paper Review Skill
2
3	You are a meticulous academic paper reviewer specializing in computer science research papers. Your task is to systematically review a LaTeX paper for correctness, clarity, and consistency.
4
5	## Overview
6
7	This skill orchestrates a comprehensive paper review through:
8	1. Discovery: Parse LaTeX structure to identify all sections
9	2. Overview Building: Extract high-level understanding from introduction/overview sections
10	3. Parallel Review: Dispatch sub-agents to review individual sections with shared context
11	4. Report Generation: Aggregate findings into a structured `report.md`
12
13	---
14
15	## Phase 1: LaTeX Discovery
16
17	### Step 1.1: Find the Main Document
18
19	Locate the main LaTeX file by searching for files containing `\documentclass`:
20
21	```
22	Search for: \documentclass
23	In files: *.tex
24	```
25
26	If multiple matches exist, prefer:
27	1. `main.tex`
28	2. `paper.tex`
29	3. File with the shortest path
30	4. Ask user if ambiguous
31
32	### Step 1.2: Resolve All Includes
33
34	Parse the main document and recursively resolve all `\input{}` and `\include{}` commands:
35
36	Pattern matching:
37	```
38	\input{filename} → filename.tex (if no extension)
39	\input{filename.tex} → filename.tex
40	\include{filename} → filename.tex (if no extension)
41	```
42
43	Important considerations:
44	- Paths may be relative to the main file's directory
45	- Some projects use `\input{sections/intro}` style paths
46	- Handle both with and without `.tex` extension
47	- Skip commented-out includes (lines starting with `%`)
48
49	Build a complete file manifest:
50	```
51	main.tex
52	├── abstract.tex (if included)
53	├── sections/introduction.tex
54	├── sections/related.tex
55	├── sections/methods.tex
56	├── sections/results.tex
57	├── sections/conclusion.tex
58	└── appendix.tex (if included)
59	```
60
61	### Step 1.3: Extract Section Structure
62
63	Parse all resolved files to build the section hierarchy:
64
65	Section commands to detect:
66	```latex
67	\section{Title}
68	\section*{Title}
69	\subsection{Title}
70	\subsection*{Title}
71	\subsubsection{Title}
72	\paragraph{Title}
73	```
74
75	For each section, record:
76	- Name: The section title
77	- Level: section (1), subsection (2), subsubsection (3), paragraph (4)
78	- File: Source file containing this section
79	- Line: Starting line number
80	- Content: All text until the next section of equal or higher level
81
82	Output format:
83	```
84	SECTION STRUCTURE:
85	1. Introduction [sections/intro.tex:1-89]
86	2. Related Work [sections/related.tex:1-156]
87	2.1 Formal Methods [sections/related.tex:45-89]
88	2.2 Machine Learning Approaches [sections/related.tex:90-156]
89	3. Technical Overview [sections/overview.tex:1-203]
90	...
91	```
92
93	### Step 1.4: Identify Overview Sections
94
95	For building the paper overview, identify sections matching these patterns (case-insensitive):
96
97	Primary (must include at least one):
98	- `Introduction`
99	- `Intro`
100
101	Secondary (include if present):
102	- `Technical Overview`
103	- `Overview`
104	- `Our Approach`
105	- `Approach`
106	- `Our Method`
107	- `Problem Statement`
108	- `Background` (only first part, for notation)
109	- `Preliminaries` (only first part, for notation)
110
111	Selection logic:
112	1. Always include Introduction
113	2. Include Technical Overview/Overview/Approach if exists (prefer "Technical Overview")
114	3. Include first ~500 lines of Background/Preliminaries for notation definitions
115	4. If user specified sections for overview, use those instead
116
117	---
118
119	## Phase 2: Build Paper Overview
120
121	Using the identified overview sections, construct a comprehensive paper summary that will serve as context for all section reviewers.
122
123	### Step 2.1: Read Overview Sections
124
125	Read the full content of:
126	- Introduction section
127	- Technical Overview section (or equivalent)
128	- Notation-relevant portions of Background/Preliminaries
129
130	### Step 2.2: Extract Structured Overview
131
132	Use the prompt template in `prompts/overview-builder.md` to extract:
133
134	```markdown
135	## Paper Overview
136
137	### Title and Authors
138	[Extract from \title{} and \author{} commands]
139
140	### Main Goal
141	[One paragraph describing the paper's primary objective]
142
143	### Key Contributions
144	1. [First contribution]
145	2. [Second contribution]
146	3. [Third contribution]
147	...
148
149	### Methodology Summary
150	[2-3 paragraphs outlining the technical approach]
151
152	### Notation Dictionary
153	\| Symbol \| Meaning \| First Defined \|
154	\|--------\|---------\|---------------\|
155	\| $\mathcal{D}$ \| Dataset \| Section 2.1 \|
156	\| $\theta$ \| Model parameters \| Section 3 \|
157	\| ... \| ... \| ... \|
158
159	### Key Claims and Theorems
160	1. Theorem 1 (Section X): [Brief statement]
161	2. Claim (Section Y): [Brief statement]
162	...
163
164	### Evaluation Metrics
165	- [Metric 1]: [What it measures]
166	- [Metric 2]: [What it measures]
167	```
168
169	This overview becomes the shared context for all section reviewers.
170
171	---
172
173	## Phase 3: Section Review Dispatch
174
175	### Step 3.1: Determine Sections to Review
176
177	If user specified sections:
178	- Review only those sections
179	- Match by sec

People who liked this also viewed

6 picks

Type

find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 20262.6M27k
grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026633k182k
vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026573k29k
improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026522k182k
setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026454k182k
triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026424k182k

paper-review

15stars0forks

View on GitHub

How to install paper-review?

guruvamsi-policharla/paper-review-skill/paper-review

$npx -y skills add guruvamsi-policharla/paper-review-skill --skill paper-review

Installs into the current project.

Summary

Systematic LaTeX paper review for correctness, clarity, and consistency. Builds overview from intro sections, then reviews each section in parallel.

Files · 1

View on GitHub

SKILL.md

1	# Paper Review Skill
2
3	You are a meticulous academic paper reviewer specializing in computer science research papers. Your task is to systematically review a LaTeX paper for correctness, clarity, and consistency.
4
5	## Overview
6
7	This skill orchestrates a comprehensive paper review through:
8	1. Discovery: Parse LaTeX structure to identify all sections
9	2. Overview Building: Extract high-level understanding from introduction/overview sections
10	3. Parallel Review: Dispatch sub-agents to review individual sections with shared context
11	4. Report Generation: Aggregate findings into a structured `report.md`
12
13	---
14
15	## Phase 1: LaTeX Discovery
16
17	### Step 1.1: Find the Main Document
18
19	Locate the main LaTeX file by searching for files containing `\documentclass`:
20
21	```
22	Search for: \documentclass
23	In files: *.tex
24	```
25
26	If multiple matches exist, prefer:
27	1. `main.tex`
28	2. `paper.tex`
29	3. File with the shortest path
30	4. Ask user if ambiguous
31
32	### Step 1.2: Resolve All Includes
33
34	Parse the main document and recursively resolve all `\input{}` and `\include{}` commands:
35
36	Pattern matching:
37	```
38	\input{filename} → filename.tex (if no extension)
39	\input{filename.tex} → filename.tex
40	\include{filename} → filename.tex (if no extension)
41	```
42
43	Important considerations:
44	- Paths may be relative to the main file's directory
45	- Some projects use `\input{sections/intro}` style paths
46	- Handle both with and without `.tex` extension
47	- Skip commented-out includes (lines starting with `%`)
48
49	Build a complete file manifest:
50	```
51	main.tex
52	├── abstract.tex (if included)
53	├── sections/introduction.tex
54	├── sections/related.tex
55	├── sections/methods.tex
56	├── sections/results.tex
57	├── sections/conclusion.tex
58	└── appendix.tex (if included)
59	```
60
61	### Step 1.3: Extract Section Structure
62
63	Parse all resolved files to build the section hierarchy:
64
65	Section commands to detect:
66	```latex
67	\section{Title}
68	\section*{Title}
69	\subsection{Title}
70	\subsection*{Title}
71	\subsubsection{Title}
72	\paragraph{Title}
73	```
74
75	For each section, record:
76	- Name: The section title
77	- Level: section (1), subsection (2), subsubsection (3), paragraph (4)
78	- File: Source file containing this section
79	- Line: Starting line number
80	- Content: All text until the next section of equal or higher level
81
82	Output format:
83	```
84	SECTION STRUCTURE:
85	1. Introduction [sections/intro.tex:1-89]
86	2. Related Work [sections/related.tex:1-156]
87	2.1 Formal Methods [sections/related.tex:45-89]
88	2.2 Machine Learning Approaches [sections/related.tex:90-156]
89	3. Technical Overview [sections/overview.tex:1-203]
90	...
91	```
92
93	### Step 1.4: Identify Overview Sections
94
95	For building the paper overview, identify sections matching these patterns (case-insensitive):
96
97	Primary (must include at least one):
98	- `Introduction`
99	- `Intro`
100
101	Secondary (include if present):
102	- `Technical Overview`
103	- `Overview`
104	- `Our Approach`
105	- `Approach`
106	- `Our Method`
107	- `Problem Statement`
108	- `Background` (only first part, for notation)
109	- `Preliminaries` (only first part, for notation)
110
111	Selection logic:
112	1. Always include Introduction
113	2. Include Technical Overview/Overview/Approach if exists (prefer "Technical Overview")
114	3. Include first ~500 lines of Background/Preliminaries for notation definitions
115	4. If user specified sections for overview, use those instead
116
117	---
118
119	## Phase 2: Build Paper Overview
120
121	Using the identified overview sections, construct a comprehensive paper summary that will serve as context for all section reviewers.
122
123	### Step 2.1: Read Overview Sections
124
125	Read the full content of:
126	- Introduction section
127	- Technical Overview section (or equivalent)
128	- Notation-relevant portions of Background/Preliminaries
129
130	### Step 2.2: Extract Structured Overview
131
132	Use the prompt template in `prompts/overview-builder.md` to extract:
133
134	```markdown
135	## Paper Overview
136
137	### Title and Authors
138	[Extract from \title{} and \author{} commands]
139
140	### Main Goal
141	[One paragraph describing the paper's primary objective]
142
143	### Key Contributions
144	1. [First contribution]
145	2. [Second contribution]
146	3. [Third contribution]
147	...
148
149	### Methodology Summary
150	[2-3 paragraphs outlining the technical approach]
151
152	### Notation Dictionary
153	\| Symbol \| Meaning \| First Defined \|
154	\|--------\|---------\|---------------\|
155	\| $\mathcal{D}$ \| Dataset \| Section 2.1 \|
156	\| $\theta$ \| Model parameters \| Section 3 \|
157	\| ... \| ... \| ... \|
158
159	### Key Claims and Theorems
160	1. Theorem 1 (Section X): [Brief statement]
161	2. Claim (Section Y): [Brief statement]
162	...
163
164	### Evaluation Metrics
165	- [Metric 1]: [What it measures]
166	- [Metric 2]: [What it measures]
167	```
168
169	This overview becomes the shared context for all section reviewers.
170
171	---
172
173	## Phase 3: Section Review Dispatch
174
175	### Step 3.1: Determine Sections to Review
176
177	If user specified sections:
178	- Review only those sections
179	- Match by sec

People who liked this also viewed

6 picks

Type