Loading video...

Video Failed to Load

There was a problem loading this video. This could be due to a temporary network issue or the video might be unavailable.

The PMs screenshotting Claude Code outputs and saying "fix the alignment" five times are playing QA on a system that can QA itself. The default workflow for anything visual: generate a slide, screenshot it, give feedback, screenshot again, give more feedback. Five rounds of you being the quality layer... between Claude and the final output. A Puppeteer skill eliminates that loop completely. You embed a screenshot tool directly in the skill file. Claude renders HTML, captures its own output, measures whether text overflows the page dimensions, and iterates three times before you ever see it. Pixel-level self-correction with zero human review. One detail that stuck with me: a recent Google paper showed that literally running the same prompt twice improves output quality. The serious Claude Code builders are encoding that into every skill. Generate, re-validate against the original rules, generate again. Quality compounds automatically with each pass. This is the builder-validator pattern. The AI does the work, then the AI audits the work against the same spec. You stop functioning as the manual checkpoint. The setup cost is one skill file with Puppeteer embedded. The return is every visual task from that point forward shipping at production quality without a screenshot loop. Build the check into the system. Stop being the system.show more

Aakash Gupta

257,744 subscribers

61,435 views • 3 months ago •via X (Twitter)

News & Politics Science & Technology

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

I tested 4 AI tools with one specific prompt. The Results: • Grok & Claude: Provided high-quality research and text. However, the output remained a document. No slide design was provided. • Gemini: Organized the content into a structured outline, but the final layout lacked visual hierarchy. • Converted the prompt directly into a formatted deck. While others generate the content, builds the presentation. It handles the design, layouts, and visual flow automatically. If you need a finished file rather than a text draft, the choice is clear.

I tested 4 AI tools with one specific prompt. The Results: • Grok & Claude: Provided high-quality research and text. However, the output remained a document. No slide design was provided. • Gemini: Organized the content into a structured outline, but the final layout lacked visual hierarchy. • Converted the prompt directly into a formatted deck. While others generate the content, builds the presentation. It handles the design, layouts, and visual flow automatically. If you need a finished file rather than a text draft, the choice is clear.

Vinay Bharambe

39,524 views • 4 months ago

My favorite way of interacting with Claude Code is to have it generate static HTML files as outputs (reports, explorations, code structure, mockups etc.) I wanted to iterate on the file by commenting in browser and having Claude update the output live. So, I built this Claude Skill👇 How it works: - Install Claude Code skill (ask it to clone repo) - Build an HTML page for anything (e.g. research coding agents and generate HTML report) - Ask it to make the page interactive That's it. CC will launch a localhost server and allow you to then leave comments on the page itself and once it updates, will give you a tour of changes. It's like Google Docs kind of comments/iteration but for HTML pages.

My favorite way of interacting with Claude Code is to have it generate static HTML files as outputs (reports, explorations, code structure, mockups etc.) I wanted to iterate on the file by commenting in browser and having Claude update the output live. So, I built this Claude Skill👇 How it works: - Install Claude Code skill (ask it to clone repo) - Build an HTML page for anything (e.g. research coding agents and generate HTML report) - Ask it to make the page interactive That's it. CC will launch a localhost server and allow you to then leave comments on the page itself and once it updates, will give you a tour of changes. It's like Google Docs kind of comments/iteration but for HTML pages.

Paras Chopra

215,021 views • 1 month ago

THIS IS HOW A SENIOR ENGINEER ACTUALLY SCALES THEMSELVES WITH CLAUDE CODE the biggest change with AI isn't coding faster. it's where you actually spend your time now. more detailed prompts, more code review, more planning, less typing, etc. here's the workflow: this guy has been shipping code since the days of cgi and perl. he uses a compound engineering plugin that runs 5 separate agents on every task. one brainstorms, one plans the technical implementation, one executes, one reviews, one checks different verticals. every step is documented in markdown files. it's slow and way more waiting. but the output quality is way higher because each agent is focused on one thing. then the REAL multiplier is in git worktrees if Claude Code made you 10x faster, worktrees multiplies that again depending on how many agents you can manage in parallel his team runs 4-8 Claude Code sessions at the same time across different worktrees with each one working on a separate task. the skill is managing multiple AI agents in parallel without losing track, that's the next evolution of engineering

THIS IS HOW A SENIOR ENGINEER ACTUALLY SCALES THEMSELVES WITH CLAUDE CODE the biggest change with AI isn't coding faster. it's where you actually spend your time now. more detailed prompts, more code review, more planning, less typing, etc. here's the workflow: this guy has been shipping code since the days of cgi and perl. he uses a compound engineering plugin that runs 5 separate agents on every task. one brainstorms, one plans the technical implementation, one executes, one reviews, one checks different verticals. every step is documented in markdown files. it's slow and way more waiting. but the output quality is way higher because each agent is focused on one thing. then the REAL multiplier is in git worktrees if Claude Code made you 10x faster, worktrees multiplies that again depending on how many agents you can manage in parallel his team runs 4-8 Claude Code sessions at the same time across different worktrees with each one working on a separate task. the skill is managing multiple AI agents in parallel without losing track, that's the next evolution of engineering

Om Patel

159,179 views • 3 months ago

