← ClaudeAtlas

pre-submission-reviewlisted

Evidence-anchored evaluation of the USER'S OWN manuscript before journal submission. Use when the user wants their draft evaluated ("review my draft", "is this ready for submission", "act as reviewer 2 on my paper", "check my manuscript before I send it"), names a target journal for their own paper, or asks how their study would fare in peer review. Handles original research AND research syntheses (systematic/scoping reviews, meta-analyses) in language assessment / applied linguistics. Produces a prioritized revision plan plus a 0–100 quality estimate derived from the evidence. NOT for reviewing other people's manuscripts under journal peer review — that is a different activity with different obligations.
Shalice-in-AIland/claude-language-assessment-research-kit · ★ 6 · Code & Development · score 68
Install: claude install-skill Shalice-in-AIland/claude-language-assessment-research-kit
# pre-submission-review Evaluates the user's own manuscript before journal submission, through the criteria its eventual reviewers will apply. Two passes: an **evidence pass** that reads the manuscript and records every observation with a page location and, where relevant, the recomputed number — then a **writing pass** that produces a prioritized revision plan and a quality-score estimate from that verified material only. Unlocated criticism is not recorded. This skill evaluates **the user's own manuscript only.** Reviewing someone else's submission for a journal is a different activity, with confidentiality and publisher-policy obligations this skill does not manage — most publishers prohibit uploading others' manuscripts to AI tools at all. **Confidentiality of outputs.** The manuscript is unpublished and this skill's outputs quote it: treat the notes and plan as part of the manuscript's confidential record — store them beside it, never in a public repository, and leave them out of anything shared beyond the author team. ## Step 0 — intake Read the manuscript. Text extraction is not reading: **figures and appendices are where the checkable material lives**, and extraction drops images — prose may come from the text layer, but **anything two-dimensional may not**: tables, figures, diagrams, and appendix grids are read from rendered page images. Extraction linearizes tables — cell-position is destroyed and rows silently vanish at page breaks — so any numeric or absence