Skip to content
Visual Design

PPT Visual

claude-office-skills

Plan slide hierarchy and reading order before choosing visuals; use one argument per slide and label evidence.

SKILL.md

---
name: knoveya-ppt-visual
description: "Plan slide hierarchy and reading order before choosing visuals; use one argument per slide and label evidence. Use for matching visual design work."
---

# PPT Visual

## Scope

Apply this guidance when the requested task matches the description. Honor the user's chosen outcome, repository rules, and existing authorization.

## Workflow

Plan slide hierarchy and reading order before choosing visuals; use one argument per slide and label evidence.

Before acting, inspect the relevant artifact and ask only for information that materially changes the result. Use existing tools and conventions; do not install dependencies, publish, send messages, deploy, or mutate external data unless the user has authorized that operation.

## Acceptance check

Text remains readable at presentation distance and charts preserve their meaning.

## Example task

Replace a paragraph-heavy results slide with a conclusion and supporting chart.

## Report

State what changed, the evidence checked, and what remains unverified. Do not claim a successful operation or completed test without observing it.

How to use

Copy the full block, including its frontmatter, into a new folder named knoveya-ppt-visual as SKILL.md. Review the instructions before enabling them. For Codex, a user skill normally lives in ~/.codex/skills/knoveya-ppt-visual/SKILL.md; check the current documentation for another agent's supported location. Do not overwrite an existing skill.

This is an independent Knoveya skill. No files are installed by this website.

Example

Replace a paragraph-heavy results slide with a conclusion and supporting chart.

Verify

Text remains readable at presentation distance and charts preserve their meaning.

Test the skill on a small, authorized example. File validation alone does not prove that an agent will make good decisions.

Limits

The skill supplies instructions, not tool access or expertise guarantees. Inspect generated work and preserve the user's approval boundaries.