REAL ESTATE PEOPLE WILL HATE HIM FOR THIS. HE BUILT A CLAUDE AGENT THAT TURNS ANY LISTING INTO A SELLABLE VIDEO ON ITS OWN Playbook: connect Claude to a video generator, paste a listing, get a cinematic tour of every room, sell it to the agent But typing the prompt for every listing doesn't scale. He turned it into a skill his Claude runs on its own Here's how to build the automated version: 1. Connect the video engine once. In Claude, go to Customize, Connectors, Add Custom Connector, name it Higgsfield, and paste the server URL from higgsfield. ai/mcp. Authenticate through your account. No API keys. Now Claude can generate video straight from chat 2. Turn the workflow into a skill. Instead of pasting the same prompt every time, have Claude build a skill. Tell it: "Create a skill called listing-to-video. When I give it a listing URL, scrape the room photos, generate a cinematic clip of each room with Higgsfield, and save them to a folder." Now the whole process is one command, not a wall of text 3. Let the agent run the listing. Hand it a URL and say "run listing-to-video on this." It pulls the photos, fires each room through the video model, and brings the clips back. You wrote the prompt once, inside the skill. You never write it again 4. Stitch and deliver. Drop the clips together into one tour. Send a free sample to the listing's agent, then charge per video or a monthly rate for ongoing listings 5. Scale it with your team. Add a skill that drafts the outreach email and one that builds a simple landing page for the agent. Now one operator runs sourcing, production, and pitching from a single Claude session The edge isn't generating one video. It's building the skill once so every future listing runs itself Bookmark this

REAL ESTATE PEOPLE WILL HATE HIM FOR THIS. HE BUILT A CLAUDE AGENT THAT TURNS ANY LISTING INTO A SELLABLE VIDEO ON ITS OWN Playbook: connect Claude to a video generator, paste a listing, get a cinematic tour of every room, sell it to the agent But typing the prompt for every listing doesn't scale. He turned it into a skill his Claude runs on its own Here's how to build the automated version: 1. Connect the video engine once. In Claude, go to Customize, Connectors, Add Custom Connector, name it Higgsfield, and paste the server URL from higgsfield. ai/mcp. Authenticate through your account. No API keys. Now Claude can generate video straight from chat 2. Turn the workflow into a skill. Instead of pasting the same prompt every time, have Claude build a skill. Tell it: "Create a skill called listing-to-video. When I give it a listing URL, scrape the room photos, generate a cinematic clip of each room with Higgsfield, and save them to a folder." Now the whole process is one command, not a wall of text 3. Let the agent run the listing. Hand it a URL and say "run listing-to-video on this." It pulls the photos, fires each room through the video model, and brings the clips back. You wrote the prompt once, inside the skill. You never write it again 4. Stitch and deliver. Drop the clips together into one tour. Send a free sample to the listing's agent, then charge per video or a monthly rate for ongoing listings 5. Scale it with your team. Add a skill that drafts the outreach email and one that builds a simple landing page for the agent. Now one operator runs sourcing, production, and pitching from a single Claude session The edge isn't generating one video. It's building the skill once so every future listing runs itself Bookmark this

Yarchi

54,763 views • 1 month ago

I just built a self-improving second brain in Claude Code 🤯 A brain that runs your brand: every tool reads from it, it's wired to your live data, and it gets smarter every week. All running on the Claude Agent SDK. Perfect for DTC brands and agencies whose AI output sounds generic because every new chat starts from zero. If you're re-explaining your brand to AI every single time — re-pasting the voice guidelines, re-describing the customer you've described a hundred times, re-uploading the same positioning doc you uploaded yesterday, and still editing for an hour to strip out the generic phrasing... A brand second brain fixes the entire loop: → Build 3 foundation files once: brand DNA, voice, and customer → Every skill you create reads from them automatically → Wire in live data — your ad account, competitor ads, customer reviews → A weekly routine refreshes the brain with what's actually working → Every output comes back on-brand on the first pass No re-briefing AI on every chat. No hour of editing to undo generic phrasing. No brain that goes stale the week after you build it. What a second brain gives you: → The exact 3-file foundation that runs the whole system → The skill structure that makes every tool brand-aware by default → The live-data wiring that keeps it grounded in reality → The weekly self-improvement loop that keeps it sharp → The cold-start sequence to stand it all up from zero Built 100% in Claude Code. I put together the full playbook with the file structure, the wiring, and the exact setup. Want it for free? > Like this post > Comment "BRAIN" And I'll send it over (must be following so I can DM)

Mike Futia

17,713 views • 27 days ago

Anthropic team: "Most people are prompting Claude wrong" They dropped a 24-minute workshop on how Claude prompts are actually built Free From the people who built the model There are 6 elements in a real Claude prompt Most people use 1 That is why their outputs feel generic Better wording is not enough Claude rewards structure, context, examples, constraints, and feedback I watched it twice Then built a Claude Skill that applies all 6 automatically You write normally The skill structures the prompt before Claude sees it Bookmark and watch this Then save the setup below

Anthropic team: "Most people are prompting Claude wrong" They dropped a 24-minute workshop on how Claude prompts are actually built Free From the people who built the model There are 6 elements in a real Claude prompt Most people use 1 That is why their outputs feel generic Better wording is not enough Claude rewards structure, context, examples, constraints, and feedback I watched it twice Then built a Claude Skill that applies all 6 automatically You write normally The skill structures the prompt before Claude sees it Bookmark and watch this Then save the setup below

rari

15,655 views • 20 days ago

THIS GUY SPENT 5 MINUTES SETTING UP A $20 CLAUDE WORKSPACE AND TURNED 30 MINUTES OF DAILY PROMPT CHAOS INTO A SYSTEM Most people open Claude, type 1 messy prompt, rewrite it 10 times, get the same generic answer and call the model “bad.” He opens Claude Cowork, adds the project rules, past context, working files, examples, decisions and a clean place for the model to remember what it is doing. Same Claude. Same $20 tool. Completely different output. The funny part is there is no magic prompt here. No secret template. No “10x Claude” trick. Just the boring layer Karpathy keeps pointing at: context, memory and structure before output. A setup like this can save 30 minutes a day, which is 15 hours a month. If you use Claude for client work at $50 to $100/hour, that is $750 to $1,500/month in time you stop burning on repeated prompts. The model is real. The output is real. The edge is in not making Claude start from zero every single time.

