Menu
Drafts a point-by-point response letter to referee comments with suggested edits. Use after a revise-and-resubmit.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Scaffold a Quarto analysis notebook (generic or method-specific — DiD, IV, RDD, LASSO, Panel FE), register it in _quarto.yml, apply publication-quality figure styling, and generate dataset codebooks. Use when starting a new analysis notebook.
Manage the project's literature workflow — ideate research questions, run structured literature reviews, add citations to references.bib, write annotation notes in references/, and audit citation integrity. Use for any bibliography or literature task.
Audit a Quarto manuscript or a single notebook — freeze freshness, data-path existence, citation integrity, figure/table export presence, placeholder and anonymization checks. Produces a scored review report under notes/. Read-only — never modifies notebooks, data, or the manuscript.
Build publication-quality regression and robustness tables from notebook estimation output, exported to tables/ as CSV + Markdown + LaTeX. Use when creating a results table.
Draft and revise manuscript prose for index.qmd — sections, the abstract, regression-result interpretation, and referee responses. Use when writing or revising the manuscript.
Reads the manuscript and notebooks to generate a structured abstract. Use when writing or updating the abstract.
Baseado na classificação ocupacional SOC
| name | referee-response |
| description | Drafts a point-by-point response letter to referee comments with suggested edits. Use after a revise-and-resubmit. |
| argument-hint | <path> or 'paste' |
| allowed-tools | Bash, Read, Write, Edit, Glob, Grep |
| version | 1.0.0 |
| workflow_stage | writing |
| tags | ["revision","referee","response-letter"] |
Draft a structured point-by-point response to referee comments.
$ARGUMENTS — path to a file containing referee comments (e.g., notes/referee-report-R1.txt), or the word "paste" to accept inline inputRead the referee comments:
Read index.qmd to understand the current manuscript content, structure, and arguments.
Parse the referee comments into individual points. Each point typically starts with a number, letter, or dash.
For each referee point, draft a structured response:
**Point N:** [Quote or paraphrase the referee's comment]
**Response:** [Address the comment — acknowledge the concern, explain what was done
or why you disagree, provide additional evidence or reasoning]
**Changes made:** [Describe specific edits with section references, e.g.,
"We have added two paragraphs to Section 3 (@sec-data) clarifying the sample selection."]
Use appropriate response conventions:
Organize the response by referee:
# Response to Referee Comments
## Referee 1
[Point-by-point responses]
## Referee 2
[Point-by-point responses]
## Editor
[Point-by-point responses]
Save the response letter to notes/referee-response-R<N>.md where N is the revision round number (check existing files to determine the round).
Generate a separate list of suggested manuscript edits — specific changes to index.qmd or notebooks that address the referee's concerns. Present these to the user but do NOT apply them without explicit approval.
Report the response letter file path and the list of suggested edits.