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

Title Footer Page Number Consistency

ASecurity

Aligns titles and makes footers, dividers, and page numbers consistent so a long deck reads as one document.

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

Works with

cli

Security Analysis

A100/100

Scanned 9/19/2026

Install to Claude Code

$npx -y skills add andreworia/claude-pptx-skills --skill title-footer-page-number-consistency --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Title Footer Page Number Consistency?

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

Security grade badge for Title Footer Page Number Consistency
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/andreworia-title-footer-page-number-consistency/badge)](https://www.skillsdirectory.com/skills/andreworia-title-footer-page-number-consistency)

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

Download with Pro
Files
SKILL.md
---
name: title-footer-page-number-consistency
description: Aligns titles and makes footers, dividers, and page numbers consistent so a long deck reads as one document.
---

# Title, Footer and Page-Number Consistency

## When to use

Use this skill when titles jump position and footers or page numbers are inconsistent. Symptoms include a title that sits at a different height on every slide, a footer with the project name on some slides and blank on others, page numbers that are present, missing, or in a different spot, and section dividers that do not match. Run this first in Stage 4, before the full audit, because these are the repeated elements a reviewer notices immediately.

## What it does

It makes the deck's persistent furniture consistent: titles at one position and style, a footer with the same content and placement throughout, page numbers present and uniform, and dividers that share one design. The result is a deck that reads as a single, finished document rather than a stitched-together file.

## Method

Persistent elements belong on the slide master and layouts, not hand-placed per slide. The job is to get them onto the master and uniform across the deck.

1. **Fix titles to one position.** Confirm every title is in the Title placeholder at the layout's position (the Grid skill handles drift; here confirm the result). Titles should share one top edge, one left edge, one size, and one case rule across the deck.

2. **Standardize the footer.** Decide the footer content from the brand: typically the confidentiality note, the project or client name, or a copyright line. Set it once via Insert then Header and Footer (or on the master) and apply to all, so it is identical on every slide. Remove per-slide manual footers.

3. **Enforce page numbers.** Turn on the slide-number placeholder and confirm it appears on every content slide in the brand's position and style. Decide the convention: whether the title slide and dividers carry a number, and whether numbering is "n" or "n of N." Apply it uniformly.

4. **Unify dividers.** Make every section divider use the same layout, the same background, the same title treatment, and the same numbering ("Part 1," "Part 2") so sections feel parallel.

5. **Handle the title slide and closing exceptions.** The title slide and closing slide usually omit the footer and page number by design. Set these exceptions deliberately rather than leaving them inconsistent by accident.

6. **Check the running header if present.** If the brand uses a running header or a section label that updates per section, confirm it reflects the right section on each slide and is in the same place throughout.

7. **Confine furniture to the safe zone.** Keep footers and page numbers inside the safe zone and out of the trim, and keep the footer logo's clear space (coordinate with the Logo skill).

## Inputs

- The deck.
- The brand rules for footer content, page-number convention and position, and divider design. If undocumented, ask, or state a single convention and apply it.

## Output format

A consistency report:

- The chosen conventions: title position and case, footer content and placement, page-number convention and position, divider design, and the title or closing exceptions.
- A per-slide list of furniture that deviates and the fix (move title, set footer, add page number, restyle divider).

Close with a confirmation that titles, footers, page numbers, and dividers are uniform across the deck.

## Example

Input: a 30-slide deck where page numbers appear on about half the slides and the footer text varies.

Output:

- Conventions: title at the layout position, sentence case; footer "Confidential. Project Atlas." bottom-left; page numbers "n" bottom-right, off on the title and dividers; dividers on the Section Header layout numbered "Part n."
- Set the footer and page number on the master and apply to all; turn off on the title and dividers.
- Restyle two dividers that used the wrong layout.
- Result: uniform titles, footer, page numbers, and dividers.

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 →