THIS GUY SPENT 5 MINUTES SETTING UP A $20 CLAUDE WORKSPACE AND TURNED 30 MINUTES OF DAILY PROMPT CHAOS INTO A SYSTEM Most people open Claude, type 1 messy prompt, rewrite it 10 times, get the same generic answer and call the model “bad.” He opens Claude Cowork, adds the project rules, past context, working files, examples, decisions and a clean place for the model to remember what it is doing. Same Claude. Same $20 tool. Completely different output. The funny part is there is no magic prompt here. No secret template. No “10x Claude” trick. Just the boring layer Karpathy keeps pointing at: context, memory and structure before output. A setup like this can save 30 minutes a day, which is 15 hours a month. If you use Claude for client work at $50 to $100/hour, that is $750 to $1,500/month in time you stop burning on repeated prompts. The model is real. The output is real. The edge is in not making Claude start from zero every single time.

Gipp 🦅

14,871 views • 1 month ago

Claude Skills are a cheat code for DTC creative teams 🤯 One setup, reusable forever. Claude automatically follows your exact creative process — briefs, hooks, ad copy, research — without you explaining anything twice. Perfect for e-comm brands and agencies who are using Claude for creative work but wasting time re-explaining context every single conversation. Here's the problem: You open Claude: you paste in your brand guidelines, explain your brief format, write the copy, you close the chat. Next day, you do it all over again. Every conversation starts from zero. You're burning 20 minutes on setup before you even get to the actual work. Claude Skills fix this: → Write your creative process once as a Skill (a simple markdown file) → Claude reads it automatically whenever the task comes up → Skills compose — research triggers the research Skill, briefs trigger the brief Skill, copy triggers the copy Skill → All in one conversation, all building on each other → Share across your team so everyone gets the same quality output No re-explaining your brand voice. No pasting the same context every chat. No siloed projects that don't talk to each other. What's in the playbook: → The full architecture (how Skills trigger, chain, and compose) → 5 ready-to-use Skill templates built for DTC and agency creative teams → Step-by-step setup from zero to working Skills → How to write instructions that produce consistent output every time → The composability framework for running multi-step creative workflows in one conversation I put together the complete Claude Skills Playbook for DTC brands and creative agencies. Want it for free? >Like this post >Comment "SKILLS" And I'll send it over (must be following so I can DM)

Mike Futia

31,891 views • 4 months ago

The gap between a PM getting AI slop from Claude Code and one getting 10x output is about one hour of file structure. Three folders. > A knowledge folder with static context: who you work with, what each stakeholder cares about, reference material that rarely changes. > A projects folder where every task accumulates research, drafts, and artifacts that load instantly into your next session. > And a people folder that auto-updates from meeting transcripts through Granola's MCP. The people folder is the part that compounds. Build a skill that pulls what each person said in your last meeting, what they pushed back on, what they committed to. Now when you draft a message to your VP of Engineering, Claude Code already knows their communication preferences from 30 real conversations. That's context no prompt can replicate. Carl walked through this system on the episode and the compounding math stuck with me. Day 1, Claude Code knows nothing about your work. Day 30, it knows your stakeholders, your project history, your patterns. Day 90, it's surfacing connections across your work you haven't consciously noticed. Then layer on skills. A standup command that pulls from GitHub, Linear, your calendar, and your task folder in one shot. Website traffic compared against your LinkedIn posts this week. Analyses that would be impossible clicking between individual UIs, running before your first meeting. One hour of setup. Compounding returns every day after. The PMs typing prompts into a blank terminal and the PMs who built the operating system around it are already producing completely different categories of work. Build the operating system.

The gap between a PM getting AI slop from Claude Code and one getting 10x output is about one hour of file structure. Three folders. > A knowledge folder with static context: who you work with, what each stakeholder cares about, reference material that rarely changes. > A projects folder where every task accumulates research, drafts, and artifacts that load instantly into your next session. > And a people folder that auto-updates from meeting transcripts through Granola's MCP. The people folder is the part that compounds. Build a skill that pulls what each person said in your last meeting, what they pushed back on, what they committed to. Now when you draft a message to your VP of Engineering, Claude Code already knows their communication preferences from 30 real conversations. That's context no prompt can replicate. Carl walked through this system on the episode and the compounding math stuck with me. Day 1, Claude Code knows nothing about your work. Day 30, it knows your stakeholders, your project history, your patterns. Day 90, it's surfacing connections across your work you haven't consciously noticed. Then layer on skills. A standup command that pulls from GitHub, Linear, your calendar, and your task folder in one shot. Website traffic compared against your LinkedIn posts this week. Analyses that would be impossible clicking between individual UIs, running before your first meeting. One hour of setup. Compounding returns every day after. The PMs typing prompts into a blank terminal and the PMs who built the operating system around it are already producing completely different categories of work. Build the operating system.

Aakash Gupta

82,865 views • 3 months ago

I created a skill that improves the quality of goal runs for both Codex and Claude Code: It's called the Goal Ledger, and lets agents track the progress of their goal in a HTML file that you can view. Minimal, yet VERY powerful for long running goal runs! Git Link Below 👇🔗

I created a skill that improves the quality of goal runs for both Codex and Claude Code: It's called the Goal Ledger, and lets agents track the progress of their goal in a HTML file that you can view. Minimal, yet VERY powerful for long running goal runs! Git Link Below 👇🔗

BOOTOSHI 👑

14,766 views • 2 months ago

