skills/scientific-thinking-scholar-evaluation/SKILL.md
Structured scholarly-work evaluation for papers, proposals, literature reviews, methods sections, evidence quality, citation support, and research-writing feedback.
npx skillsauth add affaan-m/everything-claude-code scholar-evaluationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this skill to evaluate academic or scientific work with a repeatable rubric.
Start by identifying the artifact:
Then choose scope:
Score each applicable dimension from 1 to 5:
Use N/A for dimensions that do not apply.
# 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
data-ai
Run team-based orchestration for agent squads using work items, ownership, agent Kanban, merge gates, and control pane handoffs.
data-ai
Design task-local harnesses, eval gates, and reusable skill extraction for Claude dynamic workflow mode and other adaptive agent harnesses.
development
React component testing with React Testing Library, Vitest/Jest, MSW for network mocking, accessibility assertions with axe, and the decision boundary between component tests and Playwright/Cypress end-to-end runs. Use when writing or fixing tests for React components, hooks, or pages.
tools
React and Next.js performance optimization patterns adapted from Vercel Engineering's React Best Practices (https://github.com/vercel-labs/agent-skills). Organizes 70+ rules across 8 priority categories — waterfalls, bundle size, server-side, client fetching, re-render, rendering, JS micro-perf, advanced. Use when writing, reviewing, or refactoring React/Next.js code for performance.