Audience-aware presentation framing for pitches, reports, and technical handoffs
SaferSkills independently audited Deck-Lens (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Deck Lens decides how a presentation should be told before producing anything. It is not a generic slide generator — it first picks the right narrative lens for the audience, context, and goal, then generates the matching structure, PPTX, or speech script.
The same project told through the wrong lens fails. A budget request told as a competition pitch feels like a performance; a competition pitch told as a government submission feels lifeless. Choosing the lens is the job.
Before anything else, understand who the deck is for and why it exists. Ask the user, or infer from what they've already said:
If the user already made this clear, don't re-ask — move to Step 2.
Deck Lens has four lenses. Match the situation to one:
| Lens | Use for | Core logic |
|---|---|---|
| Pitch | Competition, fundraising, client demo, product launch | Win attention → feel the pain → solution → pricing → call to action |
| Internal Report | Leadership / management / cross-department reporting | Conclusion first, then evidence (pyramid principle) |
| Government / Institution | Government bodies, public institutions, regulators | Legitimacy → objective evidence → reliability → verifiable outcomes → risk control |
| Technical Handoff | Developers, architects, technical client stakeholders | Requirement discovery → design → logic → implementation → testing → delivery |
Auto-detection signals:
Always confirm before proceeding. State your pick and the reasoning, then ask. Example:
This looks like Internal Report mode — the audience is internal leadership, so they'll want the conclusion up front, then the supporting evidence. Shall I proceed with this lens?
Do not skip confirmation even when the signal is strong. The user may know something about the room that you don't.
Hybrid situations: If a deck genuinely spans two lenses (e.g. a technical pitch, or an internal report that also requests budget), pick one primary lens and borrow at most one beat from the other. Name the borrowed beat explicitly. Do not blend all four — a four-way hybrid has no shape.
Once the lens is confirmed:
What output format do you need? 1. PPTX file — A ready-to-open slide deck 2. Speech script — A detailed written script for speaking or memorizing 3. Both — PPTX + matching speech script
Ask the user to describe (skip any they've already provided):
Default content depth is non-technical (no code, no architecture, no implementation detail) for every lens except Technical Handoff, which has its own depth rules.
modes/ and follow its structure beat by beat.templates/design-default.md. If the user has their own template, use theirs instead./mnt/skills/public/pptx/SKILL.md first and follow its instructions.modes/pitch.md — Pitchmodes/internal.md — Internal Reportmodes/government.md — Government / Institutionmodes/technical.md — Technical Handofftemplates/design-default.md — Default lens (Royal Blue, bright background). Replaceable — copy it, change the values, and point the skill at the new file.examples/spectrum-analyzer.md — A worked example using the Pitch lens.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.