正在加载视频...

视频加载失败

I just one-shotted a 3D world with proper collision physics using the SpAItial AI API and PlayCanvas Here's how i did it: -> Install the spaitial-playcanvas-world skill: npx skills add spaitial-dev/spaitial-playcanvas-world -> Open Cursor or your preferred coding agent -> Paste the following prompt or use your own: "Using...

22,266 次观看 • 1 个月前 •via X (Twitter)

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

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,840 次观看 • 1 个月前

Start building for an agent-first world. If you have a product, you need to start offering skills for Claude, Codex, Cursor, and any other agents. Your skills should specify: • How to navigate and use your product • Best practices the agent must follow • Detailed instructions on how to accomplish things • Anti-patterns to avoid Redis is one of the most popular in-memory data stores in the world, and they just released their agent skills. It takes one second to install, and it will turn your agent into a Senior Redis Engineer: $ npx skills add redis/agent-skills In the attached video, I show you how to install it as a plugin in Claude Code and some of its benefits. This is the easiest way to "teach" models what they don't know and keep their knowledge up to date. If you ask me, skills is literally one of the most brilliant ideas that Anthropic has put out there. If you use Redis, their skill is a must-have. If you don't, this skill will show you how to build and structure yours. Here is what their skill teaches your agent: 1. Current patterns for common use cases: caching, rate limiting, session management, vector search, semantic caching, pub/sub, streams. 2. Which data structure to use and when: hashes vs. JSON vs. sorted sets vs. vector sets. 3. Anti-patterns to avoid: no KEYS in loops, no unbounded key growth, no large values that amplify every operation. 4. Production-aware defaults: connection pooling, pipelining, cluster compatibility, error handling that doesn't silently swallow failures.

Santiago

37,546 次观看 • 4 个月前

F it, full automated money making now on Larrybrain. I have released the app template I use for Snugly that generated me revenue without touching anything on Larrybrain. The template gives your agent ideas of what the app can become and how to create it. Most importantly, it will give your openclaw agent full context of your app to automate your marketing with Larry's viral marketing skill - now used by over 5500 agents. It is my entire playbook from app, to marketing all the way down to revenue generation. All you have to do is ask your agent "install the larrybrain skill please" Or click the link in replies. Then ask to use the Larry marketing skill with the AI Image App Template. As always, the best part about any of the Openclaw skills is they are not a black box. This is just a template, you can rip it apart and customise it how you want. The key is to show you what is possible with these skills and how you can start to use the power of larrybrain and the context of knowing about the different skills to build extremely powerful and useful tools. This is the first skill specifically designed to work hand in hand with another. To note as this confuses a lot of people: Larrybrain doesn't download the entire marketplace once installed. It just is aware of everything on the marketplace at all times, so when you ask it questions, it can search and find the best skills for you to achieve your goals. When you download some skills, like this new AI image app template, it is aware of the larry marketing skill to help it reach it's full potential. Larrybrain will not install skills without you asking it, just like on Clawhub. No information you add to any of the skills gets sent back through Larrybrain, this is all hosted locally and communicated between you and whatever endpoint you are using. It is a powerful marketplace tool to help enable you to reach your goals. Link below.

Oliver Henry

110,044 次观看 • 4 个月前

how to use Google's NEW open source Design.md + AI Skills to make your startup look like a $100 million company in 1 hour: 1. Design.md is an open source file from Google that captures the soul of a design. Typography, colors, spacing, all in one markdown file. You attach it to your prompt and your agent builds beautiful things every time. 2. Think of it this way. The HTML is the finished dish. The design.md is the recipe. The skills are the ingredients. Put them together and everything you build looks consistent and professional. 3. Don't create a design system from scratch. Find a brand you love. Linear, Stripe, Vercel, whatever resonates. Study it. Use ChatGPT or Claude to help you extract the design language into your own design.md file. 4. Build skills on top of your design.md. A landing page skill. A mobile app skill. A motion design skill. A slide deck skill. Each one references the same design.md so everything looks like it came from the same designer. 5. The biggest mistake people make: they nail one screen and then everything else looks generic. Design.md solves this. One file keeps every page, every format, every medium consistent. 6. Use it across everything. Your landing page. Your app. Your pitch deck. Your promo videos. Same DNA. Same taste. Same system. That's what separates a startup that looks real from one that looks vibe-coded. 7. Build a second brain for design inspiration. When you see something beautiful in the real world or online, capture it. Save it. When you're building something new, reference it. Taste is developed, not downloaded. 8. It's obvious but the difference between a product people trust and a product people bounce from is how it looks and feels. Design.md gives you that edge. you can watch below shoutout to Meng To for coming on The Startup Ideas Podcast (SIP) 🧃 and walking through his full workflow. if you want to use AI to actually build gorgeous designs, you'll want to use see this. watch

GREG ISENBERG

506,010 次观看 • 2 个月前

🚀 Announcing Echo — our new frontier model for 3D world generation. Echo turns a simple text prompt or image into a fully explorable, 3D-consistent world. Instead of disconnected views, the result is a single, coherent spatial representation you can move through freely. This is part of a bigger shift in AI: from generating pixels and tokens to generating spaces. Echo predicts a geometry-grounded 3D scene at metric scale, meaning every novel view, depth map, and interaction comes from the same underlying world — not independent hallucinations. Once generated, the world is interactive in real time. You control the camera, explore from any angle, and render instantly — even on low-end hardware, directly in the browser. High-quality 3D world exploration is no longer gated by expensive equipment. Under the hood, Echo infers a physically grounded 3D representation and converts it into a renderable format. For our web demo, we use 3D Gaussian Splatting (3DGS) for fast, GPU-friendly rendering — but the representation itself is flexible and can be easily adapted. Why this matters: consistent 3D worlds unlock real workflows — digital twins, 3D design, game environments, robotics simulation, and more. From a single photo or a line of text, Echo builds worlds that are reliable, editable, and spatially faithful. Echo also enables scene editing and restyling. Change materials, remove or add objects, explore design variations — all while preserving global 3D consistency. Editing no longer breaks the world. This is only the beginning. Echo is the foundation for future world models with dynamics, physical reasoning, and richer interaction — environments that don’t just look right, but behave right. Explore the generated worlds on our website and sign up for the closed beta. The era of spatial intelligence starts here. 🌍 #Echo #WorldModels #SpatialAI #3DFoundationModels Check it out:

SpAItial AI

176,105 次观看 • 7 个月前

Claude Cowork + Seedance 2.0 is f*cking wild 🤯 I built a skill inside Claude Cowork that generates UGC video ads on demand using Seedance 2.0, the best AI video model. One product image + one prompt = a full UGC ad with multiple shots, dialogue, and on-brand pacing. All inside Claude Cowork. Perfect for DTC brands and agencies who need UGC creative at volume without hiring creators or paying per-video SaaS fees. If you're briefing creators every week, waiting days for footage, paying $150–$300 per UGC video, and still getting ads that miss the brand vibe... This skill eliminates the entire loop: → Drop a product image into Claude Cowork → Tell it the ad angle (unboxing, review, lifestyle, demo) → Claude writes the dialogue, shot list, and pacing → Fires it to Seedance 2.0 via FAL AI API → Downloads finished clips into organized folders → Stitches multiple shots into one finished ad No creator briefs. No waiting for footage. No $200/video platform fees. What you get: → UGC video ads generated in minutes, not days → Full control over dialogue, pacing, and shot composition → Your product photos as reference so Seedance matches your real packaging → A reusable skill: new product, new folder, same pipeline Built 100% in Claude Cowork with the Seedance 2.0 API. I put together a full playbook with the Claude Cowork skill file, the exact prompts, and the FAL AI setup to get this running yourself. Want it for free? > Like this post > Comment "UGC" And I'll send it over (must be following so I can DM)

Mike Futia

79,770 次观看 • 3 个月前

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 次观看 • 3 个月前

Fast Company just published a great piece on World Labs , Fei-Fei Li , Marble, and the idea that spatial intelligence / world models may be one of the next big shifts in AI. I was happy to be quoted in the article, but I also wanted to share more context about my own experience with World Labs and Marble, and why this direction is especially interesting to me. My starting point: volumetric capture — For the past few years I’ve been exploring and using volumetric capture and reconstruction (photogrammetry, NeRFs, 3D Gaussian Splats) mostly capturing locations around Montreal. Alleys, museums, urban interiors. I love every step of it: the capture itself, the pipeline, and what can be done with the output. Turning real spaces into real-time explorable systems. I do this personally, sharing explorations here, and professionally as chief technologist, and co-founder of Dpt. Physical reality + generative manipulation — In my work I’m especially drawn to mixing physical reality with generative and digital manipulation: using physical interfaces (light, clay, ink, ... ) to drive generative AI pipelines, building mixed reality prototypes that reshape your surroundings, or starting from real captured spaces and transforming them using tools like Marble. Like many people, I saw the World Labs announcement on Twitter in September 2024, and Marble when it surfaced in early December. But by then, I already had a sense something was coming. The first conversation — As someone deep into volumetric capture and radiance fields, I obviously knew about Ben Mildenhall and his pioneering work on NeRF. To my surprise, Ben reached out to me in late June 2024. He’d been following some of my experiments and wanted to chat about my process and workflows and how I was using this “stuff” creatively. At that point he didn’t share what he was building, but we had a genuinely great conversation about radiance fields, AI, and my work. He was curious about the creative perspective, not just the technical one. When the World Labs announcement dropped a few months later, it all made sense. I understood what Ben had been working on, and why the creative angle mattered to them. Then in August 2025, he invited me to try the Marble beta, and I’ve been experimenting with it since. Experimenting with Marble — The first thing I used Marble for was materializing scene and world concepts during ideation at the studio, and seeing if and how it could fit into our production pipeline. In parallel, I dove into a series of experiments focused on world manipulation: starting from real captured spaces and transforming them using Marble. I’d already been exploring that idea using img2img diffusion with ControlNet on NeRF renders, real-time video streams, and even mixed reality using headset camera feeds. But Marble brings something different. It generates persistent, spatially cohesive 3D worlds that can be rendered in real time across a wide range of devices. That’s a real shift. Experiment 01: Parallel Realities — The first experiment, Parallel Realities, starts from a volumetric capture of a real location, reconstructed as 3D Gaussian Splats. Using Marble, I generate an alternate version of that same space, something informed by the original architecture: abandoned, nature-reclaimed, alternate era. Then, using Spark (World Labs’ 3D Gaussian Splatting renderer for THREE.js) I make both realities coexist in the same spatial coordinate system. From there, I use a portal UX mechanic to let the user step between the real reconstruction and the Marble-generated version. Experiment 02: Hidden Depth The second experiment, Hidden Depth, does not transform a space as much as expand it. A captured location has a visual boundary (a mural, a doorway, a dark corridor) and Marble generates what exists beyond it. For example: a Montreal alley has a painted mural; step through it and you’re inside a world informed by what is actually depicted there. World Labs showcased part of this work here: And in their Spark 2.0 post: The project page is here: Why this matters to me — Being able to start from a real 3D Gaussian Splat scene and manipulate it with Marble opens up a lot of ideas. The 3DGS pipeline is becoming an increasingly compelling foundation for exploration, experimentation, and storytelling. What matters most to me right now is more control. The more I can steer the generated scene or world, the more useful the tool becomes. I want more features like the already existing multiple input images and Chisel, the blockout-based approach. I would like better local control, the ability to expand a generated world more and more while preserving coherence, and the ability to directly import 3D Gaussian Splat scenes to be used as a starting point. I want more ways to shape the result, not just a “prompt and hope” approach. — It is exciting to see this field moving from research and demos toward actual creative workflows.

Hugues Bruyère

65,393 次观看 • 1 个月前