Behind the scenes: how this class was built with AI

Watch

Chapters

Each chapter starts the class video at that moment.

1. Start planning in a chat that already has context8:33
2. Plan by voice: a live two-way conversation9:49
3. Voice mode on commutes and walks10:46
4. The first draft: 28 slides11:34
5. Grok’s “Canvas” is its artifact format12:01
6. The first canvas deck vs. Claude Design12:33
7. Give it examples: start from templates13:05
8. A prior deck built with Claude Design motion13:55
9. One slide per area, then a PDF14:50
10. A hero reel with Higgsfield16:40
11. Disclosure, and the models inside Higgsfield17:11
12. ElevenLabs: voices and Eleven Reader17:37
13. Voice cloning: original vs. AI18:27
14. Text-to-speech and transcription18:58
15. Don’t connect every tool to every assistant19:38
16. One connector layer across assistants20:08
17. Missing a connector? Have the agent build it21:13
18. For teams: observability and access control21:25
19. It gets faster as it learns your usage22:28
20. Q&A: connecting an assistant to Composio23:38
21. Zapier: where it fits24:04
22. Relevance AI for enterprise agents25:01
23. Storyboard before you spend credits25:45
24. Pick a direction and render26:32
25. The first-cut reel26:46
26. About a minute of work: good enough?27:15
27. Use short video to break up long content28:02

From the class

What this module covers

Before the agenda, JP showed how he produced this class: planning with an agent that already had the context, iterating the deck from a template, generating a hero reel and voice, and routing every tool through one connector layer.

• He planned the class in a voice conversation with a bot dedicated to his HRI work, which already knew where the class materials were.
• Voice mode is two-way: it listens while it talks and can be interrupted. He uses it on commutes and walks.
• The first draft was a 28-page deck, unrealistic for 90 minutes, so he went back and forth with it.
• In Grok, an artifact is called a Canvas. He uses the agent for speed and turns to specialist tools for heavy design.
• Good design needs examples. Unless you're a professional designer, start from a template you like.
• He showed a deck from an earlier class built in Claude Design. Animation adds polish and can also distract.
• He told the agent to rebuild the deck as one slide per area and to make a PDF. With an example, the result was far better, and still too busy to present. The deck file is not published on this page.
• For the hero reel he used Higgsfield, which he rates highly and not cheap. He disclosed in class that he is an investor in Higgsfield.
• ElevenLabs: realistic voices, and Eleven Reader to turn documents into audio he uses every week. Text-to-speech can narrate a presentation. A voice comparison was played in class and is not published as its own file.
• He does not connect every tool to every assistant. He routes tools through one connector layer, Composio, so a new assistant connects once instead of tool by tool.
• If a tool isn't already connected, have the agent build a custom connector once.
• For teams: observability so confidential data doesn't leak, managed onboarding, and no unauthorized tool connections.
• Repeated calls get faster as the layer learns how you use each tool.
• To connect an assistant, tell it to connect to Composio. After that, the apps you've added are available to it.
• Zapier wasn't designed for AI and is more manual, so he stopped using it day to day. Relevance AI suits enterprise agents with process, workflow and knowledge bases. He uses it for his business-council agents.
• Storyboard before you render. Video generation spends credits quickly. He picked one of two six-frame options and rendered that.
• About a minute of work produced a usable first cut. More time buys more quality. Short video at the start, middle or end of long content holds attention.

Try it

Put it to work

Video generation spends credits quickly. Storyboard and approve before rendering.

Ask IT before routing company tools through any third-party connector layer.

1. Plan your next presentation in a chat, or a voice chat, inside a project that already holds the background material.
2. Give the assistant one example deck or template you like, and ask for one slide per topic.
3. Export a PDF and compare it with a first draft made without the example.
4. Optional: ask for a six-frame storyboard of a 30-second intro and approve it before rendering any video.
5. List the tools you want every assistant to reach, and check which ones a connector layer already supports.

That's too many slides for a 90-minute session. Rebuild it as one slide per area, using the template I gave you, and create a PDF.

Use the attached template as the design reference. Match its layout, type and colors, and don't invent a new style. Flag any slide that doesn't fit the template.

Before generating any video, give me a six-frame storyboard in two different styles for a 30-second intro to [topic]. Don't render anything until I pick one.

Connect to Composio so you can use my other tools through it. Tell me which tools are available and which would need a custom connector.

Check your work

You're done when

• You've made one deck from an example template, one slide per area.
• If you tried video, you storyboarded before generating anything.
• You know which of your tools you'd connect once through a connector layer.

Tools

Mentioned in this module

• Claude Design — Used for an earlier class deck with motion.
• Higgsfield — Hero-reel video. He disclosed that he is an investor.
• ElevenLabs — Voices, text-to-speech and transcription. The voice comparison stays inside the class video.
• Composio — One connector layer across assistants.
• Relevance AI — Enterprise agents, including his business-council agents.

Also on the class guide

Written before class

• Pre-class guide: run of show

Between classes

WhatsApp and YouTube

Join the AI Practicum WhatsApp group

Hive Research Institute on YouTube