It works in your language: write to it in Italian, Spanish or English, and it answers and builds the slides in that language.
Overview
It works in your language: write to it in Italian, Spanish or English, and it answers and builds the slides in that language. The slides after a client call always say the same three things: what was done, what is blocked, what happens next. The facts are already in the transcript, and your brand and tone never change. So the agent writes the deck, and you only check it. and unzip the folder: it is called presentation-agent-main. With git: The instructions for the agent are in CLAUDE.md (Claude Code) and AGENTS.md (Codex and the others), same text. The first time, the agent sees the repo is empty and asks a few questions: what presentation you want, your company, what you do, logo, colors, fonts, how you write, who you are. With your answers it writes company/ and people/. You do it once, it takes five minutes. Export the transcript from your notetaker and drag the file into the chat, or paste the text. The agent saves it in meetings/YYYY-MM-DD_ .
README
The idea in three lines. The slides after a client call always say the same three things: what was done, what is blocked, what happens next. The facts are already in the transcript, and your brand and tone never change. So the agent writes the deck, and you only check it.
Contents
- What you need
- How it works
- What the agent reads
- The progress update
- Corrections
- How it is organized
- A new presentation type
- Your copy stays yours
What you need
| Why | |
|---|---|
| A coding agent | Claude Code, Codex or similar. It reads the files and writes the presentation. You need its subscription. |
| GitHub | You download the repo from here. You need an account only if you want to keep your copy online. |
| Your brand guidelines | Logo, colors, fonts. The logo and two colors are enough. |
| A notetaker | Fireflies, Granola, tl;dv, Otter, or the Google Meet or Teams transcript. You need the transcript as text. |
| Google Chrome | For the layout check and the PDF export. |
| Node.js | To run the layout check and the export. Then cd deck-kit && npm install, once. |
How it works
1. Download the repo and do the onboarding
Download the ZIP and unzip the folder: it is called presentation-agent-main. With git:
git clone https://github.com/CommerceClarity/presentation-agent.git
cd presentation-agent
claude
The instructions for the agent are in CLAUDE.md (Claude Code) and AGENTS.md (Codex and the others), same text.
The first time, the agent sees the repo is empty and asks a few questions: what presentation you want, your company, what you do, logo, colors, fonts, how you write, who you are. With your answers it writes company/ and people/. You do it once, it takes five minutes.
2. Upload the meeting transcript
Export the transcript from your notetaker and drag the file into the chat, or paste the text. The agent saves it in meetings/YYYY-MM-DD_.md and, if the client is new, creates clients/.md with what the meeting says. It shows you what it saved and asks you to fill in what is missing.
3. Ask for the presentation
Make me the progress update for today’s meeting with Rossi.
The agent reads company, client and meeting. It proposes the outline, waits for your ok, builds the slides, checks the layout and puts the folder in your Downloads. Open index.html in the browser. The folder already holds style, logo and fonts, so you can send it as it is.
What the agent reads
- Every number, name and date comes from a file. If a fact the slide needs is missing, it writes
[TO VERIFY]and tells you when it delivers. - Before the slides it writes an extract,
extract.md: every fact with the transcript sentence it comes from. - Only this folder counts. The agent does not use local memory, connectors or the name the session runs under. If it is not in the repo and you did not say it, it asks.
The progress update
The deck you send the client after the progress call. The client reads it in two minutes and knows what was done, what you are waiting for from them, and what happens before the next meeting. Same five slides, same order, every time. Full spec in skills/deck-progress-update/SKILL.md.
Corrections
Open the presentation, gear icon at the bottom left, Review. Write or draw on the slides, press Copy feedback and export and paste the text into the chat. The text is enough. An image deck-feedback.png with your drawings is downloaded too: opened from your disk it shows the drawings but not the slide behind them.
How it is organized
presentation-agent/
├── CLAUDE.md · AGENTS.md # the file the agent reads first (same text)
├── company/ # your company: profile, voice, brand (written by the onboarding)
├── people/ # who uses the repo: role, language, how they write
├── clients/ # one file per client
├── meetings/ # one file per meeting, with the link to the client
├── skills/ # onboarding + one presentation type per folder
│ ├── onboarding/
│ └── deck-progress-update/
├── deck-kit/ # style, navigation, layout check, PDF export
└── examples/ # presentations kept as a reference
Meetings and clients are separate. A meeting points to its client with the client: field, so all the meetings of a client are one search away. The slide engine is documented in deck-kit/README.md.
A new presentation type
Need a kickoff, a proposal, anything else? Ask the agent. It copies skills/deck-progress-update/ to skills/deck-/, asks you what each slide must say, rewrites the outline and adds the type to CLAUDE.md and AGENTS.md. It never builds a presentation without its skill.
Your copy stays yours
After the onboarding the folder holds your company’s data, your clients and the meeting transcripts. If you upload it to GitHub, make it private.
Built by CommerceClarity.
Recommended Tools
Try a different keyword or remove a filter.
Install
npx skillfish add commerceclarity/presentation-agent