Most people use Claude Code like a chatbot, then wonder why it forgets everything by Tuesday. The ones quietly building $10K AI workflows give it a second brain instead, and it’s free. It’s called Obsidian. You download it, point it at one folder on your computer, and that folder becomes a vault. Every note inside it is now something Claude Code can read end to end. Open Claude in that folder and it’s connected, that simple. The trick isn’t the tool, it’s the map. 3 folders, that’s the whole system. Raw, you dump everything here. Notes, transcripts, screenshots, half thoughts, zero structure. Wiki, Claude reads the raw pile and writes clean Wikipedia style articles about it, structured, searchable, permanent. Output, when you want a deliverable, a PDF, a slide deck, a script, it pulls from the wiki and ships it. Most people skip the wiki layer and feed Claude a junk drawer of 400 files, then blame the model when the answers are garbage. The model isn’t the problem, your folder is. Give it a path it can follow and it finds anything in 1 second, give it chaos and it guesses. You don’t even have to design the structure yourself. Open the vault, tell Claude to build a file system that fits your work, and watch it organize your entire brain in one prompt. Free tool, 3 folders, a second brain that compounds while you sleep. The people falling behind are still copy pasting into a chat window.

Most people use Claude Code like a chatbot, then wonder why it forgets everything by Tuesday. The ones quietly building $10K AI workflows give it a second brain instead, and it’s free. It’s called Obsidian. You download it, point it at one folder on your computer, and that folder becomes a vault. Every note inside it is now something Claude Code can read end to end. Open Claude in that folder and it’s connected, that simple. The trick isn’t the tool, it’s the map. 3 folders, that’s the whole system. Raw, you dump everything here. Notes, transcripts, screenshots, half thoughts, zero structure. Wiki, Claude reads the raw pile and writes clean Wikipedia style articles about it, structured, searchable, permanent. Output, when you want a deliverable, a PDF, a slide deck, a script, it pulls from the wiki and ships it. Most people skip the wiki layer and feed Claude a junk drawer of 400 files, then blame the model when the answers are garbage. The model isn’t the problem, your folder is. Give it a path it can follow and it finds anything in 1 second, give it chaos and it guesses. You don’t even have to design the structure yourself. Open the vault, tell Claude to build a file system that fits your work, and watch it organize your entire brain in one prompt. Free tool, 3 folders, a second brain that compounds while you sleep. The people falling behind are still copy pasting into a chat window.

West Lord

32,731 views • 27 days ago

$Hermes + Claude + Higgsfield MCP + ViralBuilder = 💰💰💰 Four tools. One prompt chain. Hook to finished video in 10 minutes. I built a Claude skill that writes shot-by-shot Higgsfield prompts from a single creative brief. ViralBuilder tells you what's winning. The skill turns it into a production-ready prompt. Higgsfield renders it. No creative director. No guessing. No separate tools. Here is the setup: Higgsfield MCP → Open Claude Code → Settings → Connectors → Enter: → Connect your account Hermes → The agent layer running underneath Claude Code → It holds your skills, crons, memory, and routing rules → When you prompt Claude, Hermes feeds it the context it needs ViralBuilder (like Gethookd) → The winning ecom video database → Scrapes top performing ecom videos across platforms → Claude reads the data and extracts what styles, hooks, and formats are actually scaling The skill: video-prompt-builder → Installed inside Claude via Hermes → Takes a creative brief and outputs a full shot-by-shot prompt → Covers camera work, effects, transitions, pacing, and energy arc → Every output is structured for Higgsfield to render without ambiguity No switching apps. No export steps. Everything runs from one place. ▸ FIND WINNING CREATIVE ANGLES ViralBuilder tells you what the market already validated. Claude reads it and extracts the pattern. Prompts to run: "Search ViralBuilder for the top performing ecom videos in [niche] over the last 21 days. Extract the 3 dominant hook styles and rank by view velocity." "Pull the winning video formats in [niche] from ViralBuilder. Which opening 3 seconds appears most across videos spending over $10k?" "Find what video style is scaling right now in [niche] for the US market. UGC, talking head, or product demo. Filter for videos with over 1M views." "Pull the last 30 days of viral ecom hooks in [niche] from ViralBuilder. Cluster by emotional trigger. Which cluster has the most longevity?" You are not guessing at angles. You are reading what the market already spent money validating. ▸ BUILD THE PROMPT WITH THE SKILL This is where the video-prompt-builder skill takes over. You give Claude the winning angle. The skill outputs a complete shot-by-shot prompt with effects, transitions, pacing, and energy arc ready to fire into Higgsfield. Prompts to run: "Use the video-prompt-builder skill. Brief: 15-second UGC ad for [product] in [niche]. Hook style: [style from ViralBuilder]. Tone: direct to camera, US English. Output the full shot-by-shot effects timeline, effects inventory, density map, and energy arc." "Use the video-prompt-builder skill. The dominant hook in [niche] this week is [hook]. Build a 10-second product video prompt that opens with a speed ramp into a close-up product reveal. Include a signature visual effect and a low-density CTA landing." "Use the video-prompt-builder skill. Brief: replicate the pacing and energy of a [style description] video for [product]. Target duration: 20 seconds. Output all four sections. Then generate the video with Higgsfield using the shot-by-shot prompt." The skill outputs four sections every time: → Shot-by-shot effects timeline with camera, movement, and transitions per shot → Master effects inventory showing every technique used and where → Effects density map showing high, medium, and low intensity across the timeline → Energy arc describing how the video opens, builds, and lands That output goes directly into Higgsfield. No rewriting. No translating. ▸ GENERATE THE CREATIVE Claude writes the brief via the skill. Higgsfield MCP builds the video. Both happen in the same session. Prompts to run: "Use the video-prompt-builder skill to write a 15-second UGC prompt for [product]. Hook in the first 3 seconds, speed ramp into product reveal, slow-motion CTA landing. Then generate with Higgsfield in 9:16 format." "Build 3 prompt variations on this winning angle: [angle]. Each variation opens with a different effect — speed ramp, digital zoom, whip pan. Use the video-prompt-builder skill for each. Then generate all three with Higgsfield." "Use the video-prompt-builder skill. Brief: problem-solution ad for [product], 20 seconds, US market. Problem shot at high density, product reveal at medium, result and CTA at low. Generate with Higgsfield in 9:16." No separate tool. No file transfer. The video comes back in the same thread. ▸ CHAIN THE WHOLE STACK One prompt. All four tools firing together. "You are my ad creative director. Hermes has loaded my brand context. Pull the top performing video style in [niche] from ViralBuilder this week. Use the video-prompt-builder skill to write a full shot-by-shot prompt for [product] that replicates that style — 20 seconds, 9:16, US market, hook in the first 3 seconds. Output the effects timeline, inventory, density map, and energy arc. Then generate the video with Higgsfield." That single prompt replaces a half-day of production. The math before this stack: Brief: 30 minutes Script: 1 hour Creative production: 2 to 3 hours Agency or freelancer cost: $500 to $2,000 per creative With this stack: Hook to finished creative: 10 minutes Cost per creative: tool subscription, a fraction of agency rate 5 product tests in the time it used to take to brief one Bad product tests are where US ad budget disappears. $600 to $1,500 per failed test, before you even know if the angle works. This stack shows you what the market already validated before you spend a dollar on production. Hermes = your context layer. Brand, goals, past performance. Claude is always informed. ViralBuilder = your winning video database. See exactly what styles, hooks, and formats are scaling before you produce anything. video-prompt-builder skill = the translation layer. Turns a creative brief into a structured, production-ready Higgsfield prompt every time. Claude = the brain. Reads the market, writes the brief, chains the tools. Higgsfield MCP = the output. Video generated directly from the prompt. No export step. Four tools. One session. 10 minutes. Comment + RT "STACK" and I'll DM you the full workflow + the video-prompt-builder skill file.$

