Загрузка видео...

Не удалось загрузить видео

На главную

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...

MarioNawfal's profile picture

Mario Nawfal

3,595,527 subscribers

55,754 просмотров • 20 дней назад •via X (Twitter)

Наука и технологии
LIVE

Anya Rossi• Live Now

Private livecam show

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

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𝕩

876,663 просмотров • 1 месяц назад

Garry Tan (CEO of Y-Combinator): "when someone asks how I 'prompt' my AI, the answer is: I don't. the skills are the prompts." [if I had this weekend to master skills and how to use them to automate workflows:] → read the Skillify 11-item checklist (SKILL.md in gbrain) → watch Murag + Barry Zhang: "Don't Build Agents. Build Skills Instead." → Read "Designing, Refining, and Maintaining Agent Skills at Perplexity" → do one workflow. type /skillify. watch it become permanent. that's the whole day. here is how to set it up: 1. clone GBrain (his open-source second brain, Postgres-backed memory + 30 skills) 2. add GStack (23 battle-tested slash-command skills, drops right in) 3. do anything once → type /skillify → it's a skill forever prompting is dead. skillifying is next.
2:16

Garry Tan (CEO of Y-Combinator): "when someone asks how I 'prompt' my AI, the answer is: I don't. the skills are the prompts." [if I had this weekend to master skills and how to use them to automate workflows:] → read the Skillify 11-item checklist (SKILL.md in gbrain) → watch Murag + Barry Zhang: "Don't Build Agents. Build Skills Instead." → Read "Designing, Refining, and Maintaining Agent Skills at Perplexity" → do one workflow. type /skillify. watch it become permanent. that's the whole day. here is how to set it up: 1. clone GBrain (his open-source second brain, Postgres-backed memory + 30 skills) 2. add GStack (23 battle-tested slash-command skills, drops right in) 3. do anything once → type /skillify → it's a skill forever prompting is dead. skillifying is next.

Avid

192,630 просмотров • 12 дней назад

Garry Tan (CEO of Y-Combinator): "when someone asks how I 'prompt' my AI, the answer is: I don't. the skills are the prompts." [if I had 7 days to master skills and how to use them to automate workflows:] → read the Skillify 11-item checklist (SKILL.md in gbrain) → watch Murag + Barry Zhang: "Don't Build Agents. Build Skills Instead." → Read "Designing, Refining, and Maintaining Agent Skills at Perplexity" → do one workflow. type /skillify. watch it become permanent. that's the whole day. here is how to set it up: 1. clone GBrain (his open-source second brain, Postgres-backed memory + 30 skills) 2. add GStack (23 battle-tested slash-command skills, drops right in) 3. do anything once → type /skillify → it's a skill forever prompting is dead. skillifying is next.
2:16

Garry Tan (CEO of Y-Combinator): "when someone asks how I 'prompt' my AI, the answer is: I don't. the skills are the prompts." [if I had 7 days to master skills and how to use them to automate workflows:] → read the Skillify 11-item checklist (SKILL.md in gbrain) → watch Murag + Barry Zhang: "Don't Build Agents. Build Skills Instead." → Read "Designing, Refining, and Maintaining Agent Skills at Perplexity" → do one workflow. type /skillify. watch it become permanent. that's the whole day. here is how to set it up: 1. clone GBrain (his open-source second brain, Postgres-backed memory + 30 skills) 2. add GStack (23 battle-tested slash-command skills, drops right in) 3. do anything once → type /skillify → it's a skill forever prompting is dead. skillifying is next.

Avid

271,600 просмотров • 1 месяц назад

🧠 Want to give your coding agent new capabilities? Use Agent Skills in Visual Studio Code! Agent skills let you package instructions and resources into reusable capabilities for your agent. Skills can be loaded on demand and called directly from chat using slash commands like /skill-name. Learn more:
0:26

🧠 Want to give your coding agent new capabilities? Use Agent Skills in Visual Studio Code! Agent skills let you package instructions and resources into reusable capabilities for your agent. Skills can be loaded on demand and called directly from chat using slash commands like /skill-name. Learn more:

Visual Studio Code

55,115 просмотров • 3 месяцев назад

Important new course: Agent Skills with Anthropic, built with Anthropic and taught by Elie Schoppik! Skills are constructed as folders of instructions that equip agents with on-demand knowledge and workflows. This short course teaches you how to create them following best practices. Because skills follow an open standard format, you can build them once and deploy across any skills-compatible agent, like Claude Code. What you'll learn: - Create custom skills for code generation and review, data analysis, and research - Build complex workflows using Anthropic's pre-built skills (Excel, PowerPoint, skill creation) and custom skills - Combine skills with MCP and subagents to create agentic systems with specialized knowledge - Deploy the same skills across Claude Code, the Claude API, and the Claude Agent SDK Join and learn to equip agents with the specialized knowledge they need for reliable, repeatable workflows.
1:59

