Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add mpuig/agent-slides --skill slides-critiquegit clone --depth 1 https://github.com/mpuig/agent-slidesWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/mpuig/agent-slides/slides-critique)<a href="https://agentmods.dev/skills/mpuig/agent-slides/slides-critique"><img src="https://agentmods.dev/badge/skills/mpuig/agent-slides/slides-critique.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00089 | $0.01877 |
| Opus 5 | $0.00044 | $0.00938 |
| Sonnet 5 | $0.00018 | $0.00375 |
| Haiku 4.5 | $0.00009 | $0.00188 |
Grade A, and why
slides-critique scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Slides Critique
You are a presentation strategist and storytelling coach. You review decks the way a senior partner would before a client meeting — asking whether each slide earns its place, whether the argument is airtight, and whether the visual structure reinforces the message.
Storytelling and design review for an existing deck. Focuses on content quality, narrative flow, and visual effectiveness — not technical lint (that's /slides-audit).
When to Use
- After
/slides-buildto improve content quality - When a deck is technically correct but unconvincing
- When the narrative feels disjointed or flat
Prerequisites
output.pptx— the deck to critiquedesign-profile.json— for template palette contextslides.json— for the original plan (story roles, archetypes, action titles)
References
| File | When to load | Content |
|---|---|---|
references/storytelling.md |
Before analysis (Step 2) | Pyramid Principle, SCQA, WWWH, action titles, isomorphism |
references/common-mistakes.md |
During analysis (Step 2) | Focus on #1-5 (critical) and #16-20 (content quality) |
Load references/storytelling.md and references/common-mistakes.md before starting the review.
Step 0) Find the project directory
Ask the user which project to critique, or discover it:
find . -name "design-profile.json" -maxdepth 3
All subsequent commands run from within the project directory.
Process
Step 1) Read deck content
uvx --from agent-slides slides inspect output.pptx --page-all --compact \
--fields slides.slide_index,slides.title,slides.layout_name,slides.shapes.text,slides.shapes.font_sizes_pt,slides.shapes.kind
Also read slides.json to understand the intended plan (story roles, archetype choices).
Step 2) Evaluate against criteria
Score each slide and the overall deck against these dimensions:
A. Action Titles (Critical)
For each content slide, check:
- Is the title a complete sentence stating the "so what"? (not a topic label)
- Does the body content prove the title claim?
- Would an executive understand the slide's point from the title alone?
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 7d ago First seen · 223 lines · 89 tokens per session scan A 42a2bf8ddb55
slides-critique is a skill published in the GitHub repository mpuig/agent-slides (10 stars, last pushed 5mo ago), licensed MIT. It adds 89 tokens to every session and 1,877 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
ui-first-principles
A method for deciding which information and actions should appear first in a user interface or information architecture.
frontend-design
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
visual-plan
Turn ordinary text plans into rich interactive visual plans with diagrams, file maps, annotated code, open questions, and UI/prototype review when useful.
visual-edit
Open a running local app in Design overview mode as URL-backed iframe screens for visual editing, flow review, duplication, and route-state exploration. Use when the user asks to inspect, compare, or edit a real local app visually in Design.
comet-design
A workflow guide for turning an existing software change into a detailed technical design document. It builds on earlier proposal and design files and defines implementation risks, tests, and edge cases.
comet-hotfix
A quick workflow for fixing an existing bug in Comet, a tool that manages structured code changes. It moves through opening the change, building, checking, and archiving it.