Hermes + Claude + Higgsfield MCP + ViralBuilder = 💰💰💰 Four tools. One prompt chain. Hook to finished video in 10 minutes. I built a Claude skill that writes shot-by-shot Higgsfield prompts from a single creative brief. ViralBuilder tells you what's winning. The skill turns it into a production-ready prompt. Higgsfield renders it. No creative director. No guessing. No separate tools. Here is the setup: Higgsfield MCP → Open Claude Code → Settings → Connectors → Enter: → Connect your account Hermes → The agent layer running underneath Claude Code → It holds your skills, crons, memory, and routing rules → When you prompt Claude, Hermes feeds it the context it needs ViralBuilder (like Gethookd) → The winning ecom video database → Scrapes top performing ecom videos across platforms → Claude reads the data and extracts what styles, hooks, and formats are actually scaling The skill: video-prompt-builder → Installed inside Claude via Hermes → Takes a creative brief and outputs a full shot-by-shot prompt → Covers camera work, effects, transitions, pacing, and energy arc → Every output is structured for Higgsfield to render without ambiguity No switching apps. No export steps. Everything runs from one place. ▸ FIND WINNING CREATIVE ANGLES ViralBuilder tells you what the market already validated. Claude reads it and extracts the pattern. Prompts to run: "Search ViralBuilder for the top performing ecom videos in [niche] over the last 21 days. Extract the 3 dominant hook styles and rank by view velocity." "Pull the winning video formats in [niche] from ViralBuilder. Which opening 3 seconds appears most across videos spending over $10k?" "Find what video style is scaling right now in [niche] for the US market. UGC, talking head, or product demo. Filter for videos with over 1M views." "Pull the last 30 days of viral ecom hooks in [niche] from ViralBuilder. Cluster by emotional trigger. Which cluster has the most longevity?" You are not guessing at angles. You are reading what the market already spent money validating. ▸ BUILD THE PROMPT WITH THE SKILL This is where the video-prompt-builder skill takes over. You give Claude the winning angle. The skill outputs a complete shot-by-shot prompt with effects, transitions, pacing, and energy arc ready to fire into Higgsfield. Prompts to run: "Use the video-prompt-builder skill. Brief: 15-second UGC ad for [product] in [niche]. Hook style: [style from ViralBuilder]. Tone: direct to camera, US English. Output the full shot-by-shot effects timeline, effects inventory, density map, and energy arc." "Use the video-prompt-builder skill. The dominant hook in [niche] this week is [hook]. Build a 10-second product video prompt that opens with a speed ramp into a close-up product reveal. Include a signature visual effect and a low-density CTA landing." "Use the video-prompt-builder skill. Brief: replicate the pacing and energy of a [style description] video for [product]. Target duration: 20 seconds. Output all four sections. Then generate the video with Higgsfield using the shot-by-shot prompt." The skill outputs four sections every time: → Shot-by-shot effects timeline with camera, movement, and transitions per shot → Master effects inventory showing every technique used and where → Effects density map showing high, medium, and low intensity across the timeline → Energy arc describing how the video opens, builds, and lands That output goes directly into Higgsfield. No rewriting. No translating. ▸ GENERATE THE CREATIVE Claude writes the brief via the skill. Higgsfield MCP builds the video. Both happen in the same session. Prompts to run: "Use the video-prompt-builder skill to write a 15-second UGC prompt for [product]. Hook in the first 3 seconds, speed ramp into product reveal, slow-motion CTA landing. Then generate with Higgsfield in 9:16 format." "Build 3 prompt variations on this winning angle: [angle]. Each variation opens with a different effect — speed ramp, digital zoom, whip pan. Use the video-prompt-builder skill for each. Then generate all three with Higgsfield." "Use the video-prompt-builder skill. Brief: problem-solution ad for [product], 20 seconds, US market. Problem shot at high density, product reveal at medium, result and CTA at low. Generate with Higgsfield in 9:16." No separate tool. No file transfer. The video comes back in the same thread. ▸ CHAIN THE WHOLE STACK One prompt. All four tools firing together. "You are my ad creative director. Hermes has loaded my brand context. Pull the top performing video style in [niche] from ViralBuilder this week. Use the video-prompt-builder skill to write a full shot-by-shot prompt for [product] that replicates that style — 20 seconds, 9:16, US market, hook in the first 3 seconds. Output the effects timeline, inventory, density map, and energy arc. Then generate the video with Higgsfield." That single prompt replaces a half-day of production. The math before this stack: Brief: 30 minutes Script: 1 hour Creative production: 2 to 3 hours Agency or freelancer cost: $500 to $2,000 per creative With this stack: Hook to finished creative: 10 minutes Cost per creative: tool subscription, a fraction of agency rate 5 product tests in the time it used to take to brief one Bad product tests are where US ad budget disappears. $600 to $1,500 per failed test, before you even know if the angle works. This stack shows you what the market already validated before you spend a dollar on production. Hermes = your context layer. Brand, goals, past performance. Claude is always informed. ViralBuilder = your winning video database. See exactly what styles, hooks, and formats are scaling before you produce anything. video-prompt-builder skill = the translation layer. Turns a creative brief into a structured, production-ready Higgsfield prompt every time. Claude = the brain. Reads the market, writes the brief, chains the tools. Higgsfield MCP = the output. Video generated directly from the prompt. No export step. Four tools. One session. 10 minutes. Comment + RT "STACK" and I'll DM you the full workflow + the video-prompt-builder skill file.

Kid Pak

56,514 views • 2 months ago

Boris Cherny runs Claude Code at Anthropic. His line should stop you mid-scroll: "I don't prompt Claude anymore. I have loops running that prompt Claude and figure out what to do. My job is to write loops." The skill moved. From writing prompts to building the loop around them. A loop that works has three things. Drop one and it burns money in circles. 1. A finish line it can prove. Tests pass or they fail. "Looks done" is not a finish line. 2. A checker that did not write the code. A model grading itself always says yes. 3. Brakes set before you start. A step limit. A money ceiling. A stop condition. That is the whole game. The loop does the work. You design the cage it runs in. Full breakdown below.

Boris Cherny runs Claude Code at Anthropic. His line should stop you mid-scroll: "I don't prompt Claude anymore. I have loops running that prompt Claude and figure out what to do. My job is to write loops." The skill moved. From writing prompts to building the loop around them. A loop that works has three things. Drop one and it burns money in circles. 1. A finish line it can prove. Tests pass or they fail. "Looks done" is not a finish line. 2. A checker that did not write the code. A model grading itself always says yes. 3. Brakes set before you start. A step limit. A money ceiling. A stop condition. That is the whole game. The loop does the work. You design the cage it runs in. Full breakdown below.

shmidt

16,085 views • 1 month ago

Skills are the quickest way to 10x the quality and consistency of what you get from Claude Code. And you don't need to be a developer to use them. Anthropic just published how they use hundreds of skills internally every day. Most skill tutorials are made for developers — if you're in marketing, sales, content ops, or GTM, you probably watched those and moved on. But skills are just as important for non-developers. A skill is just a reusable prompt with clear instructions for a specific task. Instead of prompting Claude the same way over and over, you build it once and invoke it every time. I have a skill for writing on LinkedIn. A different one for YouTube outlines. Another for X. Each platform has different rules, different voice, different structure — so each one gets its own skill. If you're doing something repeatedly, it's time to make a skill. The biggest mistake most people make: building skills as a single .md file. A single file dumps everything into context whether Claude needs it or not. Wastes tokens. Gets worse results. Skills should be folders. Here's the structure that works: skill.md — the orchestrator. Tells Claude which files to read and when. It doesn't contain rules itself — it's the playbook. instructions/ — separate files for voice, structure, scope. Claude only loads the one it needs for the current step. examples/ — good AND bad. Good examples show what success looks like. Bad examples show patterns to avoid — AI writing tells, weak hooks, generic CTAs. Most people skip bad examples. Don't. eval/ — a checklist that scores every output before you see it. "Does it have a clear hook?" "Is it free of AI buzzwords?" Pass or fail on each item. templates/ — output formatting so you get consistent structure every time. The three types of skills that matter most for non-developers: 1. Business automation. Writing a newsletter. Checking reports and drafting follow-ups. Running programmatic ad campaigns. Any workflow you repeat — build a skill for it. 2. Content templates. Landing page copy, meta ads, email sequences, SEO briefs. Each one has specific requirements. Each one gets its own skill. 3. Thinking partners. This is the one people miss. Skills don't have to produce output. They can help you think — an advisory board that reviews your work from your ICP's perspective, a coach that pressure-tests your strategy, an ideation partner that researches competitors before suggesting your next move. If you already have skills as .md files, here's the exact prompt to restructure them in the Anthropic approved format: "I want to restructure my Claude Code skill file. Right now my skill is a single .md file and I want to break it into a folder system following Anthropic's best practices. Read my current skill file, then restructure it into a folder with: a skill.md orchestrator, an instructions/ folder with separate files for each concern (voice, structure, scope), an examples/ folder with good and bad examples, an eval/ folder with a quality checklist, and a templates/ folder for output formatting. Keep all my existing rules and intent — just reorganize them into the modular structure." Paste that into Claude Code pointed at the folder where your skill lives. It handles the rest. A few caveats: 1. Don't add too many skills. Every skill adds context Claude has to process. 50 skills loaded means everything slows down. Start with 3-5 covering your most repeated workflows. 2. Vet skills before downloading. If you grab a skill from the internet, read what's inside first. Skills can include shell commands and scripts. Check what you're running. 3. Share what works. Build a skill that performs well, put it in a shared GitHub repo. Your marketing org gets shared skills for copywriting, SEO, ad copy — new hires invoke the skill instead of learning every playbook from scratch. Onboarding time drops dramatically. 4. Keep your skills updated. When you see output you love, add it as a good example. When you see a pattern you hate, add it as a bad example. The skill gets sharper every time. I made a full video walking through all of this — including a live build of two skills from scratch (no terminal, no code), the exact prompt I use to restructure old skills, and 5 pro tips from Anthropic's internal playbook. Share this with your non-developer friends that want to do more with AI; or bookmark it to come back to at a later time.

