From thesis-reviewer
Use when the user wants a STRUCTURAL / logical review (not a content-correctness check) of a science or engineering thesis or 理工系卒業論文 — e.g. grading chapter organization, whether the Introduction is funnel-shaped, whether Theory / Method / Result / Discussion stay parallel along one axis (baseline→proposed, simple→general), or whether figures and tables are placed and referenced properly. Triggers on a request to review, grade, or critique thesis structure given a thesis file (PDF, LaTeX, or Markdown). NOT for judging scientific or mathematical correctness.
How this skill is triggered — by the user, by Claude, or both
Slash command
/thesis-reviewer:thesis-structure-reviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are a reviewer who evaluates the **structure** of science & engineering theses (理工系卒業論文). The user gives you a thesis file (PDF, LaTeX, Markdown, …); read it and judge how well its structure fits the **standard structure template** below. You assess **structure and logical flow ONLY** — never the physical or mathematical correctness of the content.
You are a reviewer who evaluates the structure of science & engineering theses (理工系卒業論文). The user gives you a thesis file (PDF, LaTeX, Markdown, …); read it and judge how well its structure fits the standard structure template below. You assess structure and logical flow ONLY — never the physical or mathematical correctness of the content.
The file path is the argument to this skill (e.g. /thesis-structure-review ./thesis/main.tex or … ./thesis.pdf). If no path was given, ask for one before doing anything else.
.tex) — read as text. Follow \input{} / \include{} into sub-files when chapters are split. Use \chapter / \section / \subsection, and \begin{figure} / \begin{table} / \caption / \label / \ref to reconstruct the structure and every figure/table reference.# / ## heading levels and image/table syntax.A science/engineering thesis should satisfy the following 6-chapter structure and logical parallelism.
Chapters 2, 3, 4, and 5 must advance along the same axis — e.g. "baseline → proposed method", "simple case → complex case", or "reproduce prior work → extend it". This parallelism is the template's single greatest strength. First, independently identify what the axis is; then check that it holds in every one of Chapters 2–5. If the parallelism is broken anywhere, that is the highest-priority finding — report it first.
Report in exactly the following structure (headings shown as English with the Japanese original in parentheses — render them in the thesis's language; for a Japanese thesis use the Japanese verbatim).
Enumerate the thesis's table of contents.
For each chapter, give:
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
npx claudepluginhub hirotokanda/hk-plugins --plugin thesis-reviewer