rw-research-referee

Original🇨🇳 Chinese
Translated
1 scriptsChecked / no sensitive code detected

Check the evidence, biases, alternative explanations, and reporting boundaries required for research conclusions before implementation or submission. Use when the user asks for “review my research design”, “act as a strict reviewer”, “challenge this conclusion”, or requests the rw-research-referee workflow. Runs without a private local workspace or preset research-lab; use user-provided material and bundled public-source methods.

3installs
Added on

NPX Install

npx skill4agent add rolandwonglonam/rw-research-skill rw-research-referee

SKILL.md Content (Chinese)

View Translation Comparison →

RW Research Referee

Check the evidence, biases, alternative explanations, and reporting boundaries required for research conclusions before implementation or submission.

Startup

  1. Read
    references/standalone.md
    ,
    references/method.md
    , and
    references/standards.md
    .
  2. Read the materials provided by the user in this session; if no materials are provided, only complete the part allowed by the current evidence.
  3. Retrieve
    references/atoms.jsonl
    when rule judgment is needed; read
    references/cases.md
    when encountering similar tasks.
  4. Read
    references/domain-guide.md
    when selecting methods or tools, and use
    assets/worksheet.md
    to organize deliverables.
  5. Read
    references/acceptance.md
    .
    references/behavior-tests.json
    is only used for testing and not as factual information for user tasks.
  6. When current literature, APIs, reporting specifications, or journal requirements may change, verify and record the date by opening the official links in
    references/source-map.md
    .

Work Phases

  1. Extract the author's strongest conclusion, target population, comparisons, and required evidence.
  2. Select a bias framework based on the research type; do not mix reporting checklists and bias tools.
  3. Check for selection, confounding, allocation, deviation, missingness, measurement, analysis, and selective reporting.
  4. List at least two alternative explanations and the evidence that can distinguish them.
  5. Determine whether the issue belongs to blocking, major revision, minor revision, or reporting clarification.
  6. Output the issue, location of evidence, impact on conclusions, corrective actions, and irreparable parts.

Operating Rules

  • Review the strongest conclusions first, then the language.
  • Missing reports do not automatically prove that the method was not implemented, but will limit evaluability.
  • Risk of bias should be targeted at specific results and target effects.
  • Randomized trials and non-randomized intervention studies cannot use the same bias assessment pathway.
  • Statistical significance does not eliminate design bias.
  • Large samples cannot fix systematic measurement errors.
  • Selection of adjustment variables requires causal or substantive reasons, not just based on univariate P-values.
  • Multiple analyses, subgroups, and post-hoc hypotheses should be checked for selective reporting.
  • Alternative explanations should specify what new evidence is needed to rule them out.
  • External validity issues cannot be solved merely by expanding wording.
  • Irreparable design limitations should reduce the strength of conclusions.
  • Each criticism must explain how it would change the conclusion or decision.

Output

  • A list of issues sorted by blocking level.
  • Evidence requirements, impact on conclusions, and corrective actions.
  • Judgment of pass, revise, redo, or stop.

Stop Conditions

  • Do not issue a pass judgment when key design information is missing.
  • Do not reject a methodologically sound study due to rough language.
  • Do not hide irreparable limitations for the author.
  • Do not treat general review as an ethical or statistical professional signature.

Independent Operation

  • By default, do not read private workspaces, personal corpus directories, or preset research-lab.
  • Files, text, links, and data provided by the user are inputs for the current task, not installation dependencies.
  • When the network is unavailable, continue using stable methods within the Skill; mark parts requiring current facts as pending verification.
  • Can connect with other research Skills in this package if they exist; when installed alone, directly return instructions for the next step without stopping the current task.

Source Discipline

  • Separate user materials, public sources, current inferences, and unknown matters.
  • Reporting specifications only check reporting transparency, not automatically prove design quality.
  • Public source abstracts are stored within the Skill; when versions, fees, policies, APIs, or journal status are needed, return to the official page.
  • Do not generate non-existent papers, data, DOIs, tool operation results, or journal requirements.