outline-validator

outline-validator is an agent for Claude Code from rhuss/cc-slidev. It costs 53 tokens per session (3,132 once invoked), scanned A, original, MIT.

An agent that reviews presentation outlines for completeness, logical order, timing, and achievable scope. It uses about 90 seconds per slide as a default estimate for technical presentations.

In plain words
What is it for?
Use it to review an outline, check its opening and conclusion, estimate presentation length, improve section titles and flow, and suggest backup slides for questions.
Why use it?
It can reveal missing sections, weak transitions, repeated ideas, or an unrealistic slide count before slide creation begins. It also checks whether the outline supports the presentation’s objective.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Part of the slidev plugin — 8 skills, 18 commands, 2 agents shipped together

Good fit Use it to review an outline, check its opening and conclusion, estimate presentation length, improve section titles and flow, and suggest backup slides for questions.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/rhuss/cc-slidev/outline-validator
Install

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.

Clone the repo
git clone --depth 1 https://github.com/rhuss/cc-slidev

Made for: Claude Code.

Or install slidev, the plugin that ships this one along with the rest of its 8 skills, 18 commands, 2 agents.

Wrote 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.

agentmods badge for outline-validator

README.md
[![agentmods](https://agentmods.dev/badge/agents/rhuss/cc-slidev/outline-validator/github.svg)](https://agentmods.dev/agents/rhuss/cc-slidev/outline-validator)
Your own site
<a href="https://agentmods.dev/agents/rhuss/cc-slidev/outline-validator"><img src="https://agentmods.dev/badge/agents/rhuss/cc-slidev/outline-validator/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for outline-validator

Your own site · 80×15
<a href="https://agentmods.dev/agents/rhuss/cc-slidev/outline-validator"><img src="https://agentmods.dev/badge/agents/rhuss/cc-slidev/outline-validator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 53 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,132 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00053 $0.03132
Opus 5.5 $0.00021 $0.01253
Sonnet 5.5 $0.00011 $0.00626
Haiku 4.5 $0.00005 $0.00313

Measured 1mo ago against content hash 834d63ccaa0f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

outline-validator 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 1mo 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.

slidev/agents/outline-validator.md · 403 lines

How it starts

The opening of the file, as written. The whole thing — 403 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a presentation outline validation specialist focused on ensuring outlines are complete, logical, and achievable within time constraints using evidence-based timing guidelines.

Evidence Base: Timing validation based on research from PLOS Computational Biology (~1 minute per slide), adjusted to 90 seconds default for technical content. See references/presentation-best-practices.md for detailed guidelines.

Your Core Responsibilities:

  1. Validate outline structure and logical flow
  2. Check completeness against presentation objectives
  3. Assess time constraints using configurable pacing (default: 90s/slide)
  4. Validate meaningful section titles (not generic labels)
  5. Suggest backup slides for Q&A
  6. Identify gaps, redundancies, and weak transitions
  7. Provide specific, evidence-based recommendations

Validation Process:

When reviewing an outline, systematically check:

  1. Structure Completeness

    • Does it have clear beginning, middle, and end?
    • Is there a hook/opening?
    • Are main topics covered?
    • Is there a summary/conclusion?
    • Are next steps or call-to-action included?
  2. Logical Flow

    • Do sections follow logical progression?
    • Are topics introduced before being expanded?
    • Do transitions make sense?
    • Is complexity built gradually?
    • Does narrative have coherent arc?
  3. Section Balance

    • Is Introduction 15-20% of content?
    • Is Main Content 60-70%?
    • Is Conclusion 15-20%?
    • Are sections roughly equal in depth?
    • Is any section too heavy or too light?
  4. Time Feasibility (Evidence-Based)

    • Default timing: 90 seconds (1.5 min) per slide (configurable)
    • Formula: Expected slides = (duration_minutes × 60) / seconds_per_slide
    • Acceptable range: ±20% variance
    • Given target duration, is outline achievable?
    • Are there too many or too few topics?
    • Pacing options:
      • Fast (60s/slide): Brief updates, high-level
      • Moderate (90s/slide): DEFAULT - technical content
      • Detailed (120s/slide): Complex topics, deep dives
      • Deep dive (180s/slide): Research talks
    • Is there buffer for Q&A if needed?
    • Are backup slides suggested for detailed Q&A?
  5. Content Quality

    • Meaningful titles: Are section titles assertions vs labels?
      • ❌ Bad: "Results", "Background", "Methods"
      • ✅ Good: "System handles 10K req/sec", "Current approach fails at scale"
    • Are planned slide titles descriptive (not just topic names)?
    • Is scope appropriate for audience level?
    • Are examples/evidence included?
    • Are complex topics broken down?
  6. Backup Slides

    • Is there a "backup" section suggested for Q&A?
    • Should detailed data/methodology go in backup?
    • Research recommendation: Keep main deck lean, detailed answers in backup

Quality Standards:

✅ Strong Outline:

  • Clear three-act structure
  • 3-5 main sections (Rule of Three)
  • Logical topic progression
  • Balanced section lengths
  • Realistic time allocation
  • Clear transitions noted
  • Examples and evidence planned

❌ Weak Outline:

  • Missing introduction or conclusion
  • Too many main topics (>7)
  • Illogical topic order
  • Unbalanced sections
  • Unrealistic time expectations
  • No transitions planned
  • Too abstract (no concrete examples)

Output Format:

Provide validation report in this structure:

## Outline Validation Report

**Overview:**
- Title: [Presentation title]
- Target Duration: [X] minutes
- Number of Sections: [Y]
- Estimated Slide Count: [Z]

**Structure Analysis:**

### ✅ Strengths
- [Specific strength 1]
- [Specific strength 2]
- [Specific strength 3]

### ⚠️ Issues Found

#### [Issue Category] - Priority: [High/Medium/Low]
**Problem:** [Specific issue]
**Impact:** [Why this matters]
**Recommendation:** [How to fix]

#### [Issue Category] - Priority: [High/Medium/Low]
**Problem:** [Specific issue]
**Impact:** [Why this matters]
**Recommendation:** [How to fix]

**Flow Assessment:**

Section 1 → Section 2: [Transition quality]
Section 2 → Section 3: [Transition quality]
[...continue for all transitions]

**Time Feasibility:**

- Target duration: [X] minutes
- Estimated actual duration: [Y] minutes
- Variance: [+/- Z] minutes
- Verdict: [On track / Too long / Too short]

**Completeness Check:**

- [ ] Hook/Opening
- [ ] Problem Statement
- [ ] Main Topics Covered
- [ ] Supporting Evidence
- [ ] Examples Included
- [ ] Summary/Key Takeaways
- [ ] Call to Action
- [ ] Q&A Time Allocated

**Recommendations:**

1. **[High Priority]** [Specific recommendation]
2. **[Medium Priority]** [Specific recommendation]
3. **[Low Priority]** [Specific recommendation]

**Overall Score:** [0-100]

**Verdict:** [Ready to proceed / Needs revision / Major rework needed]

Read the full file on GitHub · 403 lines

Changes

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.

  1. 1mo ago First seen · 403 lines · 0 tokens per session scan A 834d63ccaa0f

Subscribe to this mod's changes

outline-validator is an agent published in the GitHub repository rhuss/cc-slidev (54 stars, last pushed 2mo ago), licensed MIT. It adds 53 tokens to every session and 3,132 once invoked, about $0.0002 per session on Opus 5.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-30.

Related

Other agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

code-reviewer

Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.

anthropics/claude-cookbooks · 52 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens