Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Presentation

ASecurity

Build a deck or talk — slides for a meeting, review, training, conference or client. Use when asked to "make a presentation", structure slides, or turn a document into a talk. For investor decks use pitch-deck instead.

2 stars
0 votes
0 copies
0 views
Added 10/3/2026
ai-agents

Works with

cli

Security Analysis

A100/100

Scanned 10/3/2026

$npx -y skills add ivanvp91/TRCode --skill presentation --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Presentation?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Presentation
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ivanvp91-presentation/badge)](https://www.skillsdirectory.com/skills/ivanvp91-presentation)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: presentation
description: Build a deck or talk — slides for a meeting, review, training, conference or client. Use when asked to "make a presentation", structure slides, or turn a document into a talk. For investor decks use pitch-deck instead.
description_ru: Собрать презентацию или выступление — слайды для встречи, разбора, обучения, конференции или клиента. Когда просят «сделай презентацию», выстроить слайды или превратить документ в доклад. Для инвесторов — pitch-deck.
triggers: презентация, презентацию, презу, слайд, слайды, slides, deck, дек, доклад, выступление, keynote, powerpoint
---

# Presentations

## 1. Three questions before any slide
- **Audience**: who is in the room, what they already know, what they care about.
- **Decision**: what they must think, feel or approve when you finish. A deck without a decision is a document — write a document instead.
- **Format**: presented live (slides support you, few words) or sent to read (slides carry the argument, more words). These are different artefacts; do not build one and use it as the other.

## 2. Write the story first, in text
Draft the slide titles as full sentences that state the claim: "Churn comes from onboarding, not price". Read the titles in order — if that sequence alone does not make the argument, no amount of design will save it. Fix it here, where editing is cheap.

Default arc: **Situation → Complication → Question → Answer → Evidence → What we need**. Put the answer early for a senior audience; build up to it only when you must bring people along.

## 3. One idea per slide
The title is the idea. The body is the single piece of evidence for it. If a slide needs two titles, it is two slides. Six to ten words per bullet, at most four bullets — or better, replace the bullets with one chart, one image, or three words.

## 4. Numbers and charts
- One message per chart, and the message is the chart's title.
- Simplest form that carries it: line for trend, bar for comparison, single big number for a headline metric.
- Label directly instead of using a legend; drop gridlines, borders and 3D.
- Always state the source and the period. Round hard — "≈40%", not "39.7431%".

## 5. Visual discipline
Consistent template: same title position, same type scale (title / body / caption only), one accent colour, generous margins. Minimum 24pt body text for a room. Never paste a screenshot of a table nobody can read — crop to the row that matters, or restate it as a number.

## 6. Endings and appendix
Close with the ask and the next step, not "Thank you / Questions". Move backup detail, methodology and long tables into an appendix after the close — it is what makes a deck survive the Q&A.

## What not to do
- No agenda slide for a deck under ten slides.
- No wall of text read aloud.
- No animation that delays information.
- No slide you cannot explain in one sentence — cut it.

## Answer format
Slide-by-slide outline: number, sentence-title, what is on the slide, what you say. If asked to produce the deck itself, generate a self-contained HTML file with one section per slide (keyboard navigation, 16:9, the type/colour rules above) or Markdown slides — and say which tool it targets.

Attribution

ivanvp91ivanvp91
View sourceSee grades on GitHubMore from ivanvp91 →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698431 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →