WEBVTT Kind: captions Language: en 00:00:00.160 --> 00:00:02.950 align:start position:0% Take<00:00:00.320> a<00:00:00.400> look<00:00:00.560> at<00:00:00.719> this.<00:00:01.280> A<00:00:01.520> branded<00:00:02.080> video,<00:00:02.639> a 00:00:02.950 --> 00:00:02.960 align:start position:0% Take a look at this. A branded video, a 00:00:02.960 --> 00:00:05.510 align:start position:0% Take a look at this. A branded video, a high<00:00:03.280> quality<00:00:03.679> Instagram<00:00:04.160> ad,<00:00:04.960> content 00:00:05.510 --> 00:00:05.520 align:start position:0% high quality Instagram ad, content 00:00:05.520 --> 00:00:07.749 align:start position:0% high quality Instagram ad, content scheduled<00:00:05.920> and<00:00:06.160> posted<00:00:06.560> across<00:00:07.120> YouTube, 00:00:07.749 --> 00:00:07.759 align:start position:0% scheduled and posted across YouTube, 00:00:07.759 --> 00:00:10.709 align:start position:0% scheduled and posted across YouTube, Instagram,<00:00:08.320> and<00:00:08.559> threads.<00:00:09.599> All<00:00:09.840> from<00:00:10.240> one 00:00:10.709 --> 00:00:10.719 align:start position:0% Instagram, and threads. All from one 00:00:10.719 --> 00:00:13.190 align:start position:0% Instagram, and threads. All from one single<00:00:11.120> command.<00:00:11.679> We<00:00:11.920> didn't<00:00:12.240> do<00:00:12.400> any<00:00:12.639> of<00:00:12.880> this 00:00:13.190 --> 00:00:13.200 align:start position:0% single command. We didn't do any of this 00:00:13.200 --> 00:00:16.070 align:start position:0% single command. We didn't do any of this manually.<00:00:14.000> We<00:00:14.240> didn't<00:00:14.400> hire<00:00:14.719> a<00:00:14.960> team.<00:00:15.599> We<00:00:15.759> just 00:00:16.070 --> 00:00:16.080 align:start position:0% manually. We didn't hire a team. We just 00:00:16.080 --> 00:00:19.590 align:start position:0% manually. We didn't hire a team. We just ran<00:00:16.720> five<00:00:17.119> AI<00:00:17.440> agents<00:00:17.840> inside<00:00:18.320> clock<00:00:18.720> code<00:00:19.279> and 00:00:19.590 --> 00:00:19.600 align:start position:0% ran five AI agents inside clock code and 00:00:19.600 --> 00:00:21.670 align:start position:0% ran five AI agents inside clock code and they<00:00:19.920> handled<00:00:20.480> everything<00:00:20.960> automatically. 00:00:21.670 --> 00:00:21.680 align:start position:0% they handled everything automatically. 00:00:21.680 --> 00:00:23.269 align:start position:0% they handled everything automatically. So,<00:00:21.840> if<00:00:22.000> you<00:00:22.160> have<00:00:22.320> been<00:00:22.480> watching<00:00:22.720> the<00:00:22.960> AI 00:00:23.269 --> 00:00:23.279 align:start position:0% So, if you have been watching the AI 00:00:23.279 --> 00:00:25.349 align:start position:0% So, if you have been watching the AI space<00:00:23.519> lately,<00:00:24.080> you<00:00:24.320> already<00:00:24.640> know<00:00:24.960> how 00:00:25.349 --> 00:00:25.359 align:start position:0% space lately, you already know how 00:00:25.359 --> 00:00:28.070 align:start position:0% space lately, you already know how popular<00:00:25.840> clock<00:00:26.480> is.<00:00:26.960> And<00:00:27.119> with<00:00:27.439> open<00:00:27.760> claw 00:00:28.070 --> 00:00:28.080 align:start position:0% popular clock is. And with open claw 00:00:28.080 --> 00:00:30.550 align:start position:0% popular clock is. And with open claw blowing<00:00:28.480> up,<00:00:29.119> everyone<00:00:29.519> is<00:00:29.840> talking<00:00:30.240> about 00:00:30.550 --> 00:00:30.560 align:start position:0% blowing up, everyone is talking about 00:00:30.560 --> 00:00:33.750 align:start position:0% blowing up, everyone is talking about how<00:00:30.880> to<00:00:31.119> build<00:00:31.439> multi-<00:00:31.840> aents<00:00:32.320> workflow.<00:00:33.440> But 00:00:33.750 --> 00:00:33.760 align:start position:0% how to build multi- aents workflow. But 00:00:33.760 --> 00:00:35.830 align:start position:0% how to build multi- aents workflow. But most<00:00:34.239> people<00:00:34.559> are<00:00:34.880> actually<00:00:35.120> burning<00:00:35.520> through 00:00:35.830 --> 00:00:35.840 align:start position:0% most people are actually burning through 00:00:35.840 --> 00:00:38.869 align:start position:0% most people are actually burning through tokens<00:00:36.719> and<00:00:37.040> getting<00:00:37.440> nowhere<00:00:37.920> fast.<00:00:38.559> So 00:00:38.869 --> 00:00:38.879 align:start position:0% tokens and getting nowhere fast. So 00:00:38.879 --> 00:00:40.150 align:start position:0% tokens and getting nowhere fast. So today<00:00:39.120> we're<00:00:39.440> going<00:00:39.520> to<00:00:39.680> show<00:00:39.840> you<00:00:39.920> the 00:00:40.150 --> 00:00:40.160 align:start position:0% today we're going to show you the 00:00:40.160 --> 00:00:41.990 align:start position:0% today we're going to show you the smarter<00:00:40.480> way<00:00:40.640> to<00:00:40.800> do<00:00:40.960> this.<00:00:41.360> We<00:00:41.600> are<00:00:41.680> building 00:00:41.990 --> 00:00:42.000 align:start position:0% smarter way to do this. We are building 00:00:42.000 --> 00:00:44.310 align:start position:0% smarter way to do this. We are building a<00:00:42.320> full<00:00:42.719> social<00:00:43.040> media<00:00:43.360> marketing<00:00:43.760> engine. 00:00:44.310 --> 00:00:44.320 align:start position:0% a full social media marketing engine. 00:00:44.320 --> 00:00:46.229 align:start position:0% a full social media marketing engine. Five<00:00:44.640> agents<00:00:45.040> working<00:00:45.280> together.<00:00:46.000> One 00:00:46.229 --> 00:00:46.239 align:start position:0% Five agents working together. One 00:00:46.239 --> 00:00:48.470 align:start position:0% Five agents working together. One researches<00:00:46.800> your<00:00:47.120> content<00:00:47.440> ideas.<00:00:48.160> One 00:00:48.470 --> 00:00:48.480 align:start position:0% researches your content ideas. One 00:00:48.480 --> 00:00:50.790 align:start position:0% researches your content ideas. One builds<00:00:48.800> actual<00:00:49.200> video<00:00:49.520> using<00:00:49.920> Remotion.<00:00:50.559> One 00:00:50.790 --> 00:00:50.800 align:start position:0% builds actual video using Remotion. One 00:00:50.800 --> 00:00:53.910 align:start position:0% builds actual video using Remotion. One designs<00:00:51.280> your<00:00:51.520> Instagram<00:00:51.920> ads<00:00:52.239> in<00:00:52.480> HTML.<00:00:53.600> One 00:00:53.910 --> 00:00:53.920 align:start position:0% designs your Instagram ads in HTML. One 00:00:53.920 --> 00:00:56.150 align:start position:0% designs your Instagram ads in HTML. One writes<00:00:54.239> your<00:00:54.480> captions<00:00:54.879> for<00:00:55.120> every<00:00:55.440> platform. 00:00:56.150 --> 00:00:56.160 align:start position:0% writes your captions for every platform. 00:00:56.160 --> 00:00:58.549 align:start position:0% writes your captions for every platform. and<00:00:56.559> one<00:00:56.800> schedules<00:00:57.360> and<00:00:57.600> posts<00:00:58.079> everything 00:00:58.549 --> 00:00:58.559 align:start position:0% and one schedules and posts everything 00:00:58.559 --> 00:01:00.869 align:start position:0% and one schedules and posts everything automatically.<00:00:59.440> So<00:00:59.600> basically<00:01:00.160> a<00:01:00.559> fivep 00:01:00.869 --> 00:01:00.879 align:start position:0% automatically. So basically a fivep 00:01:00.879 --> 00:01:03.430 align:start position:0% automatically. So basically a fivep person<00:01:01.280> content<00:01:01.680> team<00:01:02.160> running<00:01:02.640> inside<00:01:03.120> your 00:01:03.430 --> 00:01:03.440 align:start position:0% person content team running inside your 00:01:03.440 --> 00:01:06.230 align:start position:0% person content team running inside your clock<00:01:03.840> code<00:01:04.400> for<00:01:04.720> the<00:01:04.879> cost<00:01:05.199> of<00:01:05.519> just<00:01:05.760> a<00:01:06.000> few 00:01:06.230 --> 00:01:06.240 align:start position:0% clock code for the cost of just a few 00:01:06.240 --> 00:01:09.670 align:start position:0% clock code for the cost of just a few API<00:01:06.640> calls.<00:01:07.360> Let's<00:01:07.680> get<00:01:07.840> into<00:01:08.080> it.<00:01:09.280> Let's 00:01:09.670 --> 00:01:09.680 align:start position:0% API calls. Let's get into it. Let's 00:01:09.680 --> 00:01:10.950 align:start position:0% API calls. Let's get into it. Let's start<00:01:09.920> by<00:01:10.159> walking<00:01:10.479> through<00:01:10.720> the 00:01:10.950 --> 00:01:10.960 align:start position:0% start by walking through the 00:01:10.960 --> 00:01:13.910 align:start position:0% start by walking through the environment.<00:01:12.080> And<00:01:12.400> before<00:01:12.799> any<00:01:13.040> agent<00:01:13.439> runs, 00:01:13.910 --> 00:01:13.920 align:start position:0% environment. And before any agent runs, 00:01:13.920 --> 00:01:17.109 align:start position:0% environment. And before any agent runs, we<00:01:14.240> just<00:01:14.560> need<00:01:15.040> three<00:01:15.439> things<00:01:15.840> in<00:01:16.080> place.<00:01:16.960> And 00:01:17.109 --> 00:01:17.119 align:start position:0% we just need three things in place. And 00:01:17.119 --> 00:01:19.670 align:start position:0% we just need three things in place. And I<00:01:17.360> want<00:01:17.520> to<00:01:17.600> go<00:01:17.759> through<00:01:18.080> each<00:01:18.400> one<00:01:19.119> because 00:01:19.670 --> 00:01:19.680 align:start position:0% I want to go through each one because 00:01:19.680 --> 00:01:22.789 align:start position:0% I want to go through each one because understanding<00:01:20.320> what<00:01:20.880> and<00:01:21.360> why<00:01:22.159> can<00:01:22.400> make<00:01:22.640> the 00:01:22.789 --> 00:01:22.799 align:start position:0% understanding what and why can make the 00:01:22.799 --> 00:01:25.190 align:start position:0% understanding what and why can make the rest<00:01:22.960> of<00:01:23.119> this<00:01:23.439> build<00:01:23.840> make<00:01:24.080> sense.<00:01:24.799> This<00:01:25.040> is 00:01:25.190 --> 00:01:25.200 align:start position:0% rest of this build make sense. This is 00:01:25.200 --> 00:01:26.870 align:start position:0% rest of this build make sense. This is where<00:01:25.439> we<00:01:25.600> put<00:01:25.920> all<00:01:26.159> the<00:01:26.400> creative 00:01:26.870 --> 00:01:26.880 align:start position:0% where we put all the creative 00:01:26.880 --> 00:01:29.109 align:start position:0% where we put all the creative references.<00:01:27.759> And<00:01:28.000> right<00:01:28.240> now<00:01:28.400> we<00:01:28.640> have<00:01:28.799> sample 00:01:29.109 --> 00:01:29.119 align:start position:0% references. And right now we have sample 00:01:29.119 --> 00:01:31.990 align:start position:0% references. And right now we have sample assets<00:01:29.520> in<00:01:29.759> here.<00:01:30.479> Things<00:01:30.799> the<00:01:31.040> AI<00:01:31.439> can<00:01:31.680> pull 00:01:31.990 --> 00:01:32.000 align:start position:0% assets in here. Things the AI can pull 00:01:32.000 --> 00:01:35.670 align:start position:0% assets in here. Things the AI can pull from<00:01:32.560> as<00:01:33.040> official<00:01:34.079> and<00:01:34.479> creative<00:01:34.880> context 00:01:35.670 --> 00:01:35.680 align:start position:0% from as official and creative context 00:01:35.680 --> 00:01:37.830 align:start position:0% from as official and creative context when<00:01:36.079> it<00:01:36.320> is<00:01:36.560> generating<00:01:37.119> output<00:01:37.439> for<00:01:37.680> the 00:01:37.830 --> 00:01:37.840 align:start position:0% when it is generating output for the 00:01:37.840 --> 00:01:39.830 align:start position:0% when it is generating output for the brand.<00:01:38.320> So<00:01:38.479> you<00:01:38.720> can<00:01:38.799> think<00:01:38.960> of<00:01:39.119> this<00:01:39.360> as<00:01:39.600> the 00:01:39.830 --> 00:01:39.840 align:start position:0% brand. So you can think of this as the 00:01:39.840 --> 00:01:42.390 align:start position:0% brand. So you can think of this as the mood<00:01:40.240> board<00:01:40.799> that<00:01:41.040> your<00:01:41.360> team<00:01:41.600> would<00:01:41.920> normally 00:01:42.390 --> 00:01:42.400 align:start position:0% mood board that your team would normally 00:01:42.400 --> 00:01:45.030 align:start position:0% mood board that your team would normally keep<00:01:42.720> in<00:01:42.880> a<00:01:43.119> shared<00:01:43.439> drive.<00:01:44.000> And<00:01:44.240> except<00:01:44.640> here, 00:01:45.030 --> 00:01:45.040 align:start position:0% keep in a shared drive. And except here, 00:01:45.040 --> 00:01:47.510 align:start position:0% keep in a shared drive. And except here, Claude<00:01:45.520> has<00:01:45.759> direct<00:01:46.159> access<00:01:46.720> here.<00:01:47.200> And<00:01:47.360> then 00:01:47.510 --> 00:01:47.520 align:start position:0% Claude has direct access here. And then 00:01:47.520 --> 00:01:50.149 align:start position:0% Claude has direct access here. And then the<00:01:47.680> next<00:01:47.840> one<00:01:48.079> is<00:01:48.320> the<00:01:48.560> knowledge<00:01:49.040> folder.<00:01:49.840> So 00:01:50.149 --> 00:01:50.159 align:start position:0% the next one is the knowledge folder. So 00:01:50.159 --> 00:01:53.270 align:start position:0% the next one is the knowledge folder. So you<00:01:50.399> can<00:01:50.560> think<00:01:50.640> of<00:01:50.799> this<00:01:51.040> like<00:01:51.360> a<00:01:51.680> brand<00:01:52.399> brain 00:01:53.270 --> 00:01:53.280 align:start position:0% you can think of this like a brand brain 00:01:53.280 --> 00:01:55.030 align:start position:0% you can think of this like a brand brain like<00:01:53.600> everything<00:01:54.000> Claude<00:01:54.399> needs<00:01:54.640> to<00:01:54.799> know 00:01:55.030 --> 00:01:55.040 align:start position:0% like everything Claude needs to know 00:01:55.040 --> 00:01:57.510 align:start position:0% like everything Claude needs to know about<00:01:55.360> who<00:01:55.680> this<00:01:55.920> brand<00:01:56.159> is<00:01:56.560> and<00:01:56.960> how<00:01:57.200> it 00:01:57.510 --> 00:01:57.520 align:start position:0% about who this brand is and how it 00:01:57.520 --> 00:01:59.830 align:start position:0% about who this brand is and how it communicates<00:01:58.479> and<00:01:58.719> we<00:01:58.960> have<00:01:59.200> three<00:01:59.439> files 00:01:59.830 --> 00:01:59.840 align:start position:0% communicates and we have three files 00:01:59.840 --> 00:02:02.870 align:start position:0% communicates and we have three files inside.<00:02:00.560> The<00:02:00.799> first<00:02:00.960> one<00:02:01.280> is<00:02:01.759> brand<00:02:02.159> identity. 00:02:02.870 --> 00:02:02.880 align:start position:0% inside. The first one is brand identity. 00:02:02.880 --> 00:02:04.870 align:start position:0% inside. The first one is brand identity. This<00:02:03.119> can<00:02:03.360> cover<00:02:03.600> the<00:02:03.759> brand<00:02:04.159> personality, 00:02:04.870 --> 00:02:04.880 align:start position:0% This can cover the brand personality, 00:02:04.880 --> 00:02:07.429 align:start position:0% This can cover the brand personality, core<00:02:05.280> traits<00:02:05.680> and<00:02:05.920> tone<00:02:06.159> of<00:02:06.399> voice.<00:02:07.040> So<00:02:07.200> this 00:02:07.429 --> 00:02:07.439 align:start position:0% core traits and tone of voice. So this 00:02:07.439 --> 00:02:09.510 align:start position:0% core traits and tone of voice. So this is<00:02:07.520> a<00:02:07.759> kind<00:02:07.920> of<00:02:08.080> document<00:02:08.479> that<00:02:08.720> a<00:02:09.200> brand 00:02:09.510 --> 00:02:09.520 align:start position:0% is a kind of document that a brand 00:02:09.520 --> 00:02:12.309 align:start position:0% is a kind of document that a brand strategist<00:02:10.160> would<00:02:10.479> spend<00:02:11.039> weeks<00:02:11.440> building. 00:02:12.309 --> 00:02:12.319 align:start position:0% strategist would spend weeks building. 00:02:12.319 --> 00:02:14.790 align:start position:0% strategist would spend weeks building. And<00:02:12.560> here<00:02:13.040> this<00:02:13.280> is<00:02:13.440> a<00:02:13.760> structured<00:02:14.319> file<00:02:14.560> that 00:02:14.790 --> 00:02:14.800 align:start position:0% And here this is a structured file that 00:02:14.800 --> 00:02:16.790 align:start position:0% And here this is a structured file that every<00:02:15.120> agent<00:02:15.520> in<00:02:15.760> this<00:02:16.000> pipeline<00:02:16.560> can 00:02:16.790 --> 00:02:16.800 align:start position:0% every agent in this pipeline can 00:02:16.800 --> 00:02:18.869 align:start position:0% every agent in this pipeline can reference.<00:02:17.280> So<00:02:17.520> the<00:02:17.760> second<00:02:18.080> file<00:02:18.480> is 00:02:18.869 --> 00:02:18.879 align:start position:0% reference. So the second file is 00:02:18.879 --> 00:02:21.830 align:start position:0% reference. So the second file is platform<00:02:19.520> guidelines<00:02:20.720> and<00:02:21.040> this<00:02:21.280> is<00:02:21.440> exactly 00:02:21.830 --> 00:02:21.840 align:start position:0% platform guidelines and this is exactly 00:02:21.840 --> 00:02:24.229 align:start position:0% platform guidelines and this is exactly what<00:02:22.000> it<00:02:22.239> sounds<00:02:22.480> like<00:02:22.879> like<00:02:23.040> a<00:02:23.280> guide<00:02:23.599> on<00:02:23.920> how 00:02:24.229 --> 00:02:24.239 align:start position:0% what it sounds like like a guide on how 00:02:24.239 --> 00:02:27.270 align:start position:0% what it sounds like like a guide on how the<00:02:24.480> brand<00:02:24.800> formats<00:02:25.440> content<00:02:26.400> depending<00:02:26.959> on 00:02:27.270 --> 00:02:27.280 align:start position:0% the brand formats content depending on 00:02:27.280 --> 00:02:30.390 align:start position:0% the brand formats content depending on where<00:02:27.520> it<00:02:27.760> is<00:02:27.920> going<00:02:28.879> like<00:02:29.280> Instagram's<00:02:29.920> bags 00:02:30.390 --> 00:02:30.400 align:start position:0% where it is going like Instagram's bags 00:02:30.400 --> 00:02:34.309 align:start position:0% where it is going like Instagram's bags YouTube<00:02:30.800> structure<00:02:31.599> threats<00:02:32.080> tone<00:02:33.280> etc<00:02:34.080> and 00:02:34.309 --> 00:02:34.319 align:start position:0% YouTube structure threats tone etc and 00:02:34.319 --> 00:02:37.430 align:start position:0% YouTube structure threats tone etc and each<00:02:34.640> platform<00:02:35.120> has<00:02:35.440> its<00:02:35.840> own<00:02:36.160> rules<00:02:36.720> and<00:02:37.200> this 00:02:37.430 --> 00:02:37.440 align:start position:0% each platform has its own rules and this 00:02:37.440 --> 00:02:39.910 align:start position:0% each platform has its own rules and this file<00:02:37.840> can<00:02:38.160> actually<00:02:38.720> lay<00:02:38.800> them<00:02:39.040> out<00:02:39.440> clearly 00:02:39.910 --> 00:02:39.920 align:start position:0% file can actually lay them out clearly 00:02:39.920 --> 00:02:41.830 align:start position:0% file can actually lay them out clearly so<00:02:40.239> every<00:02:40.640> agent<00:02:41.120> follows<00:02:41.519> them 00:02:41.830 --> 00:02:41.840 align:start position:0% so every agent follows them 00:02:41.840 --> 00:02:43.910 align:start position:0% so every agent follows them automatically.<00:02:42.720> All<00:02:42.720> right<00:02:43.040> so<00:02:43.280> the<00:02:43.519> third 00:02:43.910 --> 00:02:43.920 align:start position:0% automatically. All right so the third 00:02:43.920 --> 00:02:47.350 align:start position:0% automatically. All right so the third file<00:02:44.319> is<00:02:44.879> product<00:02:45.519> campaign.<00:02:46.560> So<00:02:46.800> this<00:02:46.959> file 00:02:47.350 --> 00:02:47.360 align:start position:0% file is product campaign. So this file 00:02:47.360 --> 00:02:49.270 align:start position:0% file is product campaign. So this file basically<00:02:47.760> outlines<00:02:48.239> how<00:02:48.480> the<00:02:48.800> brand 00:02:49.270 --> 00:02:49.280 align:start position:0% basically outlines how the brand 00:02:49.280 --> 00:02:52.790 align:start position:0% basically outlines how the brand typically<00:02:50.160> approaches<00:02:50.800> campaigns<00:02:51.840> and<00:02:52.319> how 00:02:52.790 --> 00:02:52.800 align:start position:0% typically approaches campaigns and how 00:02:52.800 --> 00:02:55.589 align:start position:0% typically approaches campaigns and how visuals<00:02:53.360> are<00:02:53.519> usually<00:02:53.920> handled<00:02:54.720> and<00:02:55.040> also<00:02:55.440> is 00:02:55.589 --> 00:02:55.599 align:start position:0% visuals are usually handled and also is 00:02:55.599 --> 00:02:57.750 align:start position:0% visuals are usually handled and also is about<00:02:55.840> what<00:02:56.160> a<00:02:56.400> typical<00:02:56.800> content<00:02:57.280> package 00:02:57.750 --> 00:02:57.760 align:start position:0% about what a typical content package 00:02:57.760 --> 00:03:00.229 align:start position:0% about what a typical content package looks<00:02:58.080> like<00:02:58.560> and<00:02:58.800> it<00:02:59.040> gives<00:02:59.360> the<00:02:59.599> agent<00:03:00.000> a 00:03:00.229 --> 00:03:00.239 align:start position:0% looks like and it gives the agent a 00:03:00.239 --> 00:03:02.550 align:start position:0% looks like and it gives the agent a frame<00:03:00.560> of<00:03:00.800> reference<00:03:01.360> before<00:03:01.680> they<00:03:02.080> start 00:03:02.550 --> 00:03:02.560 align:start position:0% frame of reference before they start 00:03:02.560 --> 00:03:04.390 align:start position:0% frame of reference before they start generating<00:03:03.200> everything.<00:03:03.840> All<00:03:03.840> right.<00:03:04.159> Then 00:03:04.390 --> 00:03:04.400 align:start position:0% generating everything. All right. Then 00:03:04.400 --> 00:03:08.790 align:start position:0% generating everything. All right. Then we<00:03:04.640> have<00:03:05.280> clot<00:03:06.480> md.<00:03:07.519> This<00:03:07.760> is<00:03:07.840> the<00:03:08.319> file<00:03:08.560> that 00:03:08.790 --> 00:03:08.800 align:start position:0% we have clot md. This is the file that 00:03:08.800 --> 00:03:11.350 align:start position:0% we have clot md. This is the file that we<00:03:09.120> have<00:03:09.680> and<00:03:09.920> if<00:03:10.159> you<00:03:10.319> have<00:03:10.480> worked<00:03:10.720> with<00:03:10.959> clot 00:03:11.350 --> 00:03:11.360 align:start position:0% we have and if you have worked with clot 00:03:11.360 --> 00:03:14.550 align:start position:0% we have and if you have worked with clot code<00:03:11.680> before<00:03:12.560> you<00:03:12.800> know<00:03:12.879> this<00:03:13.200> file<00:03:13.920> and<00:03:14.319> if 00:03:14.550 --> 00:03:14.560 align:start position:0% code before you know this file and if 00:03:14.560 --> 00:03:17.350 align:start position:0% code before you know this file and if you<00:03:14.720> have<00:03:14.879> not<00:03:15.360> this<00:03:15.599> is<00:03:15.760> the<00:03:16.080> most<00:03:16.640> important 00:03:17.350 --> 00:03:17.360 align:start position:0% you have not this is the most important 00:03:17.360 --> 00:03:20.390 align:start position:0% you have not this is the most important file<00:03:17.760> in<00:03:18.080> any<00:03:18.480> clot<00:03:18.879> code<00:03:19.200> project.<00:03:20.080> So 00:03:20.390 --> 00:03:20.400 align:start position:0% file in any clot code project. So 00:03:20.400 --> 00:03:22.149 align:start position:0% file in any clot code project. So basically<00:03:20.800> you<00:03:20.959> can<00:03:21.120> treat<00:03:21.360> this<00:03:21.599> empty<00:03:22.000> file 00:03:22.149 --> 00:03:22.159 align:start position:0% basically you can treat this empty file 00:03:22.159 --> 00:03:24.229 align:start position:0% basically you can treat this empty file as<00:03:22.319> the<00:03:22.560> source<00:03:22.800> of<00:03:23.040> truth<00:03:23.440> for<00:03:23.680> the<00:03:23.920> entire 00:03:24.229 --> 00:03:24.239 align:start position:0% as the source of truth for the entire 00:03:24.239 --> 00:03:27.030 align:start position:0% as the source of truth for the entire workspace<00:03:25.200> because<00:03:25.519> it<00:03:25.840> can<00:03:26.080> tell<00:03:26.400> clot<00:03:26.879> what 00:03:27.030 --> 00:03:27.040 align:start position:0% workspace because it can tell clot what 00:03:27.040 --> 00:03:29.270 align:start position:0% workspace because it can tell clot what the<00:03:27.280> project<00:03:27.599> is,<00:03:28.400> how<00:03:28.560> the<00:03:28.720> folder<00:03:29.040> is 00:03:29.270 --> 00:03:29.280 align:start position:0% the project is, how the folder is 00:03:29.280 --> 00:03:31.750 align:start position:0% the project is, how the folder is structured,<00:03:29.920> what<00:03:30.159> files<00:03:30.560> are<00:03:30.799> available<00:03:31.519> and 00:03:31.750 --> 00:03:31.760 align:start position:0% structured, what files are available and 00:03:31.760 --> 00:03:33.830 align:start position:0% structured, what files are available and what<00:03:32.000> rules<00:03:32.319> to<00:03:32.560> follow<00:03:32.879> when<00:03:33.280> navigating 00:03:33.830 --> 00:03:33.840 align:start position:0% what rules to follow when navigating 00:03:33.840 --> 00:03:36.550 align:start position:0% what rules to follow when navigating everything.<00:03:34.480> So<00:03:34.720> without<00:03:35.040> it,<00:03:35.519> Clot<00:03:35.920> is<00:03:36.239> just 00:03:36.550 --> 00:03:36.560 align:start position:0% everything. So without it, Clot is just 00:03:36.560 --> 00:03:39.110 align:start position:0% everything. So without it, Clot is just guessing.<00:03:37.280> And<00:03:37.440> with<00:03:37.680> it,<00:03:38.239> Clot<00:03:38.720> knows 00:03:39.110 --> 00:03:39.120 align:start position:0% guessing. And with it, Clot knows 00:03:39.120 --> 00:03:41.190 align:start position:0% guessing. And with it, Clot knows exactly<00:03:39.599> where<00:03:39.840> it<00:03:40.000> is<00:03:40.239> and<00:03:40.560> what<00:03:40.799> it<00:03:40.959> is 00:03:41.190 --> 00:03:41.200 align:start position:0% exactly where it is and what it is 00:03:41.200 --> 00:03:43.430 align:start position:0% exactly where it is and what it is working<00:03:41.440> with<00:03:41.760> before<00:03:42.080> it<00:03:42.319> does<00:03:42.640> anything.<00:03:43.280> So 00:03:43.430 --> 00:03:43.440 align:start position:0% working with before it does anything. So 00:03:43.440 --> 00:03:45.350 align:start position:0% working with before it does anything. So if<00:03:43.599> you<00:03:43.760> look<00:03:43.840> at<00:03:44.000> this<00:03:44.319> right<00:03:44.560> now,<00:03:44.959> you<00:03:45.120> will 00:03:45.350 --> 00:03:45.360 align:start position:0% if you look at this right now, you will 00:03:45.360 --> 00:03:47.750 align:start position:0% if you look at this right now, you will notice<00:03:45.760> we<00:03:46.080> only<00:03:46.480> have<00:03:46.799> three<00:03:47.200> agents 00:03:47.750 --> 00:03:47.760 align:start position:0% notice we only have three agents 00:03:47.760 --> 00:03:50.149 align:start position:0% notice we only have three agents declared<00:03:48.319> here.<00:03:49.040> And<00:03:49.360> don't<00:03:49.680> worry<00:03:49.920> about 00:03:50.149 --> 00:03:50.159 align:start position:0% declared here. And don't worry about 00:03:50.159 --> 00:03:52.630 align:start position:0% declared here. And don't worry about that.<00:03:50.640> We<00:03:50.959> will<00:03:51.200> be<00:03:51.360> updating<00:03:51.920> this<00:03:52.159> as<00:03:52.400> we 00:03:52.630 --> 00:03:52.640 align:start position:0% that. We will be updating this as we 00:03:52.640 --> 00:03:55.110 align:start position:0% that. We will be updating this as we build<00:03:52.879> each<00:03:53.120> agent<00:03:53.599> throughout<00:03:54.080> the<00:03:54.319> video. 00:03:55.110 --> 00:03:55.120 align:start position:0% build each agent throughout the video. 00:03:55.120 --> 00:03:57.190 align:start position:0% build each agent throughout the video. All<00:03:55.200> right.<00:03:55.440> And<00:03:55.599> last,<00:03:56.000> this<00:03:56.159> is<00:03:56.400> important. 00:03:57.190 --> 00:03:57.200 align:start position:0% All right. And last, this is important. 00:03:57.200 --> 00:04:00.070 align:start position:0% All right. And last, this is important. This<00:03:57.439> is<00:03:57.599> our<00:03:58.000> comprehensive<00:03:58.959> CL<00:03:59.360> skills<00:03:59.840> and 00:04:00.070 --> 00:04:00.080 align:start position:0% This is our comprehensive CL skills and 00:04:00.080 --> 00:04:03.830 align:start position:0% This is our comprehensive CL skills and plugins<00:04:00.879> document<00:04:01.920> like<00:04:02.319> 600<00:04:02.879> lines.<00:04:03.599> We 00:04:03.830 --> 00:04:03.840 align:start position:0% plugins document like 600 lines. We 00:04:03.840 --> 00:04:06.710 align:start position:0% plugins document like 600 lines. We built<00:04:04.080> it<00:04:04.239> from<00:04:04.560> the<00:04:04.959> 33page<00:04:06.000> clot<00:04:06.400> skills 00:04:06.710 --> 00:04:06.720 align:start position:0% built it from the 33page clot skills 00:04:06.720 --> 00:04:09.750 align:start position:0% built it from the 33page clot skills guide<00:04:07.280> that<00:04:07.599> Enthropic<00:04:08.560> released<00:04:09.040> recently. 00:04:09.750 --> 00:04:09.760 align:start position:0% guide that Enthropic released recently. 00:04:09.760 --> 00:04:12.229 align:start position:0% guide that Enthropic released recently. So<00:04:10.080> everything<00:04:10.400> you<00:04:10.720> or<00:04:10.959> clot<00:04:11.280> code<00:04:11.680> needs<00:04:12.000> to 00:04:12.229 --> 00:04:12.239 align:start position:0% So everything you or clot code needs to 00:04:12.239 --> 00:04:14.309 align:start position:0% So everything you or clot code needs to know<00:04:12.560> to<00:04:12.879> create<00:04:13.120> a<00:04:13.360> well<00:04:13.599> structured 00:04:14.309 --> 00:04:14.319 align:start position:0% know to create a well structured 00:04:14.319 --> 00:04:17.110 align:start position:0% know to create a well structured reliable<00:04:14.959> skill,<00:04:15.760> it<00:04:15.920> is<00:04:16.079> in<00:04:16.320> here<00:04:16.639> like<00:04:16.880> the 00:04:17.110 --> 00:04:17.120 align:start position:0% reliable skill, it is in here like the 00:04:17.120 --> 00:04:20.069 align:start position:0% reliable skill, it is in here like the YML<00:04:18.160> front<00:04:18.560> meta<00:04:18.959> rules,<00:04:19.519> the<00:04:19.759> trigger 00:04:20.069 --> 00:04:20.079 align:start position:0% YML front meta rules, the trigger 00:04:20.079 --> 00:04:23.189 align:start position:0% YML front meta rules, the trigger patterns,<00:04:21.199> the<00:04:21.680> workflow<00:04:22.240> structures,<00:04:22.880> the 00:04:23.189 --> 00:04:23.199 align:start position:0% patterns, the workflow structures, the 00:04:23.199 --> 00:04:26.390 align:start position:0% patterns, the workflow structures, the testing<00:04:23.600> framework,<00:04:24.880> all<00:04:25.040> of<00:04:25.199> it<00:04:25.520> basically. 00:04:26.390 --> 00:04:26.400 align:start position:0% testing framework, all of it basically. 00:04:26.400 --> 00:04:28.150 align:start position:0% testing framework, all of it basically. And<00:04:26.639> this<00:04:26.880> is<00:04:27.040> not<00:04:27.280> just<00:04:27.440> a<00:04:27.759> reference 00:04:28.150 --> 00:04:28.160 align:start position:0% And this is not just a reference 00:04:28.160 --> 00:04:30.790 align:start position:0% And this is not just a reference document.<00:04:28.800> This<00:04:28.960> is<00:04:29.120> the<00:04:29.440> foundation<00:04:30.400> we<00:04:30.639> are 00:04:30.790 --> 00:04:30.800 align:start position:0% document. This is the foundation we are 00:04:30.800 --> 00:04:33.110 align:start position:0% document. This is the foundation we are building<00:04:31.280> every<00:04:31.680> agent<00:04:32.160> skill<00:04:32.400> frame.<00:04:32.800> Okay. 00:04:33.110 --> 00:04:33.120 align:start position:0% building every agent skill frame. Okay. 00:04:33.120 --> 00:04:35.510 align:start position:0% building every agent skill frame. Okay. So<00:04:33.440> before<00:04:33.840> we<00:04:34.080> jump<00:04:34.240> into<00:04:34.560> clot<00:04:34.960> code<00:04:35.280> and 00:04:35.510 --> 00:04:35.520 align:start position:0% So before we jump into clot code and 00:04:35.520 --> 00:04:37.909 align:start position:0% So before we jump into clot code and start<00:04:35.840> building,<00:04:36.240> we<00:04:36.560> need<00:04:36.720> to<00:04:36.880> be<00:04:37.120> clear<00:04:37.520> on 00:04:37.909 --> 00:04:37.919 align:start position:0% start building, we need to be clear on 00:04:37.919 --> 00:04:40.310 align:start position:0% start building, we need to be clear on what<00:04:38.320> each<00:04:38.639> skill<00:04:39.040> is<00:04:39.280> actually<00:04:39.600> supposed<00:04:40.080> to 00:04:40.310 --> 00:04:40.320 align:start position:0% what each skill is actually supposed to 00:04:40.320 --> 00:04:43.189 align:start position:0% what each skill is actually supposed to do.<00:04:40.960> And<00:04:41.120> the<00:04:41.360> best<00:04:41.520> way<00:04:41.600> to<00:04:41.840> do<00:04:42.000> this<00:04:42.720> is<00:04:42.960> just 00:04:43.189 --> 00:04:43.199 align:start position:0% do. And the best way to do this is just 00:04:43.199 --> 00:04:45.510 align:start position:0% do. And the best way to do this is just to<00:04:43.440> plan<00:04:43.759> it<00:04:43.919> first<00:04:44.320> with<00:04:44.560> cloud<00:04:45.040> of<00:04:45.199> course. 00:04:45.510 --> 00:04:45.520 align:start position:0% to plan it first with cloud of course. 00:04:45.520 --> 00:04:48.629 align:start position:0% to plan it first with cloud of course. And<00:04:45.840> here<00:04:46.000> is<00:04:46.240> what<00:04:46.479> looks<00:04:46.720> like.<00:04:47.360> We<00:04:47.680> open<00:04:48.000> CLA 00:04:48.629 --> 00:04:48.639 align:start position:0% And here is what looks like. We open CLA 00:04:48.639 --> 00:04:52.310 align:start position:0% And here is what looks like. We open CLA and<00:04:49.040> set<00:04:49.520> 4.6<00:04:50.160> is<00:04:50.560> fine<00:04:50.880> for<00:04:51.120> this.<00:04:51.680> It's<00:04:51.919> not<00:04:52.080> a 00:04:52.310 --> 00:04:52.320 align:start position:0% and set 4.6 is fine for this. It's not a 00:04:52.320 --> 00:04:55.030 align:start position:0% and set 4.6 is fine for this. It's not a complex<00:04:52.720> task.<00:04:53.199> So<00:04:53.440> we<00:04:53.680> actually<00:04:54.160> do<00:04:54.400> not<00:04:54.639> need 00:04:55.030 --> 00:04:55.040 align:start position:0% complex task. So we actually do not need 00:04:55.040 --> 00:04:58.070 align:start position:0% complex task. So we actually do not need opus<00:04:55.440> 4.6<00:04:56.080> here.<00:04:56.400> And<00:04:56.560> then<00:04:56.800> we<00:04:56.960> can<00:04:57.199> ask<00:04:57.520> it<00:04:57.840> to 00:04:58.070 --> 00:04:58.080 align:start position:0% opus 4.6 here. And then we can ask it to 00:04:58.080 --> 00:05:01.350 align:start position:0% opus 4.6 here. And then we can ask it to help<00:04:58.320> us<00:04:58.720> plan<00:04:59.040> and<00:04:59.360> draft<00:04:59.759> the<00:05:00.080> key<00:05:00.400> details 00:05:01.350 --> 00:05:01.360 align:start position:0% help us plan and draft the key details 00:05:01.360 --> 00:05:03.670 align:start position:0% help us plan and draft the key details and<00:05:01.759> description<00:05:02.240> for<00:05:02.479> the<00:05:02.639> skill<00:05:02.880> we<00:05:03.199> want<00:05:03.360> to 00:05:03.670 --> 00:05:03.680 align:start position:0% and description for the skill we want to 00:05:03.680 --> 00:05:06.150 align:start position:0% and description for the skill we want to create.<00:05:04.240> And<00:05:04.479> we<00:05:04.720> can<00:05:05.040> also<00:05:05.360> attach<00:05:05.759> the 00:05:06.150 --> 00:05:06.160 align:start position:0% create. And we can also attach the 00:05:06.160 --> 00:05:09.029 align:start position:0% create. And we can also attach the automate<00:05:06.639> clot<00:05:06.960> skills<00:05:07.360> document.<00:05:08.000> So<00:05:08.320> clot 00:05:09.029 --> 00:05:09.039 align:start position:0% automate clot skills document. So clot 00:05:09.039 --> 00:05:10.950 align:start position:0% automate clot skills document. So clot has<00:05:09.280> the<00:05:09.520> full<00:05:09.840> context<00:05:10.320> on<00:05:10.560> what<00:05:10.800> a 00:05:10.950 --> 00:05:10.960 align:start position:0% has the full context on what a 00:05:10.960 --> 00:05:13.510 align:start position:0% has the full context on what a well-built<00:05:11.759> skill<00:05:12.320> looks<00:05:12.639> like.<00:05:13.039> All<00:05:13.120> right. 00:05:13.510 --> 00:05:13.520 align:start position:0% well-built skill looks like. All right. 00:05:13.520 --> 00:05:15.590 align:start position:0% well-built skill looks like. All right. So<00:05:13.680> what's<00:05:14.000> great<00:05:14.240> about<00:05:14.400> this<00:05:14.639> step<00:05:14.880> is<00:05:15.039> that 00:05:15.590 --> 00:05:15.600 align:start position:0% So what's great about this step is that 00:05:15.600 --> 00:05:17.990 align:start position:0% So what's great about this step is that clot<00:05:16.400> does<00:05:16.639> not<00:05:16.880> just<00:05:17.120> give<00:05:17.280> you<00:05:17.440> an<00:05:17.680> answer. 00:05:17.990 --> 00:05:18.000 align:start position:0% clot does not just give you an answer. 00:05:18.000 --> 00:05:20.629 align:start position:0% clot does not just give you an answer. It<00:05:18.240> can<00:05:18.479> ask<00:05:18.720> you<00:05:19.039> questions.<00:05:20.000> It<00:05:20.240> wants<00:05:20.400> to 00:05:20.629 --> 00:05:20.639 align:start position:0% It can ask you questions. It wants to 00:05:20.639 --> 00:05:22.550 align:start position:0% It can ask you questions. It wants to understand<00:05:20.960> the<00:05:21.199> scope,<00:05:21.680> the<00:05:22.000> expected 00:05:22.550 --> 00:05:22.560 align:start position:0% understand the scope, the expected 00:05:22.560 --> 00:05:25.749 align:start position:0% understand the scope, the expected behavior,<00:05:23.280> the<00:05:23.520> edge<00:05:23.919> cases,<00:05:24.560> etc.<00:05:25.199> and<00:05:25.520> you 00:05:25.749 --> 00:05:25.759 align:start position:0% behavior, the edge cases, etc. and you 00:05:25.759 --> 00:05:27.990 align:start position:0% behavior, the edge cases, etc. and you just<00:05:26.000> answer<00:05:26.320> them<00:05:26.560> as<00:05:26.800> they<00:05:27.039> come.<00:05:27.440> So<00:05:27.680> after 00:05:27.990 --> 00:05:28.000 align:start position:0% just answer them as they come. So after 00:05:28.000 --> 00:05:30.230 align:start position:0% just answer them as they come. So after some<00:05:28.240> back<00:05:28.400> and<00:05:28.639> forth,<00:05:28.960> CL<00:05:29.360> outputs<00:05:29.840> the<00:05:30.080> key 00:05:30.230 --> 00:05:30.240 align:start position:0% some back and forth, CL outputs the key 00:05:30.240 --> 00:05:32.390 align:start position:0% some back and forth, CL outputs the key details<00:05:30.639> and<00:05:30.960> description<00:05:31.280> for<00:05:31.520> the<00:05:31.680> skill 00:05:32.390 --> 00:05:32.400 align:start position:0% details and description for the skill 00:05:32.400 --> 00:05:34.550 align:start position:0% details and description for the skill and<00:05:32.560> from<00:05:32.800> there<00:05:32.960> you<00:05:33.199> can<00:05:33.280> tweak<00:05:33.600> it,<00:05:34.080> refine 00:05:34.550 --> 00:05:34.560 align:start position:0% and from there you can tweak it, refine 00:05:34.560 --> 00:05:36.870 align:start position:0% and from there you can tweak it, refine it<00:05:34.880> or<00:05:35.120> if<00:05:35.360> you're<00:05:35.600> happy<00:05:35.759> with<00:05:36.000> it,<00:05:36.320> just<00:05:36.560> copy 00:05:36.870 --> 00:05:36.880 align:start position:0% it or if you're happy with it, just copy 00:05:36.880 --> 00:05:39.510 align:start position:0% it or if you're happy with it, just copy it<00:05:37.120> into<00:05:37.440> your<00:05:37.680> notepad<00:05:38.240> and<00:05:38.479> move<00:05:38.639> on.<00:05:39.199> And 00:05:39.510 --> 00:05:39.520 align:start position:0% it into your notepad and move on. And 00:05:39.520 --> 00:05:41.110 align:start position:0% it into your notepad and move on. And since<00:05:39.759> we<00:05:40.000> are<00:05:40.080> building<00:05:40.400> five<00:05:40.560> agents<00:05:40.960> for 00:05:41.110 --> 00:05:41.120 align:start position:0% since we are building five agents for 00:05:41.120 --> 00:05:43.830 align:start position:0% since we are building five agents for this<00:05:41.360> pipeline,<00:05:41.919> that<00:05:42.160> means<00:05:42.479> five<00:05:42.880> skills. 00:05:43.830 --> 00:05:43.840 align:start position:0% this pipeline, that means five skills. 00:05:43.840 --> 00:05:45.510 align:start position:0% this pipeline, that means five skills. You<00:05:44.080> can<00:05:44.240> go<00:05:44.400> through<00:05:44.720> this<00:05:45.120> planning 00:05:45.510 --> 00:05:45.520 align:start position:0% You can go through this planning 00:05:45.520 --> 00:05:48.550 align:start position:0% You can go through this planning conversation<00:05:46.160> five<00:05:46.479> times,<00:05:47.280> once<00:05:47.919> for<00:05:48.320> each 00:05:48.550 --> 00:05:48.560 align:start position:0% conversation five times, once for each 00:05:48.560 --> 00:05:51.189 align:start position:0% conversation five times, once for each agent<00:05:49.199> until<00:05:49.680> all<00:05:49.919> five<00:05:50.240> are<00:05:50.479> defined.<00:05:51.039> And 00:05:51.189 --> 00:05:51.199 align:start position:0% agent until all five are defined. And 00:05:51.199 --> 00:05:53.430 align:start position:0% agent until all five are defined. And here's<00:05:51.520> what<00:05:51.840> ours<00:05:52.160> looks<00:05:52.400> like<00:05:52.880> with<00:05:53.199> all 00:05:53.430 --> 00:05:53.440 align:start position:0% here's what ours looks like with all 00:05:53.440 --> 00:05:55.830 align:start position:0% here's what ours looks like with all five<00:05:53.759> done.<00:05:54.560> like<00:05:54.720> key<00:05:54.960> details,<00:05:55.520> clear 00:05:55.830 --> 00:05:55.840 align:start position:0% five done. like key details, clear 00:05:55.840 --> 00:05:58.310 align:start position:0% five done. like key details, clear descriptions,<00:05:56.880> scope<00:05:57.280> defined<00:05:57.759> for<00:05:58.000> each 00:05:58.310 --> 00:05:58.320 align:start position:0% descriptions, scope defined for each 00:05:58.320 --> 00:06:01.430 align:start position:0% descriptions, scope defined for each agent<00:05:58.800> before<00:05:59.199> we<00:05:59.600> write<00:05:59.919> a<00:06:00.240> single<00:06:00.639> line<00:06:01.039> of 00:06:01.430 --> 00:06:01.440 align:start position:0% agent before we write a single line of 00:06:01.440 --> 00:06:04.309 align:start position:0% agent before we write a single line of skill<00:06:01.759> code<00:06:02.400> and<00:06:02.560> also<00:06:02.880> we<00:06:03.120> posted<00:06:03.520> this<00:06:03.840> PDF 00:06:04.309 --> 00:06:04.319 align:start position:0% skill code and also we posted this PDF 00:06:04.319 --> 00:06:06.790 align:start position:0% skill code and also we posted this PDF and<00:06:04.479> the<00:06:04.720> ultimate<00:06:05.120> cloth<00:06:05.520> skills<00:06:05.919> MD<00:06:06.319> file<00:06:06.639> in 00:06:06.790 --> 00:06:06.800 align:start position:0% and the ultimate cloth skills MD file in 00:06:06.800 --> 00:06:08.790 align:start position:0% and the ultimate cloth skills MD file in our<00:06:07.039> premium<00:06:07.440> community<00:06:08.080> and<00:06:08.240> also<00:06:08.479> if<00:06:08.639> you 00:06:08.790 --> 00:06:08.800 align:start position:0% our premium community and also if you 00:06:08.800 --> 00:06:10.790 align:start position:0% our premium community and also if you want<00:06:08.960> it<00:06:09.120> for<00:06:09.280> free<00:06:09.680> you<00:06:09.840> can<00:06:09.919> let<00:06:10.160> us<00:06:10.319> know<00:06:10.560> in 00:06:10.790 --> 00:06:10.800 align:start position:0% want it for free you can let us know in 00:06:10.800 --> 00:06:12.469 align:start position:0% want it for free you can let us know in the<00:06:10.960> comment<00:06:11.120> section<00:06:11.440> below.<00:06:11.919> If<00:06:12.160> we<00:06:12.319> have 00:06:12.469 --> 00:06:12.479 align:start position:0% the comment section below. If we have 00:06:12.479 --> 00:06:14.390 align:start position:0% the comment section below. If we have enough<00:06:12.880> requests<00:06:13.600> then<00:06:13.840> we<00:06:14.080> are<00:06:14.160> going<00:06:14.319> to 00:06:14.390 --> 00:06:14.400 align:start position:0% enough requests then we are going to 00:06:14.400 --> 00:06:17.110 align:start position:0% enough requests then we are going to post<00:06:14.639> it<00:06:14.880> in<00:06:15.039> our<00:06:15.199> free<00:06:15.440> community<00:06:15.919> as<00:06:16.080> well. 00:06:17.110 --> 00:06:17.120 align:start position:0% post it in our free community as well. 00:06:17.120 --> 00:06:19.350 align:start position:0% post it in our free community as well. So<00:06:17.360> with<00:06:17.520> this<00:06:17.840> ready<00:06:18.160> we<00:06:18.479> can<00:06:18.639> move<00:06:18.880> into 00:06:19.350 --> 00:06:19.360 align:start position:0% So with this ready we can move into 00:06:19.360 --> 00:06:22.550 align:start position:0% So with this ready we can move into cloud<00:06:19.759> code<00:06:20.080> and<00:06:20.400> start<00:06:20.720> building.<00:06:21.360> Okay,<00:06:22.400> now 00:06:22.550 --> 00:06:22.560 align:start position:0% cloud code and start building. Okay, now 00:06:22.560 --> 00:06:25.510 align:start position:0% cloud code and start building. Okay, now that<00:06:22.800> our<00:06:23.039> research<00:06:23.360> is<00:06:23.600> ready,<00:06:24.400> it's<00:06:24.720> time<00:06:25.280> to 00:06:25.510 --> 00:06:25.520 align:start position:0% that our research is ready, it's time to 00:06:25.520 --> 00:06:27.990 align:start position:0% that our research is ready, it's time to put<00:06:25.759> it<00:06:26.080> to<00:06:26.319> work.<00:06:26.960> So<00:06:27.120> in<00:06:27.280> this<00:06:27.440> section,<00:06:27.840> we 00:06:27.990 --> 00:06:28.000 align:start position:0% put it to work. So in this section, we 00:06:28.000 --> 00:06:30.870 align:start position:0% put it to work. So in this section, we are<00:06:28.240> going<00:06:28.400> to<00:06:28.639> create<00:06:29.120> two<00:06:29.520> agents.<00:06:30.319> A<00:06:30.560> video 00:06:30.870 --> 00:06:30.880 align:start position:0% are going to create two agents. A video 00:06:30.880 --> 00:06:34.150 align:start position:0% are going to create two agents. A video ad<00:06:31.360> specialist<00:06:32.720> which<00:06:32.960> can<00:06:33.280> handle 00:06:34.150 --> 00:06:34.160 align:start position:0% ad specialist which can handle 00:06:34.160 --> 00:06:36.230 align:start position:0% ad specialist which can handle programmatic<00:06:34.720> video<00:06:35.039> content<00:06:35.360> for<00:06:35.520> the<00:06:35.680> brand 00:06:36.230 --> 00:06:36.240 align:start position:0% programmatic video content for the brand 00:06:36.240 --> 00:06:39.590 align:start position:0% programmatic video content for the brand and<00:06:36.560> also<00:06:37.199> an<00:06:37.600> ad<00:06:37.919> creative<00:06:38.400> designer<00:06:39.280> which 00:06:39.590 --> 00:06:39.600 align:start position:0% and also an ad creative designer which 00:06:39.600 --> 00:06:42.230 align:start position:0% and also an ad creative designer which can<00:06:39.840> build<00:06:40.160> static<00:06:40.639> ads<00:06:41.039> for<00:06:41.440> platforms<00:06:41.919> like 00:06:42.230 --> 00:06:42.240 align:start position:0% can build static ads for platforms like 00:06:42.240 --> 00:06:44.710 align:start position:0% can build static ads for platforms like Instagram.<00:06:43.199> And<00:06:43.360> we're<00:06:43.600> going<00:06:43.759> to<00:06:43.919> build<00:06:44.319> both 00:06:44.710 --> 00:06:44.720 align:start position:0% Instagram. And we're going to build both 00:06:44.720 --> 00:06:47.350 align:start position:0% Instagram. And we're going to build both skills<00:06:45.199> first<00:06:45.520> and<00:06:45.759> then<00:06:46.000> test<00:06:46.240> them<00:06:46.639> one<00:06:46.960> at<00:06:47.199> a 00:06:47.350 --> 00:06:47.360 align:start position:0% skills first and then test them one at a 00:06:47.360 --> 00:06:48.950 align:start position:0% skills first and then test them one at a time.<00:06:47.680> All<00:06:47.759> right.<00:06:48.000> So,<00:06:48.160> let's<00:06:48.479> start<00:06:48.639> with 00:06:48.950 --> 00:06:48.960 align:start position:0% time. All right. So, let's start with 00:06:48.960 --> 00:06:51.510 align:start position:0% time. All right. So, let's start with the<00:06:49.280> video<00:06:49.680> ad<00:06:50.000> specialist<00:06:50.479> first.<00:06:51.199> And<00:06:51.360> here 00:06:51.510 --> 00:06:51.520 align:start position:0% the video ad specialist first. And here 00:06:51.520 --> 00:06:53.510 align:start position:0% the video ad specialist first. And here in<00:06:51.759> cloud<00:06:52.080> code,<00:06:52.400> we<00:06:52.560> can<00:06:52.720> just<00:06:52.880> use<00:06:53.199> this 00:06:53.510 --> 00:06:53.520 align:start position:0% in cloud code, we can just use this 00:06:53.520 --> 00:06:55.909 align:start position:0% in cloud code, we can just use this prompt<00:06:53.919> to<00:06:54.160> kickstart.<00:06:54.880> And<00:06:55.039> the<00:06:55.199> prompt<00:06:55.520> is 00:06:55.909 --> 00:06:55.919 align:start position:0% prompt to kickstart. And the prompt is 00:06:55.919 --> 00:06:58.790 align:start position:0% prompt to kickstart. And the prompt is help<00:06:56.319> me<00:06:56.560> create<00:06:56.880> an<00:06:57.120> agent<00:06:57.520> skill.<00:06:58.400> I<00:06:58.639> will 00:06:58.790 --> 00:06:58.800 align:start position:0% help me create an agent skill. I will 00:06:58.800 --> 00:07:00.790 align:start position:0% help me create an agent skill. I will give<00:06:59.039> you<00:06:59.199> the<00:06:59.599> key<00:06:59.919> details<00:07:00.319> about<00:07:00.560> the 00:07:00.790 --> 00:07:00.800 align:start position:0% give you the key details about the 00:07:00.800 --> 00:07:03.189 align:start position:0% give you the key details about the skill.<00:07:01.360> And<00:07:01.520> then<00:07:01.759> you<00:07:02.080> can<00:07:02.240> use<00:07:02.560> the<00:07:02.800> ultimate 00:07:03.189 --> 00:07:03.199 align:start position:0% skill. And then you can use the ultimate 00:07:03.199 --> 00:07:06.309 align:start position:0% skill. And then you can use the ultimate clot<00:07:03.599> skills<00:07:04.319> and<00:07:04.560> plugins<00:07:05.280> empty<00:07:05.759> to<00:07:06.080> create 00:07:06.309 --> 00:07:06.319 align:start position:0% clot skills and plugins empty to create 00:07:06.319 --> 00:07:07.909 align:start position:0% clot skills and plugins empty to create it.<00:07:06.639> And<00:07:06.800> then<00:07:06.960> we<00:07:07.120> can<00:07:07.199> just<00:07:07.360> paste<00:07:07.599> in<00:07:07.759> the 00:07:07.909 --> 00:07:07.919 align:start position:0% it. And then we can just paste in the 00:07:07.919 --> 00:07:10.469 align:start position:0% it. And then we can just paste in the key<00:07:08.160> details<00:07:08.560> we<00:07:08.800> planned<00:07:09.199> out<00:07:09.440> earlier.<00:07:10.240> And 00:07:10.469 --> 00:07:10.479 align:start position:0% key details we planned out earlier. And 00:07:10.479 --> 00:07:12.550 align:start position:0% key details we planned out earlier. And those<00:07:10.720> are<00:07:10.880> the<00:07:11.039> details<00:07:11.520> that<00:07:11.759> we<00:07:12.000> drafted 00:07:12.550 --> 00:07:12.560 align:start position:0% those are the details that we drafted 00:07:12.560 --> 00:07:15.670 align:start position:0% those are the details that we drafted with<00:07:12.800> clot<00:07:13.360> before<00:07:14.080> coming<00:07:14.400> into<00:07:14.800> clot<00:07:15.199> code. 00:07:15.670 --> 00:07:15.680 align:start position:0% with clot before coming into clot code. 00:07:15.680 --> 00:07:17.189 align:start position:0% with clot before coming into clot code. And<00:07:15.919> that<00:07:16.080> is<00:07:16.240> the<00:07:16.479> important<00:07:16.800> thing<00:07:16.960> to 00:07:17.189 --> 00:07:17.199 align:start position:0% And that is the important thing to 00:07:17.199 --> 00:07:19.510 align:start position:0% And that is the important thing to notice<00:07:17.520> here<00:07:17.840> because<00:07:18.479> we're<00:07:18.960> not<00:07:19.199> just 00:07:19.510 --> 00:07:19.520 align:start position:0% notice here because we're not just 00:07:19.520 --> 00:07:21.670 align:start position:0% notice here because we're not just asking<00:07:19.919> clot<00:07:20.319> to<00:07:20.560> figure<00:07:20.720> out<00:07:20.880> what<00:07:21.120> the<00:07:21.280> skill 00:07:21.670 --> 00:07:21.680 align:start position:0% asking clot to figure out what the skill 00:07:21.680 --> 00:07:24.070 align:start position:0% asking clot to figure out what the skill should<00:07:21.919> do.<00:07:22.479> We<00:07:22.720> have<00:07:22.880> already<00:07:23.199> done<00:07:23.440> that.<00:07:23.840> We 00:07:24.070 --> 00:07:24.080 align:start position:0% should do. We have already done that. We 00:07:24.080 --> 00:07:26.070 align:start position:0% should do. We have already done that. We are<00:07:24.160> just<00:07:24.400> handing<00:07:24.720> it<00:07:24.960> the<00:07:25.120> brief<00:07:25.520> and<00:07:25.759> asking 00:07:26.070 --> 00:07:26.080 align:start position:0% are just handing it the brief and asking 00:07:26.080 --> 00:07:27.830 align:start position:0% are just handing it the brief and asking it<00:07:26.240> to<00:07:26.479> build.<00:07:26.880> All<00:07:26.880> right.<00:07:27.120> So<00:07:27.360> let's<00:07:27.599> hit 00:07:27.830 --> 00:07:27.840 align:start position:0% it to build. All right. So let's hit 00:07:27.840 --> 00:07:30.390 align:start position:0% it to build. All right. So let's hit enter<00:07:28.160> and<00:07:28.400> let<00:07:28.720> Claude<00:07:29.120> work<00:07:29.360> through<00:07:29.520> it.<00:07:30.160> So 00:07:30.390 --> 00:07:30.400 align:start position:0% enter and let Claude work through it. So 00:07:30.400 --> 00:07:32.629 align:start position:0% enter and let Claude work through it. So after<00:07:30.560> a<00:07:30.639> while<00:07:30.960> it's<00:07:31.280> done.<00:07:31.759> The<00:07:32.000> video<00:07:32.319> ad 00:07:32.629 --> 00:07:32.639 align:start position:0% after a while it's done. The video ad 00:07:32.639 --> 00:07:35.430 align:start position:0% after a while it's done. The video ad specialist<00:07:33.120> skill<00:07:33.520> is<00:07:34.080> ready.<00:07:34.720> And<00:07:35.120> we<00:07:35.360> can 00:07:35.430 --> 00:07:35.440 align:start position:0% specialist skill is ready. And we can 00:07:35.440 --> 00:07:37.270 align:start position:0% specialist skill is ready. And we can just<00:07:35.680> open<00:07:35.840> the<00:07:36.080> skills<00:07:36.400> folder<00:07:36.800> and<00:07:37.039> take<00:07:37.199> a 00:07:37.270 --> 00:07:37.280 align:start position:0% just open the skills folder and take a 00:07:37.280 --> 00:07:39.270 align:start position:0% just open the skills folder and take a look<00:07:37.440> at<00:07:37.680> what<00:07:38.000> Claude<00:07:38.400> actually<00:07:38.800> created. 00:07:39.270 --> 00:07:39.280 align:start position:0% look at what Claude actually created. 00:07:39.280 --> 00:07:41.189 align:start position:0% look at what Claude actually created. And<00:07:39.520> here<00:07:39.680> it<00:07:39.759> is.<00:07:40.000> We<00:07:40.319> have<00:07:40.400> a<00:07:40.800> section 00:07:41.189 --> 00:07:41.199 align:start position:0% And here it is. We have a section 00:07:41.199 --> 00:07:43.830 align:start position:0% And here it is. We have a section defining<00:07:41.840> where<00:07:42.080> the<00:07:42.319> skill<00:07:42.720> gets<00:07:43.039> triggered, 00:07:43.830 --> 00:07:43.840 align:start position:0% defining where the skill gets triggered, 00:07:43.840 --> 00:07:46.550 align:start position:0% defining where the skill gets triggered, a<00:07:44.160> critical<00:07:44.560> rule<00:07:44.880> that<00:07:45.280> can<00:07:45.520> tell<00:07:45.759> the<00:07:46.080> agent 00:07:46.550 --> 00:07:46.560 align:start position:0% a critical rule that can tell the agent 00:07:46.560 --> 00:07:49.110 align:start position:0% a critical rule that can tell the agent to<00:07:46.880> check<00:07:47.280> the<00:07:47.599> knowledge<00:07:48.080> files<00:07:48.720> before 00:07:49.110 --> 00:07:49.120 align:start position:0% to check the knowledge files before 00:07:49.120 --> 00:07:51.830 align:start position:0% to check the knowledge files before doing<00:07:49.360> anything<00:07:49.680> else<00:07:50.560> and<00:07:51.039> also<00:07:51.360> the<00:07:51.599> full 00:07:51.830 --> 00:07:51.840 align:start position:0% doing anything else and also the full 00:07:51.840 --> 00:07:54.070 align:start position:0% doing anything else and also the full workflow<00:07:52.319> steps<00:07:52.720> laid<00:07:52.960> out<00:07:53.120> in<00:07:53.360> order.<00:07:53.840> So 00:07:54.070 --> 00:07:54.080 align:start position:0% workflow steps laid out in order. So 00:07:54.080 --> 00:07:56.070 align:start position:0% workflow steps laid out in order. So basically<00:07:54.479> this<00:07:54.720> skill<00:07:55.039> wraps<00:07:55.440> around<00:07:55.759> the 00:07:56.070 --> 00:07:56.080 align:start position:0% basically this skill wraps around the 00:07:56.080 --> 00:07:59.270 align:start position:0% basically this skill wraps around the remote<00:07:56.639> skill.<00:07:57.520> So<00:07:57.759> what<00:07:58.000> that<00:07:58.240> means<00:07:58.560> is<00:07:59.039> the 00:07:59.270 --> 00:07:59.280 align:start position:0% remote skill. So what that means is the 00:07:59.280 --> 00:08:01.830 align:start position:0% remote skill. So what that means is the remotion<00:07:59.840> skill<00:08:00.319> handles<00:08:01.039> the<00:08:01.440> video 00:08:01.830 --> 00:08:01.840 align:start position:0% remotion skill handles the video 00:08:01.840 --> 00:08:04.550 align:start position:0% remotion skill handles the video creation<00:08:02.400> best<00:08:02.639> practices,<00:08:03.840> the<00:08:04.080> technical 00:08:04.550 --> 00:08:04.560 align:start position:0% creation best practices, the technical 00:08:04.560 --> 00:08:06.550 align:start position:0% creation best practices, the technical side,<00:08:05.120> the<00:08:05.440> rendering,<00:08:06.080> the<00:08:06.240> scene 00:08:06.550 --> 00:08:06.560 align:start position:0% side, the rendering, the scene 00:08:06.560 --> 00:08:09.110 align:start position:0% side, the rendering, the scene structure,<00:08:07.280> the<00:08:07.520> motion<00:08:07.840> logic,<00:08:08.479> etc.<00:08:08.879> And 00:08:09.110 --> 00:08:09.120 align:start position:0% structure, the motion logic, etc. And 00:08:09.120 --> 00:08:11.189 align:start position:0% structure, the motion logic, etc. And the<00:08:09.280> job<00:08:09.520> for<00:08:09.680> this<00:08:09.840> agent<00:08:10.160> skill<00:08:10.479> is<00:08:10.720> just 00:08:11.189 --> 00:08:11.199 align:start position:0% the job for this agent skill is just 00:08:11.199 --> 00:08:13.270 align:start position:0% the job for this agent skill is just focus<00:08:11.599> on<00:08:11.840> the<00:08:12.000> brand.<00:08:12.639> It<00:08:12.800> can<00:08:12.960> take 00:08:13.270 --> 00:08:13.280 align:start position:0% focus on the brand. It can take 00:08:13.280 --> 00:08:15.110 align:start position:0% focus on the brand. It can take everything<00:08:13.840> Remotion<00:08:14.319> knows<00:08:14.639> about<00:08:14.800> building 00:08:15.110 --> 00:08:15.120 align:start position:0% everything Remotion knows about building 00:08:15.120 --> 00:08:17.430 align:start position:0% everything Remotion knows about building Fido<00:08:15.520> and<00:08:15.680> filter<00:08:16.080> it<00:08:16.240> through<00:08:16.560> the<00:08:16.800> brand 00:08:17.430 --> 00:08:17.440 align:start position:0% Fido and filter it through the brand 00:08:17.440 --> 00:08:19.430 align:start position:0% Fido and filter it through the brand knowledge<00:08:18.000> that<00:08:18.240> we<00:08:18.400> set<00:08:18.560> up<00:08:18.800> earlier.<00:08:19.280> So 00:08:19.430 --> 00:08:19.440 align:start position:0% knowledge that we set up earlier. So 00:08:19.440 --> 00:08:21.510 align:start position:0% knowledge that we set up earlier. So basically,<00:08:19.759> it's<00:08:20.080> just<00:08:20.319> one<00:08:20.639> skill<00:08:21.039> handles 00:08:21.510 --> 00:08:21.520 align:start position:0% basically, it's just one skill handles 00:08:21.520 --> 00:08:23.749 align:start position:0% basically, it's just one skill handles the<00:08:21.759> craft<00:08:22.160> and<00:08:22.479> the<00:08:22.720> other<00:08:23.120> handles<00:08:23.520> the 00:08:23.749 --> 00:08:23.759 align:start position:0% the craft and the other handles the 00:08:23.759 --> 00:08:25.909 align:start position:0% the craft and the other handles the brand<00:08:24.319> and<00:08:24.560> together<00:08:25.039> they<00:08:25.280> can<00:08:25.440> produce 00:08:25.909 --> 00:08:25.919 align:start position:0% brand and together they can produce 00:08:25.919 --> 00:08:27.749 align:start position:0% brand and together they can produce something<00:08:26.240> that<00:08:26.560> is<00:08:26.800> both<00:08:27.199> technically 00:08:27.749 --> 00:08:27.759 align:start position:0% something that is both technically 00:08:27.759 --> 00:08:30.950 align:start position:0% something that is both technically wellbuilt<00:08:28.319> and<00:08:29.120> on<00:08:29.360> brand.<00:08:30.240> And<00:08:30.400> if<00:08:30.639> you<00:08:30.800> have 00:08:30.950 --> 00:08:30.960 align:start position:0% wellbuilt and on brand. And if you have 00:08:30.960 --> 00:08:33.350 align:start position:0% wellbuilt and on brand. And if you have not<00:08:31.360> installed<00:08:31.840> the<00:08:32.159> official<00:08:32.560> clot<00:08:32.959> remotion 00:08:33.350 --> 00:08:33.360 align:start position:0% not installed the official clot remotion 00:08:33.360 --> 00:08:35.670 align:start position:0% not installed the official clot remotion skill,<00:08:33.919> please<00:08:34.159> do<00:08:34.320> it<00:08:34.479> now.<00:08:34.959> And<00:08:35.200> also<00:08:35.440> you 00:08:35.670 --> 00:08:35.680 align:start position:0% skill, please do it now. And also you 00:08:35.680 --> 00:08:37.509 align:start position:0% skill, please do it now. And also you can<00:08:35.760> check<00:08:35.919> out<00:08:36.080> our<00:08:36.320> previous<00:08:36.640> video<00:08:36.959> on<00:08:37.200> how 00:08:37.509 --> 00:08:37.519 align:start position:0% can check out our previous video on how 00:08:37.519 --> 00:08:39.269 align:start position:0% can check out our previous video on how to<00:08:37.839> install<00:08:38.320> this<00:08:38.560> skill<00:08:38.800> as<00:08:38.959> well.<00:08:39.279> All 00:08:39.269 --> 00:08:39.279 align:start position:0% to install this skill as well. All 00:08:39.279 --> 00:08:40.870 align:start position:0% to install this skill as well. All right,<00:08:39.519> so<00:08:39.760> now<00:08:39.919> let's<00:08:40.159> move<00:08:40.320> on<00:08:40.479> to<00:08:40.640> the 00:08:40.870 --> 00:08:40.880 align:start position:0% right, so now let's move on to the 00:08:40.880 --> 00:08:43.509 align:start position:0% right, so now let's move on to the second<00:08:41.200> skill,<00:08:41.599> the<00:08:42.000> add<00:08:42.399> creative<00:08:42.959> designer. 00:08:43.509 --> 00:08:43.519 align:start position:0% second skill, the add creative designer. 00:08:43.519 --> 00:08:45.430 align:start position:0% second skill, the add creative designer. All<00:08:43.599> right,<00:08:43.760> so<00:08:44.000> same<00:08:44.320> process.<00:08:44.720> We<00:08:44.880> just<00:08:45.120> ask 00:08:45.430 --> 00:08:45.440 align:start position:0% All right, so same process. We just ask 00:08:45.440 --> 00:08:47.590 align:start position:0% All right, so same process. We just ask Claude<00:08:45.920> to<00:08:46.080> create<00:08:46.320> a<00:08:46.480> new<00:08:46.720> skill<00:08:47.279> and 00:08:47.590 --> 00:08:47.600 align:start position:0% Claude to create a new skill and 00:08:47.600 --> 00:08:49.670 align:start position:0% Claude to create a new skill and reference<00:08:48.000> the<00:08:48.160> automate<00:08:48.720> clot<00:08:49.040> skills<00:08:49.440> and 00:08:49.670 --> 00:08:49.680 align:start position:0% reference the automate clot skills and 00:08:49.680 --> 00:08:52.550 align:start position:0% reference the automate clot skills and plugins<00:08:50.320> document<00:08:50.720> as<00:08:50.880> the<00:08:51.120> guide<00:08:51.920> and<00:08:52.240> pasts 00:08:52.550 --> 00:08:52.560 align:start position:0% plugins document as the guide and pasts 00:08:52.560 --> 00:08:55.350 align:start position:0% plugins document as the guide and pasts in<00:08:52.880> the<00:08:53.200> key<00:08:53.440> details<00:08:53.920> for<00:08:54.160> this<00:08:54.399> agent.<00:08:55.040> And 00:08:55.350 --> 00:08:55.360 align:start position:0% in the key details for this agent. And 00:08:55.360 --> 00:08:57.670 align:start position:0% in the key details for this agent. And this<00:08:55.760> ad<00:08:56.080> creative<00:08:56.560> designer<00:08:57.279> has<00:08:57.519> a 00:08:57.670 --> 00:08:57.680 align:start position:0% this ad creative designer has a 00:08:57.680 --> 00:08:59.590 align:start position:0% this ad creative designer has a different<00:08:58.000> job<00:08:58.320> from<00:08:58.640> the<00:08:58.959> video<00:08:59.360> ad 00:08:59.590 --> 00:08:59.600 align:start position:0% different job from the video ad 00:08:59.600 --> 00:09:01.269 align:start position:0% different job from the video ad specialist.<00:09:00.320> So<00:09:00.480> for<00:09:00.640> the<00:09:00.720> feeder<00:09:01.120> ad 00:09:01.269 --> 00:09:01.279 align:start position:0% specialist. So for the feeder ad 00:09:01.279 --> 00:09:03.030 align:start position:0% specialist. So for the feeder ad specialist<00:09:01.760> that<00:09:02.000> agent<00:09:02.320> actually<00:09:02.560> generates 00:09:03.030 --> 00:09:03.040 align:start position:0% specialist that agent actually generates 00:09:03.040 --> 00:09:05.910 align:start position:0% specialist that agent actually generates motion<00:09:03.440> content<00:09:03.920> through<00:09:04.320> remotion<00:09:05.200> but<00:09:05.519> this 00:09:05.910 --> 00:09:05.920 align:start position:0% motion content through remotion but this 00:09:05.920 --> 00:09:08.070 align:start position:0% motion content through remotion but this ad<00:09:06.240> creative<00:09:06.720> designer<00:09:07.200> agent<00:09:07.600> actually 00:09:08.070 --> 00:09:08.080 align:start position:0% ad creative designer agent actually 00:09:08.080 --> 00:09:10.949 align:start position:0% ad creative designer agent actually focuses<00:09:08.720> on<00:09:08.959> static<00:09:09.519> ad<00:09:09.839> creatives<00:09:10.640> like 00:09:10.949 --> 00:09:10.959 align:start position:0% focuses on static ad creatives like 00:09:10.959 --> 00:09:13.190 align:start position:0% focuses on static ad creatives like square<00:09:11.279> format<00:09:11.920> Instagram<00:09:12.399> ready<00:09:12.880> built 00:09:13.190 --> 00:09:13.200 align:start position:0% square format Instagram ready built 00:09:13.200 --> 00:09:16.070 align:start position:0% square format Instagram ready built through<00:09:13.519> HTML<00:09:14.240> and<00:09:14.640> captured<00:09:15.200> as<00:09:15.519> a<00:09:15.760> clean 00:09:16.070 --> 00:09:16.080 align:start position:0% through HTML and captured as a clean 00:09:16.080 --> 00:09:18.150 align:start position:0% through HTML and captured as a clean image.<00:09:16.640> So<00:09:16.880> basically<00:09:17.440> same<00:09:17.760> prompt 00:09:18.150 --> 00:09:18.160 align:start position:0% image. So basically same prompt 00:09:18.160 --> 00:09:20.550 align:start position:0% image. So basically same prompt structure<00:09:18.720> just<00:09:19.279> different<00:09:19.760> skill<00:09:20.080> brief. 00:09:20.550 --> 00:09:20.560 align:start position:0% structure just different skill brief. 00:09:20.560 --> 00:09:22.710 align:start position:0% structure just different skill brief. All<00:09:20.640> right<00:09:20.880> so<00:09:21.040> let<00:09:21.279> us<00:09:21.519> hit<00:09:21.839> enter<00:09:22.240> and<00:09:22.480> wait 00:09:22.710 --> 00:09:22.720 align:start position:0% All right so let us hit enter and wait 00:09:22.720 --> 00:09:25.509 align:start position:0% All right so let us hit enter and wait for<00:09:22.959> clot<00:09:23.440> to<00:09:23.600> finish.<00:09:24.640> And<00:09:24.880> there<00:09:25.040> it<00:09:25.200> is. 00:09:25.509 --> 00:09:25.519 align:start position:0% for clot to finish. And there it is. 00:09:25.519 --> 00:09:27.829 align:start position:0% for clot to finish. And there it is. Both<00:09:25.920> skills<00:09:26.320> are<00:09:26.480> now<00:09:26.720> built<00:09:27.120> and<00:09:27.440> ready<00:09:27.680> for 00:09:27.829 --> 00:09:27.839 align:start position:0% Both skills are now built and ready for 00:09:27.839 --> 00:09:29.590 align:start position:0% Both skills are now built and ready for the<00:09:28.080> project.<00:09:28.560> And<00:09:28.720> as<00:09:28.959> you<00:09:29.120> can<00:09:29.200> see<00:09:29.360> the 00:09:29.590 --> 00:09:29.600 align:start position:0% the project. And as you can see the 00:09:29.600 --> 00:09:31.509 align:start position:0% the project. And as you can see the structure<00:09:30.000> is<00:09:30.240> very<00:09:30.640> similar<00:09:30.880> to<00:09:31.040> the<00:09:31.200> video 00:09:31.509 --> 00:09:31.519 align:start position:0% structure is very similar to the video 00:09:31.519 --> 00:09:34.230 align:start position:0% structure is very similar to the video ad<00:09:31.760> specialist<00:09:32.560> like<00:09:32.880> same<00:09:33.200> trigger<00:09:33.600> logic 00:09:34.230 --> 00:09:34.240 align:start position:0% ad specialist like same trigger logic 00:09:34.240 --> 00:09:36.230 align:start position:0% ad specialist like same trigger logic same<00:09:34.480> rule<00:09:34.880> about<00:09:35.279> checking<00:09:35.680> the<00:09:35.839> knowledge 00:09:36.230 --> 00:09:36.240 align:start position:0% same rule about checking the knowledge 00:09:36.240 --> 00:09:38.870 align:start position:0% same rule about checking the knowledge files<00:09:36.640> first<00:09:37.680> same<00:09:38.000> step-by-step 00:09:38.870 --> 00:09:38.880 align:start position:0% files first same step-by-step 00:09:38.880 --> 00:09:41.750 align:start position:0% files first same step-by-step workflowful<00:09:39.279> format<00:09:40.399> but<00:09:40.720> the<00:09:41.120> way<00:09:41.440> this 00:09:41.750 --> 00:09:41.760 align:start position:0% workflowful format but the way this 00:09:41.760 --> 00:09:43.829 align:start position:0% workflowful format but the way this agent<00:09:42.160> actually<00:09:42.399> works<00:09:42.640> is<00:09:43.040> quite<00:09:43.519> different 00:09:43.829 --> 00:09:43.839 align:start position:0% agent actually works is quite different 00:09:43.839 --> 00:09:47.030 align:start position:0% agent actually works is quite different from<00:09:44.160> the<00:09:44.480> video<00:09:44.959> one<00:09:46.080> and<00:09:46.320> here's<00:09:46.640> how<00:09:46.800> this 00:09:47.030 --> 00:09:47.040 align:start position:0% from the video one and here's how this 00:09:47.040 --> 00:09:49.829 align:start position:0% from the video one and here's how this one<00:09:47.279> works.<00:09:48.160> So<00:09:48.399> basically<00:09:48.800> it<00:09:49.040> starts<00:09:49.360> by 00:09:49.829 --> 00:09:49.839 align:start position:0% one works. So basically it starts by 00:09:49.839 --> 00:09:52.949 align:start position:0% one works. So basically it starts by calling<00:09:50.240> nanobanana<00:09:51.200> mcp<00:09:52.320> which<00:09:52.640> can 00:09:52.949 --> 00:09:52.959 align:start position:0% calling nanobanana mcp which can 00:09:52.959 --> 00:09:54.790 align:start position:0% calling nanobanana mcp which can generate<00:09:53.600> images<00:09:54.080> using<00:09:54.320> the<00:09:54.480> branch 00:09:54.790 --> 00:09:54.800 align:start position:0% generate images using the branch 00:09:54.800 --> 00:09:57.350 align:start position:0% generate images using the branch knowledge<00:09:55.200> folder<00:09:55.839> and<00:09:56.240> the<00:09:56.480> sample<00:09:56.959> assets 00:09:57.350 --> 00:09:57.360 align:start position:0% knowledge folder and the sample assets 00:09:57.360 --> 00:09:59.990 align:start position:0% knowledge folder and the sample assets we<00:09:57.600> set<00:09:57.839> up<00:09:58.160> earlier<00:09:58.560> as<00:09:58.800> visual<00:09:59.200> reference. 00:09:59.990 --> 00:10:00.000 align:start position:0% we set up earlier as visual reference. 00:10:00.000 --> 00:10:02.710 align:start position:0% we set up earlier as visual reference. So<00:10:00.240> the<00:10:00.560> images<00:10:01.040> it<00:10:01.279> can<00:10:01.519> produce<00:10:01.920> are<00:10:02.240> not 00:10:02.710 --> 00:10:02.720 align:start position:0% So the images it can produce are not 00:10:02.720 --> 00:10:05.910 align:start position:0% So the images it can produce are not random.<00:10:03.440> They<00:10:03.680> are<00:10:04.080> informed<00:10:04.959> by<00:10:05.200> the<00:10:05.440> brand 00:10:05.910 --> 00:10:05.920 align:start position:0% random. They are informed by the brand 00:10:05.920 --> 00:10:08.470 align:start position:0% random. They are informed by the brand and<00:10:06.160> from<00:10:06.320> that<00:10:06.560> it<00:10:06.800> just<00:10:06.959> uses<00:10:07.680> the<00:10:07.920> react 00:10:08.470 --> 00:10:08.480 align:start position:0% and from that it just uses the react 00:10:08.480 --> 00:10:11.269 align:start position:0% and from that it just uses the react canvas<00:10:08.959> to<00:10:09.279> design<00:10:09.519> the<00:10:09.839> static<00:10:10.240> at<00:10:10.640> layout<00:10:10.880> in 00:10:11.269 --> 00:10:11.279 align:start position:0% canvas to design the static at layout in 00:10:11.279 --> 00:10:16.310 align:start position:0% canvas to design the static at layout in HTML<00:10:12.560> like<00:10:13.040> typography<00:10:14.240> spacing<00:10:14.959> color<00:10:15.440> etc. 00:10:16.310 --> 00:10:16.320 align:start position:0% HTML like typography spacing color etc. 00:10:16.320 --> 00:10:18.470 align:start position:0% HTML like typography spacing color etc. All<00:10:16.640> applied<00:10:17.440> according<00:10:17.839> to<00:10:17.920> the<00:10:18.160> brand 00:10:18.470 --> 00:10:18.480 align:start position:0% All applied according to the brand 00:10:18.480 --> 00:10:20.630 align:start position:0% All applied according to the brand guidelines<00:10:19.279> and<00:10:19.440> then<00:10:19.680> this<00:10:19.920> is<00:10:20.079> the<00:10:20.320> part 00:10:20.630 --> 00:10:20.640 align:start position:0% guidelines and then this is the part 00:10:20.640 --> 00:10:23.110 align:start position:0% guidelines and then this is the part that<00:10:21.040> can<00:10:21.360> make<00:10:21.760> the<00:10:22.079> output<00:10:22.560> clean<00:10:22.800> and 00:10:23.110 --> 00:10:23.120 align:start position:0% that can make the output clean and 00:10:23.120 --> 00:10:25.509 align:start position:0% that can make the output clean and production<00:10:23.680> ready.<00:10:24.560> It<00:10:24.720> just<00:10:24.880> launches<00:10:25.279> a 00:10:25.509 --> 00:10:25.519 align:start position:0% production ready. It just launches a 00:10:25.519 --> 00:10:28.150 align:start position:0% production ready. It just launches a playright<00:10:26.160> browser<00:10:26.720> to<00:10:26.959> take<00:10:27.200> a<00:10:27.519> precise 00:10:28.150 --> 00:10:28.160 align:start position:0% playright browser to take a precise 00:10:28.160 --> 00:10:32.310 align:start position:0% playright browser to take a precise capture<00:10:28.800> of<00:10:29.040> that<00:10:29.440> HTML<00:10:30.640> file<00:10:31.279> and<00:10:31.680> saves<00:10:32.160> it 00:10:32.310 --> 00:10:32.320 align:start position:0% capture of that HTML file and saves it 00:10:32.320 --> 00:10:35.190 align:start position:0% capture of that HTML file and saves it as<00:10:32.640> a<00:10:33.120> PNG<00:10:33.760> file.<00:10:34.240> So<00:10:34.399> what<00:10:34.560> you<00:10:34.720> end<00:10:34.880> up<00:10:35.040> with 00:10:35.190 --> 00:10:35.200 align:start position:0% as a PNG file. So what you end up with 00:10:35.200 --> 00:10:38.470 align:start position:0% as a PNG file. So what you end up with is<00:10:35.600> not<00:10:36.079> just<00:10:36.320> a<00:10:36.640> rough<00:10:36.959> export<00:10:37.360> or<00:10:37.600> a<00:10:38.000> browser 00:10:38.470 --> 00:10:38.480 align:start position:0% is not just a rough export or a browser 00:10:38.480 --> 00:10:41.269 align:start position:0% is not just a rough export or a browser screenshot.<00:10:39.360> It<00:10:39.519> is<00:10:39.680> a<00:10:39.920> pixel<00:10:40.480> accurate<00:10:41.040> image 00:10:41.269 --> 00:10:41.279 align:start position:0% screenshot. It is a pixel accurate image 00:10:41.279 --> 00:10:44.230 align:start position:0% screenshot. It is a pixel accurate image of<00:10:41.519> a<00:10:41.680> designed<00:10:42.160> ad<00:10:42.800> ready<00:10:43.120> to<00:10:43.360> upload.<00:10:44.000> So 00:10:44.230 --> 00:10:44.240 align:start position:0% of a designed ad ready to upload. So 00:10:44.240 --> 00:10:46.630 align:start position:0% of a designed ad ready to upload. So this<00:10:44.720> three-step<00:10:45.279> workflow,<00:10:45.920> generate, 00:10:46.630 --> 00:10:46.640 align:start position:0% this three-step workflow, generate, 00:10:46.640 --> 00:10:49.030 align:start position:0% this three-step workflow, generate, design,<00:10:47.200> capture<00:10:47.839> is<00:10:48.079> what<00:10:48.399> actually<00:10:48.720> makes 00:10:49.030 --> 00:10:49.040 align:start position:0% design, capture is what actually makes 00:10:49.040 --> 00:10:50.949 align:start position:0% design, capture is what actually makes this<00:10:49.279> agent<00:10:49.680> produce<00:10:50.160> something<00:10:50.640> that 00:10:50.949 --> 00:10:50.959 align:start position:0% this agent produce something that 00:10:50.959 --> 00:10:53.350 align:start position:0% this agent produce something that actually<00:10:51.360> looks<00:10:51.680> like<00:10:52.160> it<00:10:52.480> came<00:10:52.800> from<00:10:53.120> a 00:10:53.350 --> 00:10:53.360 align:start position:0% actually looks like it came from a 00:10:53.360 --> 00:10:55.030 align:start position:0% actually looks like it came from a creative<00:10:53.760> team.<00:10:54.160> All<00:10:54.160> right,<00:10:54.399> so<00:10:54.560> to<00:10:54.800> set<00:10:54.880> up 00:10:55.030 --> 00:10:55.040 align:start position:0% creative team. All right, so to set up 00:10:55.040 --> 00:10:57.990 align:start position:0% creative team. All right, so to set up the<00:10:55.279> playright<00:10:56.000> SDK,<00:10:56.720> you<00:10:56.959> can<00:10:57.120> check<00:10:57.279> out<00:10:57.519> our 00:10:57.990 --> 00:10:58.000 align:start position:0% the playright SDK, you can check out our 00:10:58.000 --> 00:11:00.310 align:start position:0% the playright SDK, you can check out our previous<00:10:58.399> video<00:10:58.720> where<00:10:59.040> we<00:10:59.279> also<00:11:00.000> did 00:11:00.310 --> 00:11:00.320 align:start position:0% previous video where we also did 00:11:00.320 --> 00:11:02.230 align:start position:0% previous video where we also did something<00:11:00.720> similar<00:11:01.120> to<00:11:01.279> this<00:11:01.760> and<00:11:02.000> you<00:11:02.160> can 00:11:02.230 --> 00:11:02.240 align:start position:0% something similar to this and you can 00:11:02.240 --> 00:11:04.069 align:start position:0% something similar to this and you can find<00:11:02.480> the<00:11:02.720> link<00:11:02.959> in<00:11:03.120> the<00:11:03.360> description.<00:11:03.839> And 00:11:04.069 --> 00:11:04.079 align:start position:0% find the link in the description. And 00:11:04.079 --> 00:11:06.790 align:start position:0% find the link in the description. And now<00:11:04.320> let's<00:11:04.640> test<00:11:05.040> the<00:11:05.440> agents.<00:11:06.240> We<00:11:06.399> will<00:11:06.640> start 00:11:06.790 --> 00:11:06.800 align:start position:0% now let's test the agents. We will start 00:11:06.800 --> 00:11:09.829 align:start position:0% now let's test the agents. We will start with<00:11:07.040> the<00:11:07.360> ad<00:11:07.680> creative<00:11:08.160> designer<00:11:09.040> and<00:11:09.519> the 00:11:09.829 --> 00:11:09.839 align:start position:0% with the ad creative designer and the 00:11:09.839 --> 00:11:12.069 align:start position:0% with the ad creative designer and the static<00:11:10.240> ad.<00:11:10.720> So<00:11:10.959> here's<00:11:11.200> the<00:11:11.360> prompt<00:11:11.680> that<00:11:11.920> we 00:11:12.069 --> 00:11:12.079 align:start position:0% static ad. So here's the prompt that we 00:11:12.079 --> 00:11:14.069 align:start position:0% static ad. So here's the prompt that we are<00:11:12.240> going<00:11:12.399> to<00:11:12.560> use.<00:11:13.120> and<00:11:13.279> let<00:11:13.519> me<00:11:13.680> walk<00:11:13.839> you 00:11:14.069 --> 00:11:14.079 align:start position:0% are going to use. and let me walk you 00:11:14.079 --> 00:11:16.630 align:start position:0% are going to use. and let me walk you through<00:11:14.240> it.<00:11:14.959> So,<00:11:15.200> first<00:11:15.519> we<00:11:15.760> just<00:11:16.000> state<00:11:16.320> the 00:11:16.630 --> 00:11:16.640 align:start position:0% through it. So, first we just state the 00:11:16.640 --> 00:11:19.269 align:start position:0% through it. So, first we just state the task<00:11:17.040> and<00:11:17.279> mention<00:11:17.760> the<00:11:18.079> skill<00:11:18.640> we<00:11:18.959> want<00:11:19.040> to 00:11:19.269 --> 00:11:19.279 align:start position:0% task and mention the skill we want to 00:11:19.279 --> 00:11:21.350 align:start position:0% task and mention the skill we want to use.<00:11:19.920> And<00:11:20.160> now<00:11:20.320> you<00:11:20.480> can<00:11:20.560> trigger<00:11:20.880> a<00:11:21.040> skill 00:11:21.350 --> 00:11:21.360 align:start position:0% use. And now you can trigger a skill 00:11:21.360 --> 00:11:24.230 align:start position:0% use. And now you can trigger a skill without<00:11:21.760> naming<00:11:22.160> it<00:11:22.320> directly<00:11:23.440> because<00:11:23.760> cloud 00:11:24.230 --> 00:11:24.240 align:start position:0% without naming it directly because cloud 00:11:24.240 --> 00:11:27.269 align:start position:0% without naming it directly because cloud is<00:11:24.640> intuitive<00:11:25.279> enough<00:11:25.600> to<00:11:25.839> pick<00:11:26.079> it<00:11:26.320> up<00:11:26.880> from 00:11:27.269 --> 00:11:27.279 align:start position:0% is intuitive enough to pick it up from 00:11:27.279 --> 00:11:29.509 align:start position:0% is intuitive enough to pick it up from natural<00:11:27.680> language<00:11:28.320> most<00:11:28.560> of<00:11:28.720> the<00:11:28.959> time.<00:11:29.360> But 00:11:29.509 --> 00:11:29.519 align:start position:0% natural language most of the time. But 00:11:29.519 --> 00:11:32.069 align:start position:0% natural language most of the time. But if<00:11:29.680> you<00:11:29.839> want<00:11:29.920> to<00:11:30.160> make<00:11:30.399> absolutely<00:11:31.279> sure<00:11:31.760> that 00:11:32.069 --> 00:11:32.079 align:start position:0% if you want to make absolutely sure that 00:11:32.079 --> 00:11:34.310 align:start position:0% if you want to make absolutely sure that the<00:11:32.320> right<00:11:32.640> skill<00:11:32.880> is<00:11:33.120> being<00:11:33.360> used,<00:11:34.079> just 00:11:34.310 --> 00:11:34.320 align:start position:0% the right skill is being used, just 00:11:34.320 --> 00:11:36.630 align:start position:0% the right skill is being used, just mention<00:11:34.640> it<00:11:35.040> and<00:11:35.279> then<00:11:35.519> prompt.<00:11:36.079> And<00:11:36.240> then<00:11:36.399> the 00:11:36.630 --> 00:11:36.640 align:start position:0% mention it and then prompt. And then the 00:11:36.640 --> 00:11:39.190 align:start position:0% mention it and then prompt. And then the goal<00:11:36.880> for<00:11:37.040> this<00:11:37.279> prompt<00:11:37.600> is<00:11:38.000> very<00:11:38.320> simple. 00:11:39.190 --> 00:11:39.200 align:start position:0% goal for this prompt is very simple. 00:11:39.200 --> 00:11:41.990 align:start position:0% goal for this prompt is very simple. Just<00:11:39.600> produce<00:11:40.160> an<00:11:40.560> Instagram<00:11:41.120> ad.<00:11:41.600> We<00:11:41.839> just 00:11:41.990 --> 00:11:42.000 align:start position:0% Just produce an Instagram ad. We just 00:11:42.000 --> 00:11:44.389 align:start position:0% Just produce an Instagram ad. We just supply<00:11:42.320> it<00:11:42.480> with<00:11:42.800> JSON<00:11:43.200> inputs<00:11:43.760> that<00:11:44.079> can 00:11:44.389 --> 00:11:44.399 align:start position:0% supply it with JSON inputs that can 00:11:44.399 --> 00:11:47.190 align:start position:0% supply it with JSON inputs that can define<00:11:44.959> what<00:11:45.200> the<00:11:45.440> ad<00:11:45.839> should<00:11:46.320> contain<00:11:46.959> like 00:11:47.190 --> 00:11:47.200 align:start position:0% define what the ad should contain like 00:11:47.200 --> 00:11:49.190 align:start position:0% define what the ad should contain like the<00:11:47.440> headline,<00:11:48.079> the<00:11:48.240> copy<00:11:48.560> and<00:11:48.720> the<00:11:48.800> facial 00:11:49.190 --> 00:11:49.200 align:start position:0% the headline, the copy and the facial 00:11:49.200 --> 00:11:51.190 align:start position:0% the headline, the copy and the facial direction.<00:11:49.839> And<00:11:50.000> then<00:11:50.160> we<00:11:50.320> just<00:11:50.560> instruct<00:11:50.959> it 00:11:51.190 --> 00:11:51.200 align:start position:0% direction. And then we just instruct it 00:11:51.200 --> 00:11:54.550 align:start position:0% direction. And then we just instruct it to<00:11:51.440> build<00:11:51.680> the<00:11:51.839> ad<00:11:52.160> in<00:11:52.480> HTML<00:11:53.279> with<00:11:53.680> CSS<00:11:54.160> styling 00:11:54.550 --> 00:11:54.560 align:start position:0% to build the ad in HTML with CSS styling 00:11:54.560 --> 00:11:56.310 align:start position:0% to build the ad in HTML with CSS styling applied.<00:11:55.120> And<00:11:55.360> that<00:11:55.519> is<00:11:55.760> exactly<00:11:56.079> the 00:11:56.310 --> 00:11:56.320 align:start position:0% applied. And that is exactly the 00:11:56.320 --> 00:11:58.790 align:start position:0% applied. And that is exactly the workflow<00:11:56.720> we<00:11:56.959> walked<00:11:57.360> through<00:11:57.760> earlier. 00:11:58.790 --> 00:11:58.800 align:start position:0% workflow we walked through earlier. 00:11:58.800 --> 00:12:01.110 align:start position:0% workflow we walked through earlier. Generate,<00:11:59.600> design,<00:12:00.320> and<00:12:00.640> capture.<00:12:01.120> All 00:12:01.110 --> 00:12:01.120 align:start position:0% Generate, design, and capture. All 00:12:01.120 --> 00:12:02.949 align:start position:0% Generate, design, and capture. All right.<00:12:01.360> So<00:12:01.519> now<00:12:01.680> I've<00:12:01.920> already<00:12:02.399> run<00:12:02.720> this 00:12:02.949 --> 00:12:02.959 align:start position:0% right. So now I've already run this 00:12:02.959 --> 00:12:05.269 align:start position:0% right. So now I've already run this prompt<00:12:03.360> and<00:12:03.680> as<00:12:03.920> you<00:12:04.079> can<00:12:04.160> see<00:12:04.560> all<00:12:04.720> the<00:12:04.959> steps 00:12:05.269 --> 00:12:05.279 align:start position:0% prompt and as you can see all the steps 00:12:05.279 --> 00:12:07.590 align:start position:0% prompt and as you can see all the steps have<00:12:05.600> finished<00:12:06.000> executing.<00:12:06.959> So<00:12:07.120> let's<00:12:07.360> just 00:12:07.590 --> 00:12:07.600 align:start position:0% have finished executing. So let's just 00:12:07.600 --> 00:12:10.389 align:start position:0% have finished executing. So let's just open<00:12:07.839> the<00:12:08.079> output<00:12:08.560> folder<00:12:09.440> and<00:12:09.760> see<00:12:09.920> what<00:12:10.160> came 00:12:10.389 --> 00:12:10.399 align:start position:0% open the output folder and see what came 00:12:10.399 --> 00:12:14.310 align:start position:0% open the output folder and see what came out.<00:12:11.279> And<00:12:11.519> here<00:12:11.680> it<00:12:11.839> is.<00:12:12.720> So<00:12:13.040> honestly<00:12:13.519> for<00:12:14.079> the 00:12:14.310 --> 00:12:14.320 align:start position:0% out. And here it is. So honestly for the 00:12:14.320 --> 00:12:16.550 align:start position:0% out. And here it is. So honestly for the amount<00:12:14.560> of<00:12:14.720> input<00:12:15.040> we<00:12:15.279> gave<00:12:15.440> it,<00:12:16.000> it<00:12:16.160> is<00:12:16.320> a 00:12:16.550 --> 00:12:16.560 align:start position:0% amount of input we gave it, it is a 00:12:16.560 --> 00:12:19.750 align:start position:0% amount of input we gave it, it is a pretty<00:12:16.959> strong<00:12:17.360> result.<00:12:18.560> Like<00:12:18.959> just<00:12:19.279> basic 00:12:19.750 --> 00:12:19.760 align:start position:0% pretty strong result. Like just basic 00:12:19.760 --> 00:12:22.389 align:start position:0% pretty strong result. Like just basic JSON<00:12:20.240> inputs,<00:12:20.880> a<00:12:21.120> simple<00:12:21.440> prompt,<00:12:22.079> no 00:12:22.389 --> 00:12:22.399 align:start position:0% JSON inputs, a simple prompt, no 00:12:22.399 --> 00:12:25.350 align:start position:0% JSON inputs, a simple prompt, no detailed<00:12:23.120> design<00:12:23.519> brief<00:12:23.839> at<00:12:24.000> all,<00:12:24.560> no<00:12:24.880> menu 00:12:25.350 --> 00:12:25.360 align:start position:0% detailed design brief at all, no menu 00:12:25.360 --> 00:12:28.389 align:start position:0% detailed design brief at all, no menu layout<00:12:25.680> work,<00:12:26.560> and<00:12:26.800> the<00:12:27.040> agent<00:12:27.440> can<00:12:27.760> produce<00:12:28.160> a 00:12:28.389 --> 00:12:28.399 align:start position:0% layout work, and the agent can produce a 00:12:28.399 --> 00:12:31.750 align:start position:0% layout work, and the agent can produce a clean<00:12:28.880> styled<00:12:29.600> onbrand<00:12:30.240> static<00:12:30.639> ad<00:12:31.360> and<00:12:31.600> ready 00:12:31.750 --> 00:12:31.760 align:start position:0% clean styled onbrand static ad and ready 00:12:31.760 --> 00:12:34.310 align:start position:0% clean styled onbrand static ad and ready to<00:12:32.000> use.<00:12:32.880> So<00:12:33.120> this<00:12:33.279> is<00:12:33.440> what<00:12:33.760> a<00:12:34.000> well 00:12:34.310 --> 00:12:34.320 align:start position:0% to use. So this is what a well 00:12:34.320 --> 00:12:36.389 align:start position:0% to use. So this is what a well ststructured<00:12:35.040> skill<00:12:35.360> with<00:12:35.680> good<00:12:36.079> brand 00:12:36.389 --> 00:12:36.399 align:start position:0% ststructured skill with good brand 00:12:36.399 --> 00:12:38.710 align:start position:0% ststructured skill with good brand context<00:12:36.880> can<00:12:37.200> deliver.<00:12:37.839> So<00:12:37.920> you<00:12:38.160> do<00:12:38.320> not<00:12:38.480> need 00:12:38.710 --> 00:12:38.720 align:start position:0% context can deliver. So you do not need 00:12:38.720 --> 00:12:42.150 align:start position:0% context can deliver. So you do not need to<00:12:39.040> overengineer<00:12:40.240> the<00:12:40.480> prompt<00:12:41.519> because<00:12:41.839> the 00:12:42.150 --> 00:12:42.160 align:start position:0% to overengineer the prompt because the 00:12:42.160 --> 00:12:45.030 align:start position:0% to overengineer the prompt because the skill<00:12:42.480> can<00:12:42.800> already<00:12:43.360> know<00:12:44.079> what<00:12:44.320> to<00:12:44.639> do<00:12:44.800> with 00:12:45.030 --> 00:12:45.040 align:start position:0% skill can already know what to do with 00:12:45.040 --> 00:12:46.870 align:start position:0% skill can already know what to do with the<00:12:45.279> information<00:12:45.680> you<00:12:45.920> give<00:12:46.079> it.<00:12:46.399> So<00:12:46.639> now 00:12:46.870 --> 00:12:46.880 align:start position:0% the information you give it. So now 00:12:46.880 --> 00:12:49.670 align:start position:0% the information you give it. So now let's<00:12:47.200> test<00:12:47.600> the<00:12:47.920> video<00:12:48.240> ad<00:12:48.480> specialist.<00:12:49.440> And 00:12:49.670 --> 00:12:49.680 align:start position:0% let's test the video ad specialist. And 00:12:49.680 --> 00:12:50.949 align:start position:0% let's test the video ad specialist. And here's<00:12:49.920> the<00:12:50.160> prompt<00:12:50.399> that<00:12:50.560> we're<00:12:50.720> going<00:12:50.800> to 00:12:50.949 --> 00:12:50.959 align:start position:0% here's the prompt that we're going to 00:12:50.959 --> 00:12:53.910 align:start position:0% here's the prompt that we're going to use.<00:12:51.680> Just<00:12:51.920> like<00:12:52.079> the<00:12:52.399> static<00:12:52.720> ad,<00:12:53.440> we're<00:12:53.760> just 00:12:53.910 --> 00:12:53.920 align:start position:0% use. Just like the static ad, we're just 00:12:53.920 --> 00:12:56.790 align:start position:0% use. Just like the static ad, we're just keeping<00:12:54.240> it<00:12:54.399> very<00:12:54.720> simple.<00:12:55.839> We<00:12:56.160> are<00:12:56.320> going<00:12:56.560> to 00:12:56.790 --> 00:12:56.800 align:start position:0% keeping it very simple. We are going to 00:12:56.800 --> 00:12:59.670 align:start position:0% keeping it very simple. We are going to ask<00:12:57.120> it<00:12:57.440> to<00:12:57.839> create<00:12:58.160> a<00:12:58.480> promotional<00:12:59.040> video<00:12:59.440> for 00:12:59.670 --> 00:12:59.680 align:start position:0% ask it to create a promotional video for 00:12:59.680 --> 00:13:02.870 align:start position:0% ask it to create a promotional video for the<00:12:59.839> brand.<00:13:00.959> So<00:13:01.200> we<00:13:01.360> can<00:13:01.519> define<00:13:02.240> the<00:13:02.560> target 00:13:02.870 --> 00:13:02.880 align:start position:0% the brand. So we can define the target 00:13:02.880 --> 00:13:05.509 align:start position:0% the brand. So we can define the target audience<00:13:03.680> and<00:13:03.920> we<00:13:04.079> can<00:13:04.320> lay<00:13:04.480> out<00:13:04.639> five<00:13:04.959> sins<00:13:05.279> in 00:13:05.509 --> 00:13:05.519 align:start position:0% audience and we can lay out five sins in 00:13:05.519 --> 00:13:08.949 align:start position:0% audience and we can lay out five sins in total.<00:13:06.399> And<00:13:06.639> we<00:13:06.959> will<00:13:07.279> include<00:13:08.079> a<00:13:08.399> few<00:13:08.560> rules 00:13:08.949 --> 00:13:08.959 align:start position:0% total. And we will include a few rules 00:13:08.959 --> 00:13:12.470 align:start position:0% total. And we will include a few rules around<00:13:09.440> how<00:13:09.760> the<00:13:10.639> SVGs<00:13:11.519> should<00:13:11.839> be<00:13:12.000> handled. 00:13:12.470 --> 00:13:12.480 align:start position:0% around how the SVGs should be handled. 00:13:12.480 --> 00:13:14.790 align:start position:0% around how the SVGs should be handled. And<00:13:12.639> that's<00:13:12.800> it.<00:13:13.200> No<00:13:13.519> detailed<00:13:14.079> storyboard, 00:13:14.790 --> 00:13:14.800 align:start position:0% And that's it. No detailed storyboard, 00:13:14.800 --> 00:13:17.590 align:start position:0% And that's it. No detailed storyboard, no<00:13:15.040> frame<00:13:15.360> by<00:13:15.600> frame<00:13:15.920> direction,<00:13:16.880> just<00:13:17.200> the 00:13:17.590 --> 00:13:17.600 align:start position:0% no frame by frame direction, just the 00:13:17.600 --> 00:13:19.670 align:start position:0% no frame by frame direction, just the essentials.<00:13:18.160> And<00:13:18.560> we<00:13:18.800> can<00:13:18.959> let<00:13:19.120> the<00:13:19.360> skill 00:13:19.670 --> 00:13:19.680 align:start position:0% essentials. And we can let the skill 00:13:19.680 --> 00:13:21.990 align:start position:0% essentials. And we can let the skill fill<00:13:20.000> in<00:13:20.240> the<00:13:20.480> rest.<00:13:20.959> So<00:13:21.040> we<00:13:21.279> can<00:13:21.440> hit<00:13:21.600> enter 00:13:21.990 --> 00:13:22.000 align:start position:0% fill in the rest. So we can hit enter 00:13:22.000 --> 00:13:23.990 align:start position:0% fill in the rest. So we can hit enter and<00:13:22.240> wait<00:13:22.480> for<00:13:22.639> the<00:13:22.880> output.<00:13:23.360> So<00:13:23.600> now<00:13:23.760> you 00:13:23.990 --> 00:13:24.000 align:start position:0% and wait for the output. So now you 00:13:24.000 --> 00:13:26.150 align:start position:0% and wait for the output. So now you might<00:13:24.240> be<00:13:24.480> wondering<00:13:24.880> why<00:13:25.120> we<00:13:25.360> are<00:13:25.680> suddenly 00:13:26.150 --> 00:13:26.160 align:start position:0% might be wondering why we are suddenly 00:13:26.160 --> 00:13:29.590 align:start position:0% might be wondering why we are suddenly in<00:13:26.720> Google<00:13:27.040> anti-gravity's<00:13:28.000> AI<00:13:28.399> chat<00:13:28.959> when<00:13:29.279> we 00:13:29.590 --> 00:13:29.600 align:start position:0% in Google anti-gravity's AI chat when we 00:13:29.600 --> 00:13:32.389 align:start position:0% in Google anti-gravity's AI chat when we were<00:13:30.160> just<00:13:30.639> inside<00:13:31.279> clock<00:13:31.600> code.<00:13:32.079> So<00:13:32.160> the 00:13:32.389 --> 00:13:32.399 align:start position:0% were just inside clock code. So the 00:13:32.399 --> 00:13:34.389 align:start position:0% were just inside clock code. So the reason<00:13:32.560> is<00:13:32.880> very<00:13:33.040> straightforward.<00:13:33.920> These 00:13:34.389 --> 00:13:34.399 align:start position:0% reason is very straightforward. These 00:13:34.399 --> 00:13:36.790 align:start position:0% reason is very straightforward. These are<00:13:34.560> quick<00:13:34.800> individual<00:13:35.519> agent<00:13:36.000> tests.<00:13:36.399> We<00:13:36.560> do 00:13:36.790 --> 00:13:36.800 align:start position:0% are quick individual agent tests. We do 00:13:36.800 --> 00:13:39.430 align:start position:0% are quick individual agent tests. We do not<00:13:36.959> want<00:13:37.120> to<00:13:37.360> burn<00:13:37.600> through<00:13:38.000> CL<00:13:38.399> code<00:13:38.800> tokens 00:13:39.430 --> 00:13:39.440 align:start position:0% not want to burn through CL code tokens 00:13:39.440 --> 00:13:42.069 align:start position:0% not want to burn through CL code tokens on<00:13:39.839> isolated<00:13:40.480> test<00:13:40.800> runs.<00:13:41.200> Right?<00:13:41.600> So<00:13:41.760> for 00:13:42.069 --> 00:13:42.079 align:start position:0% on isolated test runs. Right? So for 00:13:42.079 --> 00:13:44.949 align:start position:0% on isolated test runs. Right? So for this<00:13:42.560> just<00:13:42.959> smaller<00:13:43.360> test,<00:13:44.160> we<00:13:44.399> can<00:13:44.560> just<00:13:44.720> use 00:13:44.949 --> 00:13:44.959 align:start position:0% this just smaller test, we can just use 00:13:44.959 --> 00:13:47.590 align:start position:0% this just smaller test, we can just use school<00:13:45.200> antigravity.<00:13:46.160> It<00:13:46.399> can<00:13:46.639> keep<00:13:47.120> things 00:13:47.590 --> 00:13:47.600 align:start position:0% school antigravity. It can keep things 00:13:47.600 --> 00:13:50.629 align:start position:0% school antigravity. It can keep things efficient<00:13:48.800> and<00:13:49.279> when<00:13:49.519> we<00:13:49.839> run<00:13:50.000> the<00:13:50.240> complete 00:13:50.629 --> 00:13:50.639 align:start position:0% efficient and when we run the complete 00:13:50.639 --> 00:13:53.750 align:start position:0% efficient and when we run the complete five<00:13:50.880> agent<00:13:51.279> pipeline<00:13:51.760> at<00:13:52.000> the<00:13:52.160> end<00:13:53.200> that<00:13:53.519> is 00:13:53.750 --> 00:13:53.760 align:start position:0% five agent pipeline at the end that is 00:13:53.760 --> 00:13:56.310 align:start position:0% five agent pipeline at the end that is when<00:13:54.079> we<00:13:54.240> are<00:13:54.399> going<00:13:54.639> to<00:13:54.880> go<00:13:55.120> back<00:13:55.600> into<00:13:55.920> cloud 00:13:56.310 --> 00:13:56.320 align:start position:0% when we are going to go back into cloud 00:13:56.320 --> 00:13:58.230 align:start position:0% when we are going to go back into cloud code<00:13:56.560> and<00:13:56.720> let<00:13:57.040> everything<00:13:57.519> run<00:13:57.760> together 00:13:58.230 --> 00:13:58.240 align:start position:0% code and let everything run together 00:13:58.240 --> 00:14:00.629 align:start position:0% code and let everything run together properly.<00:13:58.880> All<00:13:58.880> right.<00:13:59.120> So<00:13:59.440> this<00:13:59.600> is<00:13:59.760> done<00:14:00.240> and 00:14:00.629 --> 00:14:00.639 align:start position:0% properly. All right. So this is done and 00:14:00.639 --> 00:14:03.590 align:start position:0% properly. All right. So this is done and unlike<00:14:01.600> our<00:14:01.920> previous<00:14:02.399> remote<00:14:02.880> videos<00:14:03.279> where 00:14:03.590 --> 00:14:03.600 align:start position:0% unlike our previous remote videos where 00:14:03.600 --> 00:14:05.829 align:start position:0% unlike our previous remote videos where you<00:14:03.839> open<00:14:04.160> Remotion<00:14:04.639> Studio<00:14:05.040> and<00:14:05.279> manually 00:14:05.829 --> 00:14:05.839 align:start position:0% you open Remotion Studio and manually 00:14:05.839 --> 00:14:09.110 align:start position:0% you open Remotion Studio and manually click<00:14:06.240> render,<00:14:07.199> we<00:14:07.440> just<00:14:07.760> built<00:14:08.079> an<00:14:08.480> automatic 00:14:09.110 --> 00:14:09.120 align:start position:0% click render, we just built an automatic 00:14:09.120 --> 00:14:11.829 align:start position:0% click render, we just built an automatic render<00:14:09.600> script<00:14:10.079> directly<00:14:10.720> into<00:14:11.040> the<00:14:11.279> skill. 00:14:11.829 --> 00:14:11.839 align:start position:0% render script directly into the skill. 00:14:11.839 --> 00:14:14.150 align:start position:0% render script directly into the skill. So<00:14:12.000> the<00:14:12.240> finished<00:14:12.560> video<00:14:12.959> just<00:14:13.279> go<00:14:13.519> straight 00:14:14.150 --> 00:14:14.160 align:start position:0% So the finished video just go straight 00:14:14.160 --> 00:14:16.790 align:start position:0% So the finished video just go straight to<00:14:14.480> the<00:14:14.720> outputs<00:14:15.199> folder<00:14:15.519> without<00:14:16.000> any<00:14:16.399> menu 00:14:16.790 --> 00:14:16.800 align:start position:0% to the outputs folder without any menu 00:14:16.800 --> 00:14:18.790 align:start position:0% to the outputs folder without any menu steps.<00:14:17.360> And<00:14:17.519> let's<00:14:17.839> open<00:14:18.079> it<00:14:18.240> and<00:14:18.480> take<00:14:18.560> a<00:14:18.720> look 00:14:18.790 --> 00:14:18.800 align:start position:0% steps. And let's open it and take a look 00:14:18.800 --> 00:14:21.350 align:start position:0% steps. And let's open it and take a look at<00:14:18.959> this. 00:14:21.350 --> 00:14:21.360 align:start position:0% at this. 00:14:21.360 --> 00:14:23.670 align:start position:0% at this. Great.<00:14:21.680> It<00:14:21.839> looks<00:14:22.079> pretty<00:14:22.320> good.<00:14:23.360> Not 00:14:23.670 --> 00:14:23.680 align:start position:0% Great. It looks pretty good. Not 00:14:23.680 --> 00:14:25.829 align:start position:0% Great. It looks pretty good. Not mind-blowing,<00:14:24.639> but<00:14:24.959> with<00:14:25.120> the<00:14:25.360> prompt<00:14:25.680> we 00:14:25.829 --> 00:14:25.839 align:start position:0% mind-blowing, but with the prompt we 00:14:25.839 --> 00:14:27.910 align:start position:0% mind-blowing, but with the prompt we gave<00:14:26.000> it,<00:14:26.560> this<00:14:26.800> is<00:14:26.959> exactly<00:14:27.360> what<00:14:27.600> you 00:14:27.910 --> 00:14:27.920 align:start position:0% gave it, this is exactly what you 00:14:27.920 --> 00:14:30.310 align:start position:0% gave it, this is exactly what you expect.<00:14:28.720> So<00:14:28.959> what's<00:14:29.360> happening<00:14:29.680> here<00:14:29.839> is<00:14:30.079> that 00:14:30.310 --> 00:14:30.320 align:start position:0% expect. So what's happening here is that 00:14:30.320 --> 00:14:32.870 align:start position:0% expect. So what's happening here is that Claude<00:14:30.720> just<00:14:31.279> read<00:14:31.680> the<00:14:32.000> brand<00:14:32.480> knowledge 00:14:32.870 --> 00:14:32.880 align:start position:0% Claude just read the brand knowledge 00:14:32.880 --> 00:14:35.430 align:start position:0% Claude just read the brand knowledge folder<00:14:33.440> and<00:14:33.680> then<00:14:33.920> pulled<00:14:34.399> the<00:14:34.639> right<00:14:35.040> facial 00:14:35.430 --> 00:14:35.440 align:start position:0% folder and then pulled the right facial 00:14:35.440 --> 00:14:38.790 align:start position:0% folder and then pulled the right facial references<00:14:36.399> and<00:14:36.800> produced<00:14:37.600> an<00:14:37.920> infographic 00:14:38.790 --> 00:14:38.800 align:start position:0% references and produced an infographic 00:14:38.800 --> 00:14:42.150 align:start position:0% references and produced an infographic style<00:14:39.199> video<00:14:39.519> that<00:14:39.839> feels<00:14:40.480> on<00:14:40.720> brand.<00:14:41.440> So<00:14:41.920> no 00:14:42.150 --> 00:14:42.160 align:start position:0% style video that feels on brand. So no 00:14:42.160 --> 00:14:44.230 align:start position:0% style video that feels on brand. So no detailed<00:14:42.720> brief,<00:14:43.279> no<00:14:43.519> manual<00:14:43.839> scene 00:14:44.230 --> 00:14:44.240 align:start position:0% detailed brief, no manual scene 00:14:44.240 --> 00:14:46.710 align:start position:0% detailed brief, no manual scene building,<00:14:45.040> just<00:14:45.279> a<00:14:45.600> first<00:14:45.920> simple<00:14:46.160> prompt<00:14:46.480> and 00:14:46.710 --> 00:14:46.720 align:start position:0% building, just a first simple prompt and 00:14:46.720 --> 00:14:49.350 align:start position:0% building, just a first simple prompt and brand<00:14:47.040> context<00:14:47.760> and<00:14:48.079> that<00:14:48.320> is<00:14:48.639> the<00:14:48.880> solid 00:14:49.350 --> 00:14:49.360 align:start position:0% brand context and that is the solid 00:14:49.360 --> 00:14:51.590 align:start position:0% brand context and that is the solid baseline.<00:14:50.079> All<00:14:50.079> right.<00:14:50.399> So<00:14:50.720> both<00:14:51.199> creative 00:14:51.590 --> 00:14:51.600 align:start position:0% baseline. All right. So both creative 00:14:51.600 --> 00:14:54.389 align:start position:0% baseline. All right. So both creative agents<00:14:52.000> are<00:14:52.160> built<00:14:52.320> and<00:14:52.560> tested.<00:14:53.440> Now<00:14:53.839> we<00:14:54.079> can 00:14:54.389 --> 00:14:54.399 align:start position:0% agents are built and tested. Now we can 00:14:54.399 --> 00:14:57.189 align:start position:0% agents are built and tested. Now we can add<00:14:54.639> the<00:14:54.959> intelligence<00:14:55.839> layer<00:14:56.079> that<00:14:56.399> can<00:14:56.639> feed 00:14:57.189 --> 00:14:57.199 align:start position:0% add the intelligence layer that can feed 00:14:57.199 --> 00:15:00.230 align:start position:0% add the intelligence layer that can feed everything<00:14:58.079> which<00:14:58.399> is<00:14:58.560> the<00:14:58.880> research<00:14:59.600> agent. 00:15:00.230 --> 00:15:00.240 align:start position:0% everything which is the research agent. 00:15:00.240 --> 00:15:03.189 align:start position:0% everything which is the research agent. So<00:15:00.480> what<00:15:00.720> this<00:15:00.880> agent<00:15:01.279> actually<00:15:01.600> does<00:15:02.000> is<00:15:02.959> more 00:15:03.189 --> 00:15:03.199 align:start position:0% So what this agent actually does is more 00:15:03.199 --> 00:15:05.750 align:start position:0% So what this agent actually does is more than<00:15:03.440> just<00:15:03.680> research.<00:15:04.639> There<00:15:04.880> are<00:15:05.279> basically 00:15:05.750 --> 00:15:05.760 align:start position:0% than just research. There are basically 00:15:05.760 --> 00:15:08.150 align:start position:0% than just research. There are basically two<00:15:06.000> things<00:15:06.240> happening<00:15:06.560> here.<00:15:07.360> The<00:15:07.600> agent 00:15:08.150 --> 00:15:08.160 align:start position:0% two things happening here. The agent 00:15:08.160 --> 00:15:11.750 align:start position:0% two things happening here. The agent finds<00:15:08.560> and<00:15:08.959> synthesizes<00:15:10.079> information<00:15:11.120> but<00:15:11.440> it 00:15:11.750 --> 00:15:11.760 align:start position:0% finds and synthesizes information but it 00:15:11.760 --> 00:15:13.670 align:start position:0% finds and synthesizes information but it also<00:15:12.079> creates<00:15:12.480> resources<00:15:13.040> that<00:15:13.279> you<00:15:13.519> can 00:15:13.670 --> 00:15:13.680 align:start position:0% also creates resources that you can 00:15:13.680 --> 00:15:16.069 align:start position:0% also creates resources that you can specialize<00:15:14.160> and<00:15:14.480> share<00:15:14.800> with<00:15:15.199> other<00:15:15.519> people. 00:15:16.069 --> 00:15:16.079 align:start position:0% specialize and share with other people. 00:15:16.079 --> 00:15:18.069 align:start position:0% specialize and share with other people. So<00:15:16.320> you<00:15:16.480> can<00:15:16.639> think<00:15:16.800> about<00:15:17.040> like<00:15:17.440> formatted 00:15:18.069 --> 00:15:18.079 align:start position:0% So you can think about like formatted 00:15:18.079 --> 00:15:20.949 align:start position:0% So you can think about like formatted briefs,<00:15:18.720> structured<00:15:19.360> outputs,<00:15:20.320> things<00:15:20.560> that 00:15:20.949 --> 00:15:20.959 align:start position:0% briefs, structured outputs, things that 00:15:20.959 --> 00:15:23.829 align:start position:0% briefs, structured outputs, things that you<00:15:21.199> can<00:15:21.519> actually<00:15:22.000> hand<00:15:22.320> to<00:15:22.480> a<00:15:22.800> client<00:15:23.199> or<00:15:23.600> a 00:15:23.829 --> 00:15:23.839 align:start position:0% you can actually hand to a client or a 00:15:23.839 --> 00:15:26.150 align:start position:0% you can actually hand to a client or a team<00:15:24.079> member<00:15:24.399> without<00:15:24.880> doing<00:15:25.199> extra<00:15:25.600> work<00:15:25.920> and 00:15:26.150 --> 00:15:26.160 align:start position:0% team member without doing extra work and 00:15:26.160 --> 00:15:28.069 align:start position:0% team member without doing extra work and that<00:15:26.399> can<00:15:26.480> make<00:15:26.639> it<00:15:26.959> really<00:15:27.279> useful<00:15:27.680> beyond 00:15:28.069 --> 00:15:28.079 align:start position:0% that can make it really useful beyond 00:15:28.079 --> 00:15:30.389 align:start position:0% that can make it really useful beyond just<00:15:28.560> being<00:15:28.800> a<00:15:29.120> background<00:15:29.600> process<00:15:30.000> in<00:15:30.240> the 00:15:30.389 --> 00:15:30.399 align:start position:0% just being a background process in the 00:15:30.399 --> 00:15:33.350 align:start position:0% just being a background process in the pipeline.<00:15:31.120> So<00:15:31.360> there<00:15:31.680> are<00:15:32.240> two<00:15:32.639> layers<00:15:32.959> in 00:15:33.350 --> 00:15:33.360 align:start position:0% pipeline. So there are two layers in 00:15:33.360 --> 00:15:36.150 align:start position:0% pipeline. So there are two layers in this<00:15:33.680> research<00:15:34.160> agent.<00:15:35.040> The<00:15:35.279> first<00:15:35.440> one<00:15:35.600> is<00:15:35.920> of 00:15:36.150 --> 00:15:36.160 align:start position:0% this research agent. The first one is of 00:15:36.160 --> 00:15:38.470 align:start position:0% this research agent. The first one is of course<00:15:36.560> web<00:15:36.959> search<00:15:37.600> and<00:15:37.839> for<00:15:38.000> this<00:15:38.160> we<00:15:38.320> are 00:15:38.470 --> 00:15:38.480 align:start position:0% course web search and for this we are 00:15:38.480 --> 00:15:40.790 align:start position:0% course web search and for this we are using<00:15:38.720> a<00:15:38.959> simple<00:15:39.279> and<00:15:39.600> reliable<00:15:40.160> web<00:15:40.480> search 00:15:40.790 --> 00:15:40.800 align:start position:0% using a simple and reliable web search 00:15:40.800 --> 00:15:43.990 align:start position:0% using a simple and reliable web search API<00:15:41.279> called<00:15:41.600> Tavly<00:15:42.320> AI.<00:15:42.880> It<00:15:43.120> is<00:15:43.600> clean, 00:15:43.990 --> 00:15:44.000 align:start position:0% API called Tavly AI. It is clean, 00:15:44.000 --> 00:15:45.910 align:start position:0% API called Tavly AI. It is clean, straightforward<00:15:44.800> and<00:15:45.040> built<00:15:45.279> for<00:15:45.519> exactly 00:15:45.910 --> 00:15:45.920 align:start position:0% straightforward and built for exactly 00:15:45.920 --> 00:15:48.470 align:start position:0% straightforward and built for exactly this<00:15:46.240> kind<00:15:46.399> of<00:15:46.560> use<00:15:46.720> case.<00:15:47.760> And<00:15:47.920> then<00:15:48.160> the 00:15:48.470 --> 00:15:48.480 align:start position:0% this kind of use case. And then the 00:15:48.480 --> 00:15:51.110 align:start position:0% this kind of use case. And then the second<00:15:48.880> one<00:15:49.279> is<00:15:49.519> the<00:15:49.759> agent<00:15:50.240> skill<00:15:50.560> itself<00:15:50.959> of 00:15:51.110 --> 00:15:51.120 align:start position:0% second one is the agent skill itself of 00:15:51.120 --> 00:15:54.150 align:start position:0% second one is the agent skill itself of course<00:15:51.839> and<00:15:52.079> that<00:15:52.320> can<00:15:52.639> take<00:15:53.199> what<00:15:53.600> tally 00:15:54.150 --> 00:15:54.160 align:start position:0% course and that can take what tally 00:15:54.160 --> 00:15:57.030 align:start position:0% course and that can take what tally finds<00:15:54.639> and<00:15:55.040> it<00:15:55.199> kills<00:15:55.519> the<00:15:55.759> research<00:15:56.160> workflow 00:15:57.030 --> 00:15:57.040 align:start position:0% finds and it kills the research workflow 00:15:57.040 --> 00:15:59.590 align:start position:0% finds and it kills the research workflow like<00:15:57.360> synthesizing<00:15:58.079> the<00:15:58.240> results 00:15:59.590 --> 00:15:59.600 align:start position:0% like synthesizing the results 00:15:59.600 --> 00:16:01.509 align:start position:0% like synthesizing the results structuring<00:16:00.000> the<00:16:00.240> output<00:16:00.639> and<00:16:00.880> formatting 00:16:01.509 --> 00:16:01.519 align:start position:0% structuring the output and formatting 00:16:01.519 --> 00:16:03.670 align:start position:0% structuring the output and formatting everything<00:16:01.920> into<00:16:02.240> something<00:16:02.639> usable<00:16:03.120> later. 00:16:03.670 --> 00:16:03.680 align:start position:0% everything into something usable later. 00:16:03.680 --> 00:16:07.110 align:start position:0% everything into something usable later. So<00:16:03.920> basically<00:16:04.639> Tavly<00:16:05.360> handles<00:16:05.920> the<00:16:06.320> searching 00:16:07.110 --> 00:16:07.120 align:start position:0% So basically Tavly handles the searching 00:16:07.120 --> 00:16:09.189 align:start position:0% So basically Tavly handles the searching and<00:16:07.519> the<00:16:07.759> skill<00:16:08.079> handles<00:16:08.480> the<00:16:08.720> thinking.<00:16:09.120> All 00:16:09.189 --> 00:16:09.199 align:start position:0% and the skill handles the thinking. All 00:16:09.199 --> 00:16:10.710 align:start position:0% and the skill handles the thinking. All right.<00:16:09.360> So<00:16:09.600> let's<00:16:09.839> start<00:16:10.079> with<00:16:10.240> the<00:16:10.480> skill 00:16:10.710 --> 00:16:10.720 align:start position:0% right. So let's start with the skill 00:16:10.720 --> 00:16:12.870 align:start position:0% right. So let's start with the skill itself.<00:16:11.519> Just<00:16:11.759> like<00:16:11.920> what<00:16:12.079> we<00:16:12.240> did<00:16:12.399> for<00:16:12.639> the 00:16:12.870 --> 00:16:12.880 align:start position:0% itself. Just like what we did for the 00:16:12.880 --> 00:16:14.790 align:start position:0% itself. Just like what we did for the previous<00:16:13.199> two<00:16:13.440> agents,<00:16:14.000> we<00:16:14.160> can<00:16:14.320> just<00:16:14.480> type<00:16:14.639> in 00:16:14.790 --> 00:16:14.800 align:start position:0% previous two agents, we can just type in 00:16:14.800 --> 00:16:17.670 align:start position:0% previous two agents, we can just type in the<00:16:14.959> prompt<00:16:15.360> asking<00:16:15.839> clot<00:16:16.240> to<00:16:16.399> create<00:16:16.560> a<00:16:16.880> skill 00:16:17.670 --> 00:16:17.680 align:start position:0% the prompt asking clot to create a skill 00:16:17.680 --> 00:16:19.829 align:start position:0% the prompt asking clot to create a skill and<00:16:17.839> then<00:16:18.079> just<00:16:18.480> paste<00:16:18.800> in<00:16:18.959> the<00:16:19.120> key<00:16:19.360> details 00:16:19.829 --> 00:16:19.839 align:start position:0% and then just paste in the key details 00:16:19.839 --> 00:16:22.550 align:start position:0% and then just paste in the key details we<00:16:20.160> planned<00:16:20.560> out<00:16:20.959> earlier.<00:16:21.600> So<00:16:21.759> Clot<00:16:22.160> can<00:16:22.320> read 00:16:22.550 --> 00:16:22.560 align:start position:0% we planned out earlier. So Clot can read 00:16:22.560 --> 00:16:24.790 align:start position:0% we planned out earlier. So Clot can read through<00:16:22.880> everything<00:16:23.440> and<00:16:23.680> it<00:16:23.920> can<00:16:24.320> use<00:16:24.560> the 00:16:24.790 --> 00:16:24.800 align:start position:0% through everything and it can use the 00:16:24.800 --> 00:16:26.710 align:start position:0% through everything and it can use the ultimate<00:16:25.199> clot<00:16:25.600> skills<00:16:26.000> and<00:16:26.160> plotins 00:16:26.710 --> 00:16:26.720 align:start position:0% ultimate clot skills and plotins 00:16:26.720 --> 00:16:30.310 align:start position:0% ultimate clot skills and plotins documents<00:16:27.440> as<00:16:27.759> the<00:16:28.079> guide<00:16:28.959> and<00:16:29.680> it<00:16:29.920> can<00:16:30.079> then 00:16:30.310 --> 00:16:30.320 align:start position:0% documents as the guide and it can then 00:16:30.320 --> 00:16:32.150 align:start position:0% documents as the guide and it can then build<00:16:30.560> the<00:16:30.800> skill<00:16:31.040> file.<00:16:31.519> Great,<00:16:31.839> it<00:16:32.000> is 00:16:32.150 --> 00:16:32.160 align:start position:0% build the skill file. Great, it is 00:16:32.160 --> 00:16:34.470 align:start position:0% build the skill file. Great, it is ready.<00:16:32.880> And<00:16:33.199> if<00:16:33.440> we<00:16:33.600> check<00:16:33.839> the<00:16:34.079> skills 00:16:34.470 --> 00:16:34.480 align:start position:0% ready. And if we check the skills 00:16:34.480 --> 00:16:37.910 align:start position:0% ready. And if we check the skills folder,<00:16:35.519> here<00:16:35.680> it<00:16:35.920> is<00:16:36.800> like<00:16:37.120> same<00:16:37.519> structure 00:16:37.910 --> 00:16:37.920 align:start position:0% folder, here it is like same structure 00:16:37.920 --> 00:16:40.550 align:start position:0% folder, here it is like same structure as<00:16:38.160> the<00:16:38.399> others<00:16:39.120> like<00:16:39.360> trigger<00:16:39.680> logic<00:16:40.240> and 00:16:40.550 --> 00:16:40.560 align:start position:0% as the others like trigger logic and 00:16:40.560 --> 00:16:42.870 align:start position:0% as the others like trigger logic and waffle<00:16:40.959> steps<00:16:41.440> clean<00:16:41.839> and<00:16:42.000> consistent.<00:16:42.880> All 00:16:42.870 --> 00:16:42.880 align:start position:0% waffle steps clean and consistent. All 00:16:42.880 --> 00:16:44.870 align:start position:0% waffle steps clean and consistent. All right.<00:16:43.199> Now<00:16:43.440> let's<00:16:43.759> set<00:16:43.920> up<00:16:44.079> the<00:16:44.399> tablet 00:16:44.870 --> 00:16:44.880 align:start position:0% right. Now let's set up the tablet 00:16:44.880 --> 00:16:46.710 align:start position:0% right. Now let's set up the tablet integration.<00:16:45.519> And<00:16:45.680> here<00:16:45.920> we<00:16:46.079> just<00:16:46.240> simply<00:16:46.480> ask 00:16:46.710 --> 00:16:46.720 align:start position:0% integration. And here we just simply ask 00:16:46.720 --> 00:16:49.590 align:start position:0% integration. And here we just simply ask claude<00:16:47.120> to<00:16:47.279> set<00:16:47.440> up<00:16:47.600> the<00:16:47.839> Tavly<00:16:48.320> AI<00:16:48.720> SDK<00:16:49.360> for 00:16:49.590 --> 00:16:49.600 align:start position:0% claude to set up the Tavly AI SDK for 00:16:49.600 --> 00:16:52.550 align:start position:0% claude to set up the Tavly AI SDK for us.<00:16:50.480> And<00:16:50.800> we<00:16:51.120> can<00:16:51.199> use<00:16:51.440> this<00:16:51.680> prompt<00:16:52.000> and<00:16:52.240> paste 00:16:52.550 --> 00:16:52.560 align:start position:0% us. And we can use this prompt and paste 00:16:52.560 --> 00:16:55.269 align:start position:0% us. And we can use this prompt and paste in<00:16:52.720> the<00:16:52.959> Tavly<00:16:53.440> documentation<00:16:54.160> directly.<00:16:54.959> And 00:16:55.269 --> 00:16:55.279 align:start position:0% in the Tavly documentation directly. And 00:16:55.279 --> 00:16:57.350 align:start position:0% in the Tavly documentation directly. And you<00:16:55.519> can<00:16:55.680> find<00:16:55.920> the<00:16:56.320> documentation<00:16:56.880> link<00:16:57.120> in 00:16:57.350 --> 00:16:57.360 align:start position:0% you can find the documentation link in 00:16:57.360 --> 00:17:00.230 align:start position:0% you can find the documentation link in the<00:16:57.519> description.<00:16:58.800> So<00:16:59.120> just<00:16:59.440> open<00:16:59.680> it,<00:17:00.000> hit 00:17:00.230 --> 00:17:00.240 align:start position:0% the description. So just open it, hit 00:17:00.240 --> 00:17:02.550 align:start position:0% the description. So just open it, hit the<00:17:00.399> copy<00:17:00.800> button<00:17:01.440> and<00:17:01.759> paste<00:17:02.079> it<00:17:02.320> straight 00:17:02.550 --> 00:17:02.560 align:start position:0% the copy button and paste it straight 00:17:02.560 --> 00:17:04.710 align:start position:0% the copy button and paste it straight in.<00:17:02.959> And<00:17:03.199> same<00:17:03.440> reason<00:17:03.759> as<00:17:04.000> the<00:17:04.160> playright 00:17:04.710 --> 00:17:04.720 align:start position:0% in. And same reason as the playright 00:17:04.720 --> 00:17:07.350 align:start position:0% in. And same reason as the playright setup<00:17:05.039> earlier,<00:17:05.600> we're<00:17:06.000> not<00:17:06.559> asking<00:17:06.959> Claude 00:17:07.350 --> 00:17:07.360 align:start position:0% setup earlier, we're not asking Claude 00:17:07.360 --> 00:17:10.549 align:start position:0% setup earlier, we're not asking Claude to<00:17:07.600> guess.<00:17:08.400> We<00:17:08.720> are<00:17:09.039> giving<00:17:09.360> it<00:17:09.679> the<00:17:10.000> exact 00:17:10.549 --> 00:17:10.559 align:start position:0% to guess. We are giving it the exact 00:17:10.559 --> 00:17:13.110 align:start position:0% to guess. We are giving it the exact current<00:17:11.120> documentation<00:17:11.839> so<00:17:12.079> that<00:17:12.319> the<00:17:12.640> setup 00:17:13.110 --> 00:17:13.120 align:start position:0% current documentation so that the setup 00:17:13.120 --> 00:17:14.949 align:start position:0% current documentation so that the setup is<00:17:13.360> accurate<00:17:13.760> from<00:17:14.000> the<00:17:14.160> start.<00:17:14.480> And<00:17:14.720> great, 00:17:14.949 --> 00:17:14.959 align:start position:0% is accurate from the start. And great, 00:17:14.959 --> 00:17:17.669 align:start position:0% is accurate from the start. And great, it<00:17:15.120> is<00:17:15.199> done.<00:17:15.520> Tablet<00:17:15.919> is<00:17:16.160> installed<00:17:17.120> and<00:17:17.439> all 00:17:17.669 --> 00:17:17.679 align:start position:0% it is done. Tablet is installed and all 00:17:17.679 --> 00:17:20.470 align:start position:0% it is done. Tablet is installed and all we<00:17:17.919> need<00:17:18.160> to<00:17:18.400> get<00:17:18.559> it<00:17:18.799> working<00:17:19.120> is<00:17:19.439> the<00:17:19.760> EMV 00:17:20.470 --> 00:17:20.480 align:start position:0% we need to get it working is the EMV 00:17:20.480 --> 00:17:23.669 align:start position:0% we need to get it working is the EMV file<00:17:20.880> and<00:17:21.199> the<00:17:21.520> API<00:17:22.160> key<00:17:22.480> inside.<00:17:23.360> All<00:17:23.439> right, 00:17:23.669 --> 00:17:23.679 align:start position:0% file and the API key inside. All right, 00:17:23.679 --> 00:17:25.750 align:start position:0% file and the API key inside. All right, so<00:17:23.919> this<00:17:24.079> is<00:17:24.240> how<00:17:24.400> it<00:17:24.559> looks.<00:17:24.959> This<00:17:25.199> is<00:17:25.439> an 00:17:25.750 --> 00:17:25.760 align:start position:0% so this is how it looks. This is an 00:17:25.760 --> 00:17:28.630 align:start position:0% so this is how it looks. This is an example<00:17:26.400> EMV<00:17:27.039> file<00:17:27.600> and<00:17:27.919> you<00:17:28.160> can<00:17:28.319> see 00:17:28.630 --> 00:17:28.640 align:start position:0% example EMV file and you can see 00:17:28.640 --> 00:17:31.029 align:start position:0% example EMV file and you can see something<00:17:28.960> like<00:17:29.280> this<00:17:29.840> and<00:17:30.080> also<00:17:30.320> the<00:17:30.559> Tavly 00:17:31.029 --> 00:17:31.039 align:start position:0% something like this and also the Tavly 00:17:31.039 --> 00:17:33.750 align:start position:0% something like this and also the Tavly API<00:17:31.440> key<00:17:31.919> and<00:17:32.160> all<00:17:32.400> you<00:17:32.559> need<00:17:32.640> to<00:17:32.799> do<00:17:33.039> is<00:17:33.280> just 00:17:33.750 --> 00:17:33.760 align:start position:0% API key and all you need to do is just 00:17:33.760 --> 00:17:35.590 align:start position:0% API key and all you need to do is just paste<00:17:34.080> your<00:17:34.240> key<00:17:34.480> here<00:17:34.720> and<00:17:35.039> it<00:17:35.200> can<00:17:35.360> start 00:17:35.590 --> 00:17:35.600 align:start position:0% paste your key here and it can start 00:17:35.600 --> 00:17:37.990 align:start position:0% paste your key here and it can start working.<00:17:36.080> So<00:17:36.400> you<00:17:36.640> may<00:17:36.960> ask,<00:17:37.280> hey<00:17:37.440> Andy,<00:17:37.840> how 00:17:37.990 --> 00:17:38.000 align:start position:0% working. So you may ask, hey Andy, how 00:17:38.000 --> 00:17:40.230 align:start position:0% working. So you may ask, hey Andy, how to<00:17:38.160> get<00:17:38.240> the<00:17:38.480> API<00:17:38.880> key.<00:17:39.600> So<00:17:39.679> you<00:17:39.919> can<00:17:40.000> just<00:17:40.160> get 00:17:40.230 --> 00:17:40.240 align:start position:0% to get the API key. So you can just get 00:17:40.240 --> 00:17:43.510 align:start position:0% to get the API key. So you can just get it<00:17:40.400> from<00:17:40.640> your<00:17:40.799> dashboard<00:17:41.840> and<00:17:42.160> you<00:17:42.400> can<00:17:42.640> just 00:17:43.510 --> 00:17:43.520 align:start position:0% it from your dashboard and you can just 00:17:43.520 --> 00:17:46.950 align:start position:0% it from your dashboard and you can just click<00:17:43.840> the<00:17:44.320> add<00:17:44.640> API<00:17:45.280> key<00:17:45.679> button<00:17:46.480> and<00:17:46.799> just 00:17:46.950 --> 00:17:46.960 align:start position:0% click the add API key button and just 00:17:46.960 --> 00:17:49.270 align:start position:0% click the add API key button and just name<00:17:47.200> your<00:17:47.440> key<00:17:47.679> and<00:17:47.919> then<00:17:48.160> click<00:17:48.400> create.<00:17:49.039> And 00:17:49.270 --> 00:17:49.280 align:start position:0% name your key and then click create. And 00:17:49.280 --> 00:17:51.110 align:start position:0% name your key and then click create. And just<00:17:49.440> like<00:17:49.600> that,<00:17:49.760> your<00:17:49.919> API<00:17:50.320> key<00:17:50.559> is<00:17:50.720> ready. 00:17:51.110 --> 00:17:51.120 align:start position:0% just like that, your API key is ready. 00:17:51.120 --> 00:17:53.909 align:start position:0% just like that, your API key is ready. Just<00:17:51.360> click<00:17:51.679> copy<00:17:52.000> and<00:17:52.240> paste<00:17:52.640> in<00:17:52.880> your<00:17:53.360> EMV 00:17:53.909 --> 00:17:53.919 align:start position:0% Just click copy and paste in your EMV 00:17:53.919 --> 00:17:56.150 align:start position:0% Just click copy and paste in your EMV file.<00:17:54.240> All<00:17:54.320> right.<00:17:54.799> So<00:17:55.039> the<00:17:55.360> research<00:17:55.840> agent 00:17:56.150 --> 00:17:56.160 align:start position:0% file. All right. So the research agent 00:17:56.160 --> 00:17:58.549 align:start position:0% file. All right. So the research agent is<00:17:56.320> built<00:17:56.559> and<00:17:56.799> the<00:17:56.960> web<00:17:57.440> search<00:17:58.080> layer<00:17:58.320> is 00:17:58.549 --> 00:17:58.559 align:start position:0% is built and the web search layer is 00:17:58.559 --> 00:18:00.630 align:start position:0% is built and the web search layer is already<00:17:59.120> done.<00:17:59.600> And<00:17:59.840> now<00:18:00.000> let<00:18:00.160> us<00:18:00.400> put 00:18:00.630 --> 00:18:00.640 align:start position:0% already done. And now let us put 00:18:00.640 --> 00:18:03.029 align:start position:0% already done. And now let us put together<00:18:01.039> with<00:18:01.200> the<00:18:01.520> final<00:18:01.919> two<00:18:02.160> agents<00:18:02.720> and 00:18:03.029 --> 00:18:03.039 align:start position:0% together with the final two agents and 00:18:03.039 --> 00:18:05.110 align:start position:0% together with the final two agents and get<00:18:03.200> the<00:18:03.360> full<00:18:03.679> pipeline<00:18:04.160> connected.<00:18:04.720> And<00:18:04.960> now 00:18:05.110 --> 00:18:05.120 align:start position:0% get the full pipeline connected. And now 00:18:05.120 --> 00:18:07.590 align:start position:0% get the full pipeline connected. And now let's<00:18:05.440> build<00:18:05.679> the<00:18:05.919> copyrightiting<00:18:06.880> agent. 00:18:07.590 --> 00:18:07.600 align:start position:0% let's build the copyrightiting agent. 00:18:07.600 --> 00:18:09.750 align:start position:0% let's build the copyrightiting agent. And<00:18:07.919> at<00:18:08.160> this<00:18:08.400> point<00:18:08.880> the<00:18:09.120> process<00:18:09.440> is 00:18:09.750 --> 00:18:09.760 align:start position:0% And at this point the process is 00:18:09.760 --> 00:18:11.669 align:start position:0% And at this point the process is familiar<00:18:10.240> like<00:18:10.480> same<00:18:10.799> prom<00:18:11.120> structure<00:18:11.440> as 00:18:11.669 --> 00:18:11.679 align:start position:0% familiar like same prom structure as 00:18:11.679 --> 00:18:13.750 align:start position:0% familiar like same prom structure as before.<00:18:12.240> We<00:18:12.480> just<00:18:12.720> ask<00:18:13.039> CL<00:18:13.280> to<00:18:13.440> create<00:18:13.600> the 00:18:13.750 --> 00:18:13.760 align:start position:0% before. We just ask CL to create the 00:18:13.760 --> 00:18:15.990 align:start position:0% before. We just ask CL to create the skill<00:18:14.160> past<00:18:14.400> in<00:18:14.559> the<00:18:14.720> key<00:18:14.960> details<00:18:15.440> we<00:18:15.600> planned 00:18:15.990 --> 00:18:16.000 align:start position:0% skill past in the key details we planned 00:18:16.000 --> 00:18:18.470 align:start position:0% skill past in the key details we planned earlier<00:18:16.400> and<00:18:16.559> just<00:18:16.799> hit<00:18:17.039> enter.<00:18:17.600> So<00:18:18.080> as<00:18:18.240> the 00:18:18.470 --> 00:18:18.480 align:start position:0% earlier and just hit enter. So as the 00:18:18.480 --> 00:18:20.470 align:start position:0% earlier and just hit enter. So as the name<00:18:18.640> suggests,<00:18:19.440> the<00:18:19.679> agent<00:18:20.080> basically 00:18:20.470 --> 00:18:20.480 align:start position:0% name suggests, the agent basically 00:18:20.480 --> 00:18:22.630 align:start position:0% name suggests, the agent basically handles<00:18:21.120> all<00:18:21.360> the<00:18:21.600> marketing<00:18:21.919> copy<00:18:22.400> like 00:18:22.630 --> 00:18:22.640 align:start position:0% handles all the marketing copy like 00:18:22.640 --> 00:18:24.870 align:start position:0% handles all the marketing copy like captions,<00:18:23.360> descriptions,<00:18:24.240> platform, 00:18:24.870 --> 00:18:24.880 align:start position:0% captions, descriptions, platform, 00:18:24.880 --> 00:18:27.510 align:start position:0% captions, descriptions, platform, specific<00:18:25.360> writing,<00:18:26.080> anything<00:18:26.400> that<00:18:26.799> requires 00:18:27.510 --> 00:18:27.520 align:start position:0% specific writing, anything that requires 00:18:27.520 --> 00:18:30.150 align:start position:0% specific writing, anything that requires words<00:18:28.080> tailored<00:18:28.640> to<00:18:28.799> a<00:18:29.039> specific<00:18:29.440> channel<00:18:29.919> and 00:18:30.150 --> 00:18:30.160 align:start position:0% words tailored to a specific channel and 00:18:30.160 --> 00:18:33.270 align:start position:0% words tailored to a specific channel and audience.<00:18:30.799> So<00:18:31.200> it<00:18:31.520> can<00:18:31.840> know<00:18:32.080> the<00:18:32.400> brand<00:18:32.799> voice 00:18:33.270 --> 00:18:33.280 align:start position:0% audience. So it can know the brand voice 00:18:33.280 --> 00:18:35.990 align:start position:0% audience. So it can know the brand voice from<00:18:33.600> the<00:18:33.919> knowledge<00:18:34.400> folder<00:18:34.880> and<00:18:35.200> it<00:18:35.679> can 00:18:35.990 --> 00:18:36.000 align:start position:0% from the knowledge folder and it can 00:18:36.000 --> 00:18:38.150 align:start position:0% from the knowledge folder and it can know<00:18:36.320> the<00:18:36.880> platform<00:18:37.360> formats<00:18:37.760> from<00:18:37.919> the 00:18:38.150 --> 00:18:38.160 align:start position:0% know the platform formats from the 00:18:38.160 --> 00:18:40.470 align:start position:0% know the platform formats from the guidelines<00:18:38.720> that<00:18:38.960> we<00:18:39.200> set<00:18:39.360> up<00:18:39.600> at<00:18:39.840> the<00:18:40.000> start. 00:18:40.470 --> 00:18:40.480 align:start position:0% guidelines that we set up at the start. 00:18:40.480 --> 00:18:42.630 align:start position:0% guidelines that we set up at the start. And<00:18:40.720> it's<00:18:40.960> done.<00:18:41.360> Another<00:18:41.760> skill<00:18:42.160> added<00:18:42.480> to 00:18:42.630 --> 00:18:42.640 align:start position:0% And it's done. Another skill added to 00:18:42.640 --> 00:18:46.230 align:start position:0% And it's done. Another skill added to the<00:18:42.799> folder.<00:18:44.000> Okay,<00:18:44.559> now<00:18:45.120> the<00:18:45.360> last<00:18:45.679> agent, 00:18:46.230 --> 00:18:46.240 align:start position:0% the folder. Okay, now the last agent, 00:18:46.240 --> 00:18:48.789 align:start position:0% the folder. Okay, now the last agent, the<00:18:46.640> distribution<00:18:47.360> agent.<00:18:47.919> This<00:18:48.160> agent<00:18:48.559> just 00:18:48.789 --> 00:18:48.799 align:start position:0% the distribution agent. This agent just 00:18:48.799 --> 00:18:52.310 align:start position:0% the distribution agent. This agent just has<00:18:49.360> two<00:18:49.919> main<00:18:50.320> jobs.<00:18:51.200> Publishing<00:18:51.919> content 00:18:52.310 --> 00:18:52.320 align:start position:0% has two main jobs. Publishing content 00:18:52.320 --> 00:18:55.350 align:start position:0% has two main jobs. Publishing content uploads<00:18:52.880> programmatically<00:18:54.080> and<00:18:54.720> generating 00:18:55.350 --> 00:18:55.360 align:start position:0% uploads programmatically and generating 00:18:55.360 --> 00:18:58.470 align:start position:0% uploads programmatically and generating the<00:18:55.679> right<00:18:56.000> metadata<00:18:56.720> for<00:18:56.960> YouTube<00:18:57.360> uploads. 00:18:58.470 --> 00:18:58.480 align:start position:0% the right metadata for YouTube uploads. 00:18:58.480 --> 00:19:01.590 align:start position:0% the right metadata for YouTube uploads. So<00:18:58.880> title,<00:18:59.440> description,<00:19:00.160> tags,<00:19:00.880> like<00:19:01.200> all<00:19:01.440> of 00:19:01.590 --> 00:19:01.600 align:start position:0% So title, description, tags, like all of 00:19:01.600 --> 00:19:04.470 align:start position:0% So title, description, tags, like all of it<00:19:01.840> handled<00:19:02.320> by<00:19:02.559> this<00:19:02.880> agent.<00:19:03.760> So<00:19:04.000> nothing<00:19:04.320> has 00:19:04.470 --> 00:19:04.480 align:start position:0% it handled by this agent. So nothing has 00:19:04.480 --> 00:19:06.789 align:start position:0% it handled by this agent. So nothing has to<00:19:04.640> be<00:19:04.880> filled<00:19:05.120> in<00:19:05.440> manually.<00:19:06.160> And<00:19:06.480> in<00:19:06.720> order 00:19:06.789 --> 00:19:06.799 align:start position:0% to be filled in manually. And in order 00:19:06.799 --> 00:19:08.950 align:start position:0% to be filled in manually. And in order to<00:19:07.039> make<00:19:07.120> this<00:19:07.360> work,<00:19:07.679> we<00:19:07.919> need<00:19:08.320> three<00:19:08.720> more 00:19:08.950 --> 00:19:08.960 align:start position:0% to make this work, we need three more 00:19:08.960 --> 00:19:12.310 align:start position:0% to make this work, we need three more API<00:19:09.440> integrations.<00:19:10.400> YouTube<00:19:10.799> API,<00:19:11.760> the<00:19:12.000> meta 00:19:12.310 --> 00:19:12.320 align:start position:0% API integrations. YouTube API, the meta 00:19:12.320 --> 00:19:14.870 align:start position:0% API integrations. YouTube API, the meta Instagram<00:19:13.039> and<00:19:13.360> threats<00:19:13.760> API.<00:19:14.400> We<00:19:14.640> actually 00:19:14.870 --> 00:19:14.880 align:start position:0% Instagram and threats API. We actually 00:19:14.880 --> 00:19:16.789 align:start position:0% Instagram and threats API. We actually have<00:19:15.039> a<00:19:15.280> previous<00:19:15.600> video<00:19:16.000> to<00:19:16.320> talk<00:19:16.480> about<00:19:16.640> how 00:19:16.789 --> 00:19:16.799 align:start position:0% have a previous video to talk about how 00:19:16.799 --> 00:19:18.470 align:start position:0% have a previous video to talk about how we<00:19:16.960> can<00:19:17.120> set<00:19:17.280> this<00:19:17.440> up.<00:19:17.760> You<00:19:17.919> can<00:19:18.080> also<00:19:18.320> check 00:19:18.470 --> 00:19:18.480 align:start position:0% we can set this up. You can also check 00:19:18.480 --> 00:19:20.470 align:start position:0% we can set this up. You can also check it<00:19:18.640> out<00:19:18.799> in<00:19:19.120> our<00:19:19.440> description.<00:19:20.080> Now,<00:19:20.240> you<00:19:20.400> can 00:19:20.470 --> 00:19:20.480 align:start position:0% it out in our description. Now, you can 00:19:20.480 --> 00:19:22.310 align:start position:0% it out in our description. Now, you can see<00:19:20.559> that<00:19:20.720> we<00:19:20.960> have<00:19:21.120> already<00:19:21.360> done<00:19:21.520> the<00:19:21.760> setup. 00:19:22.310 --> 00:19:22.320 align:start position:0% see that we have already done the setup. 00:19:22.320 --> 00:19:24.710 align:start position:0% see that we have already done the setup. So,<00:19:22.559> next<00:19:23.280> we<00:19:23.520> can<00:19:23.679> focus<00:19:24.000> on<00:19:24.160> the<00:19:24.320> agent 00:19:24.710 --> 00:19:24.720 align:start position:0% So, next we can focus on the agent 00:19:24.720 --> 00:19:26.230 align:start position:0% So, next we can focus on the agent skill.<00:19:25.120> And<00:19:25.280> just<00:19:25.440> like<00:19:25.600> earlier,<00:19:26.000> we<00:19:26.160> can 00:19:26.230 --> 00:19:26.240 align:start position:0% skill. And just like earlier, we can 00:19:26.240 --> 00:19:28.230 align:start position:0% skill. And just like earlier, we can just<00:19:26.400> use<00:19:26.559> the<00:19:26.720> key<00:19:26.960> details<00:19:27.679> that<00:19:27.919> we've 00:19:28.230 --> 00:19:28.240 align:start position:0% just use the key details that we've 00:19:28.240 --> 00:19:30.230 align:start position:0% just use the key details that we've built<00:19:28.559> with<00:19:28.880> Claude<00:19:29.280> in<00:19:29.520> the<00:19:29.679> very<00:19:29.919> beginning 00:19:30.230 --> 00:19:30.240 align:start position:0% built with Claude in the very beginning 00:19:30.240 --> 00:19:31.990 align:start position:0% built with Claude in the very beginning to<00:19:30.480> build<00:19:30.720> the<00:19:30.880> skill<00:19:31.120> now.<00:19:31.440> So,<00:19:31.520> if<00:19:31.679> we<00:19:31.840> check 00:19:31.990 --> 00:19:32.000 align:start position:0% to build the skill now. So, if we check 00:19:32.000 --> 00:19:34.470 align:start position:0% to build the skill now. So, if we check the<00:19:32.160> skills<00:19:32.480> photos<00:19:32.880> on<00:19:33.039> the<00:19:33.200> left,<00:19:33.840> all<00:19:34.160> five 00:19:34.470 --> 00:19:34.480 align:start position:0% the skills photos on the left, all five 00:19:34.480 --> 00:19:36.549 align:start position:0% the skills photos on the left, all five skills<00:19:34.880> are<00:19:35.039> done<00:19:35.280> and<00:19:35.600> ready<00:19:35.919> now.<00:19:36.320> the 00:19:36.549 --> 00:19:36.559 align:start position:0% skills are done and ready now. the 00:19:36.559 --> 00:19:38.950 align:start position:0% skills are done and ready now. the research<00:19:36.880> agent,<00:19:37.440> the<00:19:37.679> video<00:19:37.919> ad<00:19:38.240> specialist, 00:19:38.950 --> 00:19:38.960 align:start position:0% research agent, the video ad specialist, 00:19:38.960 --> 00:19:41.110 align:start position:0% research agent, the video ad specialist, ad<00:19:39.200> creative<00:19:39.600> designer,<00:19:40.480> copyrightiting 00:19:41.110 --> 00:19:41.120 align:start position:0% ad creative designer, copyrightiting 00:19:41.120 --> 00:19:44.230 align:start position:0% ad creative designer, copyrightiting agent<00:19:41.760> and<00:19:42.240> distribution<00:19:43.039> agent.<00:19:43.679> The<00:19:43.919> full 00:19:44.230 --> 00:19:44.240 align:start position:0% agent and distribution agent. The full 00:19:44.240 --> 00:19:46.950 align:start position:0% agent and distribution agent. The full pipeline<00:19:44.799> is<00:19:45.039> complete.<00:19:46.080> And<00:19:46.320> now<00:19:46.559> before<00:19:46.799> we 00:19:46.950 --> 00:19:46.960 align:start position:0% pipeline is complete. And now before we 00:19:46.960 --> 00:19:49.510 align:start position:0% pipeline is complete. And now before we move<00:19:47.200> on,<00:19:47.679> let<00:19:47.919> me<00:19:48.240> give<00:19:48.559> an<00:19:48.880> important<00:19:49.200> note 00:19:49.510 --> 00:19:49.520 align:start position:0% move on, let me give an important note 00:19:49.520 --> 00:19:51.830 align:start position:0% move on, let me give an important note here<00:19:49.760> first.<00:19:50.160> So<00:19:50.400> earlier<00:19:50.960> Clark<00:19:51.360> just<00:19:51.600> gave 00:19:51.830 --> 00:19:51.840 align:start position:0% here first. So earlier Clark just gave 00:19:51.840 --> 00:19:53.990 align:start position:0% here first. So earlier Clark just gave us<00:19:52.080> this<00:19:52.400> table<00:19:52.799> with<00:19:53.120> all<00:19:53.280> the<00:19:53.520> environment 00:19:53.990 --> 00:19:54.000 align:start position:0% us this table with all the environment 00:19:54.000 --> 00:19:56.630 align:start position:0% us this table with all the environment variables<00:19:54.640> needed,<00:19:55.039> right?<00:19:55.440> And<00:19:55.679> below<00:19:56.080> that 00:19:56.630 --> 00:19:56.640 align:start position:0% variables needed, right? And below that 00:19:56.640 --> 00:19:59.350 align:start position:0% variables needed, right? And below that some<00:19:56.880> notes<00:19:57.280> on<00:19:57.600> how<00:19:57.919> the<00:19:58.240> posting<00:19:58.960> actually 00:19:59.350 --> 00:19:59.360 align:start position:0% some notes on how the posting actually 00:19:59.360 --> 00:20:01.590 align:start position:0% some notes on how the posting actually works.<00:19:59.919> And<00:20:00.160> the<00:20:00.480> third<00:20:00.799> bullet<00:20:01.120> point<00:20:01.280> is<00:20:01.440> the 00:20:01.590 --> 00:20:01.600 align:start position:0% works. And the third bullet point is the 00:20:01.600 --> 00:20:04.549 align:start position:0% works. And the third bullet point is the one<00:20:01.760> that<00:20:01.919> we<00:20:02.160> need<00:20:02.240> to<00:20:02.480> pay<00:20:02.720> attention<00:20:03.039> to.<00:20:04.080> So 00:20:04.549 --> 00:20:04.559 align:start position:0% one that we need to pay attention to. So 00:20:04.559 --> 00:20:07.830 align:start position:0% one that we need to pay attention to. So for<00:20:04.880> Instagram<00:20:05.360> post<00:20:05.760> requests<00:20:06.400> to<00:20:06.720> work<00:20:07.520> like 00:20:07.830 --> 00:20:07.840 align:start position:0% for Instagram post requests to work like 00:20:07.840 --> 00:20:09.510 align:start position:0% for Instagram post requests to work like meaning<00:20:08.160> for<00:20:08.400> content<00:20:08.720> to<00:20:08.960> actually<00:20:09.280> get 00:20:09.510 --> 00:20:09.520 align:start position:0% meaning for content to actually get 00:20:09.520 --> 00:20:12.789 align:start position:0% meaning for content to actually get uploaded<00:20:10.000> to<00:20:10.240> Instagram,<00:20:11.440> the<00:20:11.760> assets<00:20:12.480> being 00:20:12.789 --> 00:20:12.799 align:start position:0% uploaded to Instagram, the assets being 00:20:12.799 --> 00:20:15.830 align:start position:0% uploaded to Instagram, the assets being posted<00:20:13.440> need<00:20:13.679> to<00:20:13.919> be<00:20:14.160> at<00:20:14.400> a<00:20:14.720> publicly 00:20:15.830 --> 00:20:15.840 align:start position:0% posted need to be at a publicly 00:20:15.840 --> 00:20:18.390 align:start position:0% posted need to be at a publicly available<00:20:16.720> URL. 00:20:18.390 --> 00:20:18.400 align:start position:0% available URL. 00:20:18.400 --> 00:20:21.750 align:start position:0% available URL. Remember<00:20:18.960> it's<00:20:19.200> a<00:20:19.600> publicly<00:20:20.480> available<00:20:21.039> URL. 00:20:21.750 --> 00:20:21.760 align:start position:0% Remember it's a publicly available URL. 00:20:21.760 --> 00:20:24.310 align:start position:0% Remember it's a publicly available URL. So<00:20:22.000> it's<00:20:22.400> not<00:20:22.720> stored<00:20:23.440> locally<00:20:23.840> on<00:20:24.080> your 00:20:24.310 --> 00:20:24.320 align:start position:0% So it's not stored locally on your 00:20:24.320 --> 00:20:28.149 align:start position:0% So it's not stored locally on your machine.<00:20:25.440> So<00:20:25.679> a<00:20:25.919> local<00:20:26.480> file<00:20:26.799> path<00:20:27.280> will<00:20:27.760> not 00:20:28.149 --> 00:20:28.159 align:start position:0% machine. So a local file path will not 00:20:28.159 --> 00:20:30.950 align:start position:0% machine. So a local file path will not work<00:20:28.400> here.<00:20:29.039> The<00:20:29.280> platforms<00:20:30.000> needs<00:20:30.400> to<00:20:30.640> be 00:20:30.950 --> 00:20:30.960 align:start position:0% work here. The platforms needs to be 00:20:30.960 --> 00:20:33.110 align:start position:0% work here. The platforms needs to be able<00:20:31.520> to<00:20:31.840> reach<00:20:32.159> the<00:20:32.400> assets<00:20:32.799> from<00:20:32.960> the 00:20:33.110 --> 00:20:33.120 align:start position:0% able to reach the assets from the 00:20:33.120 --> 00:20:34.870 align:start position:0% able to reach the assets from the outside.<00:20:33.600> Right.<00:20:33.919> And<00:20:34.080> this<00:20:34.240> is<00:20:34.400> where<00:20:34.640> the 00:20:34.870 --> 00:20:34.880 align:start position:0% outside. Right. And this is where the 00:20:34.880 --> 00:20:37.510 align:start position:0% outside. Right. And this is where the agent<00:20:35.200> will<00:20:35.520> first<00:20:35.840> upload<00:20:36.159> the<00:20:36.320> output<00:20:36.720> files 00:20:37.510 --> 00:20:37.520 align:start position:0% agent will first upload the output files 00:20:37.520 --> 00:20:41.110 align:start position:0% agent will first upload the output files so<00:20:37.840> the<00:20:38.159> APIs<00:20:38.799> can<00:20:39.200> access<00:20:39.679> them<00:20:40.159> when<00:20:40.480> we<00:20:40.799> fire 00:20:41.110 --> 00:20:41.120 align:start position:0% so the APIs can access them when we fire 00:20:41.120 --> 00:20:43.190 align:start position:0% so the APIs can access them when we fire the<00:20:41.360> post<00:20:42.000> request.<00:20:42.559> All<00:20:42.640> right.<00:20:42.799> So<00:20:42.960> before 00:20:43.190 --> 00:20:43.200 align:start position:0% the post request. All right. So before 00:20:43.200 --> 00:20:45.590 align:start position:0% the post request. All right. So before we<00:20:43.360> set<00:20:43.440> up<00:20:43.600> superbase,<00:20:44.480> we<00:20:44.720> can<00:20:44.880> just<00:20:45.200> look<00:20:45.360> at 00:20:45.590 --> 00:20:45.600 align:start position:0% we set up superbase, we can just look at 00:20:45.600 --> 00:20:48.390 align:start position:0% we set up superbase, we can just look at the<00:20:45.840> example<00:20:46.320> EMV<00:20:46.799> file<00:20:47.039> quickly.<00:20:47.840> So<00:20:48.000> we<00:20:48.240> can 00:20:48.390 --> 00:20:48.400 align:start position:0% the example EMV file quickly. So we can 00:20:48.400 --> 00:20:50.710 align:start position:0% the example EMV file quickly. So we can know<00:20:48.640> exactly<00:20:49.120> what<00:20:49.440> keys<00:20:49.840> you<00:20:50.000> are<00:20:50.159> going<00:20:50.400> to 00:20:50.710 --> 00:20:50.720 align:start position:0% know exactly what keys you are going to 00:20:50.720 --> 00:20:53.590 align:start position:0% know exactly what keys you are going to need<00:20:51.039> to<00:20:51.280> make<00:20:51.520> this<00:20:51.840> whole<00:20:52.159> pipeline<00:20:52.880> run.<00:20:53.360> So 00:20:53.590 --> 00:20:53.600 align:start position:0% need to make this whole pipeline run. So 00:20:53.600 --> 00:20:56.149 align:start position:0% need to make this whole pipeline run. So first<00:20:54.000> of<00:20:54.320> course<00:20:54.480> your<00:20:54.720> Tavly<00:20:55.200> API<00:20:55.600> key<00:20:55.919> and 00:20:56.149 --> 00:20:56.159 align:start position:0% first of course your Tavly API key and 00:20:56.159 --> 00:20:59.510 align:start position:0% first of course your Tavly API key and then<00:20:56.320> your<00:20:56.640> YouTube<00:20:57.360> Instagram<00:20:58.240> threats<00:20:58.720> keys 00:20:59.510 --> 00:20:59.520 align:start position:0% then your YouTube Instagram threats keys 00:20:59.520 --> 00:21:02.390 align:start position:0% then your YouTube Instagram threats keys and<00:20:59.840> then<00:21:00.080> your<00:21:00.240> superbase<00:21:00.880> project<00:21:01.280> URL<00:21:01.919> and 00:21:02.390 --> 00:21:02.400 align:start position:0% and then your superbase project URL and 00:21:02.400 --> 00:21:04.230 align:start position:0% and then your superbase project URL and service<00:21:02.720> key<00:21:03.039> and<00:21:03.280> we'll<00:21:03.600> go<00:21:03.760> through<00:21:03.919> exactly 00:21:04.230 --> 00:21:04.240 align:start position:0% service key and we'll go through exactly 00:21:04.240 --> 00:21:05.990 align:start position:0% service key and we'll go through exactly where<00:21:04.400> to<00:21:04.559> get<00:21:04.640> your<00:21:04.880> superbase<00:21:05.360> storage<00:21:05.600> up. 00:21:05.990 --> 00:21:06.000 align:start position:0% where to get your superbase storage up. 00:21:06.000 --> 00:21:08.789 align:start position:0% where to get your superbase storage up. So<00:21:06.240> now<00:21:06.559> let's<00:21:07.039> get<00:21:07.520> superbase<00:21:08.159> storage<00:21:08.559> set 00:21:08.789 --> 00:21:08.799 align:start position:0% So now let's get superbase storage set 00:21:08.799 --> 00:21:11.110 align:start position:0% So now let's get superbase storage set up.<00:21:09.120> This<00:21:09.280> is<00:21:09.440> the<00:21:09.679> last<00:21:09.919> piece<00:21:10.320> before<00:21:10.640> we<00:21:10.880> can 00:21:11.110 --> 00:21:11.120 align:start position:0% up. This is the last piece before we can 00:21:11.120 --> 00:21:13.029 align:start position:0% up. This is the last piece before we can run<00:21:11.280> the<00:21:11.520> full<00:21:11.760> pipeline.<00:21:12.400> So<00:21:12.640> please<00:21:12.880> pay 00:21:13.029 --> 00:21:13.039 align:start position:0% run the full pipeline. So please pay 00:21:13.039 --> 00:21:14.789 align:start position:0% run the full pipeline. So please pay attention.<00:21:13.600> Okay,<00:21:13.840> we<00:21:14.080> can<00:21:14.159> just<00:21:14.400> start<00:21:14.559> from 00:21:14.789 --> 00:21:14.799 align:start position:0% attention. Okay, we can just start from 00:21:14.799 --> 00:21:17.830 align:start position:0% attention. Okay, we can just start from a<00:21:15.039> fresh<00:21:15.679> superbase<00:21:16.400> project<00:21:17.200> and<00:21:17.440> the<00:21:17.679> first 00:21:17.830 --> 00:21:17.840 align:start position:0% a fresh superbase project and the first 00:21:17.840 --> 00:21:20.710 align:start position:0% a fresh superbase project and the first thing<00:21:18.000> you<00:21:18.240> need<00:21:18.480> is<00:21:18.720> your<00:21:19.039> project<00:21:19.600> URL<00:21:20.400> and 00:21:20.710 --> 00:21:20.720 align:start position:0% thing you need is your project URL and 00:21:20.720 --> 00:21:22.310 align:start position:0% thing you need is your project URL and you<00:21:20.880> can<00:21:21.039> find<00:21:21.120> it<00:21:21.360> right<00:21:21.600> on<00:21:21.760> the<00:21:21.919> dashboard 00:21:22.310 --> 00:21:22.320 align:start position:0% you can find it right on the dashboard 00:21:22.320 --> 00:21:24.470 align:start position:0% you can find it right on the dashboard as<00:21:22.559> soon<00:21:22.720> as<00:21:22.960> you<00:21:23.120> open<00:21:23.440> the<00:21:23.600> project.<00:21:24.240> It's 00:21:24.470 --> 00:21:24.480 align:start position:0% as soon as you open the project. It's 00:21:24.480 --> 00:21:26.630 align:start position:0% as soon as you open the project. It's very<00:21:24.720> easy<00:21:24.960> to<00:21:25.120> locate.<00:21:25.679> Just<00:21:25.919> copy<00:21:26.240> it<00:21:26.400> and 00:21:26.630 --> 00:21:26.640 align:start position:0% very easy to locate. Just copy it and 00:21:26.640 --> 00:21:29.750 align:start position:0% very easy to locate. Just copy it and paste<00:21:26.880> it<00:21:27.039> into<00:21:27.360> your<00:21:27.679> EMV<00:21:28.320> file.<00:21:28.720> So<00:21:28.960> next<00:21:29.440> is 00:21:29.750 --> 00:21:29.760 align:start position:0% paste it into your EMV file. So next is 00:21:29.760 --> 00:21:32.070 align:start position:0% paste it into your EMV file. So next is your<00:21:30.159> service<00:21:30.559> key.<00:21:31.280> And<00:21:31.440> now<00:21:31.679> if<00:21:31.760> you<00:21:31.919> have 00:21:32.070 --> 00:21:32.080 align:start position:0% your service key. And now if you have 00:21:32.080 --> 00:21:33.590 align:start position:0% your service key. And now if you have followed<00:21:32.400> our<00:21:32.640> previous<00:21:32.960> projects,<00:21:33.360> you 00:21:33.590 --> 00:21:33.600 align:start position:0% followed our previous projects, you 00:21:33.600 --> 00:21:35.430 align:start position:0% followed our previous projects, you would<00:21:33.760> notice<00:21:34.159> that<00:21:34.320> we<00:21:34.559> usually<00:21:34.880> go<00:21:35.039> for<00:21:35.200> the 00:21:35.430 --> 00:21:35.440 align:start position:0% would notice that we usually go for the 00:21:35.440 --> 00:21:38.070 align:start position:0% would notice that we usually go for the anon<00:21:35.840> key.<00:21:36.799> And<00:21:37.120> you<00:21:37.360> might<00:21:37.520> be<00:21:37.679> wondering, 00:21:38.070 --> 00:21:38.080 align:start position:0% anon key. And you might be wondering, 00:21:38.080 --> 00:21:40.390 align:start position:0% anon key. And you might be wondering, hey<00:21:38.240> Andy,<00:21:38.720> why<00:21:38.960> are<00:21:39.200> we<00:21:39.600> using<00:21:39.919> the<00:21:40.080> service 00:21:40.390 --> 00:21:40.400 align:start position:0% hey Andy, why are we using the service 00:21:40.400 --> 00:21:43.350 align:start position:0% hey Andy, why are we using the service key<00:21:40.720> here<00:21:41.039> instead?<00:21:42.000> And<00:21:42.240> here's<00:21:42.480> the<00:21:42.559> reason. 00:21:43.350 --> 00:21:43.360 align:start position:0% key here instead? And here's the reason. 00:21:43.360 --> 00:21:46.070 align:start position:0% key here instead? And here's the reason. because<00:21:43.679> this<00:21:44.000> pipeline<00:21:44.559> actually<00:21:45.360> runs<00:21:45.679> as<00:21:45.919> a 00:21:46.070 --> 00:21:46.080 align:start position:0% because this pipeline actually runs as a 00:21:46.080 --> 00:21:49.590 align:start position:0% because this pipeline actually runs as a serverside<00:21:46.799> node.js<00:21:47.679> script<00:21:48.480> and<00:21:49.039> there<00:21:49.280> is 00:21:49.590 --> 00:21:49.600 align:start position:0% serverside node.js script and there is 00:21:49.600 --> 00:21:53.270 align:start position:0% serverside node.js script and there is no<00:21:49.919> user<00:21:50.320> section<00:21:50.640> attached<00:21:51.120> to<00:21:51.440> this<00:21:52.559> and<00:21:52.880> no 00:21:53.270 --> 00:21:53.280 align:start position:0% no user section attached to this and no 00:21:53.280 --> 00:21:55.750 align:start position:0% no user section attached to this and no logged<00:21:53.760> in<00:21:54.159> superbase<00:21:54.720> user.<00:21:55.360> Basically, 00:21:55.750 --> 00:21:55.760 align:start position:0% logged in superbase user. Basically, 00:21:55.760 --> 00:21:57.830 align:start position:0% logged in superbase user. Basically, it's<00:21:56.000> just<00:21:56.080> a<00:21:56.320> backend<00:21:56.880> automation<00:21:57.520> script 00:21:57.830 --> 00:21:57.840 align:start position:0% it's just a backend automation script 00:21:57.840 --> 00:22:00.470 align:start position:0% it's just a backend automation script uploading<00:21:58.320> files<00:21:58.799> directly<00:21:59.360> to<00:21:59.760> a<00:22:00.080> storage 00:22:00.470 --> 00:22:00.480 align:start position:0% uploading files directly to a storage 00:22:00.480 --> 00:22:03.510 align:start position:0% uploading files directly to a storage bucket.<00:22:01.280> So,<00:22:01.600> if<00:22:01.840> you<00:22:02.080> used<00:22:02.320> the<00:22:02.720> anony<00:22:03.120> key<00:22:03.360> in 00:22:03.510 --> 00:22:03.520 align:start position:0% bucket. So, if you used the anony key in 00:22:03.520 --> 00:22:06.870 align:start position:0% bucket. So, if you used the anony key in this<00:22:03.679> situation,<00:22:04.320> the<00:22:04.559> upload<00:22:04.960> will<00:22:05.200> fail<00:22:06.240> and 00:22:06.870 --> 00:22:06.880 align:start position:0% this situation, the upload will fail and 00:22:06.880 --> 00:22:09.669 align:start position:0% this situation, the upload will fail and there<00:22:07.200> are<00:22:07.679> two<00:22:08.080> reasons<00:22:08.480> for<00:22:08.640> that.<00:22:09.200> First, 00:22:09.669 --> 00:22:09.679 align:start position:0% there are two reasons for that. First, 00:22:09.679 --> 00:22:11.990 align:start position:0% there are two reasons for that. First, there<00:22:09.919> is<00:22:10.159> no<00:22:10.480> authenticated<00:22:11.280> user<00:22:11.600> section 00:22:11.990 --> 00:22:12.000 align:start position:0% there is no authenticated user section 00:22:12.000 --> 00:22:14.549 align:start position:0% there is no authenticated user section attached<00:22:12.559> to<00:22:12.799> the<00:22:13.039> request.<00:22:13.679> And<00:22:13.919> second,<00:22:14.320> the 00:22:14.549 --> 00:22:14.559 align:start position:0% attached to the request. And second, the 00:22:14.559 --> 00:22:17.110 align:start position:0% attached to the request. And second, the storage<00:22:14.880> bucket<00:22:15.280> has<00:22:15.600> RO<00:22:16.159> full<00:22:16.480> security 00:22:17.110 --> 00:22:17.120 align:start position:0% storage bucket has RO full security 00:22:17.120 --> 00:22:20.149 align:start position:0% storage bucket has RO full security policies<00:22:17.919> that<00:22:18.159> can<00:22:18.400> block<00:22:18.880> unauthenticated 00:22:20.149 --> 00:22:20.159 align:start position:0% policies that can block unauthenticated 00:22:20.159 --> 00:22:22.070 align:start position:0% policies that can block unauthenticated uploads<00:22:20.640> by<00:22:20.799> default.<00:22:21.360> And<00:22:21.520> if<00:22:21.760> you<00:22:21.840> want<00:22:21.919> to 00:22:22.070 --> 00:22:22.080 align:start position:0% uploads by default. And if you want to 00:22:22.080 --> 00:22:23.590 align:start position:0% uploads by default. And if you want to learn<00:22:22.240> more<00:22:22.480> details,<00:22:22.960> you<00:22:23.200> can<00:22:23.360> actually 00:22:23.590 --> 00:22:23.600 align:start position:0% learn more details, you can actually 00:22:23.600 --> 00:22:25.750 align:start position:0% learn more details, you can actually check<00:22:23.840> out<00:22:24.000> the<00:22:24.320> superbase<00:22:24.880> documentation<00:22:25.520> as 00:22:25.750 --> 00:22:25.760 align:start position:0% check out the superbase documentation as 00:22:25.760 --> 00:22:29.669 align:start position:0% check out the superbase documentation as well.<00:22:26.480> So<00:22:26.799> the<00:22:27.120> service<00:22:27.520> ro<00:22:28.320> should<00:22:28.960> only<00:22:29.360> ever 00:22:29.669 --> 00:22:29.679 align:start position:0% well. So the service ro should only ever 00:22:29.679 --> 00:22:33.350 align:start position:0% well. So the service ro should only ever be<00:22:29.919> caught<00:22:30.400> server<00:22:30.720> side,<00:22:31.679> never<00:22:32.400> exposed<00:22:33.200> in 00:22:33.350 --> 00:22:33.360 align:start position:0% be caught server side, never exposed in 00:22:33.360 --> 00:22:36.230 align:start position:0% be caught server side, never exposed in the<00:22:33.520> browser.<00:22:34.400> And<00:22:34.799> that<00:22:35.039> is<00:22:35.360> exactly<00:22:35.840> how<00:22:36.000> we 00:22:36.230 --> 00:22:36.240 align:start position:0% the browser. And that is exactly how we 00:22:36.240 --> 00:22:38.549 align:start position:0% the browser. And that is exactly how we are<00:22:36.320> going<00:22:36.400> to<00:22:36.559> use<00:22:36.720> it<00:22:36.880> here.<00:22:37.600> a<00:22:37.919> backend 00:22:38.549 --> 00:22:38.559 align:start position:0% are going to use it here. a backend 00:22:38.559 --> 00:22:41.990 align:start position:0% are going to use it here. a backend pipeline,<00:22:39.440> no<00:22:39.760> front<00:22:40.000> end,<00:22:40.720> no<00:22:41.039> user<00:22:41.360> section. 00:22:41.990 --> 00:22:42.000 align:start position:0% pipeline, no front end, no user section. 00:22:42.000 --> 00:22:44.310 align:start position:0% pipeline, no front end, no user section. Now,<00:22:42.159> if<00:22:42.480> this<00:22:42.960> project<00:22:43.520> ever<00:22:43.760> had<00:22:43.919> a<00:22:44.159> front 00:22:44.310 --> 00:22:44.320 align:start position:0% Now, if this project ever had a front 00:22:44.320 --> 00:22:47.029 align:start position:0% Now, if this project ever had a front end,<00:22:44.960> so<00:22:45.200> like<00:22:45.440> a<00:22:45.840> dashboard<00:22:46.320> where<00:22:46.640> users 00:22:47.029 --> 00:22:47.039 align:start position:0% end, so like a dashboard where users 00:22:47.039 --> 00:22:49.029 align:start position:0% end, so like a dashboard where users upload<00:22:47.360> their<00:22:47.600> own<00:22:47.840> files,<00:22:48.400> then<00:22:48.720> you<00:22:48.880> could 00:22:49.029 --> 00:22:49.039 align:start position:0% upload their own files, then you could 00:22:49.039 --> 00:22:52.149 align:start position:0% upload their own files, then you could opt<00:22:49.360> for<00:22:49.679> the<00:22:50.159> nonkey<00:22:51.039> and<00:22:51.280> set<00:22:51.440> up<00:22:51.600> proper 00:22:52.149 --> 00:22:52.159 align:start position:0% opt for the nonkey and set up proper 00:22:52.159 --> 00:22:55.029 align:start position:0% opt for the nonkey and set up proper role<00:22:52.400> level<00:22:52.799> security<00:22:53.280> policies.<00:22:54.240> But<00:22:54.480> for<00:22:54.720> an 00:22:55.029 --> 00:22:55.039 align:start position:0% role level security policies. But for an 00:22:55.039 --> 00:22:57.110 align:start position:0% role level security policies. But for an automation<00:22:55.600> pipeline<00:22:56.159> like<00:22:56.480> this<00:22:56.720> one<00:22:56.880> that 00:22:57.110 --> 00:22:57.120 align:start position:0% automation pipeline like this one that 00:22:57.120 --> 00:22:58.630 align:start position:0% automation pipeline like this one that we're<00:22:57.360> going<00:22:57.440> to<00:22:57.520> set<00:22:57.679> up<00:22:57.840> here,<00:22:58.159> the<00:22:58.320> service 00:22:58.630 --> 00:22:58.640 align:start position:0% we're going to set up here, the service 00:22:58.640 --> 00:23:00.870 align:start position:0% we're going to set up here, the service key<00:22:58.880> is<00:22:59.200> what<00:22:59.520> we're<00:22:59.760> going<00:22:59.840> to<00:23:00.000> use.<00:23:00.480> So,<00:23:00.640> you 00:23:00.870 --> 00:23:00.880 align:start position:0% key is what we're going to use. So, you 00:23:00.880 --> 00:23:03.190 align:start position:0% key is what we're going to use. So, you now<00:23:01.120> know<00:23:01.360> where<00:23:01.600> your<00:23:01.840> service<00:23:02.159> key<00:23:02.400> is.<00:23:02.960> Just 00:23:03.190 --> 00:23:03.200 align:start position:0% now know where your service key is. Just 00:23:03.200 --> 00:23:05.830 align:start position:0% now know where your service key is. Just copy<00:23:03.520> and<00:23:03.679> paste<00:23:03.919> it<00:23:04.159> into<00:23:04.559> your<00:23:04.799> EMV<00:23:05.360> file 00:23:05.830 --> 00:23:05.840 align:start position:0% copy and paste it into your EMV file 00:23:05.840 --> 00:23:08.549 align:start position:0% copy and paste it into your EMV file alongside<00:23:06.720> your<00:23:07.120> project<00:23:07.679> URL.<00:23:08.320> All<00:23:08.320> right, 00:23:08.549 --> 00:23:08.559 align:start position:0% alongside your project URL. All right, 00:23:08.559 --> 00:23:10.630 align:start position:0% alongside your project URL. All right, so<00:23:08.880> please<00:23:09.039> hang<00:23:09.280> on.<00:23:09.520> We<00:23:09.760> are<00:23:09.919> not<00:23:10.159> quite<00:23:10.400> done 00:23:10.630 --> 00:23:10.640 align:start position:0% so please hang on. We are not quite done 00:23:10.640 --> 00:23:13.909 align:start position:0% so please hang on. We are not quite done with<00:23:11.039> Superbase<00:23:11.600> yet.<00:23:12.720> We<00:23:13.280> need<00:23:13.440> to<00:23:13.679> create 00:23:13.909 --> 00:23:13.919 align:start position:0% with Superbase yet. We need to create 00:23:13.919 --> 00:23:16.310 align:start position:0% with Superbase yet. We need to create the<00:23:14.159> storage<00:23:14.480> bucket<00:23:15.280> that<00:23:15.679> the<00:23:15.840> pipeline 00:23:16.310 --> 00:23:16.320 align:start position:0% the storage bucket that the pipeline 00:23:16.320 --> 00:23:18.549 align:start position:0% the storage bucket that the pipeline will<00:23:16.559> upload<00:23:16.960> assess<00:23:17.440> into.<00:23:18.159> From<00:23:18.400> a 00:23:18.549 --> 00:23:18.559 align:start position:0% will upload assess into. From a 00:23:18.559 --> 00:23:21.110 align:start position:0% will upload assess into. From a dashboard,<00:23:18.960> we<00:23:19.200> can<00:23:19.360> click<00:23:19.760> on<00:23:20.400> storage<00:23:20.960> on 00:23:21.110 --> 00:23:21.120 align:start position:0% dashboard, we can click on storage on 00:23:21.120 --> 00:23:23.350 align:start position:0% dashboard, we can click on storage on the<00:23:21.360> left<00:23:21.600> hand<00:23:21.840> side.<00:23:22.799> And<00:23:22.960> once<00:23:23.200> you're 00:23:23.350 --> 00:23:23.360 align:start position:0% the left hand side. And once you're 00:23:23.360 --> 00:23:25.830 align:start position:0% the left hand side. And once you're inside,<00:23:23.840> you<00:23:24.000> can<00:23:24.159> click<00:23:24.559> create<00:23:24.960> bucket<00:23:25.600> and 00:23:25.830 --> 00:23:25.840 align:start position:0% inside, you can click create bucket and 00:23:25.840 --> 00:23:27.909 align:start position:0% inside, you can click create bucket and then<00:23:26.000> give<00:23:26.159> it<00:23:26.320> a<00:23:26.480> name.<00:23:27.039> We're<00:23:27.360> specifically 00:23:27.909 --> 00:23:27.919 align:start position:0% then give it a name. We're specifically 00:23:27.919 --> 00:23:29.990 align:start position:0% then give it a name. We're specifically using<00:23:28.320> campaign-uploads 00:23:29.990 --> 00:23:30.000 align:start position:0% using campaign-uploads 00:23:30.000 --> 00:23:31.990 align:start position:0% using campaign-uploads for<00:23:30.240> this<00:23:30.480> project.<00:23:31.200> and<00:23:31.360> make<00:23:31.600> sure<00:23:31.679> to<00:23:31.840> set 00:23:31.990 --> 00:23:32.000 align:start position:0% for this project. and make sure to set 00:23:32.000 --> 00:23:34.149 align:start position:0% for this project. and make sure to set it<00:23:32.159> to<00:23:32.320> the<00:23:32.559> public.<00:23:33.120> And<00:23:33.280> this<00:23:33.600> specific<00:23:33.919> name 00:23:34.149 --> 00:23:34.159 align:start position:0% it to the public. And this specific name 00:23:34.159 --> 00:23:36.710 align:start position:0% it to the public. And this specific name is<00:23:34.320> very<00:23:34.559> important<00:23:34.880> because<00:23:35.440> in<00:23:35.840> our<00:23:36.240> code, 00:23:36.710 --> 00:23:36.720 align:start position:0% is very important because in our code, 00:23:36.720 --> 00:23:38.789 align:start position:0% is very important because in our code, the<00:23:37.039> referenced<00:23:37.520> bucket<00:23:37.919> name<00:23:38.240> from<00:23:38.559> where 00:23:38.789 --> 00:23:38.799 align:start position:0% the referenced bucket name from where 00:23:38.799 --> 00:23:42.950 align:start position:0% the referenced bucket name from where the<00:23:39.039> outputs<00:23:39.679> will<00:23:40.080> be<00:23:40.400> outload<00:23:41.120> is<00:23:41.679> hotcoded. 00:23:42.950 --> 00:23:42.960 align:start position:0% the outputs will be outload is hotcoded. 00:23:42.960 --> 00:23:44.870 align:start position:0% the outputs will be outload is hotcoded. So<00:23:43.200> please<00:23:43.600> make<00:23:43.840> sure<00:23:44.000> to<00:23:44.320> remember<00:23:44.640> what 00:23:44.870 --> 00:23:44.880 align:start position:0% So please make sure to remember what 00:23:44.880 --> 00:23:47.669 align:start position:0% So please make sure to remember what bucket<00:23:45.360> name<00:23:45.760> CL<00:23:46.159> gives<00:23:46.480> you<00:23:46.720> before<00:23:47.280> creating 00:23:47.669 --> 00:23:47.679 align:start position:0% bucket name CL gives you before creating 00:23:47.679 --> 00:23:50.149 align:start position:0% bucket name CL gives you before creating the<00:23:47.919> bucket.<00:23:48.480> And<00:23:48.640> also<00:23:48.960> the<00:23:49.280> public<00:23:49.840> setting 00:23:50.149 --> 00:23:50.159 align:start position:0% the bucket. And also the public setting 00:23:50.159 --> 00:23:52.549 align:start position:0% the bucket. And also the public setting is<00:23:50.480> what<00:23:50.880> allows<00:23:51.200> the<00:23:51.440> YouTube<00:23:51.840> and<00:23:52.080> Instagram 00:23:52.549 --> 00:23:52.559 align:start position:0% is what allows the YouTube and Instagram 00:23:52.559 --> 00:23:55.270 align:start position:0% is what allows the YouTube and Instagram APIs<00:23:53.039> to<00:23:53.280> reach<00:23:53.679> the<00:23:54.000> uploaded<00:23:54.640> files<00:23:55.120> of 00:23:55.270 --> 00:23:55.280 align:start position:0% APIs to reach the uploaded files of 00:23:55.280 --> 00:23:57.590 align:start position:0% APIs to reach the uploaded files of course.<00:23:56.080> And<00:23:56.320> this<00:23:56.559> is<00:23:56.720> exactly<00:23:57.120> what<00:23:57.360> we 00:23:57.590 --> 00:23:57.600 align:start position:0% course. And this is exactly what we 00:23:57.600 --> 00:23:59.669 align:start position:0% course. And this is exactly what we needed<00:23:58.000> for<00:23:58.159> Instagram,<00:23:58.720> right?<00:23:59.280> And<00:23:59.520> that's 00:23:59.669 --> 00:23:59.679 align:start position:0% needed for Instagram, right? And that's 00:23:59.679 --> 00:24:01.909 align:start position:0% needed for Instagram, right? And that's it.<00:24:00.080> Superbase<00:24:00.640> storage<00:24:00.880> is<00:24:01.200> configured<00:24:01.679> and 00:24:01.909 --> 00:24:01.919 align:start position:0% it. Superbase storage is configured and 00:24:01.919 --> 00:24:04.310 align:start position:0% it. Superbase storage is configured and the<00:24:02.080> bucket<00:24:02.400> is<00:24:02.640> ready.<00:24:03.039> So<00:24:03.360> all<00:24:03.679> five<00:24:03.919> agents 00:24:04.310 --> 00:24:04.320 align:start position:0% the bucket is ready. So all five agents 00:24:04.320 --> 00:24:06.630 align:start position:0% the bucket is ready. So all five agents are<00:24:04.480> built,<00:24:04.880> the<00:24:05.039> APIs<00:24:05.600> are<00:24:05.760> connected,<00:24:06.480> the 00:24:06.630 --> 00:24:06.640 align:start position:0% are built, the APIs are connected, the 00:24:06.640 --> 00:24:09.430 align:start position:0% are built, the APIs are connected, the storage<00:24:07.200> layer<00:24:07.440> is<00:24:07.679> in<00:24:07.919> place,<00:24:08.720> every<00:24:09.039> single 00:24:09.430 --> 00:24:09.440 align:start position:0% storage layer is in place, every single 00:24:09.440 --> 00:24:11.990 align:start position:0% storage layer is in place, every single piece<00:24:09.679> of<00:24:09.840> the<00:24:10.000> pipeline<00:24:10.480> is<00:24:10.960> now<00:24:11.360> ready.<00:24:11.840> And 00:24:11.990 --> 00:24:12.000 align:start position:0% piece of the pipeline is now ready. And 00:24:12.000 --> 00:24:14.390 align:start position:0% piece of the pipeline is now ready. And now<00:24:12.159> it's<00:24:12.400> time<00:24:12.559> to<00:24:12.799> see<00:24:13.039> all<00:24:13.360> five<00:24:13.679> agents<00:24:14.159> run 00:24:14.390 --> 00:24:14.400 align:start position:0% now it's time to see all five agents run 00:24:14.400 --> 00:24:17.830 align:start position:0% now it's time to see all five agents run together<00:24:14.960> as<00:24:15.440> one<00:24:16.000> connected<00:24:16.559> pipeline. 00:24:17.830 --> 00:24:17.840 align:start position:0% together as one connected pipeline. 00:24:17.840 --> 00:24:19.510 align:start position:0% together as one connected pipeline. Let's<00:24:18.159> do<00:24:18.320> the<00:24:18.480> full<00:24:18.720> test<00:24:18.960> run<00:24:19.200> now.<00:24:19.520> All 00:24:19.510 --> 00:24:19.520 align:start position:0% Let's do the full test run now. All 00:24:19.520 --> 00:24:22.070 align:start position:0% Let's do the full test run now. All right.<00:24:19.760> So<00:24:19.919> before<00:24:20.240> we<00:24:20.640> run<00:24:20.880> it<00:24:21.039> in<00:24:21.279> clot<00:24:21.600> code, 00:24:22.070 --> 00:24:22.080 align:start position:0% right. So before we run it in clot code, 00:24:22.080 --> 00:24:24.230 align:start position:0% right. So before we run it in clot code, let<00:24:22.240> me<00:24:22.480> show<00:24:22.640> you<00:24:22.960> the<00:24:23.279> prompt<00:24:23.679> that<00:24:23.919> we<00:24:24.080> are 00:24:24.230 --> 00:24:24.240 align:start position:0% let me show you the prompt that we are 00:24:24.240 --> 00:24:26.549 align:start position:0% let me show you the prompt that we are going<00:24:24.320> to<00:24:24.480> use.<00:24:25.039> So<00:24:25.279> here<00:24:25.440> it<00:24:25.600> is.<00:24:26.000> It<00:24:26.240> is<00:24:26.400> a 00:24:26.549 --> 00:24:26.559 align:start position:0% going to use. So here it is. It is a 00:24:26.559 --> 00:24:29.830 align:start position:0% going to use. So here it is. It is a simple<00:24:26.880> job<00:24:27.200> payload<00:24:28.159> like<00:24:28.640> no<00:24:28.960> need<00:24:29.279> to<00:24:29.520> over 00:24:29.830 --> 00:24:29.840 align:start position:0% simple job payload like no need to over 00:24:29.840 --> 00:24:32.549 align:start position:0% simple job payload like no need to over complicate<00:24:30.240> a<00:24:30.480> pilot<00:24:30.799> test<00:24:31.039> right<00:24:31.919> and<00:24:32.320> the 00:24:32.549 --> 00:24:32.559 align:start position:0% complicate a pilot test right and the 00:24:32.559 --> 00:24:35.110 align:start position:0% complicate a pilot test right and the payload<00:24:33.200> contains<00:24:33.600> the<00:24:33.840> core<00:24:34.080> brief<00:24:34.640> like<00:24:34.880> the 00:24:35.110 --> 00:24:35.120 align:start position:0% payload contains the core brief like the 00:24:35.120 --> 00:24:37.269 align:start position:0% payload contains the core brief like the brand<00:24:35.520> the<00:24:35.760> campaign<00:24:36.159> goal<00:24:36.640> the<00:24:36.880> content 00:24:37.269 --> 00:24:37.279 align:start position:0% brand the campaign goal the content 00:24:37.279 --> 00:24:40.710 align:start position:0% brand the campaign goal the content requirements<00:24:38.400> and<00:24:38.559> the<00:24:38.880> other<00:24:39.200> agents<00:24:40.320> can 00:24:40.710 --> 00:24:40.720 align:start position:0% requirements and the other agents can 00:24:40.720 --> 00:24:43.269 align:start position:0% requirements and the other agents can analyze<00:24:41.520> and<00:24:41.760> then<00:24:42.000> reach<00:24:42.240> it<00:24:42.480> as<00:24:42.720> it<00:24:42.960> moves 00:24:43.269 --> 00:24:43.279 align:start position:0% analyze and then reach it as it moves 00:24:43.279 --> 00:24:44.870 align:start position:0% analyze and then reach it as it moves through<00:24:43.440> the<00:24:43.679> pipeline<00:24:44.320> and<00:24:44.480> then<00:24:44.720> the 00:24:44.870 --> 00:24:44.880 align:start position:0% through the pipeline and then the 00:24:44.880 --> 00:24:46.710 align:start position:0% through the pipeline and then the distribution<00:24:45.440> agent<00:24:45.840> will<00:24:46.159> convert 00:24:46.710 --> 00:24:46.720 align:start position:0% distribution agent will convert 00:24:46.720 --> 00:24:49.269 align:start position:0% distribution agent will convert everything<00:24:47.200> into<00:24:47.600> a<00:24:47.840> JSON<00:24:48.240> script<00:24:48.799> that<00:24:49.039> can 00:24:49.269 --> 00:24:49.279 align:start position:0% everything into a JSON script that can 00:24:49.279 --> 00:24:51.590 align:start position:0% everything into a JSON script that can trigger<00:24:49.600> the<00:24:49.840> full<00:24:50.240> automation<00:24:50.880> sequence 00:24:51.590 --> 00:24:51.600 align:start position:0% trigger the full automation sequence 00:24:51.600 --> 00:24:54.149 align:start position:0% trigger the full automation sequence just<00:24:51.840> simple<00:24:52.159> input<00:24:52.880> and<00:24:53.120> then<00:24:53.440> the<00:24:53.679> agents 00:24:54.149 --> 00:24:54.159 align:start position:0% just simple input and then the agents 00:24:54.159 --> 00:24:56.149 align:start position:0% just simple input and then the agents can<00:24:54.400> do<00:24:54.559> the<00:24:54.799> rest<00:24:55.039> so<00:24:55.279> let's<00:24:55.520> Just<00:24:55.679> copy<00:24:55.919> this 00:24:56.149 --> 00:24:56.159 align:start position:0% can do the rest so let's Just copy this 00:24:56.159 --> 00:24:58.310 align:start position:0% can do the rest so let's Just copy this prompt<00:24:56.400> and<00:24:56.559> paste<00:24:56.799> it<00:24:56.960> into<00:24:57.360> clot<00:24:57.760> code.<00:24:58.159> And 00:24:58.310 --> 00:24:58.320 align:start position:0% prompt and paste it into clot code. And 00:24:58.320 --> 00:25:00.070 align:start position:0% prompt and paste it into clot code. And then<00:24:58.480> we<00:24:58.640> can<00:24:58.799> hit<00:24:59.039> enter.<00:24:59.440> And<00:24:59.679> now<00:24:59.840> you<00:25:00.000> can 00:25:00.070 --> 00:25:00.080 align:start position:0% then we can hit enter. And now you can 00:25:00.080 --> 00:25:01.909 align:start position:0% then we can hit enter. And now you can see<00:25:00.320> clot<00:25:00.640> code<00:25:00.880> is<00:25:01.120> starting<00:25:01.360> to<00:25:01.600> reference 00:25:01.909 --> 00:25:01.919 align:start position:0% see clot code is starting to reference 00:25:01.919 --> 00:25:04.070 align:start position:0% see clot code is starting to reference the<00:25:02.159> relevant<00:25:02.480> agent<00:25:02.880> skills<00:25:03.279> for<00:25:03.600> each<00:25:03.840> part 00:25:04.070 --> 00:25:04.080 align:start position:0% the relevant agent skills for each part 00:25:04.080 --> 00:25:06.789 align:start position:0% the relevant agent skills for each part of<00:25:04.240> the<00:25:04.400> task.<00:25:05.360> And<00:25:05.679> it<00:25:05.919> is<00:25:06.240> reading<00:25:06.559> the 00:25:06.789 --> 00:25:06.799 align:start position:0% of the task. And it is reading the 00:25:06.799 --> 00:25:09.669 align:start position:0% of the task. And it is reading the pipeline<00:25:07.840> identifying<00:25:08.320> which<00:25:08.720> agent<00:25:09.200> handles 00:25:09.669 --> 00:25:09.679 align:start position:0% pipeline identifying which agent handles 00:25:09.679 --> 00:25:11.990 align:start position:0% pipeline identifying which agent handles which<00:25:10.000> job<00:25:10.559> and<00:25:10.960> queuing<00:25:11.360> everything<00:25:11.679> in 00:25:11.990 --> 00:25:12.000 align:start position:0% which job and queuing everything in 00:25:12.000 --> 00:25:13.909 align:start position:0% which job and queuing everything in order.<00:25:12.400> And<00:25:12.559> now<00:25:12.720> that<00:25:12.880> the<00:25:13.039> JSON<00:25:13.440> is<00:25:13.600> ready, 00:25:13.909 --> 00:25:13.919 align:start position:0% order. And now that the JSON is ready, 00:25:13.919 --> 00:25:16.710 align:start position:0% order. And now that the JSON is ready, right,<00:25:14.320> we<00:25:14.640> will<00:25:14.960> allow<00:25:15.360> to<00:25:15.600> clot<00:25:16.080> code<00:25:16.480> to 00:25:16.710 --> 00:25:16.720 align:start position:0% right, we will allow to clot code to 00:25:16.720 --> 00:25:18.390 align:start position:0% right, we will allow to clot code to create<00:25:16.880> the<00:25:17.120> file<00:25:17.360> in<00:25:17.600> the<00:25:17.760> project.<00:25:18.240> And 00:25:18.390 --> 00:25:18.400 align:start position:0% create the file in the project. And 00:25:18.400 --> 00:25:19.750 align:start position:0% create the file in the project. And here's<00:25:18.640> the<00:25:18.799> first<00:25:19.039> breakdown<00:25:19.440> of<00:25:19.600> the 00:25:19.750 --> 00:25:19.760 align:start position:0% here's the first breakdown of the 00:25:19.760 --> 00:25:22.549 align:start position:0% here's the first breakdown of the payload.<00:25:20.799> And<00:25:21.360> it's<00:25:21.679> looking<00:25:22.000> pretty<00:25:22.240> good, 00:25:22.549 --> 00:25:22.559 align:start position:0% payload. And it's looking pretty good, 00:25:22.559 --> 00:25:25.350 align:start position:0% payload. And it's looking pretty good, right?<00:25:23.039> All<00:25:23.279> agents<00:25:23.760> are<00:25:24.000> cued<00:25:24.559> and<00:25:24.880> ready<00:25:25.120> for 00:25:25.350 --> 00:25:25.360 align:start position:0% right? All agents are cued and ready for 00:25:25.360 --> 00:25:27.110 align:start position:0% right? All agents are cued and ready for execution.<00:25:25.919> But<00:25:26.080> one<00:25:26.320> thing<00:25:26.400> to<00:25:26.559> notice<00:25:26.880> here 00:25:27.110 --> 00:25:27.120 align:start position:0% execution. But one thing to notice here 00:25:27.120 --> 00:25:29.750 align:start position:0% execution. But one thing to notice here though,<00:25:27.440> the<00:25:28.000> distribution<00:25:28.480> agent<00:25:29.360> C 00:25:29.750 --> 00:25:29.760 align:start position:0% though, the distribution agent C 00:25:29.760 --> 00:25:31.990 align:start position:0% though, the distribution agent C actually<00:25:30.240> has<00:25:30.480> added<00:25:30.799> a<00:25:31.039> constraint<00:25:31.679> that 00:25:31.990 --> 00:25:32.000 align:start position:0% actually has added a constraint that 00:25:32.000 --> 00:25:34.549 align:start position:0% actually has added a constraint that sued<00:25:32.559> uploads<00:25:33.120> will<00:25:33.440> run<00:25:33.679> in<00:25:34.000> simulation 00:25:34.549 --> 00:25:34.559 align:start position:0% sued uploads will run in simulation 00:25:34.559 --> 00:25:38.390 align:start position:0% sued uploads will run in simulation mode.<00:25:35.600> Meaning<00:25:36.320> no<00:25:36.640> real<00:25:36.880> API<00:25:37.360> call<00:25:37.760> goes<00:25:38.000> out 00:25:38.390 --> 00:25:38.400 align:start position:0% mode. Meaning no real API call goes out 00:25:38.400 --> 00:25:40.070 align:start position:0% mode. Meaning no real API call goes out and<00:25:38.640> that<00:25:38.799> is<00:25:38.960> not<00:25:39.120> what<00:25:39.279> we<00:25:39.440> want,<00:25:39.760> right? 00:25:40.070 --> 00:25:40.080 align:start position:0% and that is not what we want, right? 00:25:40.080 --> 00:25:41.990 align:start position:0% and that is not what we want, right? Because<00:25:40.240> we<00:25:40.559> need<00:25:40.799> the<00:25:41.039> actual<00:25:41.360> upload<00:25:41.760> to 00:25:41.990 --> 00:25:42.000 align:start position:0% Because we need the actual upload to 00:25:42.000 --> 00:25:44.549 align:start position:0% Because we need the actual upload to happen<00:25:42.480> so<00:25:42.720> that<00:25:43.039> the<00:25:43.279> Instagram<00:25:43.760> API<00:25:44.320> can 00:25:44.549 --> 00:25:44.559 align:start position:0% happen so that the Instagram API can 00:25:44.559 --> 00:25:47.110 align:start position:0% happen so that the Instagram API can reach<00:25:44.880> the<00:25:45.200> files.<00:25:46.240> So<00:25:46.480> then<00:25:46.640> we<00:25:46.799> can<00:25:46.960> just 00:25:47.110 --> 00:25:47.120 align:start position:0% reach the files. So then we can just 00:25:47.120 --> 00:25:50.390 align:start position:0% reach the files. So then we can just tell<00:25:47.600> clot<00:25:48.080> to<00:25:48.320> proceed<00:25:48.799> with<00:25:49.360> real<00:25:49.760> superbase 00:25:50.390 --> 00:25:50.400 align:start position:0% tell clot to proceed with real superbase 00:25:50.400 --> 00:25:53.350 align:start position:0% tell clot to proceed with real superbase uploads<00:25:50.960> before<00:25:51.520> we<00:25:51.760> let<00:25:52.000> it<00:25:52.240> run.<00:25:52.720> Okay,<00:25:53.120> that 00:25:53.350 --> 00:25:53.360 align:start position:0% uploads before we let it run. Okay, that 00:25:53.360 --> 00:25:55.190 align:start position:0% uploads before we let it run. Okay, that should<00:25:53.520> do<00:25:53.679> it.<00:25:53.919> And<00:25:54.080> now<00:25:54.320> we<00:25:54.480> can<00:25:54.559> just<00:25:54.720> wait. 00:25:55.190 --> 00:25:55.200 align:start position:0% should do it. And now we can just wait. 00:25:55.200 --> 00:25:56.789 align:start position:0% should do it. And now we can just wait. This<00:25:55.440> will<00:25:55.679> take<00:25:55.760> a<00:25:56.000> few<00:25:56.240> minutes<00:25:56.480> to 00:25:56.789 --> 00:25:56.799 align:start position:0% This will take a few minutes to 00:25:56.799 --> 00:25:59.750 align:start position:0% This will take a few minutes to complete.<00:25:57.840> All<00:25:57.919> right,<00:25:58.400> after<00:25:59.279> everything<00:25:59.520> is 00:25:59.750 --> 00:25:59.760 align:start position:0% complete. All right, after everything is 00:25:59.760 --> 00:26:02.710 align:start position:0% complete. All right, after everything is done<00:26:00.320> and<00:26:00.640> before<00:26:00.960> we<00:26:01.440> approve<00:26:01.919> the<00:26:02.240> upload, 00:26:02.710 --> 00:26:02.720 align:start position:0% done and before we approve the upload, 00:26:02.720 --> 00:26:04.710 align:start position:0% done and before we approve the upload, we<00:26:02.880> can<00:26:03.039> just<00:26:03.200> check<00:26:03.360> the<00:26:03.600> outputs<00:26:04.000> first.<00:26:04.559> So 00:26:04.710 --> 00:26:04.720 align:start position:0% we can just check the outputs first. So 00:26:04.720 --> 00:26:06.470 align:start position:0% we can just check the outputs first. So we<00:26:04.960> can<00:26:05.039> start<00:26:05.200> from<00:26:05.440> the<00:26:05.600> research<00:26:06.000> report. 00:26:06.470 --> 00:26:06.480 align:start position:0% we can start from the research report. 00:26:06.480 --> 00:26:08.710 align:start position:0% we can start from the research report. We<00:26:06.720> actually<00:26:07.039> have<00:26:07.200> two<00:26:07.440> versions<00:26:07.840> here.<00:26:08.480> One 00:26:08.710 --> 00:26:08.720 align:start position:0% We actually have two versions here. One 00:26:08.720 --> 00:26:12.149 align:start position:0% We actually have two versions here. One in<00:26:08.960> document<00:26:09.440> format<00:26:09.840> and<00:26:10.159> one<00:26:10.480> in<00:26:11.039> HTML.<00:26:11.919> And 00:26:12.149 --> 00:26:12.159 align:start position:0% in document format and one in HTML. And 00:26:12.159 --> 00:26:14.070 align:start position:0% in document format and one in HTML. And this<00:26:12.320> is<00:26:12.480> quite<00:26:12.720> a<00:26:12.960> nice<00:26:13.200> bonus,<00:26:13.600> right?<00:26:13.840> It 00:26:14.070 --> 00:26:14.080 align:start position:0% this is quite a nice bonus, right? It 00:26:14.080 --> 00:26:17.190 align:start position:0% this is quite a nice bonus, right? It can<00:26:14.400> give<00:26:14.559> us<00:26:15.520> two<00:26:15.840> different<00:26:16.159> use<00:26:16.400> cases<00:26:16.799> from 00:26:17.190 --> 00:26:17.200 align:start position:0% can give us two different use cases from 00:26:17.200 --> 00:26:19.590 align:start position:0% can give us two different use cases from the<00:26:17.440> same<00:26:17.600> output.<00:26:18.159> So<00:26:18.400> let's<00:26:18.640> open<00:26:18.799> the<00:26:18.960> HTML 00:26:19.590 --> 00:26:19.600 align:start position:0% the same output. So let's open the HTML 00:26:19.600 --> 00:26:21.830 align:start position:0% the same output. So let's open the HTML version.<00:26:20.080> And<00:26:20.320> here<00:26:20.480> it<00:26:20.559> is<00:26:20.880> an<00:26:21.200> interactive 00:26:21.830 --> 00:26:21.840 align:start position:0% version. And here it is an interactive 00:26:21.840 --> 00:26:24.549 align:start position:0% version. And here it is an interactive research<00:26:22.320> dashboard.<00:26:23.520> Clean<00:26:23.919> layout,<00:26:24.320> easy 00:26:24.549 --> 00:26:24.559 align:start position:0% research dashboard. Clean layout, easy 00:26:24.559 --> 00:26:27.350 align:start position:0% research dashboard. Clean layout, easy to<00:26:24.799> follow,<00:26:25.360> and<00:26:25.679> the<00:26:26.000> brand<00:26:26.320> colors<00:26:26.799> are 00:26:27.350 --> 00:26:27.360 align:start position:0% to follow, and the brand colors are 00:26:27.360 --> 00:26:28.870 align:start position:0% to follow, and the brand colors are actually<00:26:27.679> being<00:26:28.000> applied<00:26:28.400> throughout, 00:26:28.870 --> 00:26:28.880 align:start position:0% actually being applied throughout, 00:26:28.880 --> 00:26:30.789 align:start position:0% actually being applied throughout, right?<00:26:29.200> And<00:26:29.360> this<00:26:29.520> is<00:26:29.600> a<00:26:29.840> kind<00:26:30.000> of<00:26:30.159> output<00:26:30.559> you 00:26:30.789 --> 00:26:30.799 align:start position:0% right? And this is a kind of output you 00:26:30.799 --> 00:26:33.909 align:start position:0% right? And this is a kind of output you would<00:26:31.120> share<00:26:31.360> with<00:26:31.520> a<00:26:31.760> client<00:26:32.400> or<00:26:32.880> a<00:26:33.200> team<00:26:33.520> lead 00:26:33.909 --> 00:26:33.919 align:start position:0% would share with a client or a team lead 00:26:33.919 --> 00:26:36.310 align:start position:0% would share with a client or a team lead before<00:26:34.240> a<00:26:34.559> campaign<00:26:35.200> kicks<00:26:35.520> off,<00:26:35.760> right?<00:26:36.080> And 00:26:36.310 --> 00:26:36.320 align:start position:0% before a campaign kicks off, right? And 00:26:36.320 --> 00:26:38.789 align:start position:0% before a campaign kicks off, right? And also<00:26:36.640> the<00:26:36.880> information<00:26:37.360> quality<00:26:37.760> is<00:26:38.159> solid 00:26:38.789 --> 00:26:38.799 align:start position:0% also the information quality is solid 00:26:38.799 --> 00:26:41.110 align:start position:0% also the information quality is solid and<00:26:39.279> it<00:26:39.520> is<00:26:39.760> already<00:26:40.080> presented<00:26:40.480> in<00:26:40.640> a<00:26:40.799> format 00:26:41.110 --> 00:26:41.120 align:start position:0% and it is already presented in a format 00:26:41.120 --> 00:26:44.230 align:start position:0% and it is already presented in a format that<00:26:41.360> is<00:26:41.600> easy<00:26:41.919> to<00:26:42.159> digest.<00:26:42.960> So<00:26:43.200> if<00:26:43.520> you<00:26:43.679> need<00:26:43.919> a 00:26:44.230 --> 00:26:44.240 align:start position:0% that is easy to digest. So if you need a 00:26:44.240 --> 00:26:46.549 align:start position:0% that is easy to digest. So if you need a more<00:26:44.640> traditional<00:26:45.200> format,<00:26:46.080> the 00:26:46.549 --> 00:26:46.559 align:start position:0% more traditional format, the 00:26:46.559 --> 00:26:48.470 align:start position:0% more traditional format, the documentation<00:26:47.200> version<00:26:47.440> is<00:26:47.679> there<00:26:47.919> as<00:26:48.080> well 00:26:48.470 --> 00:26:48.480 align:start position:0% documentation version is there as well 00:26:48.480 --> 00:26:51.110 align:start position:0% documentation version is there as well and<00:26:48.720> it<00:26:48.960> is<00:26:49.120> in<00:26:49.279> mockdown<00:26:50.159> but<00:26:50.720> that<00:26:50.960> is 00:26:51.110 --> 00:26:51.120 align:start position:0% and it is in mockdown but that is 00:26:51.120 --> 00:26:53.430 align:start position:0% and it is in mockdown but that is straightforward<00:26:51.600> to<00:26:51.840> convert<00:26:52.240> to<00:26:52.559> a<00:26:53.039> like 00:26:53.430 --> 00:26:53.440 align:start position:0% straightforward to convert to a like 00:26:53.440 --> 00:26:55.750 align:start position:0% straightforward to convert to a like Google<00:26:53.760> doc<00:26:54.080> or<00:26:54.480> word<00:26:54.799> file.<00:26:55.120> And<00:26:55.279> now<00:26:55.520> let's 00:26:55.750 --> 00:26:55.760 align:start position:0% Google doc or word file. And now let's 00:26:55.760 --> 00:26:58.549 align:start position:0% Google doc or word file. And now let's check<00:26:56.000> the<00:26:56.240> static<00:26:56.640> ad<00:26:57.039> and<00:26:57.279> the<00:26:57.440> video<00:26:57.760> ad. 00:26:58.549 --> 00:26:58.559 align:start position:0% check the static ad and the video ad. 00:26:58.559 --> 00:27:00.870 align:start position:0% check the static ad and the video ad. Here's<00:26:58.799> the<00:26:59.039> static<00:26:59.360> ad.<00:26:59.760> Very<00:27:00.080> simple<00:27:00.559> and 00:27:00.870 --> 00:27:00.880 align:start position:0% Here's the static ad. Very simple and 00:27:00.880 --> 00:27:02.789 align:start position:0% Here's the static ad. Very simple and looks<00:27:01.279> pretty<00:27:01.520> good,<00:27:01.840> right?<00:27:02.320> And<00:27:02.559> what 00:27:02.789 --> 00:27:02.799 align:start position:0% looks pretty good, right? And what 00:27:02.799 --> 00:27:04.950 align:start position:0% looks pretty good, right? And what stands<00:27:03.039> out<00:27:03.200> is<00:27:03.360> the<00:27:03.600> consistency<00:27:04.159> here.<00:27:04.720> And 00:27:04.950 --> 00:27:04.960 align:start position:0% stands out is the consistency here. And 00:27:04.960 --> 00:27:07.110 align:start position:0% stands out is the consistency here. And this<00:27:05.120> is<00:27:05.200> the<00:27:05.440> second<00:27:05.679> time<00:27:06.000> that<00:27:06.400> our<00:27:06.799> ad 00:27:07.110 --> 00:27:07.120 align:start position:0% this is the second time that our ad 00:27:07.120 --> 00:27:09.029 align:start position:0% this is the second time that our ad creative<00:27:07.600> designer<00:27:08.159> has<00:27:08.400> produced<00:27:08.799> something 00:27:09.029 --> 00:27:09.039 align:start position:0% creative designer has produced something 00:27:09.039 --> 00:27:11.990 align:start position:0% creative designer has produced something that<00:27:09.360> looks<00:27:09.679> pretty<00:27:10.000> good<00:27:10.320> and<00:27:10.640> on<00:27:10.960> brand<00:27:11.600> with 00:27:11.990 --> 00:27:12.000 align:start position:0% that looks pretty good and on brand with 00:27:12.000 --> 00:27:14.789 align:start position:0% that looks pretty good and on brand with minimal<00:27:12.400> input.<00:27:13.039> And<00:27:13.200> that<00:27:13.440> consistency<00:27:14.159> is 00:27:14.789 --> 00:27:14.799 align:start position:0% minimal input. And that consistency is 00:27:14.799 --> 00:27:17.190 align:start position:0% minimal input. And that consistency is what<00:27:15.039> makes<00:27:15.360> this<00:27:15.600> workflow<00:27:16.159> really<00:27:16.559> great. 00:27:17.190 --> 00:27:17.200 align:start position:0% what makes this workflow really great. 00:27:17.200 --> 00:27:19.750 align:start position:0% what makes this workflow really great. Okay,<00:27:17.600> so<00:27:17.840> now<00:27:18.080> the<00:27:18.320> video<00:27:18.640> ad,<00:27:19.360> let's<00:27:19.679> go 00:27:19.750 --> 00:27:19.760 align:start position:0% Okay, so now the video ad, let's go 00:27:19.760 --> 00:27:23.909 align:start position:0% Okay, so now the video ad, let's go ahead<00:27:20.000> and<00:27:20.240> find<00:27:20.480> it<00:27:20.960> here<00:27:21.520> and<00:27:21.840> hit<00:27:22.240> play. 00:27:23.909 --> 00:27:23.919 align:start position:0% ahead and find it here and hit play. 00:27:23.919 --> 00:27:26.149 align:start position:0% ahead and find it here and hit play. It's<00:27:24.240> pretty<00:27:24.480> good,<00:27:24.720> right?<00:27:25.200> For<00:27:25.440> a<00:27:25.840> simple 00:27:26.149 --> 00:27:26.159 align:start position:0% It's pretty good, right? For a simple 00:27:26.159 --> 00:27:28.630 align:start position:0% It's pretty good, right? For a simple prompt<00:27:26.559> with<00:27:26.960> no<00:27:27.279> custom<00:27:27.760> assets<00:27:28.080> and<00:27:28.400> no 00:27:28.630 --> 00:27:28.640 align:start position:0% prompt with no custom assets and no 00:27:28.640 --> 00:27:30.950 align:start position:0% prompt with no custom assets and no detailed<00:27:29.360> storyboard.<00:27:30.159> So<00:27:30.320> you<00:27:30.480> can<00:27:30.640> imagine 00:27:30.950 --> 00:27:30.960 align:start position:0% detailed storyboard. So you can imagine 00:27:30.960 --> 00:27:33.909 align:start position:0% detailed storyboard. So you can imagine with<00:27:31.279> comprehensive<00:27:31.919> prompts,<00:27:32.320> a<00:27:32.559> proper<00:27:32.880> PRD 00:27:33.909 --> 00:27:33.919 align:start position:0% with comprehensive prompts, a proper PRD 00:27:33.919 --> 00:27:37.590 align:start position:0% with comprehensive prompts, a proper PRD and<00:27:34.240> custom<00:27:34.720> worked<00:27:35.520> assets.<00:27:36.640> This<00:27:36.880> workflow 00:27:37.590 --> 00:27:37.600 align:start position:0% and custom worked assets. This workflow 00:27:37.600 --> 00:27:40.070 align:start position:0% and custom worked assets. This workflow with<00:27:37.919> remote<00:27:38.559> can<00:27:38.880> actually<00:27:39.200> produce 00:27:40.070 --> 00:27:40.080 align:start position:0% with remote can actually produce 00:27:40.080 --> 00:27:42.230 align:start position:0% with remote can actually produce impressive<00:27:40.880> outputs.<00:27:41.520> And<00:27:41.679> again<00:27:41.919> what<00:27:42.159> we 00:27:42.230 --> 00:27:42.240 align:start position:0% impressive outputs. And again what we 00:27:42.240 --> 00:27:43.750 align:start position:0% impressive outputs. And again what we are<00:27:42.400> seeing<00:27:42.559> here<00:27:42.720> is<00:27:42.880> just<00:27:43.120> the<00:27:43.360> baseline 00:27:43.750 --> 00:27:43.760 align:start position:0% are seeing here is just the baseline 00:27:43.760 --> 00:27:46.710 align:start position:0% are seeing here is just the baseline quality<00:27:44.320> not<00:27:44.559> the<00:27:44.720> best<00:27:44.960> quality<00:27:45.360> yet.<00:27:46.480> Now 00:27:46.710 --> 00:27:46.720 align:start position:0% quality not the best quality yet. Now 00:27:46.720 --> 00:27:48.470 align:start position:0% quality not the best quality yet. Now that<00:27:46.880> we<00:27:47.039> are<00:27:47.200> happy<00:27:47.440> with<00:27:47.600> the<00:27:47.840> deliverables 00:27:48.470 --> 00:27:48.480 align:start position:0% that we are happy with the deliverables 00:27:48.480 --> 00:27:51.110 align:start position:0% that we are happy with the deliverables right<00:27:48.799> we<00:27:48.960> can<00:27:49.120> just<00:27:49.360> publish<00:27:49.760> them.<00:27:50.720> So<00:27:50.960> over 00:27:51.110 --> 00:27:51.120 align:start position:0% right we can just publish them. So over 00:27:51.120 --> 00:27:53.269 align:start position:0% right we can just publish them. So over here<00:27:51.279> in<00:27:51.520> superbase<00:27:52.080> we<00:27:52.320> can<00:27:52.559> already<00:27:52.960> see<00:27:53.120> the 00:27:53.269 --> 00:27:53.279 align:start position:0% here in superbase we can already see the 00:27:53.279 --> 00:27:55.750 align:start position:0% here in superbase we can already see the outputs<00:27:53.840> sitting<00:27:54.159> in<00:27:54.320> the<00:27:54.559> storage<00:27:54.880> bucket 00:27:55.750 --> 00:27:55.760 align:start position:0% outputs sitting in the storage bucket 00:27:55.760 --> 00:27:57.990 align:start position:0% outputs sitting in the storage bucket and<00:27:56.080> the<00:27:56.320> pipeline<00:27:56.880> actually<00:27:57.200> handled<00:27:57.679> the 00:27:57.990 --> 00:27:58.000 align:start position:0% and the pipeline actually handled the 00:27:58.000 --> 00:28:00.950 align:start position:0% and the pipeline actually handled the upload<00:27:58.480> automatically.<00:27:59.919> And<00:28:00.159> now<00:28:00.480> here<00:28:00.799> is 00:28:00.950 --> 00:28:00.960 align:start position:0% upload automatically. And now here is 00:28:00.960 --> 00:28:03.990 align:start position:0% upload automatically. And now here is our<00:28:01.360> publish<00:28:02.080> MD<00:28:02.480> file.<00:28:02.960> It<00:28:03.200> has<00:28:03.600> basically 00:28:03.990 --> 00:28:04.000 align:start position:0% our publish MD file. It has basically 00:28:04.000 --> 00:28:06.149 align:start position:0% our publish MD file. It has basically everything<00:28:04.320> in<00:28:04.559> one<00:28:04.799> place<00:28:05.279> like<00:28:05.600> public 00:28:06.149 --> 00:28:06.159 align:start position:0% everything in one place like public 00:28:06.159 --> 00:28:08.870 align:start position:0% everything in one place like public urls,<00:28:06.720> copy,<00:28:07.200> metadata,<00:28:08.240> scheduling 00:28:08.870 --> 00:28:08.880 align:start position:0% urls, copy, metadata, scheduling 00:28:08.880 --> 00:28:12.310 align:start position:0% urls, copy, metadata, scheduling details,<00:28:09.760> etc.<00:28:10.559> And<00:28:10.880> all<00:28:11.120> we<00:28:11.360> have<00:28:11.520> to<00:28:11.679> do<00:28:12.000> is 00:28:12.310 --> 00:28:12.320 align:start position:0% details, etc. And all we have to do is 00:28:12.320 --> 00:28:14.789 align:start position:0% details, etc. And all we have to do is to<00:28:12.559> just<00:28:12.880> approve<00:28:13.200> this<00:28:13.440> with<00:28:13.679> a<00:28:14.000> simple 00:28:14.789 --> 00:28:14.799 align:start position:0% to just approve this with a simple 00:28:14.799 --> 00:28:16.950 align:start position:0% to just approve this with a simple confirmation<00:28:15.360> prompt<00:28:15.840> just<00:28:16.080> like<00:28:16.320> this.<00:28:16.720> Now 00:28:16.950 --> 00:28:16.960 align:start position:0% confirmation prompt just like this. Now 00:28:16.960 --> 00:28:19.029 align:start position:0% confirmation prompt just like this. Now we<00:28:17.120> can<00:28:17.279> wait<00:28:17.440> for<00:28:17.679> claude<00:28:18.159> to<00:28:18.399> write<00:28:18.640> the 00:28:19.029 --> 00:28:19.039 align:start position:0% we can wait for claude to write the 00:28:19.039 --> 00:28:22.230 align:start position:0% we can wait for claude to write the upload<00:28:19.600> script<00:28:20.240> and<00:28:20.559> contact<00:28:21.200> the<00:28:21.600> YouTube 00:28:22.230 --> 00:28:22.240 align:start position:0% upload script and contact the YouTube 00:28:22.240 --> 00:28:25.830 align:start position:0% upload script and contact the YouTube and<00:28:22.559> meta<00:28:23.039> APIs<00:28:24.000> and<00:28:24.559> this<00:28:24.799> should<00:28:25.039> be<00:28:25.200> fast. 00:28:25.830 --> 00:28:25.840 align:start position:0% and meta APIs and this should be fast. 00:28:25.840 --> 00:28:28.310 align:start position:0% and meta APIs and this should be fast. Great,<00:28:26.159> this<00:28:26.320> is<00:28:26.480> done.<00:28:26.720> Here<00:28:27.200> is<00:28:27.440> the<00:28:27.760> publish 00:28:28.310 --> 00:28:28.320 align:start position:0% Great, this is done. Here is the publish 00:28:28.320 --> 00:28:31.669 align:start position:0% Great, this is done. Here is the publish confirmation.<00:28:29.440> And<00:28:30.320> there<00:28:30.559> it<00:28:30.720> is,<00:28:31.039> the 00:28:31.669 --> 00:28:31.679 align:start position:0% confirmation. And there it is, the 00:28:31.679 --> 00:28:33.830 align:start position:0% confirmation. And there it is, the YouTube<00:28:32.080> video<00:28:32.399> link.<00:28:32.960> You<00:28:33.120> can<00:28:33.279> just<00:28:33.440> open<00:28:33.679> it 00:28:33.830 --> 00:28:33.840 align:start position:0% YouTube video link. You can just open it 00:28:33.840 --> 00:28:36.549 align:start position:0% YouTube video link. You can just open it and<00:28:34.159> see<00:28:34.399> if<00:28:34.640> the<00:28:34.960> upload<00:28:35.840> went<00:28:36.080> through. 00:28:36.549 --> 00:28:36.559 align:start position:0% and see if the upload went through. 00:28:36.559 --> 00:28:38.630 align:start position:0% and see if the upload went through. Great,<00:28:36.880> the<00:28:37.120> video<00:28:37.360> is<00:28:37.520> live<00:28:37.919> on<00:28:38.159> our<00:28:38.320> test 00:28:38.630 --> 00:28:38.640 align:start position:0% Great, the video is live on our test 00:28:38.640 --> 00:28:42.149 align:start position:0% Great, the video is live on our test channel.<00:28:39.760> It<00:28:40.000> is<00:28:40.159> uploaded<00:28:40.640> and<00:28:40.880> playable. 00:28:42.149 --> 00:28:42.159 align:start position:0% channel. It is uploaded and playable. 00:28:42.159 --> 00:28:44.070 align:start position:0% channel. It is uploaded and playable. And<00:28:42.320> let's<00:28:42.640> check<00:28:43.039> Instagram.<00:28:43.600> And<00:28:43.760> again, 00:28:44.070 --> 00:28:44.080 align:start position:0% And let's check Instagram. And again, 00:28:44.080 --> 00:28:47.110 align:start position:0% And let's check Instagram. And again, this<00:28:44.320> is<00:28:44.399> our<00:28:44.640> test<00:28:44.880> account.<00:28:46.320> Great.<00:28:46.720> You<00:28:46.960> can 00:28:47.110 --> 00:28:47.120 align:start position:0% this is our test account. Great. You can 00:28:47.120 --> 00:28:49.990 align:start position:0% this is our test account. Great. You can see<00:28:47.520> the<00:28:47.919> posts<00:28:48.320> here,<00:28:48.960> including<00:28:49.360> some<00:28:49.679> from 00:28:49.990 --> 00:28:50.000 align:start position:0% see the posts here, including some from 00:28:50.000 --> 00:28:52.310 align:start position:0% see the posts here, including some from previous<00:28:50.399> projects<00:28:50.880> we<00:28:51.120> built<00:28:51.440> with<00:28:51.840> the<00:28:52.080> same 00:28:52.310 --> 00:28:52.320 align:start position:0% previous projects we built with the same 00:28:52.320 --> 00:28:54.870 align:start position:0% previous projects we built with the same setup.<00:28:52.799> And<00:28:52.960> now<00:28:53.279> you<00:28:53.520> can<00:28:53.679> notice<00:28:54.080> there<00:28:54.480> are 00:28:54.870 --> 00:28:54.880 align:start position:0% setup. And now you can notice there are 00:28:54.880 --> 00:28:57.909 align:start position:0% setup. And now you can notice there are four<00:28:55.360> copies<00:28:55.919> of<00:28:56.159> the<00:28:56.399> ad<00:28:56.720> uploaded<00:28:57.520> because 00:28:57.909 --> 00:28:57.919 align:start position:0% four copies of the ad uploaded because 00:28:57.919 --> 00:29:00.549 align:start position:0% four copies of the ad uploaded because we<00:28:58.240> specified<00:28:58.960> four<00:28:59.279> uploads<00:28:59.760> in<00:28:59.919> the<00:29:00.080> prompt 00:29:00.549 --> 00:29:00.559 align:start position:0% we specified four uploads in the prompt 00:29:00.559 --> 00:29:03.350 align:start position:0% we specified four uploads in the prompt but<00:29:00.880> only<00:29:01.200> asked<00:29:01.600> for<00:29:01.919> one<00:29:02.240> ad<00:29:02.480> to<00:29:02.720> be<00:29:02.799> created. 00:29:03.350 --> 00:29:03.360 align:start position:0% but only asked for one ad to be created. 00:29:03.360 --> 00:29:05.750 align:start position:0% but only asked for one ad to be created. So<00:29:03.600> the<00:29:03.840> agent<00:29:04.320> did<00:29:04.640> exactly<00:29:05.039> what<00:29:05.360> it<00:29:05.600> was 00:29:05.750 --> 00:29:05.760 align:start position:0% So the agent did exactly what it was 00:29:05.760 --> 00:29:08.870 align:start position:0% So the agent did exactly what it was told.<00:29:06.240> It<00:29:06.480> uploaded<00:29:07.039> the<00:29:07.440> one<00:29:08.000> ad<00:29:08.399> for<00:29:08.640> four 00:29:08.870 --> 00:29:08.880 align:start position:0% told. It uploaded the one ad for four 00:29:08.880 --> 00:29:11.669 align:start position:0% told. It uploaded the one ad for four times.<00:29:09.360> So<00:29:09.600> you<00:29:09.760> can<00:29:09.840> just<00:29:10.080> fix<00:29:10.320> this<00:29:10.559> by<00:29:11.039> just 00:29:11.669 --> 00:29:11.679 align:start position:0% times. So you can just fix this by just 00:29:11.679 --> 00:29:13.590 align:start position:0% times. So you can just fix this by just tweaking<00:29:12.080> your<00:29:12.399> prompt<00:29:12.880> to<00:29:13.120> match<00:29:13.360> your 00:29:13.590 --> 00:29:13.600 align:start position:0% tweaking your prompt to match your 00:29:13.600 --> 00:29:16.470 align:start position:0% tweaking your prompt to match your intentions.<00:29:14.399> So<00:29:14.640> to<00:29:14.880> recap,<00:29:15.440> from<00:29:15.679> a<00:29:16.080> single 00:29:16.470 --> 00:29:16.480 align:start position:0% intentions. So to recap, from a single 00:29:16.480 --> 00:29:19.430 align:start position:0% intentions. So to recap, from a single job<00:29:16.880> payload,<00:29:17.919> five<00:29:18.240> agents<00:29:18.720> actually<00:29:19.120> worked 00:29:19.430 --> 00:29:19.440 align:start position:0% job payload, five agents actually worked 00:29:19.440 --> 00:29:22.310 align:start position:0% job payload, five agents actually worked in<00:29:19.840> sequence<00:29:20.720> to<00:29:21.039> produce<00:29:21.520> a<00:29:21.919> research 00:29:22.310 --> 00:29:22.320 align:start position:0% in sequence to produce a research 00:29:22.320 --> 00:29:25.590 align:start position:0% in sequence to produce a research report,<00:29:22.960> a<00:29:23.279> static<00:29:23.679> ad,<00:29:24.240> a<00:29:24.480> video<00:29:24.799> ad, 00:29:25.590 --> 00:29:25.600 align:start position:0% report, a static ad, a video ad, 00:29:25.600 --> 00:29:28.950 align:start position:0% report, a static ad, a video ad, platform<00:29:26.080> specific<00:29:26.640> copy,<00:29:27.520> and<00:29:28.000> a<00:29:28.320> scheduled 00:29:28.950 --> 00:29:28.960 align:start position:0% platform specific copy, and a scheduled 00:29:28.960 --> 00:29:31.590 align:start position:0% platform specific copy, and a scheduled upload<00:29:29.279> to<00:29:29.520> YouTube<00:29:29.919> and<00:29:30.159> Instagram.<00:29:31.279> All 00:29:31.590 --> 00:29:31.600 align:start position:0% upload to YouTube and Instagram. All 00:29:31.600 --> 00:29:34.950 align:start position:0% upload to YouTube and Instagram. All connected<00:29:32.960> or<00:29:33.360> automated.<00:29:34.159> And<00:29:34.320> this<00:29:34.559> is<00:29:34.720> what 00:29:34.950 --> 00:29:34.960 align:start position:0% connected or automated. And this is what 00:29:34.960 --> 00:29:37.029 align:start position:0% connected or automated. And this is what it<00:29:35.120> looks<00:29:35.440> like<00:29:35.679> when<00:29:36.000> your<00:29:36.320> marketing<00:29:36.720> team 00:29:37.029 --> 00:29:37.039 align:start position:0% it looks like when your marketing team 00:29:37.039 --> 00:29:40.149 align:start position:0% it looks like when your marketing team actually<00:29:37.520> runs<00:29:38.240> on<00:29:38.640> skills. 00:29:40.149 --> 00:29:40.159 align:start position:0% actually runs on skills. 00:29:40.159 --> 00:29:42.070 align:start position:0% actually runs on skills. All<00:29:40.240> right.<00:29:40.480> So<00:29:40.640> that's<00:29:40.960> your<00:29:41.200> full<00:29:41.520> content 00:29:42.070 --> 00:29:42.080 align:start position:0% All right. So that's your full content 00:29:42.080 --> 00:29:44.470 align:start position:0% All right. So that's your full content marketing<00:29:42.480> team<00:29:42.960> running<00:29:43.360> on<00:29:43.679> autopilot 00:29:44.470 --> 00:29:44.480 align:start position:0% marketing team running on autopilot 00:29:44.480 --> 00:29:48.630 align:start position:0% marketing team running on autopilot inside<00:29:44.960> CL<00:29:45.360> code.<00:29:46.240> Research,<00:29:47.120> video,<00:29:47.919> ads, 00:29:48.630 --> 00:29:48.640 align:start position:0% inside CL code. Research, video, ads, 00:29:48.640 --> 00:29:51.830 align:start position:0% inside CL code. Research, video, ads, copy,<00:29:49.360> scheduling,<00:29:50.399> five<00:29:50.720> agents,<00:29:51.520> one 00:29:51.830 --> 00:29:51.840 align:start position:0% copy, scheduling, five agents, one 00:29:51.840 --> 00:29:53.830 align:start position:0% copy, scheduling, five agents, one single<00:29:52.159> workflow.<00:29:52.720> And<00:29:52.880> now<00:29:53.120> if<00:29:53.279> you<00:29:53.440> want<00:29:53.600> the 00:29:53.830 --> 00:29:53.840 align:start position:0% single workflow. And now if you want the 00:29:53.840 --> 00:29:55.830 align:start position:0% single workflow. And now if you want the exact<00:29:54.320> template<00:29:54.720> and<00:29:54.960> workflow<00:29:55.360> we<00:29:55.600> used 00:29:55.830 --> 00:29:55.840 align:start position:0% exact template and workflow we used 00:29:55.840 --> 00:29:58.310 align:start position:0% exact template and workflow we used today,<00:29:56.720> plus<00:29:57.039> if<00:29:57.200> you<00:29:57.360> want<00:29:57.520> to<00:29:57.679> have<00:29:57.840> the<00:29:58.000> AI 00:29:58.310 --> 00:29:58.320 align:start position:0% today, plus if you want to have the AI 00:29:58.320 --> 00:30:00.310 align:start position:0% today, plus if you want to have the AI website<00:29:58.720> design<00:29:59.039> course<00:29:59.360> and<00:29:59.600> 101<00:30:00.080> tech 00:30:00.310 --> 00:30:00.320 align:start position:0% website design course and 101 tech 00:30:00.320 --> 00:30:03.029 align:start position:0% website design course and 101 tech support,<00:30:01.120> feel<00:30:01.360> free<00:30:01.600> to<00:30:01.919> join<00:30:02.159> our<00:30:02.480> any<00:30:02.720> no 00:30:03.029 --> 00:30:03.039 align:start position:0% support, feel free to join our any no 00:30:03.039 --> 00:30:05.269 align:start position:0% support, feel free to join our any no code<00:30:03.279> premium<00:30:03.760> community.<00:30:04.720> You<00:30:04.880> can<00:30:04.960> find<00:30:05.120> a 00:30:05.269 --> 00:30:05.279 align:start position:0% code premium community. You can find a 00:30:05.279 --> 00:30:06.870 align:start position:0% code premium community. You can find a link<00:30:05.440> in<00:30:05.679> the<00:30:05.840> description<00:30:06.240> and<00:30:06.480> drop<00:30:06.640> a 00:30:06.870 --> 00:30:06.880 align:start position:0% link in the description and drop a 00:30:06.880 --> 00:30:08.789 align:start position:0% link in the description and drop a comment<00:30:07.120> below<00:30:07.279> and<00:30:07.600> tell<00:30:07.760> me<00:30:08.000> which<00:30:08.399> agent 00:30:08.789 --> 00:30:08.799 align:start position:0% comment below and tell me which agent 00:30:08.799 --> 00:30:12.070 align:start position:0% comment below and tell me which agent that<00:30:09.039> you<00:30:09.279> are<00:30:09.679> most<00:30:10.240> excited<00:30:10.640> to<00:30:10.880> try<00:30:11.200> first. 00:30:12.070 --> 00:30:12.080 align:start position:0% that you are most excited to try first. 00:30:12.080 --> 00:30:13.909 align:start position:0% that you are most excited to try first. I<00:30:12.399> read<00:30:12.640> every<00:30:12.960> single<00:30:13.360> one<00:30:13.520> of<00:30:13.679> your 00:30:13.909 --> 00:30:13.919 align:start position:0% I read every single one of your 00:30:13.919 --> 00:30:15.669 align:start position:0% I read every single one of your comments.<00:30:14.399> And<00:30:14.640> also,<00:30:14.880> if<00:30:15.120> you<00:30:15.279> found<00:30:15.440> this 00:30:15.669 --> 00:30:15.679 align:start position:0% comments. And also, if you found this 00:30:15.679 --> 00:30:17.669 align:start position:0% comments. And also, if you found this video<00:30:15.919> helpful,<00:30:16.720> hit<00:30:16.960> the<00:30:17.120> like<00:30:17.360> and 00:30:17.669 --> 00:30:17.679 align:start position:0% video helpful, hit the like and 00:30:17.679 --> 00:30:19.750 align:start position:0% video helpful, hit the like and subscribe<00:30:18.080> button<00:30:18.640> for<00:30:18.880> more<00:30:19.200> video<00:30:19.520> like 00:30:19.750 --> 00:30:19.760 align:start position:0% subscribe button for more video like 00:30:19.760 --> 00:30:21.909 align:start position:0% subscribe button for more video like this<00:30:19.919> in<00:30:20.159> the<00:30:20.240> future.<00:30:20.960> I'll<00:30:21.279> see<00:30:21.360> you<00:30:21.520> in<00:30:21.679> our 00:30:21.909 --> 00:30:21.919 align:start position:0% this in the future. I'll see you in our 00:30:21.919 --> 00:30:24.399 align:start position:0% this in the future. I'll see you in our next<00:30:22.080> one.