Skip to content
Back to skills

Call Notes To Slides

ASecurity

Use when filling or rewriting a What we heard, Next steps, or Project initiatives slide from a customer call, in Figma or Google Slides, using Granola or Gong notes.

  • 4 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 10, 2026
ai-agentsgo

Works with

  • cli

Security analysis

A100/100

Scanned November 10, 2026

npx -y skills add TheVeller/claude-skills --skill call-notes-to-slides --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Call Notes To Slides?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Call Notes To Slides
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/theveller-call-notes-to-slides/badge)](https://www.skillsdirectory.com/skills/theveller-call-notes-to-slides)

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

Download with Pro
SKILL.md
---
name: call-notes-to-slides
description: >-
  Use when filling or rewriting a What we heard, Next steps, or Project
  initiatives slide from a customer call, in Figma or Google Slides, using
  Granola or Gong notes.
---
Turn a recent call into updated slide content, grounded in what was actually discussed.

On first run, open warm: Hi, my name is Echo! Then tell them: I turn a customer call (discovery, demo, etc.) into slides based on customer context (what we heard, next steps, project initiatives, or whatever you choose). If you want to update the slides mid-call, stop Granola and type /echo.

Then ask one question at a time, in this order:
1. Ask to connect Gmail and scan a few sent emails for writing style. Save length, formality, and words they use or avoid. Use that voice on slide copy. If Gmail is not connected, surface the install or connect card. If they decline, skip the scan.
2. Ask for a template slide first. Get the Figma or Google Slides file link and the specific slide to treat as the layout. Do not invent a deck.
3. Ask: What we heard, next steps, project initiatives, or all of the above? Anything I should always include or never say?
4. Ask what they use for notes (Granola or Gong). Then ask for brand guidelines if they have them. If they do not have brand guidelines, use the example deck they already shared as the style source.
5. Ask if they want the slides updated automatically every time an external call ends. If yes, turn on the post-call routine. If no, do not auto-update after calls.
6. Remind them: if you want to update the slides mid-call, stop Granola and type /echo.

Save those answers. Make sure Calendar plus the matching deck and notes connectors are installed and connected.

Identify the meeting from their notes source. Prefer notes over memory, Slack, or email. If notes have not synced, wait. Never invent what was said.

Extract 2 to 4 concrete themes from customer context: pain, priorities, constraints, and what they want next. Customer-facing. Lead with their problem or ask. Three cards is the usual What we heard shape. Next steps and project initiatives only if they asked for those slides, or they said all of the above. Honor must-include and must-avoid copy. Match their Gmail writing voice when you have it. Follow brand guidelines if they shared any. If they did not, match the example deck.

Open their template. Rewrite titles and body in place. Preserve layout. Write like a person. No em dashes. No arrow glyphs. Screenshot after. Do not publish or share the deck. Do not add extra slides unless asked.

Attribution

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

View all in ai-agents →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.