Important new course: Agent Skills with Anthropic, built with Anthropic and taught by Elie Schoppik! Skills are constructed as folders of instructions that equip agents with on-demand knowledge and workflows. This short course teaches you how to create them following best practices. Because skills follow an open standard format, you can build them once and deploy across any skills-compatible agent, like Claude Code. What you'll learn: - Create custom skills for code generation and review, data analysis, and research - Build complex workflows using Anthropic's pre-built skills (Excel, PowerPoint, skill creation) and custom skills - Combine skills with MCP and subagents to create agentic systems with specialized knowledge - Deploy the same skills across Claude Code, the Claude API, and the Claude Agent SDK Join and learn to equip agents with the specialized knowledge they need for reliable, repeatable workflows.

Andrew Ng

886,292 просмотров • 4 месяцев назад

This is literally the easiest way to build an AI agent. Zero code. You only need to run a couple of commands. (I've said this before, but Google ADK is my favorite way to build code-first agents.) Here is what you need to do: 1. Open your terminal and create an empty folder 2. Run `uv init` inside the folder (if you don't have uv installed, you are really missing out!) 3. Install the google-adk library using the following command: `uv add google-adk`. 4. At this point, you can use the ask to create your agent with a single command: `uv run adk create --type=config my_agent`. This will ask you a couple of questions, including your GEMINI_API_KEY (you can create one online). 5. The command above will create a my_agent/root_agent.yaml file. Open it and add the following two lines at the end of the file so your agent can use Google to search for stuff: tools: - name: google_search 6. You have everything you need now. Run the adk web interface and start playing with your agent: `uv run adk web` That's it! Literally zero code. The agent works off the YAML configuration file.
1:33

This is literally the easiest way to build an AI agent. Zero code. You only need to run a couple of commands. (I've said this before, but Google ADK is my favorite way to build code-first agents.) Here is what you need to do: 1. Open your terminal and create an empty folder 2. Run `uv init` inside the folder (if you don't have uv installed, you are really missing out!) 3. Install the google-adk library using the following command: `uv add google-adk`. 4. At this point, you can use the ask to create your agent with a single command: `uv run adk create --type=config my_agent`. This will ask you a couple of questions, including your GEMINI_API_KEY (you can create one online). 5. The command above will create a my_agent/root_agent.yaml file. Open it and add the following two lines at the end of the file so your agent can use Google to search for stuff: tools: - name: google_search 6. You have everything you need now. Run the adk web interface and start playing with your agent: `uv run adk web` That's it! Literally zero code. The agent works off the YAML configuration file.

Santiago

140,737 просмотров • 6 месяцев назад

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

494,422 просмотров • 1 месяц назад

Type ! followed by your bash command to run it instantly without leaving Claude Code. The output is injected in the context window. Saves you tokens, time, and keeps you in the flow.
0:21

Type ! followed by your bash command to run it instantly without leaving Claude Code. The output is injected in the context window. Saves you tokens, time, and keeps you in the flow.

Ado

97,255 просмотров • 4 месяцев назад

xAI just gave Grok reusable Skills. Which means you can finally stop repeating yourself like a confused office intern. Build a skill once. Grok can reuse it across chats, edit files, check Gmail, touch GitHub, run code, and handle repeat tasks on command. “Use the skill.” Done. Grok is starting to feel less like a chatbot and more like a digital employee with insomnia. Grok
0:30

xAI just gave Grok reusable Skills. Which means you can finally stop repeating yourself like a confused office intern. Build a skill once. Grok can reuse it across chats, edit files, check Gmail, touch GitHub, run code, and handle repeat tasks on command. “Use the skill.” Done. Grok is starting to feel less like a chatbot and more like a digital employee with insomnia. Grok

Mario Nawfal

32,819 просмотров • 1 месяц назад

Introducing Skills in SciSpace Agent. Specialized modes built for specific research workflows. Describe the task, and the right workflow activates automatically. Yes, the right Skill gets loaded based on what you need. Built to simplify multi-step research work and reduce friction around execution. Skills are now live. Try it inside SciSpace Agent.
0:40

Introducing Skills in SciSpace Agent. Specialized modes built for specific research workflows. Describe the task, and the right workflow activates automatically. Yes, the right Skill gets loaded based on what you need. Built to simplify multi-step research work and reduce friction around execution. Skills are now live. Try it inside SciSpace Agent.

SciSpace