Skills are the quickest way to 10x the quality and consistency of what you get from Claude Code. And you don't need to be a developer to use them. Anthropic just published how they use hundreds of skills internally every day. Most skill tutorials are made for developers — if you're in marketing, sales, content ops, or GTM, you probably watched those and moved on. But skills are just as important for non-developers. A skill is just a reusable prompt with clear instructions for a specific task. Instead of prompting Claude the same way over and over, you build it once and invoke it every time. I have a skill for writing on LinkedIn. A different one for YouTube outlines. Another for X. Each platform has different rules, different voice, different structure — so each one gets its own skill. If you're doing something repeatedly, it's time to make a skill. The biggest mistake most people make: building skills as a single .md file. A single file dumps everything into context whether Claude needs it or not. Wastes tokens. Gets worse results. Skills should be folders. Here's the structure that works: skill.md — the orchestrator. Tells Claude which files to read and when. It doesn't contain rules itself — it's the playbook. instructions/ — separate files for voice, structure, scope. Claude only loads the one it needs for the current step. examples/ — good AND bad. Good examples show what success looks like. Bad examples show patterns to avoid — AI writing tells, weak hooks, generic CTAs. Most people skip bad examples. Don't. eval/ — a checklist that scores every output before you see it. "Does it have a clear hook?" "Is it free of AI buzzwords?" Pass or fail on each item. templates/ — output formatting so you get consistent structure every time. The three types of skills that matter most for non-developers: 1. Business automation. Writing a newsletter. Checking reports and drafting follow-ups. Running programmatic ad campaigns. Any workflow you repeat — build a skill for it. 2. Content templates. Landing page copy, meta ads, email sequences, SEO briefs. Each one has specific requirements. Each one gets its own skill. 3. Thinking partners. This is the one people miss. Skills don't have to produce output. They can help you think — an advisory board that reviews your work from your ICP's perspective, a coach that pressure-tests your strategy, an ideation partner that researches competitors before suggesting your next move. If you already have skills as .md files, here's the exact prompt to restructure them in the Anthropic approved format: "I want to restructure my Claude Code skill file. Right now my skill is a single .md file and I want to break it into a folder system following Anthropic's best practices. Read my current skill file, then restructure it into a folder with: a skill.md orchestrator, an instructions/ folder with separate files for each concern (voice, structure, scope), an examples/ folder with good and bad examples, an eval/ folder with a quality checklist, and a templates/ folder for output formatting. Keep all my existing rules and intent — just reorganize them into the modular structure." Paste that into Claude Code pointed at the folder where your skill lives. It handles the rest. A few caveats: 1. Don't add too many skills. Every skill adds context Claude has to process. 50 skills loaded means everything slows down. Start with 3-5 covering your most repeated workflows. 2. Vet skills before downloading. If you grab a skill from the internet, read what's inside first. Skills can include shell commands and scripts. Check what you're running. 3. Share what works. Build a skill that performs well, put it in a shared GitHub repo. Your marketing org gets shared skills for copywriting, SEO, ad copy — new hires invoke the skill instead of learning every playbook from scratch. Onboarding time drops dramatically. 4. Keep your skills updated. When you see output you love, add it as a good example. When you see a pattern you hate, add it as a bad example. The skill gets sharper every time. I made a full video walking through all of this — including a live build of two skills from scratch (no terminal, no code), the exact prompt I use to restructure old skills, and 5 pro tips from Anthropic's internal playbook. Share this with your non-developer friends that want to do more with AI; or bookmark it to come back to at a later time.

JJ Englert

29,322 views • 3 months ago

I built a Claude Code skill that allows it to generate a deep research report over any collection of complex docs (PDFs, Word, Pptx)….and generate word-level citations and bounding boxes directly back to the source! 📝 Check out “/research-docs”. 1. It parses out text and bounding boxes from every doc with liteparse, in seconds. 2. It then generates a full HTML report of the outputs that let you see word-level citations in each page. Raw Claude obviously has deep research capabilities, but it lacks an audit trail back to the source. This skill gives you a researched report that can be audited by others. Check it out: LiteParse:

I built a Claude Code skill that allows it to generate a deep research report over any collection of complex docs (PDFs, Word, Pptx)….and generate word-level citations and bounding boxes directly back to the source! 📝 Check out “/research-docs”. 1. It parses out text and bounding boxes from every doc with liteparse, in seconds. 2. It then generates a full HTML report of the outputs that let you see word-level citations in each page. Raw Claude obviously has deep research capabilities, but it lacks an audit trail back to the source. This skill gives you a researched report that can be audited by others. Check it out: LiteParse:

Jerry Liu

77,259 views • 3 months ago

