devils-advocate

Devil's Advocate Review

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "devils-advocate" with this command: npx skills add pedrohcgs/claude-code-my-workflow/pedrohcgs-claude-code-my-workflow-devils-advocate

Devil's Advocate Review

Critically examine a slide deck and challenge its design with 5-7 specific pedagogical questions.

Philosophy: "We arrive at the best possible presentation through active dialogue."

Setup

  • Read the target file (the lecture being challenged)

  • Read the knowledge base in .claude/rules/ for notation conventions and narrative arc

  • If applicable, read adjacent lectures for narrative continuity

Challenge Categories

Generate 5-7 challenges from these categories:

  1. Ordering Challenges

"Could students understand this better if we showed X before Y?"

  1. Prerequisite Challenges

"Do students have the background for this notation at this point?"

  1. Gap Challenges

"Should we include an intuitive example before this formal proof?"

  1. Alternative Presentation Challenges

"Here are 2 other ways to visualize/present this concept."

  1. Notation Conflict Challenges

"This symbol conflicts with earlier lecture usage."

  1. Cognitive Load Challenges

"This slide has too many new symbols. Can we split?"

  1. Book Vision Challenges

"If this becomes a book chapter, does this section stand alone?"

Output Format

Devil's Advocate: [Lecture Title]

Challenges

Challenge 1: [Category] — [Short title]

Question: [The specific pedagogical question] Why it matters: [What could go wrong] Suggested resolution: [Specific action] Slides affected: [Numbers or titles] Severity: [High / Medium / Low]

[Repeat for 5-7 challenges]

Summary Verdict

Strengths: [2-3 things done well] Critical changes: [0-2 changes before teaching] Suggested improvements: [2-3 nice-to-have changes]

Principles

  • Be specific: Reference exact slides and notation

  • Be constructive: Every challenge has a suggested resolution

  • Be honest: If the deck is good, say so

  • Prioritize: Notation conflicts > missed metaphors

  • Think like a student: Where do they get lost?

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Coding

review-paper

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

data-analysis

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

create-lecture

No summary provided by upstream source.

Repository SourceNeeds Review