agentsclimarketplace

Proofread

Skill brycewang-stanford/Auto-Empirical-Research-Skills/skills/15-Felpix-Studios-social-science-research/skills/proofread

🔬 A curated collection of 23,000+ agent skills for empirical research across 8 social science disciplines. | 精选 23,000+ AI Agent 技能库，覆盖8大社会科学学科的实证研究。CoPaper.AI 20分钟完成一篇可复现的规范实证论文，并支持用户上传 Skills。-- Maintained by CoPaper.AI from Stanford REAP.

Install
npx -y skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill proofread

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.

What its author says it does

Copied from the file, not written here

Run the proofreading protocol on academic writing — papers or manuscripts. Checks grammar, typos, layout issues, consistency, and academic writing quality. Produces a report without editing files. Make sure to use this skill whenever the user wants surface-level writing errors found — not substantive academic critique. Triggers include: "proofread", "check for typos", "grammar check", "look for errors in my draft", "proofread all", "polish this", "check my writing", "are there any mistakes", "proofread before I send this", or when the user wants a clean-up pass rather than feedback on arguments or methods.

SKILL.md

2.9 KB, as published. Nobody here has run it

Proofread Academic Writing

Run the mandatory proofreading protocol on papers or manuscripts. Produces a report of all issues WITHOUT editing any source files.

Steps

  1. Identify files to review:

    • If $ARGUMENTS is a specific filename: review that file only
    • If $ARGUMENTS is all: review all files in manuscripts/ and Quarto/ (if it exists)
    • If $ARGUMENTS is a file in manuscripts/: treat as manuscript (not slides)
    • If $ARGUMENTS is empty or ambiguous and multiple files exist, use AskUserQuestion:
      • header: "Files"
      • question: "Which files should I proofread?"
      • multiSelect: true
      • options: list up to 4 found files (label: filename, description: directory and file type). User can select multiple or choose "Other" to specify a path.

  2. For each file, launch the proofreader agent that checks for:

    GRAMMAR: Subject-verb agreement, articles (a/an/the), prepositions, tense consistency TYPOS: Misspellings, search-and-replace artifacts, duplicated words LAYOUT ISSUES: Overfull hbox (LaTeX slides/manuscripts), content exceeding slide boundaries (Quarto), table/column overflow in manuscripts CONSISTENCY: Citation format, notation, terminology, variable names matching table column names ACADEMIC QUALITY: Informal language, missing words, awkward constructions

  3. Produce a detailed report for each file listing every finding with:

    • Location (line number or section heading)
    • Current text (what's wrong)
    • Proposed fix (what it should be)
    • Category and severity

  4. Save each report to quality_reports/:

    • For .tex slide files: quality_reports/FILENAME_report.md
    • For .qmd slide files: quality_reports/FILENAME_qmd_report.md
    • For manuscript files: quality_reports/FILENAME_proofread.md

  5. IMPORTANT: Do NOT edit any source files. Only produce the report. Fixes are applied separately after user review (see rules/proofreading-protocol.md).

  6. Present summary to the user:

    • Total issues found per file
    • Breakdown by category
    • Most critical issues highlighted

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.