43,196 просмотров • 3 месяцев назад

You can now use skills in v0. Attach one from the prompt bar, and the agent uses it in every generation. Pull them from your saved skills, or your repo.
0:30

You can now use skills in v0. Attach one from the prompt bar, and the agent uses it in every generation. Pull them from your saved skills, or your repo.

v0

44,783 просмотров • 3 дней назад

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

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

Mike Futia

31,814 просмотров • 3 месяцев назад

Extensions now support Agent Skills and Hooks! 🛠️ Gemini CLI extensions let you bundle up: 🎓- Agent Skills 🪝- Hooks 🔌- MCP servers 📝- Context files 🧑‍💻- Custom commands Install one of the 300+ extensions that are live today or build your own.
0:44

Extensions now support Agent Skills and Hooks! 🛠️ Gemini CLI extensions let you bundle up: 🎓- Agent Skills 🪝- Hooks 🔌- MCP servers 📝- Context files 🧑‍💻- Custom commands Install one of the 300+ extensions that are live today or build your own.

Gemini CLI

169,562 просмотров • 4 месяцев назад

Think of it as the Shopify of Claude Code, but for agents, commands, and MCPs 🚀 Pick what you need, “add to cart,” and… it’s 100% FREE. Just copy the command, paste it in your terminal, and instantly get the perfect Claude Code stack for your project. Built as an open-source project so the community can spin up, share, and install Claude Code stacks in seconds, no setup headaches, no paywalls. Here’s the video showing how I built this post… and yes, if you share the command, anyone can clone the exact same stack you’re using. Enjoy, share, and help others build faster with Claude Code ✨
0:59

Think of it as the Shopify of Claude Code, but for agents, commands, and MCPs 🚀 Pick what you need, “add to cart,” and… it’s 100% FREE. Just copy the command, paste it in your terminal, and instantly get the perfect Claude Code stack for your project. Built as an open-source project so the community can spin up, share, and install Claude Code stacks in seconds, no setup headaches, no paywalls. Here’s the video showing how I built this post… and yes, if you share the command, anyone can clone the exact same stack you’re using. Enjoy, share, and help others build faster with Claude Code ✨

Daniel San

124,913 просмотров • 10 месяцев назад

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

191,951 просмотров • 2 месяцев назад

Stop repeating yourself and start building skills. 🛠️ In Antigravity, creating new agent skills is as simple as a single prompt. Watch how the agent captures repetitive coding actions.
0:29

Stop repeating yourself and start building skills. 🛠️ In Antigravity, creating new agent skills is as simple as a single prompt. Watch how the agent captures repetitive coding actions.

Google Antigravity

208,470 просмотров • 4 месяцев назад

Wait did anyone catch this? Supabase just dropped Agent Skills. Your AI agent stops guessing CLI commands. Starts respecting RLS. Builds on Supabase the way Supabase is meant to be built on Claude Code. Codex. Cursor. One command, every agent. npx skills add supabase/agent-skills
0:21

Wait did anyone catch this? Supabase just dropped Agent Skills. Your AI agent stops guessing CLI commands. Starts respecting RLS. Builds on Supabase the way Supabase is meant to be built on Claude Code. Codex. Cursor. One command, every agent. npx skills add supabase/agent-skills

Sam Rome

11,865 просмотров • 1 месяц назад

Using Skills with the Claude Agent SDK How do you use skills to build agents? Here's an example demo I've built using one of our premade skills to make an excel demo agent.
1:27

Using Skills with the Claude Agent SDK How do you use skills to build agents? Here's an example demo I've built using one of our premade skills to make an excel demo agent.

Thariq

38,217 просмотров • 7 месяцев назад

Introducing... The Base Skills Repo 📙🔧 Power your Claude, Codex, OpenClaw with skills to build on Base I show in this video how I one shot a Base Pay demo in one simple prompt with the Base Account skill Use it now: npx skills add base/skills
3:30

Introducing... The Base Skills Repo 📙🔧 Power your Claude, Codex, OpenClaw with skills to build on Base I show in this video how I one shot a Base Pay demo in one simple prompt with the Base Account skill Use it now: npx skills add base/skills

Youssef

56,202 просмотров • 3 месяцев назад

Introducing Gemini CLI extensions, a new framework that allows you to customize Gemini CLI and connect it to the tools you use most—all from the command line. No more context-switching. Start using your favorite tools directly in your workflow today →
0:33

Introducing Gemini CLI extensions, a new framework that allows you to customize Gemini CLI and connect it to the tools you use most—all from the command line. No more context-switching. Start using your favorite tools directly in your workflow today →

Google Cloud Tech

80,461 просмотров • 8 месяцев назад