sci-review

Name: sci-review
Author: ShZhao27208

188installs23forks

How to install sci-review?

shzhao27208/aut_sci_write/sci-review

$npx -y skills add ShZhao27208/Aut_Sci_Write --skill sci-review

Installs into the current project.

Summary

Specialized workflows for drafting, refining, and responding to academic literature reviews and peer review feedback. Use this skill for literature review outlines, research-gap synthesis, reviewer rebuttals, response letters, and academic writing tone repair.

Files · 1

View on GitHub

SKILL.md

1	# Sci-Review
2
3	Use this skill to produce structured literature-review writing and professional reviewer responses.
4
5	## Literature Review Structure
6
7	Use this four-part structure unless the user requests a different journal format:
8
9	1. Introduction: background, problem definition, gap identification, and contribution.
10	2. Methodology: taxonomy, method classes, comparison dimensions, and performance evidence.
11	3. Challenges: phenomenon, cause, and direction. Make the problem visible before proposing a route forward.
12	4. Conclusion: distilled insights and a future roadmap.
13
14	Prefer specific evidence over broad claims. Replace vague phrases such as "significantly better" with measured comparisons when data is available.
15
16	## Rebuttal Structure
17
18	For each reviewer point, use:
19
20	1. Reviewer concern: restate the concern accurately and neutrally.
21	2. Response: answer with evidence, clarification, or a limitation acknowledgement.
22	3. Revision plan: state the exact manuscript change, including section, table, figure, appendix, or experiment when possible.
23
24	Avoid adversarial phrasing such as "reviewer misunderstood" or "the reviewer is wrong". Use constructive language such as "we will clarify this point in the manuscript" or "we agree that additional evidence would improve the presentation".
25
26	## Validation
27
28	The skill includes a lightweight validator. Run from the `skills/sci-review/` directory:
29
30	```bash
31	# From the skills/sci-review/ directory:
32	python scripts/validate_review_output.py --case literature-review --output output.md
33	python scripts/validate_review_output.py --case rebuttal --output output.md
34	python scripts/validate_review_output.py --list-golden
35	```
36
37	The validator checks required section names and banned phrases. Golden cases live in `tests/golden_cases.json`; they define expected output features rather than exact wording.
38
39	## Best Practices
40
41	- Read the source literature, reviewer comments, or draft before rewriting.
42	- Preserve technical nuance. Do not invent experiments, results, baselines, or citations.
43	- Mark uncertainty explicitly when source evidence is missing.
44	- Keep tone professional, direct, and evidence-driven.

People who liked this also viewed

6 picks

Type

sci-review

188installs23forks

View on GitHub

How to install sci-review?

shzhao27208/aut_sci_write/sci-review

$npx -y skills add ShZhao27208/Aut_Sci_Write --skill sci-review

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Sci-Review
2
3	Use this skill to produce structured literature-review writing and professional reviewer responses.
4
5	## Literature Review Structure
6
7	Use this four-part structure unless the user requests a different journal format:
8
9	1. Introduction: background, problem definition, gap identification, and contribution.
10	2. Methodology: taxonomy, method classes, comparison dimensions, and performance evidence.
11	3. Challenges: phenomenon, cause, and direction. Make the problem visible before proposing a route forward.
12	4. Conclusion: distilled insights and a future roadmap.
13
14	Prefer specific evidence over broad claims. Replace vague phrases such as "significantly better" with measured comparisons when data is available.
15
16	## Rebuttal Structure
17
18	For each reviewer point, use:
19
20	1. Reviewer concern: restate the concern accurately and neutrally.
21	2. Response: answer with evidence, clarification, or a limitation acknowledgement.
22	3. Revision plan: state the exact manuscript change, including section, table, figure, appendix, or experiment when possible.
23
24	Avoid adversarial phrasing such as "reviewer misunderstood" or "the reviewer is wrong". Use constructive language such as "we will clarify this point in the manuscript" or "we agree that additional evidence would improve the presentation".
25
26	## Validation
27
28	The skill includes a lightweight validator. Run from the `skills/sci-review/` directory:
29
30	```bash
31	# From the skills/sci-review/ directory:
32	python scripts/validate_review_output.py --case literature-review --output output.md
33	python scripts/validate_review_output.py --case rebuttal --output output.md
34	python scripts/validate_review_output.py --list-golden
35	```
36
37	The validator checks required section names and banned phrases. Golden cases live in `tests/golden_cases.json`; they define expected output features rather than exact wording.
38
39	## Best Practices
40
41	- Read the source literature, reviewer comments, or draft before rewriting.
42	- Preserve technical nuance. Do not invent experiments, results, baselines, or citations.
43	- Mark uncertainty explicitly when source evidence is missing.
44	- Keep tone professional, direct, and evidence-driven.

People who liked this also viewed

6 picks

Type