I just built a Brand Operating System inside Claude Cowork 🤯 A connected system of files that every skill automatically reads from, so your hook writer, brief generator, and script writer all speak in your exact brand voice. All inside Claude Cowork. Perfect for DTC brands and agencies tired of generic AI output that sounds like every other brand in their category. If you're opening a new Claude chat and re-explaining your brand, re-pasting your voice guidelines, and re-describing your customers every single time, a Brand OS fixes the entire loop: → Build 3 foundation files once per brand → Every skill you create reads from the Brand OS automatically → Hook writer pulls your voice + customer pain points → Brief generator pulls your positioning + angles → Script writer pulls the brief + brand DNA → Every output is calibrated to your brand on the first pass No re-briefing Claude on every chat. No editing for an hour to fix generic AI phrasing. No creative that sounds like it could belong to any brand. What you get in the playbook: → The exact Brand OS file structure I use → Templates for all 3 files you can fill in for any brand → The architecture that makes every Claude skill 10x sharper → The exact setup for agencies running a Brand OS per client For agencies: this is how you build a perfect, reusable knowledge base for every client on your roster. Set up the Brand OS once per client, and every campaign after that is already calibrated. I put together a full playbook with the file templates, the architecture, and the exact setup process so you can build your own Brand OS for your brand or your clients. Want it for free? > Like this post > Comment "OS" And I'll send it over (must be following so I can DM)

Mike Futia

30,179 views • 3 months ago

Cat Wu, head of product for Claude Code at Anthropic: "you can build almost anything with Claude from a single prompt now" one prompt gets you a working screen, not YOUR product Claude Code has never seen your design system, so it guesses the look fresh every time. how to hand Claude Code that system is in the article. better than the $300 design course in your tabs, and this one's free.

Cat Wu, head of product for Claude Code at Anthropic: "you can build almost anything with Claude from a single prompt now" one prompt gets you a working screen, not YOUR product Claude Code has never seen your design system, so it guesses the look fresh every time. how to hand Claude Code that system is in the article. better than the $300 design course in your tabs, and this one's free.

Mnimiy

113,513 views • 1 month ago

I forked Claude's pptx skill to make Claude Code generate gorgeous presentations Claude can generate presentations using the pptx skill from Anthropic but its output can be quite bland. Especially if you're used to the high aesthetic standards of Every 📧. So I played around with the pptx skill, iterated it, built a design system, gave it image assets, gave it access to run nano-banana using api and added custom commands. End result? An every-pptx plugin! It takes you from an idea in your head → creating a file for the plan → preparing image assets using gemini nano banana → constructing the final ppt. All happening 100% inside Claude desktop app! s/o Anthony Morris ツ Now our team can use claude code to generate full-blown presentations, in the ~Every 📧 aesthetic. Check out the walkthrough below to see how it works.

I forked Claude's pptx skill to make Claude Code generate gorgeous presentations Claude can generate presentations using the pptx skill from Anthropic but its output can be quite bland. Especially if you're used to the high aesthetic standards of Every 📧. So I played around with the pptx skill, iterated it, built a design system, gave it image assets, gave it access to run nano-banana using api and added custom commands. End result? An every-pptx plugin! It takes you from an idea in your head → creating a file for the plan → preparing image assets using gemini nano banana → constructing the final ppt. All happening 100% inside Claude desktop app! s/o Anthony Morris ツ Now our team can use claude code to generate full-blown presentations, in the ~Every 📧 aesthetic. Check out the walkthrough below to see how it works.

Nityesh

74,943 views • 6 months ago

Right now, most developers are still doing the job AI should be doing. Assign a task. Wait. Review the result. Fix it. Repeat. You're not building with AI. You're babysitting it. The shift happening now is much bigger than better coding agents. It's loop engineering. Instead of managing every AI agent yourself, you build a system that manages them for you. One loop assigns the work. Another checks the output. A third retries failures. Everything keeps moving without waiting for your next prompt. Your job doesn't disappear. It changes. You stop acting like a project manager... ...and start designing the system that manages the entire team. That's exactly the transition I break down in the article below.

Right now, most developers are still doing the job AI should be doing. Assign a task. Wait. Review the result. Fix it. Repeat. You're not building with AI. You're babysitting it. The shift happening now is much bigger than better coding agents. It's loop engineering. Instead of managing every AI agent yourself, you build a system that manages them for you. One loop assigns the work. Another checks the output. A third retries failures. Everything keeps moving without waiting for your next prompt. Your job doesn't disappear. It changes. You stop acting like a project manager... ...and start designing the system that manages the entire team. That's exactly the transition I break down in the article below.

Pure

10,953 views • 12 days ago

Claude Code creator: "100% of our pull requests at Anrtopic are run by Claude Code. 80–90% of code review too. The feature I’m using the most today is /loops. I’m not prompting Claude anymore - I’m building loops" in this interview he breaks down exactly how a system changes everything: - the memory and context features that turn Claude into a second brain - the knowledge architecture most users don't know Claude can build - the integration layer that connects Claude to your actual workflow - why typing one question at a time is the most expensive way to use Claude if you've been using Claude for months and still start every conversation from scratch with zero context, you don't have a Claude problem. you have a system problem instead of another show tonight, watch this make sure to bookmark it before it gets lost in your feed full guide in the article below

Claude Code creator: "100% of our pull requests at Anrtopic are run by Claude Code. 80–90% of code review too. The feature I’m using the most today is /loops. I’m not prompting Claude anymore - I’m building loops" in this interview he breaks down exactly how a system changes everything: - the memory and context features that turn Claude into a second brain - the knowledge architecture most users don't know Claude can build - the integration layer that connects Claude to your actual workflow - why typing one question at a time is the most expensive way to use Claude if you've been using Claude for months and still start every conversation from scratch with zero context, you don't have a Claude problem. you have a system problem instead of another show tonight, watch this make sure to bookmark it before it gets lost in your feed full guide in the article below

Khairallah AL-Awady

39,243 views • 1 month ago