deck-architect-brand-validator

Design presentation narratives and validate finished decks against evidence and brand rules.

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/Cloud-Byte-Consulting/plugins --skill deck-architect-brand-validator-cloud-byte-consulting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deck-architect-brand-validator
Source: https://github.com/Cloud-Byte-Consulting/plugins/tree/main/prompt-workflows/skills/deck-architect-brand-validator
Command: npx skills add https://github.com/Cloud-Byte-Consulting/plugins --skill deck-architect-brand-validator-cloud-byte-consulting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning spreadsheet analysis, memos, or source material into a decision-driving presentation is hard: slides often end up with vague topic titles, unsupported numbers, and inconsistent branding. This Skill structures the deck before any slide is rendered and then audits the finished deck for evidence and brand compliance. ## Core Features & Use Cases - Two-phase workflow: Phase 1 builds a deck architecture (audience, decision, narrative spine, slide map with claim headlines, sources, assumptions, and review status) and pauses for approval before any rendering; Phase 2 validates the finished deck slide by slide. - Evidence-backed slide map: Each slide gets a sentence-form claim headline, role in the argument, supporting source IDs, workbook references, chart needs, and a verified / needs review / unsupported / conflicting status. - Brand and accuracy validation: Returns a table of issues per slide with severity (must fix / should fix / polish), evidence, and recommended repairs covering attribution, number accuracy, template conformance, typography, density, and compliance risks. - Use Case: You have a quarterly analysis workbook and a company template. Use this Skill to plan an executive deck with sourced claims, get the slide map approved, then audit the rendered deck so every number traces back to the workbook before it goes to the board. ## Quick Start Use the deck-architect-brand-validator skill to turn my analysis workbook into an executive deck plan and then validate the finished slides against our brand rules.

Frequently Asked Questions about deck-architect-brand-validator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn spreadsheet analysis into an executive presentation?

Start with a deck architecture phase: define the audience, the decision the deck must support, and a one-sentence narrative spine. Then build a slide map where each slide has a sentence-form claim headline linked to specific workbook tabs, cells, and source IDs before rendering anything.

How do I validate a PowerPoint deck against brand guidelines?

Review every slide against a checklist covering claim specificity, source attribution, number accuracy, chart traceability, template conformance, typography, color, density, and readability. Report findings as a table with severity levels (must fix, should fix, polish), evidence, and recommended repairs.

What makes a good slide headline for decision-driven decks?

A good headline is a full sentence stating a specific, decision-relevant claim, not a generic topic or section title. Every important number in the claim must carry a source and date so reviewers can verify it against the underlying material.

When should deck planning happen before slide rendering?

Planning should always precede rendering when the deck must drive a decision or be client- or board-safe. The slide map with claims, sources, assumptions, and review status is approved first, preventing polished design from hiding unsupported claims.

What are the limitations of automated deck validation?

Validation enumerates issues with severity and recommended repairs but does not rewrite the deck itself. It also depends on access to the source material and brand system; without them, claims cannot be verified or checked for template conformance.