My Blog

Blog

  • AI Tools: Muse Wonder Full | How to Build an AI Filmmaking Chat Agent!

    Watch on YouTube: https://www.youtube.com/watch?v=–lwdihiG3A

    Channel: fal

    Introduction

    The video titled “Muse Wonder Full | How to Build an AI Filmmaking Chat Agent!” walks through the creation of a prototype chat‑agent application that assists with pre‑production planning for film projects. The presenter uses the Muse Wonderful 1.0 model, the Fall Agent SDK, and Vercel for deployment, aiming to generate overhead diagrams and a set of camera‑coverage shots (wide, medium, over‑the‑shoulder, close‑up, insert) from user‑provided character and location images.

    What the Video Covers

    The presentation is structured around a live demonstration of the chat‑agent workflow. It begins with a brief explanation of why the creator switched from Muse Spark 1.3 to the Muse Wonderful 1.0 nightly build accessed via T3 Code. The core of the video shows how the Fall Agent SDK is used to equip the chat agent with knowledge of image and video models, allowing it to respond to custom skills that request specific visual outputs. The presenter then details the deployment steps on Vercel, including the manual addition of the Fall API key after the CLI failed to inject secrets automatically. Throughout the demo, the agent produces an overhead layout of characters and cameras, followed by a series of coverage shots that illustrate how a scene could be filmed.

    Step‑by‑Step Walkthrough

    1. Set up the development environment – Install T3 Code and connect it to the Muse Wonderful 1.0 nightly build (the notes specify using the nightly version rather than the stable Spark 1.3 release).
    2. Integrate the Fall Agent SDK – Add the SDK to the project, choose an underlying LLM, and configure the agent with custom skills that trigger image generation for overhead diagrams and various camera shots.
    3. Prepare the user interface – Build a chat interface that lets users drag‑and‑drop character images, drop location images, and type a description of the action. The UI includes a draggable divider, a fixed width of 1600 px, and a 16:9 aspect ratio for the generated visuals.
    4. Deploy to Vercel – Push the code to a Vercel repository. Because the Vercel CLI could not automatically inject secrets, the presenter manually added the Fall API key in the Vercel project settings.
    5. Test the agent – Interact with the chat agent by providing images and a scene description. The agent first returns an overhead diagram showing character placement and camera positions, then generates a set of coverage shots (wide, medium, over‑the‑shoulder, close‑up, insert).
    6. Review and iterate – Examine the outputs for issues such as duplicated shots, focus problems, or awkward angles. Adjust prompts to keep subjects stationary while rotating the camera, and experiment with alternative image models to improve shot quality.

    Tools and Numbers Mentioned

    • Muse Wonderful 1.0 (used via nightly build)
    • Muse Spark 1.3 (referenced as the model initially considered)
    • T3 Code (environment for accessing the nightly build)
    • Fall Agent SDK (framework for creating the chat agent)
    • Vercel (deployment platform)
    • Ghosty Terminal (mentioned as part of the development setup)
    • Width setting: 1600 px
    • Aspect ratio: 16:9
    • $50 plan (referenced in the context of the service tier used)

    Caveats and Hype Check

    The presenter characterizes the prototype as a first functional chat‑agent app, noting that the initial results are usable but imperfect. Specific shortcomings include duplicated shots, occasional focus issues, and some awkward camera angles, which indicate that prompt tuning is still required. No claims about revenue, earnings, or commercial success are made; the video positions the work as a work‑in‑progress that would benefit from further refinement. The tone remains exploratory, emphasizing the potential to create domain‑specific versions with custom skills rather than presenting a finished product.

    Concrete Next Actions

    • Install T3 Code and link it to the Muse Wonderful 1.0 nightly build.
    • Integrate the Fall Agent SDK, select an LLM, and add your Fall API key to the project.
    • Develop a chat interface that accepts character and location images, then prompts the agent for coverage generation.
    • Deploy the application to Vercel (or a comparable platform) and manually inject any required secrets, such as the Fall API key.
    • Iterate on the prompts: ask the agent to keep subjects fixed while rotating the camera, and test different image models to improve the quality and consistency of the generated shots.

  • Grok Bot Just Got 11 MASSIVE Updates (How to Turn Them On)

    Watch on YouTube: https://www.youtube.com/watch?v=m_thI991MLA

    Channel: Nuno Tavares | Automated Marketer

    Introduction

    The latest video from Nuno Tavares | Automated Marketer walks through eleven recent updates to Grok Bot, showing how each new capability can be turned on and used in everyday workflows. The presentation is framed as a practical guide for users who want to keep their bot up‑to‑date and start leveraging the expanded feature set without guessing where the settings live.

    Overview of the 11 Updates

    The video groups the updates into thematic areas:

    • Agent selection – setting a primary bot so Grok Bot always uses a chosen agent (e.g., Chief of Staff).
    • Version requirement – the new features require Grok Bot version 6.8 or newer (the demo shows version 6.66).
    • Dedicated email – assigning the bot its own email address via the Plugins → Connect to Apps menu.
    • Reading X (Twitter) – enabling the bot to view public X posts without consuming the user’s API key.
    • Slide‑deck creation – generating Google Slides or PowerPoint decks after connecting Google apps.
    • Enhanced Gmail drafts – formatted text, a From picker, spam search, and signature inclusion (version 68.1).
    • Financial linking – using Plaid to connect bank, investment, and subscription accounts for spending tracking and unused‑subscription detection.
    • Marketplace rename – the former marketplace is now called “Connected Apps”; bot templates remain reachable at x.ai/bot/marketplace.
    • UI and language improvements – 1920×1200 resolution, five new interface languages, and custom rule configuration in Settings.
    • Usage and billing transparency – reset timers, voice/language retention, clear usage notices, and right‑click routine controls.
    • Future automatic model selection – upcoming logic that will let Grok Bot pick the best model (e.g., Claude Opus 5.5, Midjourney, Suno) for each task.

    Step‑by‑Step Walkthrough

    Below is a concise, ordered list of the actions the presenter demonstrates for each update. Follow the exact menu paths shown in the video to avoid missing a toggle.

    • Set a primary bot – Open Settings → Bot Management → Choose “Primary Bot” and select your desired agent (e.g., Chief of Staff).
    • Update Grok Bot – Navigate to Settings → Updates → Check for updates and install version 6.8 or higher.
    • Assign a dedicated email – Go to Plugins → Connect to Apps → Email → Add a new address, then configure forwarding rules in your email provider.
    • Read X without API cost – In a chat with Grok Bot, type a command such as “Read the latest posts from @handle” and add the instruction “do not use my API key.” The bot will fetch public data via its built‑in scraper.
    • Build a slide deck – Connect Google Slides (or PowerPoint) via Plugins → Connect to Apps → Google Apps. Then ask Grok Bot: “Create a slide deck about [topic] with 10 slides.” The bot will generate the deck in your linked Google Drive.
    • Enhance Gmail drafts – Ensure you are on version 68.1 or later. In the Gmail integration, enable “Formatted drafts,” turn on the From picker, activate spam search, and toggle signature inclusion. Test by asking Grok Bot to draft an email and verify the formatting.
    • Link finances via Plaid – Open Plugins → Connect to Apps → Plaid → Follow the OAuth flow to connect your bank, investment, and subscription accounts. Once linked, you can request summaries like “Show my monthly spending” or “Find unused subscriptions.”
    • Explore the Connected Apps marketplace – Visit x.ai/bot/marketplace (the URL remains unchanged despite the rename). Browse bot templates and install any that match your workflow.
    • Configure custom rules – Go to Settings → Custom Rules → Add a new rule (e.g., “If message contains ‘budget,’ respond with the latest Plaid report”). Save and test the rule in a chat.
    • Monitor usage and billing – In Settings → Usage & Billing, view the reset timer for voice minutes, check language retention settings, and enable the right‑click menu for quick routine controls.
    • Prepare for automatic model selection – No action is required yet; the feature will be enabled in a future release. Keep the bot updated to benefit when it rolls out.

    Tools and Version Numbers Mentioned

    The video references several specific tools and version identifiers:

    • Grok Bot versions: 6.66 (demo), 6.8 (minimum for new features), 68.1 (Gmail draft enhancements), 0.69 (referenced in the UI section).
    • Display resolution: 1920×1200.
    • External services: Plaid (financial data), Google Slides, Google Docs, X (formerly Twitter).
    • Marketplace URL: x.ai/bot/marketplace.
    • App connector: Compazio (noted as connecting to 1,500 apps).
    • Future model examples: Claude Opus 5.5, Midjourney, Suno.

    Reality Check and Limitations

    The presenter characterizes the updates as “massive” and hints that they could replace multiple standalone tools. However, the video does not provide independent verification, ROI figures, or concrete time‑saving metrics. Claims about cost reduction via Plaid or accelerated slide creation remain suggestive; users should test each feature in their own environment before depending on them for critical business processes. Additionally, the automatic model selection capability is still forthcoming, so current workflows must continue to specify models manually when needed.

    Immediate Actions to Take

    Based on the video’s guidance, the following checklist can be copied into a task manager or note‑taking app:

    • [ ] Update Grok Bot to version 6.8 or later via Settings → Updates.
    • [ ] Designate a primary bot (e.g., Chief of Staff) under Settings → Bot Management.
    • [ ] Create a dedicated email address for the bot through Plugins → Connect to Apps → Email and set up forwarding rules.
    • [ ] Instruct Grok Bot to avoid using your API key when reading X posts (e.g., “Read X without API key”).
    • [ ] Connect Google Slides/Docs via Plugins → Connect to Apps → Google Apps and ask the bot to generate a slide deck.
    • [ ] Link bank, investment, and subscription accounts via Plaid under Plugins → Connect to Apps → Plaid.
    • [ ] Visit x.ai/bot/marketplace to explore available bot templates.
    • [ ] Add custom rules in Settings → Custom Rules to automate repetitive responses.
    • [ ] Test the new Gmail draft features (formatted text, From picker, spam search, signature) by requesting a draft from Grok Bot.
    • [ ] Join the free Grok Bot community and register for upcoming workshops to deepen your understanding.

  • Grok Bot: 9 Grok Bot Use Cases That Feel Illegal

    Watch on YouTube: https://www.youtube.com/watch?v=LR6BT1s4lFU

    Channel: Elisa

    Overview of Elisa’s “9 Grok Bot Use Cases That Feel Illegal”

    In this video, Elisa walks through nine concrete ways she leverages Grok Bot to automate common marketing and operational tasks. Each use case is presented with an estimated time or cost saving, the tools she integrates (such as Bland AI, Twilio, Gmail, Google Drive, Slack, Notion, and GitHub), and a brief description of the prompt or workflow she employs. The tone is enthusiastic but grounded in practical examples that entrepreneurs and marketers can replicate.

    What the Video Covers

    • Landing‑page generator – builds a full website from product details in roughly 45 minutes.
    • Dial bot – automates outbound phone calls for appointments using Bland AI and a Twilio number.
    • Bounty hunter – scans Gmail for forgotten subscriptions and refund opportunities.
    • Speed‑to‑lead bot – auto‑replies to inbound leads, reducing response time from ~15 minutes to seconds.
    • Clipper – turns long‑form video into multiple captioned shorts.
    • Website auditor – analyses SEO, accessibility, performance, and conversion, delivering a prioritized fix list.
    • Last 30 days scout – monitors Reddit, X, YouTube, etc., to surface trending topics.
    • Competitor scout – tracks specified competitors and outputs a comparison report.
    • Forge bot builder – creates a custom Grok Bot specification from a clear outcome description in 5‑10 minutes.

    Step‑by‑Step Walkthrough of Each Use Case

    1. Landing‑page generator

    Provide Grok Bot with detailed product information: name, price, target customer, problem statement, deliverables, and testimonials. The bot outputs HTML/CSS ready for upload. Elisa notes the process takes about 45 minutes versus several hours of manual design and copy work, and she estimates the resulting site could be valued at $5,000–$10,000.

    2. Dial bot (appointment calls)

    Purchase a Twilio phone number (~$1) and load Bland AI credits (~$20). Connect both services to Grok Bot, then define the call script (e.g., “Book a 15‑minute strategy call”). The bot places the call, handles responses, and logs the outcome. Elisa reports saving roughly 15–20 minutes per call compared to manual dialing.

    3. Bounty hunter (refund finder)

    Grant Grok Bot access to your Gmail via its plugin. Ask it to search for receipts, billing confirmations, or subscription notices. The bot compiles a list of potential refunds or unused services to cancel. Elisa claims this can uncover “hundreds of dollars” in savings.

    4. Speed‑to‑lead auto‑responder

    Connect Gmail to Grok Bot, set lead‑qualification criteria (e.g., contains specific keywords or comes from a known domain), and choose whether replies stay in draft mode or are sent automatically. The bot reduces reply time from ~15 minutes to seconds, which Elisa ties to a widely cited statistic: replying within two hours makes a lead ten times more likely to close.

    5. Clipper (video‑to‑shorts)

    Upload a long‑form video to Google Drive, give Grok Bot access to the file, and provide a reference short that illustrates the desired style. The bot extracts engaging moments, adds captions, and outputs multiple short clips. Elisa notes a saving of more than one hour per podcast episode.

    6. Website auditor

    Supply your site’s URL to the auditor bot. It runs checks on SEO, accessibility, performance, and conversion elements, then returns a prioritized report with actionable fixes. Elisa compares the output to a costly consultant audit and highlights savings in both time and money (described as “hours and hundreds‑to‑thousands of dollars”).

    7. Last 30 days scout (trend monitoring)

    Select a niche or topic, choose platforms (Reddit, X, YouTube, etc.), and set the bot to scan daily. It surfaces emerging discussions, hashtags, or video trends. Elisa estimates this replaces roughly four hours of manual research each day.

    8. Competitor scout

    Enter competitor handles or website URLs, define comparison criteria (e.g., pricing, content frequency, engagement metrics), and let the bot generate a side‑by‑side report. This automates what would otherwise be a time‑intensive manual analysis.

    9. Forge (custom bot builder)

    State a clear outcome (for example, “check X DMs for sponsorships”), add any constraints (frequency, message format, approval steps), and let Forge produce a full Grok Bot specification in 5‑10 minutes. Elisa emphasizes that this removes the need to manually script each new bot.

    Tools and Numbers Mentioned

    • Bland AI (voice service) + Twilio number: ~$1 for the number + $20 credits ≈ $40 total.
    • Gmail, Google Drive, Slack, Notion, GitHub – used as data sources or storage for bot outputs.
    • Time savings: 45 minutes for a landing page; 15–20 minutes per call; >1 hour per video episode; ~4 hours daily research saved.
    • Financial savings: “hundreds of dollars” from bounty hunter; “hundreds‑to‑thousands of dollars” from website auditor; potential site value $5,000–$10,000.

    Caveats / Hype Check

    The video presents high‑impact savings and revenue claims (e.g., 10× lead conversion, $5k–$10k website value, hundreds of dollars saved) without providing independent verification or detailed case studies. These figures should be treated as aspirational estimates based on Elisa’s personal experience rather than guaranteed outcomes.

    Additionally, the effectiveness of each bot depends on the quality of the prompts, the accuracy of the connected data sources, and any platform‑specific limits (e.g., Gmail API rate limits, Twilio usage costs). Users should test each workflow on a small scale before relying on it for critical operations.

    Concrete Next Actions

    • Landing page: Gather product name, price, target audience, problem, deliverables, and testimonials; feed this to Grok Bot and review the generated HTML/CSS.
    • Dial bot: Buy a Twilio number, load Bland AI credits, connect both to Grok Bot, and script the appointment‑booking dialogue.
    • Bounty hunter: Enable the Gmail plugin, ask Grok Bot to locate receipts or subscription emails, and export the list for manual review.
    • Speed‑to‑lead: Link Gmail, define lead‑qualification filters, decide draft vs. auto‑send, and monitor response times.
    • Clipper: Upload a long‑form video to Google Drive, grant Grok Bot access, supply a reference short, and collect the captioned clips.
    • Website auditor: Provide your site URL, request a prioritized SEO/accessibility/performance/conversion report, and implement the top recommendations.
    • Last 30 days scout: Choose a niche, select platforms (Reddit, X, YouTube, etc.), set a daily scan schedule, and review the trend output.
    • Competitor scout: Enter competitor URLs or handles, specify comparison metrics, and let the bot produce a report.
    • Forge: Write a clear outcome statement (e.g., “monitor X DMs for sponsorship opportunities”), add any constraints, and let Forge output a bot spec in minutes.
    • Archiving: Save important Grok Bot conversations to GitHub to preserve context and avoid losing details in long threads.

  • Marketing & Lead Gen: how i made $1,204/day selling boring pdfs using claude

    Watch on YouTube: https://www.youtube.com/watch?v=sePHV1SSb6U

    Channel: Richard Yu

    Introduction

    The video explains a method for earning over $1,200 per day by acting as an affiliate middle‑man for already‑selling digital products. No product creation, website, or customer service is required. The core idea is to connect buyers with sellers through affiliate links and earn a commission on each sale.

    What the video covers

    The presentation walks through the arbitrage model, shows how to select a product that solves a problem people are already paying for, and demonstrates how to use Claude to research buyer psychology and generate video scripts. It then outlines a rapid content workflow: posting short 7‑15 second videos, replying to comments or DMs within 15 minutes, delivering a personalized value video before sharing the affiliate link, and tracking results to scale the process.

    Step‑by‑step walkthrough

    • Find a selling digital product on a public marketplace that addresses a paid problem and that you would feel comfortable recommending to someone you like.
    • Paste the product page into Claude and ask: who buys this, what they fear, what they’ve tried, and their top three objections.
    • Take Claude’s output and craft a 15‑second video script that opens with the buyer’s fear and ends with a prompt to message you; generate 20 variations from one prompt.
    • Create short 7‑15 second videos (text over clips, no face required) and post them daily, preferably in the morning.
    • Monitor comments and DMs; reply within 15 minutes, first naming the viewer’s action (e.g., “I see you commented on…”) then asking why they did it to surface their real problem.
    • When they respond, record a quick, unlisted video that answers their specific question (no editing needed) and send it before sharing your affiliate link.
    • Track which scripts and value videos generate the most conversations and double down on those.
    • Iterate: continuously test new products, refine buyer profiles with Claude, and increase the volume of short videos.

    Tools and numbers

    • Claude – AI tool used for buyer analysis and script generation.
    • YouTube – platform for posting the short 7‑15 second videos.
    • Digital product marketplace – source of already‑selling products.
    • DMs / private messages – channel for direct conversation with interested viewers.
    • Commission ranges: 20‑40% for $3k‑$12k products, 50‑70% for $500‑$1k products, 70‑95% for $50‑$500 products, far above typical 3‑10% affiliate payouts.
    • Earnings claim: $36,130 earned in the last 30 days (~$1,204 per day).
    • Video length: 7‑15 seconds.
    • Reply window: within 15 minutes of a comment or DM.
    • Conversion ratios noted: 1 in 10 sales from video‑only click, 8 in 10 sales from conversation, 1 in 10 sales from a short call.

    Caveats / hype check

    The video’s income figure of $36,130 in 30 days assumes consistent high‑conversion traffic and may not be typical for beginners. While the arbitrage model is legitimate, the presentation emphasizes the ease of AI‑generated content and downplays the effort needed to find profitable products, maintain rapid reply times, and build trust. Viewers should treat the earnings claim as a best‑case scenario rather than a guaranteed result.

    Concrete next actions

    • Browse a public digital product marketplace and select a product that solves a problem people are already paying for.
    • Paste the product page into Claude and request buyer demographics, fears, past failed solutions, and the three main objections.
    • Use Claude’s output to write a 15‑second video script that opens with the buyer’s fear and ends with a call to message you; generate 20 variations.
    • Produce short 7‑15 second videos (text over clips, no face needed) and post them each morning.
    • Set up notifications to monitor comments and DMs; aim to reply within 15 minutes, naming the viewer’s action and asking why they took it.
    • When a viewer responds, record a brief, unlisted video that answers their specific question and send it before sharing your affiliate link.
    • Review performance data: note which scripts and value videos drive the most conversations and focus future effort on those.
    • Sign up for the free master class mentioned in the description for a detailed walkthrough of product selection, the full system, and word‑for‑DM scripts.
    • Repeat the cycle with new products, continually refining buyer profiles with Claude and scaling video output.

  • AI Tools: How to Use AI Like The Top 1% (2027)

    Watch on YouTube: https://www.youtube.com/watch?v=He-NyJjzWM0

    Channel: Nick Saraev

    Introduction

    The video positions the advantage of top AI users not in possessing superior models but in the way they interact with those models. It argues that habits such as speaking instead of typing, maintaining an always‑on voice assistant, visualizing outputs, and probing AI for weaknesses create a measurable edge in productivity and income generation.

    What the video covers

    The presenter outlines a set of practical behaviors that separate the top 1 % of AI adopters from the average user. These include using voice dictation for faster input, setting up continuous voice streams that turn meeting speech into actionable tasks, leveraging AI to generate 3‑D visualizations, letting AI interview the user to surface hidden requirements, deliberately asking AI for flaws rather than approval, personally testing model capabilities, and remaining receptive to emerging AI hardware and avatar interfaces.

    Step‑by‑step walkthrough

    • Talk, don’t type: Replace keyboard entry with voice dictation. The video notes that speaking is 3‑5 × faster than typing and recommends starting with a free dictation tool or a paid option like Hex, training it on your personal vocabulary.
    • Always‑on voice assistant: During meetings, keep a microphone open that feeds audio to a frontier LLM (e.g., GPT Real‑Time 2.1). The model transcribes speech and converts it into tasks that can be pushed directly into project‑management platforms such as Notion, Asana, or Monday.
    • Visualize with AI: Prompt the model to produce code or assets for 3‑D visualizations using libraries like 3.js, plain HTML, or engines such as Unreal Engine and Blender. Outputs can range from floor plans to animated explainers that make complex data instantly understandable.
    • Let AI interview you: Frame a prompt that asks the model to question you about a project’s goals, constraints, and unknowns. This technique surfaces requirements you might have overlooked and helps you verbalize needs more clearly.
    • Ask for flaws, not opinions: When reviewing AI‑generated advice, explicitly request potential problems or weaknesses. This counters the model’s natural tendency to agree with the user and yields more balanced, critical feedback.
    • Test capabilities yourself: Spend a few minutes giving the frontier model a concrete task you are curious about—e.g., drafting a contract clause, generating a script, or solving a calculation—and evaluate the output directly rather than relying on second‑hand reviews.
    • Stay open to new AI forms: Keep an eye on emerging interfaces such as wearable AI pendants, avatar‑based assistants, or novel hardware. The video suggests exploring programs like Maker School for hands‑on training with these evolving tools.

    Tools and numbers mentioned

    • Free voice dictation tool (unspecified)
    • Hex (paid dictation/training tool)
    • GPT Real‑Time 2.1 (frontier LLM used for transcription)
    • 3.js, HTML, Unreal Engine, Blender (options for AI‑driven 3‑D visualization)
    • Notion, Asana, Monday (task‑management destinations for voice‑generated actions)
    • Maker School (referenced as a training program for AI business skills)
    • Cost estimate for a voice‑assistant system: $1‑2 per day
    • Potential earnings reference: $300‑400 per day (cited as an example of what top users might achieve)
    • Speaker’s claim: over $10 million earned with AI (presented as an unverified assertion)

    Caveats and hype check

    While the video presents a compelling framework, several points warrant caution. The claim that the speaker has earned over $10 million using AI is not independently verified and may be exaggerated. Additionally, the recommendation to enroll in Maker School is disclosed as a paid affiliate partnership, which could represent a hype‑driven upsell rather than an unbiased endorsement. The productivity figures ($1‑2 per day for a voice‑assistant setup versus $300‑400 per day potential earnings) are presented as illustrative examples; actual results will depend on individual implementation, industry, and the specific models used.

    “The speaker claims to have made over $10 million with AI, a figure that is unverified and may be exaggerated; the video also promotes Maker School as a paid affiliate program, which could represent a hype‑driven upsell.”

    Concrete next actions

    • Install a free voice‑dictation application or trial Hex; spend time training the software on your jargon and frequently used phrases.
    • Configure a continuous audio feed from your meeting environment to a frontier LLM (e.g., GPT Real‑Time 2.1) and set up an automation that posts transcribed action items to Notion, Asana, or Monday.
    • Experiment with prompting the model to generate a simple 3‑D scene using 3.js or an HTML‑based WebGL canvas; iterate on the output to refine a visual explanation of a current project.
    • Create a prompt that asks the AI to interview you about a upcoming initiative; record the questions and answers to identify any gaps in your planning.
    • When you receive AI‑generated advice, explicitly request a list of potential flaws or failure modes before deciding to act on it.
    • Select a frontier model you have access to and assign it a small, well‑defined task (e.g., summarizing a contract clause, drafting a tweet, calculating a budget variance); assess the quality and speed of the result.
    • Research emerging AI hardware such as voice‑activated pendants or avatar assistants; consider enrolling in a hands‑on program like Maker School if you seek structured exposure to these technologies.

  • AI Tools: Claude Just Dropped MOTION. (Get Ahead of 95% in 11 Minutes.)

    Watch on YouTube: https://www.youtube.com/watch?v=yf2OwchM9nw

    Channel: Tristen O'Brien

    Overview of Claude Motion

    The video introduces Claude Motion, a new feature that converts a text prompt into an editable animation by generating underlying code rather than raster pixels. Because the output is code‑based, every element—text, shapes, timing, color, and motion—can be adjusted after the initial generation. Claude Motion is currently in beta and is available only to users on Claude Team or Enterprise plans, though a comparable workflow can be built with the free Remotion tool combined with Claude Code. The demonstration shows how Motion can be paired with Higgs Field to layer real‑world video or image assets for a higher‑production‑value result.

    What the Video Covers

    The presentation walks through the following topics:

    • Accessing Claude Motion via the Artifacts panel in Claude.
    • How the tool writes code that defines each element’s position, color, timing, and motion.
    • Editing options: the Tweaks panel for text and timing changes, and the comment button for non‑text elements such as the sun or moon.
    • Sharing and exporting finished animations as GIF or video with configurable resolution, frame rate, and quality.
    • Credit consumption: longer, more complex animations use more credits from the user’s Claude plan.
    • Integrating Higgs Field to blend AI‑generated video or image layers with Motion animations.
    • Setting up Higgs Field by adding a custom MCP connector in Claude’s Settings → Connectors → Add Custom Connector.
    • Using Remotion, a free, code‑based video tool that works with Claude Code and Higgs Field for users without Motion access.
    • Examples shown: a paper‑style bike commercial and a paper‑to‑real transition scene built with Motion, Higgs Field, and Remotion.
    • Limitations: Motion does not create realistic photos or footage; it excels at animating text, shapes, charts, and existing images.

    Step‑by‑Step Walkthrough

    1. Open Claude and navigate to the Artifacts panel.
    2. Enter a descriptive text prompt for the desired animation (e.g., “a bike riding across a paper landscape”).
    3. Claude Motion processes the prompt and returns a code‑based animation preview.
    4. To adjust textual content or timing, open the Tweaks panel, modify the relevant fields, and see the changes update in real time.
    5. To change non‑textual elements (e.g., swap a sun for a moon), click the comment button on the element, edit the property, and confirm the update.
    6. When satisfied, use the export options to save the animation as a GIF or video, selecting the desired resolution, frame rate, and quality settings.
    7. If you wish to add real‑world video or image layers, first configure Higgs Field:
      • Copy the MCP address from higgsfield.com.
      • In Claude, go to Settings → Connectors → Add Custom Connector and paste the address.
      • Authenticate the connection once.
    8. With Higgs Field connected, generate or import video/image assets and layer them onto the Motion animation within the Artifacts panel.
    9. For users on Pro or Max plans who lack Motion access, install Remotion via Claude Code plugins or terminal, then follow a similar prompt‑to‑code workflow to produce animations.
    10. Monitor credit usage in your Claude plan dashboard to gauge how animation length and complexity affect your limits.

    Tools, Numbers, and Limits Mentioned

    • Claude Motion (beta, Team/Enterprise plans)
    • Claude Code (used with Remotion)
    • Higgs Field (requires MCP connector)
    • Remotion (free, code‑based video tool)
    • Opus 5.5 (referenced as part of the Claude ecosystem)
    • Export formats: GIF, video
    • Configurable export parameters: resolution, frame rate, quality
    • Credit consumption: scales with animation length and complexity
    • Example animation length shown: 20‑second clip
    • Available Claude plans: Team, Enterprise, Pro, Max (free tier noted for Remotion)

    Caveats and Hype Check

    The video heavily promotes Higgs Field as a sponsor and partner, claiming it adds a ‘premium’ look without independent verification of cost or performance benefits; viewers should assess whether the advertised integration truly adds value for their specific use case.

    Additionally, Claude Motion is still in beta, so features may evolve and access could change. The tool does not generate realistic photographs or live‑action footage; its strength lies in animating graphical elements, text, charts, and existing images. Users should test the workflow on a small project before committing significant credits or time.

    Concrete Next Actions

    • If you have a Claude Team or Enterprise plan, enable Motion in the Artifacts panel and create a short animation to explore the Tweaks panel and comment‑button editing.
    • If you are on a Pro or Max plan, install Remotion via Claude Code plugins or terminal and experiment with generating code‑based animations.
    • Connect Higgs Field to Claude by adding a custom MCP connector (copy the MCP address from higgsfield.com, add it under Settings → Connectors → Add Custom Connector, then authenticate).
    • After generating an animation, use the Tweaks panel to edit text, timing, or motion properties, and verify the updates propagate.
    • Use the comment button to modify non‑text elements (e.g., change a sun to a moon) and observe the real‑time update.
    • Export the finished work as a GIF or video, selecting your preferred resolution, frame rate, and quality.
    • Track your Claude plan’s credit usage to understand how animation length and complexity affect your limits.
    • Review Higgs Field’s pre‑made prompts for quick integration of realistic video or image layers.
    • Combine Claude Motion (or Remotion) output with Higgs Field assets to achieve a mixed‑media, premium look.
    • Consider leaving feedback or feature requests in the video’s comment section to help shape future Motion updates.

  • Grok Bot: How I use Grok Bot to go viral on X, LI, and IG (full workflow)

    Watch on YouTube: https://www.youtube.com/watch?v=L0GnfSEZ70U

    Channel: Science Based AI

    Introduction

    The video from the Science Based AI channel demonstrates a complete workflow for turning science‑health news into viral‑ready posts on X, LinkedIn, and Instagram using Grok Bot. The presenter explains how to assemble a team of specialized AI agents, automate research and drafting, and keep a human in the loop for quality control. The approach is presented as a repeatable system that can be built with a $20‑per‑month Grok Bot subscription (or an equivalent X Premium or Cursor plan) and supplemented by a free voice‑to‑text tool called Typeless.

    What the video covers

    The presentation walks through the following elements:

    • How to create distinct AI agents inside Grok Bot – a chief, a researcher, an X writer, a LinkedIn writer, a slide designer, and a carousel builder.
    • The role, goal, inputs, process, and quality bar that each agent needs, with concrete prompt examples (especially for the LinkedIn writer named L.I. Lewis).
    • The flow of information: the researcher (Flock) scans X and news sources for the latest science/health stories, passes them to the chief (Tecumseh) for angle generation, and then routes the chosen brief to the writers and designers for draft creation.
    • The human review step: the creator evaluates AI‑generated copy, tweaks hooks or wording, and then manually posts the final version to each platform to avoid reach‑penalizing auto‑posting services.
    • How Typeless is used for voice‑to‑text input, why the presenter believes it yields higher‑quality prompts than typing, and the affiliate link that provides a $5 discount on the premium version.
    • Cost details: Grok Bot’s minimum plan is $20/month; X Premium or Cursor subscriptions can also cover the expense.
    • Claims about results: the workflow is described as roughly 70% automated and 30% human (taste/editing), and the presenter says it has helped grow his biotech startup’s social following to “tens of thousands.”
    • Advice to use external LLMs such as ChatGPT if Grok’s output lacks strong hooks, then bring the improved copy back into the Grok workflow.
    • Where to find all agent prompts, tool links, and the Typeless discount code (in the video description).

    Step‑by‑step workflow

    • Set up agents in Grok Bot: chief (Tecumseh), researcher (Flock), X writer (Shemingway), LinkedIn writer (L.I. Lewis), slide designer, and carousel builder. Assign each a role, goal, inputs, process, and quality bar using the prompt templates from the description.
    • Activate the researcher agent (Flock) to pull recent science/health stories from X and news sources.
    • Review the researcher’s output with the chief agent (Tecumseh) to generate multiple angles for each story.
    • Select one angle that fits the desired narrative and pass the brief to the writer agents.
    • Let the X writer (Shemingway) draft a tweet‑style post, the LinkedIn writer (L.I. Lewis) draft a LinkedIn article/update, and the slide designer/carousel builder create visual assets for an Instagram carousel.
    • Review all AI‑generated drafts. If hooks or wording feel weak, optionally refine the copy using an external LLM like ChatGPT, then import the improved version back into the Grok Bot workflow.
    • Manually copy the final, approved copy for each platform and post natively on X, LinkedIn, and Instagram (avoiding auto‑posting services to protect reach).
    • Track engagement metrics and iterate on agent prompts to improve output quality over time.

    Tools and numbers

    • Grok Bot minimum plan: $20/month (can be substituted by X Premium or Cursor subscriptions).
    • Typeless: free to start; premium version available with a $5 discount via the presenter’s affiliate link.
    • Additional tools mentioned in the workflow: Notion, Gmail, Google Drive, Figma.
    • Estimated workflow split: ~70% automated, ~30% human (taste/editing).
    • Result claim: the presenter states the approach has grown his biotech startup’s social following to “tens of thousands.”

    Caveats and hype check

    The video includes a promotional segment for Typeless, presenting the affiliate link as a sponsor benefit. Claims about follower growth are described as anecdotal and lack independent verification. No explicit revenue or income promises are made, but the emphasis on viral growth combined with the affiliate suggestion should be viewed with typical marketing caution. The presenter also advises against using auto‑posting services, noting that native posting helps preserve platform reach.

    “We have a no slop policy.”

    “The harder questions have become these things like, what should I talk about?”

    “If you really want a high‑quality post, that might be the way to go.”

    Concrete next actions

    • Sign up for Grok Bot (or use an X Premium/Cursor subscription) and create the six agents: chief, researcher, X writer, LinkedIn writer, slide designer, carousel builder.
    • Copy the prompt templates from the video description for each agent, filling in role, goal, inputs, process, and quality bar.
    • Install Typeless, set the F1 hotkey for voice input, and use it to dictate agent instructions for higher‑quality prompts.
    • Run a test workflow: ask Flock to pull recent science/health news, select a story, have Tecumseh generate angles, choose one, then let the writers and designers produce drafts.
    • Review the AI‑generated posts, improve hooks or wording (optionally using ChatGPT), then manually copy‑paste the final copy to X, LinkedIn, and Instagram.
    • Avoid auto‑posting services; post natively to keep platform reach high.
    • Track results and iterate on agent prompts to improve output quality over time.

  • Marketing & Lead Gen: Give Me 15 minutes, I’ll Give You 10,000 Hours of Claude Skills

    Watch on YouTube: https://www.youtube.com/watch?v=6joYowO6Op0

    Channel: Sabrina Ramonov 🍄

    Introduction

    The video presents a workflow that connects the Blotato MCP (Micro‑Connector Plugin) to Claude through a free skills plugin, enabling automated social‑media scheduling, analytics, and comment responses. By creating an “Atlas folder” (company brain) from a blog post, Claude can generate on‑brand content that Blotato then publishes across multiple platforms. The goal is to let creators focus on high‑quality content while Claude handles repetitive distribution tasks.

    What the Video Covers

    The presentation walks through installing the Blotato skills plugin, linking it to Claude via a custom connector, testing the integration, and using Claude to query scheduled posts, view analytics, and automate comment responses on Facebook and Instagram. It also shows how to build an Atlas folder from a blog link, prompt Claude to create posts or carousels, have Blotato generate visuals, and publish to up to nine social channels. The speaker shares personal metrics such as Jasper’s $1.5 billion valuation, achieving the first $1 million in sales, and scaling to eight‑figure revenue, framing the workflow as a way to apply an 80/20 focus on high‑energy tasks.

    Step‑by‑Step Walkthrough

    • Open Claude Settings → Plugins → Marketplace and install the Blotato skills plugin from the GitHub repository.
    • Click the Sync button to ensure the plugin receives automatic updates when the repository changes.
    • Navigate to Claude Settings → Connectors, add a custom connector, label it “Blot MCP”, and paste your Blotato API key.
    • In a Claude chat, type “lo” to verify that the seven Blotato skills are loaded.
    • Ask Claude to show your content schedule, view top‑performing posts, or set up comment‑response automations for Facebook and Instagram.
    • Provide a blog post link (copied from the video description) to Claude and instruct it to build an Atlas folder (company brain) from that source.
    • Prompt Claude to generate a post or carousel; once the text is ready, have Blotato create the accompanying visuals.
    • Select the platforms where you want the content published (Instagram, Facebook, TikTok, X, LinkedIn, Pinterest, Blue Sky, YouTube, Threads).
    • Review the output with follow‑up prompts, correct any misunderstandings, and then confirm publishing.
    • Monitor your Blotato credit dashboard to track usage against your subscription plan.

    Tools and Numbers Referenced

    • Blotato – the platform that provides the MCP connector and handles publishing.
    • Claude – the AI model that runs the skills plugin and generates content.
    • MCP (Micro‑Connector Plugin) – the bridge that lets Claude interact with Blotato.
    • GitHub repository – source of the Blotato skills plugin.
    • Blotato API key – required to set up the custom connector in Claude.
    • Blotato credits – usage metric tied to your subscription plan.
    • Nine supported platforms: Instagram, Facebook, TikTok, X, LinkedIn, Pinterest, Blue Sky, YouTube, Threads.
    • The presenter notes using six of those platforms in his own workflow.
    • Jasper valuation cited as $1.5 billion.
    • Milestones mentioned: first $1 million in sales and scaling to eight‑figure revenue.
    • Time allocation concept: 20 % high‑energy focus, 80 % mundane‑task automation.
    • Example of a six‑slide carousel and suggested post times (12:00 PM, 2:00 PM).

    Caveats and Hype Check

    The video makes several bold claims—such as saving hours each week, avoiding the need for a multi‑figure operations team, reaching the first $1 million in sales, and scaling to eight‑figure revenue—without presenting evidence or third‑party validation. The promise of acquiring “10,000 hours of Claude skills” in 15 minutes is clearly hyperbolic and should be viewed as promotional language rather than proven results. As noted in the hype check, the quality of content should outweigh posting large volumes of AI‑generated material, and users are encouraged to apply an 80/20 mindset to where they invest time and attention.

    I’m letting Blot and Claude handle the 80% of the mundane tasks

    Quality of content is going to outweigh posting a bunch of random AI slop online

    Be smart, work with Claude, think about the 8020 of where your time and attention needs to be

    It doesn’t have to take you 10,000 hours.

    Concrete Next Actions

    • Copy the blog post link from the video description and paste it into a Claude chat.
    • In Claude Settings → Plugins → Marketplace, add the Blotato skills plugin from the GitHub repo.
    • Click Sync to keep the plugin updated.
    • In Claude Settings → Connectors, add a custom connector, enter “Blot MCP”, and input your Blotato API key.
    • Type “lo” in Claude to confirm the seven skills are loaded.
    • Ask Claude to show your content schedule, view top‑performing posts, or set up comment‑response automations.
    • Use the blog post as context for Claude to build your Atlas folder (company brain).
    • Prompt Claude to create a post or carousel, then have Blotato generate visuals and publish to your chosen platforms.
    • Review and refine the output with follow‑up prompts before final publishing.
    • Check your Blotato credit dashboard to monitor usage against your subscription plan.

  • Grok Bot just made me $1,100…

    Watch on YouTube: https://www.youtube.com/watch?v=lmYLF3keVmw

    Channel: Alex Finn

    Introduction

    In a recent video, Alex Finn demonstrates how an autonomous AI‑agent business generated $1,100 in a single day. The example site, agentusecases.ai, scrapes AI use‑case information, attracts sponsorships, and runs itself through SEO, an automated newsletter, and continuous updates. The creator outlines a repeatable process that can be applied to any AI agent platform, emphasizing that once the bot is configured, ongoing manual effort is minimal.

    What the Video Covers

    The presentation walks through the revenue source, the autonomous routines that keep the site alive, and the technical stack required to replicate the model. It also discusses distribution strategies, potential earnings, and the caveats that viewers should keep in mind before attempting to launch their own agentic business.

    Step‑by‑Step Walkthrough

    1. Create the bot – In your chosen AI agent platform (Rock Bot, Muse, ChatGPT, Hermes, etc.), create a new agent and assign it the role “CEO of your agentic business.”
    2. Provide the core prompt – Give the bot the instruction:

      I want you to design, build, and run an autonomous business for me.

    3. Set up hosting – Deploy the site on Versel (free tier is sufficient for a starter project).
    4. Version control – Create a GitHub repository to store the site’s code and enable automatic pushes or pull requests as the bot makes changes.
    5. Email automation – Connect an email service such as Recent to handle newsletter collection and distribution without manual intervention.
    6. Payment processing – Add a Stripe connector to accept sponsorship payments and embed payment links on the site.
    7. Define autonomous routines – Program the bot to perform:
      • Daily SEO tweaks (e.g., meta‑tag updates, internal linking).
      • Weekly CEO‑style progress updates.
      • Regular bug checks and feedback monitoring.
      • Newsletter generation and dispatch via Recent.
    8. Build distribution – Begin posting regularly on X (Twitter) about the business, even with a modest follower count, to drive traffic and create a lasting moat.
    9. Launch and monitor – Publish the site, let the bot execute its routines, and watch for sponsorship inquiries or revenue notifications from Stripe.
    10. Share results – Post the live agentic business link in the video comments for potential promotion by the creator.

    Tools and Numbers Mentioned

    • Revenue: $1,100 earned in one day from two sponsorships (Pain AI and Lasso Finance).
    • Site traffic: Approximately 56,000 visitors, 123,000 views, and 2,000 newsletter subscribers.
    • Platforms/services: Rock Bot (AI agent), Versel (hosting), GitHub (code repository), Recent (email automation), Stripe (payments).
    • Key quote from the video:

      agentic income

      and

      Distribution is one of the last remaining modes

      .

    Caveats / Hype Check

    The $1,100 figure reflects two specific sponsorship deals, not passive income generated solely by the site. Earnings depend on attracting sponsors and sustaining traffic, which may not be replicable for every user. While the video claims no sponsorship from Rock Bot, it highlights the platform heavily, potentially overstating the ease of achieving consistent “agentic income.” Ongoing tasks such as niche selection, content quality, and network building still require attention, even if the bot handles many technical updates.

    Concrete Next Actions

    • Select an AI agent platform and create a new bot.
    • Assign the bot the CEO role and input the core prompt.
    • Provision a free Versel host and link it to a GitHub repo.
    • Configure Recent for automated newsletters and Stripe for payment acceptance.
    • Define the bot’s daily, weekly, and ongoing maintenance routines.
    • Begin a modest X (Twitter) posting schedule to build distribution.
    • Launch the site, monitor sponsorship inquiries, and iterate based on performance.
    • Share your live link in the video comments for community feedback and possible promotion.

  • Jev 讓你的 Claude Code 強 10 倍？

    Watch on YouTube: https://www.youtube.com/watch?v=_yFen1B8hdU

    Channel: Gary Chen

    Overview

    The video from Gary Chen demonstrates how to augment Claude Code with the Jev model—a lightweight “System 1” model that returns option probabilities instantly and at negligible cost. By treating Jev as an intuitive reflex layer for decisions such as model routing, skill selection, bulk data classification, and automated code verification, users can achieve substantial latency and cost reductions while preserving output quality.

    What the Video Covers

    • Explanation of Jev as a fast, free System 1 model suited for rapid decision nodes.
    • How to integrate Jev into Claude Code using a TypeSafe API key (or OpenRouter) and instructing Claude to consult Jev for model and skill selection.
    • Quantitative benefits: up to 70 % cost savings, skill‑selection time dropping from ~30 seconds (Opus) to <5 seconds, and error‑rate improvement from 17 % to 7.3 % with large skill libraries.
    • Bulk‑data example: classifying 1,400 YouTube comments takes seconds for a few cents with Jev versus 34 minutes and $23 with Opus.
    • Automated code‑verification workflows enabled by Jev, such as semantic linters, code‑base scans, 100‑question pre‑reviews, and adversarial testing, all running at sub‑cent costs.
    • Community validation showing Jev’s judgment accuracy matches or exceeds Opus in closed‑classification scenarios.
    • References to ready‑made resources: the shipwithjev directory and the Gary AI Bootcamp for deeper integration guides.

    Step‑by‑Step Walkthrough

    1. Obtain a Jev API key – Register on the TypeSafe website (or use OpenRouter) to receive a key that grants access to the Jev model.
    2. Configure Claude Code – Add the API key and the Jev documentation URL to Claude Code’s settings. Then prompt Claude to create a “Jev switch” that delegates model‑routing and skill‑selection decisions to Jev.
    3. Test the switch – Run a set of typical prompts with the Jev switch enabled and disabled. Compare token usage, latency, and output quality to gauge the impact.
    4. Apply to large‑scale classification – Use Jev for tasks such as tagging YouTube comments, lead scoring, or any repetitive decision‑making workload. Measure the time and cost; the video reports a reduction from 34 minutes/$23 to a few seconds/few cents for 1,400 items.
    5. Experiment with code verification – Leverage Jev to drive semantic linters, annotation scans, a 100‑question pre‑review suite, or adversarial browser tests. These checks run at negligible expense (e.g., 0.4 cents per run) while maintaining reliability.
    6. Explore community workflows – Browse the shipwithjev directory for ready‑made examples and import relevant snippets into your Claude Code setup.
    7. Identify repetitive decision steps – Review past Claude conversations to pinpoint frequent model‑ or skill‑choice points that could be offloaded to Jev.
    8. Monitor and tune – Track accuracy and cost over time. Adjust Jev prompts or confidence thresholds as needed before relying on it for production‑critical workloads.

    Tools, Numbers, and Resources Mentioned

    • TypeSafe website – source for Jev API key.
    • OpenRouter – alternative gateway for Jev access.
    • shipwithjev directory – community‑shared workflows.
    • Gary AI Bootcamp – deeper integration guide.
    • Cost metrics: up to 70 % saved, 54 % cost drop reported in tests, few‑cent expense for bulk jobs versus $23 with Opus.
    • Time metrics: skill selection <5 seconds vs ~30 seconds (Opus); 1,400‑comment classification in seconds vs 34 minutes.
    • Error‑rate improvement: from 17 % to 7.3 % with large skill libraries.
    • Scale examples: 1400 questions, 145/182 skills, 100‑question pre‑review, 227 API calls, etc.

    Caveats and Hype Check

    Claims of 70 % cost reduction and near‑zero expense are based on limited community tests; viewers should verify these savings on their own workflows before fully depending on Jev.

    The presenter advises treating the reported figures as indicative rather than guaranteed. Actual savings will depend on task complexity, prompt design, and the specific pricing of the underlying models used alongside Jev. It is prudent to run controlled A/B tests (switch on/off) and monitor both output fidelity and expenditure before scaling to production.

    Concrete Next Actions

    • Register on TypeSafe (or OpenRouter) to secure a Jev API key.
    • Add the key and Jev docs to Claude Code and instruct it to build a Jev switch for model/skill routing.
    • Run baseline tests: execute your usual prompts with the switch off, then on, and record token usage, latency, and quality.
    • Deploy Jev for a high‑volume classification task (e.g., comment tagging) and compare the measured time/cost against the Opus baseline.
    • Set up a Jev‑driven code‑verification pipeline (semantic lint, 100‑question review, adversarial test) and verify that costs stay in the sub‑cent range.
    • Import relevant examples from the shipwithjev directory into your Claude Code environment.
    • Audit past Claude interactions to locate repetitive decision points suitable for Jev offloading.
    • Continuously monitor accuracy and expense; tweak Jev prompts or confidence thresholds as needed before committing to production use.