Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
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

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Action Title Writer

ASecurity

Rewrite topic-label slide titles into headline action titles that state the so-what. Use when titles name the subject instead of delivering the message.

6 stars
0 votes
0 copies
1 views
Added 9/19/2026
ai-agentsgo

Security Analysis

A100/100

Scanned 9/19/2026

Install to Claude Code

$npx -y skills add andreworia/claude-powerpoint-skills --skill action-title-writer --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Action Title Writer?

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

Security grade badge for Action Title Writer
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/andreworia-action-title-writer/badge)](https://www.skillsdirectory.com/skills/andreworia-action-title-writer)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: action-title-writer
description: Rewrite topic-label slide titles into headline action titles that state the so-what. Use when titles name the subject instead of delivering the message.
---

# Action Title Writer

## When to use
Use this when slide titles read like file names: "Q3 Revenue", "Market Overview", "Competitive Landscape". They tell the reader what the slide is about but not what it says. You need every title rewritten as an action title, a full sentence that states the slide's single message, so a reader who reads only the titles still gets the whole argument.

## What it does
It converts each topic-label title into an action title: a complete declarative sentence carrying the slide's so-what. Read top to bottom, the action titles alone form the storyline of the deck. The body of the slide becomes proof of the title rather than a place to hunt for the point.

## Method
An action title states the conclusion of the slide, not its contents. The test is the "title-only read": if someone reads only the titles of every page, they should reconstruct the argument. Topic labels fail this test; action titles pass it.

1. Find the one message. For each slide, ask what single thing this page proves. If it proves two things, it is two slides, or one of the two is really backup. The action title carries that one message and nothing else.

2. Write it as a full sentence with a verb. "Revenue" becomes "Revenue grew 12 percent, but all of it came from one account". A label has no verb and no claim. An action title has both. The verb is where the so-what lives, so choose a real one (grew, fell, shifted, concentrated, lagged), not a placeholder (relates to, concerns).

3. State the conclusion, not the data. The chart shows the data; the title states what the data means. "Three competitors entered the segment" is closer to a label. "Competitor entry has commoditised the segment, so we cannot win on price here" is the conclusion the slide exists to support.

4. Make it specific and falsifiable. A good action title is a claim someone could dispute. "We are well positioned" is vacuous. "We hold the only distribution network with national coverage, which is the one advantage rivals cannot copy this year" can be argued with, which means it says something.

5. Keep it to one readable line. An action title is a headline, not a paragraph. Aim for a single line. If it needs two clauses, make sure both serve the one message; cut any qualifier that hedges rather than informs.

6. Check the title-only read. Lay the action titles in sequence and read just them. They should flow as a coherent argument that matches the governing thought. Where the flow jumps, a slide is missing or out of order. Where two titles say the same thing, two slides are redundant. This check doubles as a storyline audit.

7. Align the body to the title. After rewriting, confirm the slide body actually proves the title. A sharp action title over a body that argues something else is worse than a label, because it promises and does not deliver.

## Inputs
- The current slide titles (and ideally the slide contents or a one-line description of each).
- The governing thought, so the title-only read can be checked against it.

## Output format
Return, per slide: the original title, the rewritten action title, and a one-line note on whether the slide body supports it. Then the full title-only read as a numbered sequence, with a note on any gap, jump, or redundancy it reveals.

## Example
Original: "Customer Segmentation"
Action title: "Two segments drive 80 percent of profit, so the growth plan should concentrate there, not spread across all five."

Original: "Pricing Analysis"
Action title: "We hold pricing power only in the enterprise segment, which is where any price increase should be taken."

Title-only read (excerpt): 1) Growth has stalled and the old model has peaked. 2) Two segments drive most of profit. 3) We hold pricing power only in enterprise. Note: the sequence flows; consider whether a slide on the mid-market loss belongs between 2 and 3.

Attribution

andreworiaandreworia
View sourceMore from andreworia →
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

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1074701 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', ...

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

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, 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.

691 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →