Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

A Luma Skill turns your best result into a repeatable workflow. Build it once, run it on any asset, reach the same quality every time. The craft stays consistent as it scales. Try Luma Skills:

LumaLabsAI's profile picture

Luma

197,431 subscribers

22,350 görüntüleme • 2 ay önce •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

/scandinavian-design built a skill that turns any site into scandi minimalism! npx skills add ericzakariasson/scandinavian-design try it:
0:28

/scandinavian-design built a skill that turns any site into scandi minimalism! npx skills add ericzakariasson/scandinavian-design try it:

eric zakariasson

201,352 görüntüleme • 4 gün önce

Seal on Sui turns any file into a smart asset. Gate it, rent it, or sell it on your own terms, all enforced on chain. And the best part: it works across chains.
1:34

Seal on Sui turns any file into a smart asset. Gate it, rent it, or sell it on your own terms, all enforced on chain. And the best part: it works across chains.

Adeniyi.sui

48,563 görüntüleme • 1 yıl önce

Introducing the /autobrowse skill (inspired by Andrej Karpathy's autoresearch harness) Ask your agent to perform any task on the web: it explores the page using the Browserbase CLI, learns what went wrong in previous attempts, and iterates until it converges on a reliable workflow. Once token usage is optimized, it graduates the winning approach into a reusable skill for your browser.
0:25

Introducing the /autobrowse skill (inspired by Andrej Karpathy's autoresearch harness) Ask your agent to perform any task on the web: it explores the page using the Browserbase CLI, learns what went wrong in previous attempts, and iterates until it converges on a reliable workflow. Once token usage is optimized, it graduates the winning approach into a reusable skill for your browser.

Shrey Pandya

231,003 görüntüleme • 4 ay önce

This is huge!! Spline now supports Gaussian splats 👀 You can now capture anything in 3D from your phone with Luma, export the .ply file, import it into spline, crop, adjust, and embed on your site. Luma + Spline + Webflow is an insane 3D workflow 🔥
0:37

This is huge!! Spline now supports Gaussian splats 👀 You can now capture anything in 3D from your phone with Luma, export the .ply file, import it into spline, crop, adjust, and embed on your site. Luma + Spline + Webflow is an insane 3D workflow 🔥

Nick St. Pierre

1,139,944 görüntüleme • 2 yıl önce

Introducing Workflows in Runway Agent. Now you can build, run or edit your node-based workflows through natural language. Workflows unlock high quality outputs at scale. Try it now by calling the / Workflow skill at the link below.
0:37

Introducing Workflows in Runway Agent. Now you can build, run or edit your node-based workflows through natural language. Workflows unlock high quality outputs at scale. Try it now by calling the / Workflow skill at the link below.

Runway

47,984 görüntüleme • 1 ay önce

A node graph for the entire video pipeline, from brainstorm to final cut, built for scalable content production. Build a workflow once, run it forever, fork it into any project, and share it across your team with ctrl c + ctrl v. Every production agency we work with asked for Canvas, so here we go.
0:35

A node graph for the entire video pipeline, from brainstorm to final cut, built for scalable content production. Build a workflow once, run it forever, fork it into any project, and share it across your team with ctrl c + ctrl v. Every production agency we work with asked for Canvas, so here we go.

Higgsfield AI 🧩

150,335 görüntüleme • 3 ay önce

xAI is rolling out Skills on This new feature lets you create custom skills that Grok can reuse across conversations. Skills run inside Grok’s sandbox environment, so they can edit files, use your Connectors (Gmail, GitHub, Notion, etc.), run code, or perform any repeatable task you define. Once you create one, you simply tell Grok “use the [skill name] skill and do…” and it executes it instantly. You can also import skills.md files from other AI tools to bring them over quickly. It turns Grok from a one-shot chat tool into a more persistent, customizable workspace. This is a huge upgrade for anyone who uses Grok regularly.
1:16

xAI is rolling out Skills on This new feature lets you create custom skills that Grok can reuse across conversations. Skills run inside Grok’s sandbox environment, so they can edit files, use your Connectors (Gmail, GitHub, Notion, etc.), run code, or perform any repeatable task you define. Once you create one, you simply tell Grok “use the [skill name] skill and do…” and it executes it instantly. You can also import skills.md files from other AI tools to bring them over quickly. It turns Grok from a one-shot chat tool into a more persistent, customizable workspace. This is a huge upgrade for anyone who uses Grok regularly.

Myrhe𝕩

878,498 görüntüleme • 3 ay önce

Today we're launching Arcads in Claude. One skill turns it into a full ad agency: > Drop a product URL: a complete ad set comes back, ready to run > Drop any winning ad: it recreates it for your brand > It re-rolls its own weak ads before you ever see them Comment "SKILLS" and I'll send you the entire skill library.
0:28

Today we're launching Arcads in Claude. One skill turns it into a full ad agency: > Drop a product URL: a complete ad set comes back, ready to run > Drop any winning ad: it recreates it for your brand > It re-rolls its own weak ads before you ever see them Comment "SKILLS" and I'll send you the entire skill library.

Romain Torres

30,829 görüntüleme • 26 gün önce

130+ skills are now built into your Superagent. Some are ready to use, and some can be created based on what you need. Add a skill once, and your Superagent can use it as part of your workflows. Stack skills, connect tools, and build flows that run end-to-end.
0:32

130+ skills are now built into your Superagent. Some are ready to use, and some can be created based on what you need. Add a skill once, and your Superagent can use it as part of your workflows. Stack skills, connect tools, and build flows that run end-to-end.

Base44

1,860,387 görüntüleme • 4 ay önce

Today we're excited to launch dynamic workflows! Define a workflow as JSON, and Mastra will validate, register, and run it (like any other workflow). Now agents can build workflows on-the-fly:
0:36

Today we're excited to launch dynamic workflows! Define a workflow as JSON, and Mastra will validate, register, and run it (like any other workflow). Now agents can build workflows on-the-fly:

Sam Bhagwat

33,579 görüntüleme • 13 gün önce

My whole company runs on skills I bundled into a GitHub repo. Here's how to build the same thing for your team: - Put your skills in a GitHub repo - Get Claude to write the couple of JSON files that make it readable as a plugin - In Claude Code, type /plugin, go to marketplaces, add marketplace, paste your repo URL - Split the plugins by department, so your copywriter isn't installing the finance skills It works in Codex too. I've got the same team skills installed there and I use them the same way. Now when I build something like my Notion formatting skill, I add it to the repo and it lands on everyone's Claude and Codex. If someone wrecks a skill, we roll it back to an older version. The key is enabling auto-update, so when someone improves a skill everyone benefits. I don't have a clue how the JSON works. I got Claude to set the whole thing up for me. Start with one skill and before you know it your whole team will be AI pilled.
5:18

My whole company runs on skills I bundled into a GitHub repo. Here's how to build the same thing for your team: - Put your skills in a GitHub repo - Get Claude to write the couple of JSON files that make it readable as a plugin - In Claude Code, type /plugin, go to marketplaces, add marketplace, paste your repo URL - Split the plugins by department, so your copywriter isn't installing the finance skills It works in Codex too. I've got the same team skills installed there and I use them the same way. Now when I build something like my Notion formatting skill, I add it to the repo and it lands on everyone's Claude and Codex. If someone wrecks a skill, we roll it back to an older version. The key is enabling auto-update, so when someone improves a skill everyone benefits. I don't have a clue how the JSON works. I got Claude to set the whole thing up for me. Start with one skill and before you know it your whole team will be AI pilled.

The Startup Ideas Podcast (SIP) 🧃

18,942 görüntüleme • 5 gün önce

Grok Build has 52 different slash commands. You’re probably not using them. Type /. Everything shows up. Shortcuts, skills, control. This is how you stop fumbling around. Use it properly: * Type /; open the command palette * /new; start fresh without dragging context * /fork; branch into a new agent, try another approach * /compact; clean the mess, keep it usable * /copy; grab the last output instantly * /skills; open your workflow layer * /quit; exit clean Skills = where it gets serious: * Open /skills; toggle what you need * Use /implement, /review, /design; one command, full workflow * Create your own; /create-skill, stop repeating yourself * Built-in vs custom; both stack * Run it again; same output, no variation One word commands. No repetition. No drift. xAI
0:32

Grok Build has 52 different slash commands. You’re probably not using them. Type /. Everything shows up. Shortcuts, skills, control. This is how you stop fumbling around. Use it properly: * Type /; open the command palette * /new; start fresh without dragging context * /fork; branch into a new agent, try another approach * /compact; clean the mess, keep it usable * /copy; grab the last output instantly * /skills; open your workflow layer * /quit; exit clean Skills = where it gets serious: * Open /skills; toggle what you need * Use /implement, /review, /design; one command, full workflow * Create your own; /create-skill, stop repeating yourself * Built-in vs custom; both stack * Run it again; same output, no variation One word commands. No repetition. No drift. xAI

Mario Nawfal

55,877 görüntüleme • 2 ay önce

Build it once. Earn every time someone uses it. Wrap your workflow with input and output nodes, hit publish, and your one-click app goes live to millions of creators. You choose how it lives: Keep it private, share with your team, or let the whole community run it. And every single time someone runs your app? Credits land in your account. No extra work. No maintenance. Just your creativity quietly paying you back, on repeat. Your workflow. Your rules. Your credits.
0:40

Build it once. Earn every time someone uses it. Wrap your workflow with input and output nodes, hit publish, and your one-click app goes live to millions of creators. You choose how it lives: Keep it private, share with your team, or let the whole community run it. And every single time someone runs your app? Credits land in your account. No extra work. No maintenance. Just your creativity quietly paying you back, on repeat. Your workflow. Your rules. Your credits.

ImagineArt

323,644 görüntüleme • 3 ay önce

this video is the CLEAREST explanation of how claude skills + AI agents work and how to use them most people set up an AI agent and wonder why it keeps disappointing them. the context window is everything context is what the model assembles before it takes any action. think of it like everything the agent needs to read before it does anything. the quality of what goes in determines the quality of what comes out. the models are genuinely really good right now. claude and gpt are exceptional. the variable is almost always the context you give them. 1. agent.md files are mostly unnecessary every single line you put in an agent.md file gets added to every single conversation you have with your agent. a 1000 line file is around 7000 tokens burning on every run. the model already knows to use react. it can read your codebase. save the agent.md for proprietary information specific to your company that the model genuinely cannot know on its own. 2. skills are the actual unlock a skill.md file works differently. what loads into context is only the name and description, around 50 tokens. the full instructions only appear when the agent recognizes it needs that skill. so instead of 7000 tokens on every run you have 50. and the agent stays sharp because the context window stays lean. the closer you get to filling the context window the worse the agent performs, same way you perform worse when someone dumps 10 things on you at once. 3. here is how to actually build a skill the right way most people identify a workflow and immediately try to write the skill. what you want to do instead is run the workflow by hand with the agent first. walk it through every single step. tell it what to check, what good looks like, what bad looks like. correct it in real time. once you have had a full successful run from start to finish, tell the agent to review everything it just did and write the skill itself. it writes a better skill than you will because it has the full context of what actually worked in practice not in theory. 4. recursively building skills is how you go from frustrated to reliable when the skill breaks, and it will break, ask the agent exactly why it failed. it will tell you specifically what went wrong. fix it together in that same conversation. then tell it to update the skill file so that failure mode never happens again. ross mike did this five times with his youtube report generator. it now pulls from eight different data sources and runs flawlessly every single time without him touching it. 5. sub agents are something you earn not something you set up on day one start with one agent. build one workflow. turn it into one skill. once that works add another. ross mike has five sub agents now covering marketing, business, personal and more. it took months to get there and every single one exists because a workflow proved it deserved to exist. the people who set up 15 sub agents on day one and wonder why nothing works skipped all the steps that make the thing actually run. 6. your workflow is the thing the model cannot get anywhere else the model has been trained on everything. it knows more than you about most things. what it does not have is your specific process, your taste, your way of doing things. that is what skills capture. that is what makes your agent actually useful versus a generic one. downloading someone else's skill means downloading their context onto your setup and it will not work the way you want it to because it was never built around how you work. this is the clearest explanation of how agents actually work i have heard. Micky runs this stuff every single day and the results show it. full episode is now live on The Startup Ideas Podcast (SIP) 🧃 where you get your pods people charge for this sorta stuff i give away the sauce for free i just want you to win watch
35:25

this video is the CLEAREST explanation of how claude skills + AI agents work and how to use them most people set up an AI agent and wonder why it keeps disappointing them. the context window is everything context is what the model assembles before it takes any action. think of it like everything the agent needs to read before it does anything. the quality of what goes in determines the quality of what comes out. the models are genuinely really good right now. claude and gpt are exceptional. the variable is almost always the context you give them. 1. agent.md files are mostly unnecessary every single line you put in an agent.md file gets added to every single conversation you have with your agent. a 1000 line file is around 7000 tokens burning on every run. the model already knows to use react. it can read your codebase. save the agent.md for proprietary information specific to your company that the model genuinely cannot know on its own. 2. skills are the actual unlock a skill.md file works differently. what loads into context is only the name and description, around 50 tokens. the full instructions only appear when the agent recognizes it needs that skill. so instead of 7000 tokens on every run you have 50. and the agent stays sharp because the context window stays lean. the closer you get to filling the context window the worse the agent performs, same way you perform worse when someone dumps 10 things on you at once. 3. here is how to actually build a skill the right way most people identify a workflow and immediately try to write the skill. what you want to do instead is run the workflow by hand with the agent first. walk it through every single step. tell it what to check, what good looks like, what bad looks like. correct it in real time. once you have had a full successful run from start to finish, tell the agent to review everything it just did and write the skill itself. it writes a better skill than you will because it has the full context of what actually worked in practice not in theory. 4. recursively building skills is how you go from frustrated to reliable when the skill breaks, and it will break, ask the agent exactly why it failed. it will tell you specifically what went wrong. fix it together in that same conversation. then tell it to update the skill file so that failure mode never happens again. ross mike did this five times with his youtube report generator. it now pulls from eight different data sources and runs flawlessly every single time without him touching it. 5. sub agents are something you earn not something you set up on day one start with one agent. build one workflow. turn it into one skill. once that works add another. ross mike has five sub agents now covering marketing, business, personal and more. it took months to get there and every single one exists because a workflow proved it deserved to exist. the people who set up 15 sub agents on day one and wonder why nothing works skipped all the steps that make the thing actually run. 6. your workflow is the thing the model cannot get anywhere else the model has been trained on everything. it knows more than you about most things. what it does not have is your specific process, your taste, your way of doing things. that is what skills capture. that is what makes your agent actually useful versus a generic one. downloading someone else's skill means downloading their context onto your setup and it will not work the way you want it to because it was never built around how you work. this is the clearest explanation of how agents actually work i have heard. Micky runs this stuff every single day and the results show it. full episode is now live on The Startup Ideas Podcast (SIP) 🧃 where you get your pods people charge for this sorta stuff i give away the sauce for free i just want you to win watch

GREG ISENBERG

193,721 görüntüleme • 4 ay önce

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
51:01

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

509,941 görüntüleme • 3 ay önce

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
0:42

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 görüntüleme • 2 ay önce

Teach an agent a workflow once. Have it remember after every rebuild. This tutorial shows how to deploy Nous Research Hermes Agent with NVIDIA NemoClaw and OpenShell, connect it to Slack, Outlook, GitHub, and NVIDIA developer forums, then turn a chat correction into a reusable skill. Private data stays behind runtime policies. Learned skills persist across deployments.
5:02

Teach an agent a workflow once. Have it remember after every rebuild. This tutorial shows how to deploy Nous Research Hermes Agent with NVIDIA NemoClaw and OpenShell, connect it to Slack, Outlook, GitHub, and NVIDIA developer forums, then turn a chat correction into a reusable skill. Private data stays behind runtime policies. Learned skills persist across deployments.

NVIDIA AI

70,337 görüntüleme • 2 ay önce

Show Codex a workflow once. Reuse it as a skill. Record & Replay lets you show Codex a recurring task, like filing an expense report or submitting a time-off request. Codex turns that demo into an inspectable, editable skill. You control when recording starts and stops.
2:04

Show Codex a workflow once. Reuse it as a skill. Record & Replay lets you show Codex a recurring task, like filing an expense report or submitting a time-off request. Codex turns that demo into an inspectable, editable skill. You control when recording starts and stops.

OpenAI Developers

4,659,132 görüntüleme • 2 ay önce

Every company needs killer Skills library. Not a folder in GitHub that 10% of the company knows how to use. A living library the whole company benefits from. The best deal review skill gets better every time a sales rep uses it. A great research skill gets discovered instead of rebuilt 50 times. Creating a skill should be as easy as asking to create something useful from based on the context of your work. And the top skills (and skill creators) should rise to the top. Create, share, collaborate on, discover and understand usage of skills, organize them into databases by team or use case, then use them across any of your agents. Still early, but the idea is to make Notion the best home for your company’s collective AI skills. Made a quick demo (all available now)!
1:59

Every company needs killer Skills library. Not a folder in GitHub that 10% of the company knows how to use. A living library the whole company benefits from. The best deal review skill gets better every time a sales rep uses it. A great research skill gets discovered instead of rebuilt 50 times. Creating a skill should be as easy as asking to create something useful from based on the context of your work. And the top skills (and skill creators) should rise to the top. Create, share, collaborate on, discover and understand usage of skills, organize them into databases by team or use case, then use them across any of your agents. Still early, but the idea is to make Notion the best home for your company’s collective AI skills. Made a quick demo (all available now)!

Hurley

651,834 görüntüleme • 4 gün önce

This is an AI video. Made with Luma Luma Ray3. For the past couple of weeks, I've played with it, and I tried to give it the most challenging, but also very natural scenes. The result is unbelievable. Take a moment to realize that this is an AI video in 2025:
3:08

This is an AI video. Made with Luma Luma Ray3. For the past couple of weeks, I've played with it, and I tried to give it the most challenging, but also very natural scenes. The result is unbelievable. Take a moment to realize that this is an AI video in 2025:

Alex Patrascu

98,610 görüntüleme • 11 ay önce