agentleFS
JunMA98JunMA98/Computer-science-claude-skills/skills/scholar-evaluation/SKILL.md

scholar-evaluation

Skill3 starsChanged 8 months agoMITView on GitHub

Score and assess CS papers, proposals, literature reviews, and benchmark plans using a structured evaluation rubric. Use when a quantitative or semi-structured assessment is needed for research quality, novelty, technical soundness, empirical rigor, reproducibility, clarity, and submission readiness.

19 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when the user wants more structure than a free-form review but does not need a full venue-specific peer review.

    line 8
  2. Distinctive:

    Use the script when a numeric roll-up is useful.

    line 34
  3. Distinctive:

    Do not hide major flaws behind an average score.

    line 38
  4. Distinctive:

    Use scoring to support judgment, not replace it.

    line 41
  5. Distinctive:

    When no format is requested, return:

    line 45

“Common” is measured: kept by at least 6 in 10 of the 18 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Scholar Evaluation

Use this skill when the user wants more structure than a free-form review but does not need a full venue-specific peer review.

Good Fits

  • comparing multiple candidate papers
  • grading a draft literature review
  • evaluating a research proposal before implementation
  • checking whether a benchmark plan is rigorous enough
  • estimating whether a draft is close to submission quality

CS-Oriented Dimensions

Score or discuss these explicitly:

  • problem importance and positioning
  • novelty or distinct value
  • technical soundness
  • empirical rigor or evaluation adequacy
  • reproducibility and artifact clarity
  • writing clarity and organization
  • risk areas that could block publication or adoption

Local Resources

  • references/evaluation_framework.md
  • scripts/calculate_scores.py

Use the script when a numeric roll-up is useful. Otherwise keep the evaluation semi-structured and explain the score rationale.

Working Rules

  • Do not hide major flaws behind an average score.
  • Separate missing evidence from poor writing.
  • State what would most improve the work.
  • Use scoring to support judgment, not replace it.

Default Output

When no format is requested, return:

  1. dimension-by-dimension assessment
  2. strengths
  3. highest-impact weaknesses
  4. overall readiness judgment

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.