Scientific Thinking Scholar Evaluation
Structured scholarly-work evaluation for papers, proposals, literature reviews, methods sections, evidence quality, citation support, and research-writing feedback. Use when evaluating academic or scientific work — papers, proposals, methods sections, or evidence quality — against a repeatable rubric.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Scientific Thinking Scholar Evaluation when an AI agent needs a reusable SKILL.md workflow for this job: Structured scholarly-work evaluation for papers, proposals, literature reviews, methods sections, evidence quality, citation support, and research-writing feedback. Use when evaluating academic or scientific work — papers, proposals, methods sections, or evidence quality — against a repeatable rubric.
When not to use it
Skip Scientific Thinking Scholar Evaluation when the task is outside the analysis category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/scientific-thinking-scholar-evaluation # Save SKILL.md to ~/.claude/skills/scientific-thinking-scholar-evaluation/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/scientific-thinking-scholar-evaluation/SKILL.md. For a shared project, commit the folder at .claude/skills/scientific-thinking-scholar-evaluation/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Scientific Thinking Scholar Evaluation skill for this task: Reviewing a research paper, proposal, thesis chapter, or literature review. Confirm any required inputs or files before making changes.
What supports this recommendation?
74/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 82/100
- Practical detail
- 74/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Scholar Evaluation
Use this skill to evaluate academic or scientific work with a repeatable rubric.
## When to Use
- Reviewing a research paper, proposal, thesis chapter, or literature review. - Checking whether claims are supported by cited evidence. - Evaluating methodology, study design, analysis, or limitations. - Comparing two or more papers for quality or relevance. - Producing structured feedback for revision.
## Evaluation Scope
Start by identifying the artifact:
- empirical research paper - theoretical paper - technical report - systematic or narrative literature review - research proposal - thesis or dissertation chapter - conference abstract or short paper
Then choose scope:
- **comprehensive**: all rubric dimensions - **targeted**: one or two dimensions, such as method or citations - **comparative**: rank multiple works against the same rubric
## Rubric
Score each applicable dimension from 1 to 5:
- 5: excellent; clear, rigorous, and publication-ready - 4: good; minor improvements needed - 3: adequate; meaningful gaps but usable - 2: weak; substantial revision needed - 1: poor; major validity or clarity problems
Use `N/A` for dimensions that do not apply.
### 1. Problem and Research Question
- Is the problem clear and specific? - Is the contribution meaningful? - Are scope and assumptions explicit? - Does the question match the claimed contribution?
### 2. Literature and Context
- Is relevant prior work covered? - Does the work synthesize rather than merely list sources? - Are gaps accurately identified? - Are recent and foundational sources balanced?
### 3. Methodology
- Does the method answer the research question? - Are design choices justified? - Are variables, datasets, participants, or materials described clearly? - Could another researcher reproduce the work? - Are ethical and practical constraints acknowledged?
### 4. Data and Evidence
- Are data sources credible and appropriate? - Is sample size or corpus coverage adequate? - Are inclusion, exclusion, and preprocessing decisions documented? - Are missing data and bias risks discussed?
### 5. Analysis
- Are statistical, qualitative, or computational methods appropriate? - Are baselines and controls fair? - Are uncertainty, sensitivity, or robustness checks included when needed? - Are alternative explanations considered?
### 6. Results and Interpretation
- Are results clearly presented? - Do claims stay within the evidence? - Are figures, tables, and metrics understandable? - Are negative or null results handled honestly?
### 7. Limitations and Threats to Validity
- Are limitations specific rather than generic? - Are internal, external, construct, and conclusion-validity risks addressed? - Does the paper distinguish speculation from demonstrated results?
### 8. Writing and Structure
- Is the argument easy to follow? - Are sections organized around the research question? - Are definitions and notation clear? - Is the tone precise and scholarly?
### 9. Citations
- Do cited papers support the claims attached to them? - Are primary sources used where possible? - Are reviews labeled as reviews? - Are preprints labeled as preprints? - Are citation metadata and links correct?
## Review Process
1. Read the abstract, introduction, figures, and conclusion for claimed contribution. 2. Read methods and results for evidence quality. 3. Check the strongest claims against cited sources. 4. Score each applicable dimension. 5. Separate critical blockers from revision suggestions. 6. End with concrete next edits.
## Output Template
```markdown # Scholar Evaluation: <Artifact>
## Overall Assessment
- Overall score: <1-5 or N/A> - Confidence: <high | medium | low> - Summary: <3-5 sentences>
## Dimension Scores
| Dimension | Score | Evidence | Revision priority | | --- | ---: | --- | --- | | Problem and question | | | | | Literature and context | | | | | Methodology | | | | | Data and evidence | | | | | Analysis | | | | | Results and interpretation | | | | | Limitations | | | | | Writing and structure | | | | | Citations | | | |
## Critical Issues
## Recommended Revisions
## Evidence Checks Needed ```
## Pitfalls
- Do not use the score as a substitute for concrete feedback. - Do not penalize a paper for omitting a dimension outside its scope. - Do not treat citation count, venue, or author reputation as proof of quality. - Do not accept unsupported claims just because they appear in the abstract.
Intended uses
- Reviewing a research paper, proposal, thesis chapter, or literature review.
- Checking whether claims are supported by cited evidence.
- Evaluating methodology, study design, analysis, or limitations.
- Comparing two or more papers for quality or relevance.
- Producing structured feedback for revision.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.