gpsaggese/helpers / .claude/skills/slides.criticize
slides.criticize
VerifiedRead, criticize, and propose improvements for one or more lectures slides
Goal
- Review and criticize a slide deck, or a subset of its slides, given by the user
- Identify mistakes and improvements, focusing on factual errors rather than style
- Propose concrete, ranked improvements to content, flow, visual clarity, pacing, and audience fit
Workflow
Read the Material
-
Read
.claude/skills/slides.rules.mdfor the rules that slides must follow -
Read the slide deck file passed by the user
- Note the deck title, target audience, and stated learning objectives (if any)
- Read all slides in order to understand the narrative arc
-
Find the context of the presentation:
- Venue and duration (lecture, conference talk, workshop, etc.)
- Assumed prior knowledge
- Adjacent or prerequisite slide decks
Criticize
-
Read
.claude/skills/text.criticize/SKILL.mdfor general approaches to review and criticize text -
Evaluate along these axes, reporting only issues you are confident about:
- Slide-level clarity:
- Too much text per slide (exceeds visible time + cognitive load)
- Unclear titles or takeaways
- Missing or weak visual hierarchy
- Jargon or concepts assumed without intro
- Deck flow & narrative:
- Abrupt transitions between ideas
- Slides in wrong order (should come earlier/later)
- Orphaned or tangential slides
- Missing bridge slides to connect concepts
- Pacing (too slow intro, rushed conclusion, uneven rhythm)
- Audience fit:
- Level too high or too low for stated audience
- Unexplained background assumptions
- Missing motivation or context for why this matters
- Structure & consistency:
- Inconsistent formatting or visual style
- Slides that break the template (if one exists)
- Missing the mandatory standalone
* Roadmap(first slide) or* Summary(last content slide, before* References); see.claude/skills/slides.rules.md## Roadmap Slide/## Summary Slide * Roadmapout of sync with the deck's actual#topics (stale after edits), or* Summaryrestating stale takeaways- Speaker notes missing or incomplete
- Timing & scope:
- Deck too long or too short for the slot
- Individual slides that will overrun or underrun their time
- Candidates to expand, collapse, or split
- Engagement & visuals:
- Slides that rely only on bullet points (no visuals, examples, or storytelling)
- Diagrams or images that are unclear or misleading
- Missing opportunities for interaction or questions
- Slide-level clarity:
-
Rank each issue by severity:
- High: loses attention, undermines a key point, or creates wrong takeaway
- Medium: reduces clarity or engagement
- Low: minor polish or consistency
Write Result
- Write results as
plan-slides.criticize.mdin the current directory - Say in the plan file how it was generated, with this line right after the title:
- Generated by `.claude/skills/slides.criticize/SKILL.md`
Wait for Approval
- Present the criticism to the user
- Wait for the user to select items to apply by index and give corrections
- Only then edit the slide deck
- Preserve formatting, speaker notes, and visual structure
Verification
- Make sure that the updated slides render correctly, e.g.,
> gen_slides.py -i <FILE> --notes_to_pdf_args="--skip_action open_pdf" - The plan file says that it was generated by
.claude/skills/slides.criticize/SKILL.md
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| canvas-designanthropics/skillsCreate beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| docxanthropics/skillsUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| pdfanthropics/skillsUse this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| pptxanthropics/skillsUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |