mcpbeat

Pedagogy Review

pedrohcgs/pedagogy-review

Holistic pedagogical review of a lecture deck (`.qmd` or `.tex`). Checks narrative arc, prerequisite assumptions, worked examples, notation clarity, and deck-level pacing. Use when user says "pedagogy review", "does this teach well?", "is the flow right?", "will students follow?", "review the narrative", or before teaching a deck for the first time. Read-only; produces a report.

375 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
1440
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/pedrohcgs/claude-code-my-workflow --skill pedagogy-review

The instruction itself

3 sections, as written by the author

Pedagogical Review of Lecture Slides

Perform a comprehensive pedagogical review.

Steps

  • Identify the file specified in $ARGUMENTS
  • If no argument, ask user which lecture to review
  • If just a name, look in Quarto/ or Slides/
  • Launch the pedagogy-reviewer agent with the full file path
  • The agent checks 13 pedagogical patterns
  • Performs deck-level analysis (narrative arc, pacing, visual rhythm, notation)
  • Considers student perspective (prerequisites, objections)
  • The agent produces a report saved to:

quality_reports/[FILENAME_WITHOUT_EXT]_pedagogy_report.md

  • Present summary to user:
  • Patterns followed vs violated (out of 13)
  • Deck-level assessments
  • Critical recommendations (top 3-5)

Important Notes

  • This is a read-only review — no files are edited
  • Focuses on pedagogy not visual layout (use /visual-audit for that)
  • For a combined review, use /slide-excellence instead

How to use it

Copy the folder

Take pedrohcgs/pedagogy-review from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.