ppt-review

ppt-review is a skill for Claude Code, Codex from Orkas-AI/Orkas. It costs 2 tokens per session (3,340 once invoked), scanned A, original, MIT.

A review process for PowerPoint presentations that checks the file structure and examines rendered slide images. It requires visual evidence from the current presentation after changes.

In plain words
What is it for?
Use it after creating or editing a deck to validate it, render the relevant slides, and inspect layout or other visible defects.
Why use it?
It catches invalid presentation files and visual problems that source code or a successful tool result may not reveal.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it after creating or editing a deck to validate it, render the relevant slides, and inspect layout or other visible defects.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/orkas-ai/orkas/ppt-review
About the project

Orkas is a desktop application for commanding a team of AI agents through one chat, with a commander model assigning work to specialist agents in parallel or in sequence. People use it to coordinate research, writing, presentations, and software tasks while keeping files on their computer. The catalogue includes skills for extending the agents available to Orkas.

Orkas-AI/Orkas · 1,885 stars · on GitHub · orkas.ai

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.

Any agent
npx skills add Orkas-AI/Orkas --skill ppt-review
Clone the repo
git clone --depth 1 https://github.com/Orkas-AI/Orkas

Made for: Claude Code, Codex.

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 ppt-review

README.md
[![agentmods](https://agentmods.dev/badge/skills/orkas-ai/orkas/ppt-review/github.svg)](https://agentmods.dev/skills/orkas-ai/orkas/ppt-review)
Your own site
<a href="https://agentmods.dev/skills/orkas-ai/orkas/ppt-review"><img src="https://agentmods.dev/badge/skills/orkas-ai/orkas/ppt-review/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 ppt-review

Your own site · 80×15
<a href="https://agentmods.dev/skills/orkas-ai/orkas/ppt-review"><img src="https://agentmods.dev/badge/skills/orkas-ai/orkas/ppt-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,340 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00002 $0.03340
Opus 5 $0.00001 $0.01670
Sonnet 5 $0.00000 $0.00668
Haiku 4.5 $0.00000 $0.00334

Measured 11d ago against content hash a53b0428b72b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

ppt-review 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 11d 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.

resources/builtin/marketplace/agents/7e91cb9ec9e9/skills/ppt-review/SKILL.md · 188 lines

How it starts

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

PPT Review

Read this skill only after current office_review structural output and relevant rendered images exist. Do not use source code, a tool success flag, or the first-slide preview as a substitute for deck evidence.

Evidence set

  • Run office_review with action:"check_and_render" after every create or edit. Invalid OpenXML is a blocker, not a warning.
  • For a new deck, render every slide. For an existing deck, render every changed slide plus the cover, a representative unchanged content slide, and any slide whose theme, master, or shared element could be affected. Every render intended as current visual-defect evidence must set analysis_mode:"quality_review"; ordinary source understanding keeps the default understand mode.
  • After a repair affects multiple pages, request them together in one office_review call with action:"check_and_render", a pages array, and analysis_mode:"quality_review". One collected image set lets managed visual preprocessing analyze the affected pages as a batch. If one render fails after a valid check, retry only that page with action:"render" rather than rerendering the successful set.
  • Rendered image blocks are transient after the next assistant response. In the first response that sees each collected quality_review image set, write one concise plain-language evidence sentence before any follow-up tool calls: name the reviewed pages, concrete pass/defect observations, and the next action. This sentence is the durable visual-review state for later tool rounds and compaction. When exact edit paths are needed, request the targeted office_read calls together in that same response; do not rerender an unchanged artifact_revision merely to recover forgotten pixels.
  • Use the returned artifact_revision to distinguish current from stale check/render evidence and image_revision to compare rerenders. If an edit claimed to repair a visible defect but the affected page keeps the same image_revision, do not claim a visual repair: verify that the edited artifact revision was rendered, then make a supported layout/content change or retain the finding as unresolved.
  • If rendering is unavailable, mark visual checks not_run; do not infer a pass from structural validity.

Read the full file on GitHub · 188 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. 11d ago First seen · 188 lines · 2 tokens per session scan A a53b0428b72b

Subscribe to this mod's changes

ppt-review is a skill published in the GitHub repository Orkas-AI/Orkas (1,885 stars, last pushed yesterday), licensed MIT. It adds 2 tokens to every session and 3,340 once invoked, about $0.0000 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-30.