Video wird geladen...

Video konnte nicht geladen werden

Beim Laden dieses Videos ist ein Problem aufgetreten. Dies könnte an einem vorübergehenden Netzwerkproblem liegen oder das Video ist möglicherweise nicht verfügbar.

🚨the difference between a $95K developer and a $300K AI architect is knowing this list exists while most people type one-off prompts, a small group stacks specialized Claude skills and runs automated workflow factories 24/7 32 skills across 10 repositories. audited, ranked, and grouped into three stacks: > builder... show more

Fokki

12,345 subscribers

11,829 Aufrufe • vor 3 Monaten •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

> do you understand what Claude Opus 4.8 just did to the Google job market > a senior Google engineer with 11 years of experience > stacked 32 Claude skills on top of his workflow > 8hrs → 2-3hrs per day > $95K developer vs $300K AI architect > same job. different stack. very different salary > the exact skill list is here 👇

> do you understand what Claude Opus 4.8 just did to the Google job market > a senior Google engineer with 11 years of experience > stacked 32 Claude skills on top of his workflow > 8hrs → 2-3hrs per day > $95K developer vs $300K AI architect > same job. different stack. very different salary > the exact skill list is here 👇

Mr. Buzzoni

287,675 Aufrufe • vor 3 Monaten

Andrej Karpathy spent 4 minutes in an interview explaining a single idea about how most people haven’t even started learning how to use AI and everyone paying $20/month for a subscription.. that's not really using Claude at all his point is that the real skill gap is the ability to build with AI he identified 4 behaviors that break Claude Code and put them all into one file a developer expanded it into 21 rules and published it - 82,000 stars and #1 on GitHub Trending coding accuracy jumped from 65% to 94% here's what these 21 rules actually are and why most developers using Claude every day have never configured them the full breakdown is covered in the article below 👇

Andrej Karpathy spent 4 minutes in an interview explaining a single idea about how most people haven’t even started learning how to use AI and everyone paying $20/month for a subscription.. that's not really using Claude at all his point is that the real skill gap is the ability to build with AI he identified 4 behaviors that break Claude Code and put them all into one file a developer expanded it into 21 rules and published it - 82,000 stars and #1 on GitHub Trending coding accuracy jumped from 65% to 94% here's what these 21 rules actually are and why most developers using Claude every day have never configured them the full breakdown is covered in the article below 👇

rewind

3,205,843 Aufrufe • vor 4 Monaten

Today we're launching Meta Ad Researcher skills for Claude. This is a set of skills inside /gooseworks that turns Claude into an expert ad research team — find what's trending, see what competitors are running, and mine the angles that actually convert. First, install by running: npx gooseworks install --all Then you can do any of the following: /gooseworks --skill trending-ad-hook-spotter Find trending topics in my niche to run ads on right now /gooseworks --skill competitor-ad-intelligence Scrape my competitors' ads and reverse-engineer their funnel /gooseworks --skill ad-angle-miner Mine my reviews and Reddit for the angles that actually convert /gooseworks --skill brand-research Research my brand and build a reusable context pack for ads Oh and then you can use /gooseworks to make ad creatives directly from the research. /gooseworks use goose-ads remix to create 5 static ads based on the research above. All of this works right in Claude. No need to leave Claude at all. We've built a library of 100+ skills to turn Claude into an expert growth team - this includes skills for ads, social, content, research, gtm, seo and more. Comment Goose below and I'll send you an early access link.

Shiv

210,614 Aufrufe • vor 2 Monaten

Persona Spotlight - The Goddess of Envy Invidia | Rise of Eros 🔥 Basic Attack The target takes damage; if this Persona has 7 stacks of Invidia's Envy, this Skill is cast one more time on a random target. 🗡️ Special Skill All enemies take damage; if this Persona has 7 stacks of Invidia's Envy, restore HP equal to the damage dealt during this attack. Bestow Invidia's Envy on self. Passive: After an ally other than this Persona hits an enemy with an active attack, bestow Invidia's Envy on self; each ally can trigger this effect once per turn at most. ⚔️ Ultimate Skill All enemies take damage. If this Persona has Invidia's Envy, each stack of Invidia's Envy on self inflicts damage against the enemy with the highest percentage of current HP. Passive: If this Persona has 7 stacks of Invidia's Envy, immediately cast a random Skill on a random target. After the Skill is cast, remove Invidia's Envy from self. (When passive effect Skills are cast, they are not limited by cooldown and do not affect other Skills currently cooling down.) －－－ [Event Exclusive Code] Code:HpSLC8j2eTn #RiseofEros #AFeastfortheKingoftheGods #Inase

Sensitive content

Persona Spotlight - The Goddess of Envy Invidia | Rise of Eros 🔥 Basic Attack The target takes damage; if this Persona has 7 stacks of Invidia's Envy, this Skill is cast one more time on a random target. 🗡️ Special Skill All enemies take damage; if this Persona has 7 stacks of Invidia's Envy, restore HP equal to the damage dealt during this attack. Bestow Invidia's Envy on self. Passive: After an ally other than this Persona hits an enemy with an active attack, bestow Invidia's Envy on self; each ally can trigger this effect once per turn at most. ⚔️ Ultimate Skill All enemies take damage. If this Persona has Invidia's Envy, each stack of Invidia's Envy on self inflicts damage against the enemy with the highest percentage of current HP. Passive: If this Persona has 7 stacks of Invidia's Envy, immediately cast a random Skill on a random target. After the Skill is cast, remove Invidia's Envy from self. (When passive effect Skills are cast, they are not limited by cooldown and do not affect other Skills currently cooling down.) －－－ [Event Exclusive Code] Code:HpSLC8j2eTn #RiseofEros #AFeastfortheKingoftheGods #Inase

Rise of Eros

77,407 Aufrufe • vor 2 Jahren

Announcing Meta Ads skills in Claude 🦢 This is a suite of skills that turns Claude into a Meta Ads expert. You invoke it with a single command /gooseworks and Claude can now access skills and APIs like an expert ad team. Here's what it can do 👇 --- To use it, run npx gooseworks install --claude RESEARCH & INTEL 1. /gooseworks Find trending topics in my niche to run ads on right now Skill used: trending-ad-hook-spotter 2. /gooseworks Scrape my competitors' ads and reverse-engineer their funnel Skill used: competitor-ad-intelligence 3. /gooseworks Mine my reviews and Reddit for the angles that actually convert Skill used: ad-angle-miner 4. /gooseworks Research my brand and build a reusable context pack for ads Skill used: brand-research --- DIAGNOSE PERFORMANCE 5. /gooseworks Diagnose my Meta campaigns — what to cut, keep, or scale Skill used: meta-ads-analyzer 6. /gooseworks Find what's wasting budget across Google, Meta, and LinkedIn Skill used: ad-campaign-analyzer 7. /gooseworks Show true CAC per qualified lead, not vanity CPA Skill used: ad-lead-quality-analyzer 8. /gooseworks Check if my ad's promise carries through to the landing page Skill used: ad-to-landing-page-auditor --- PLAN AND REVIEW 9. /gooseworks Tell me which 1–2 paid channels to start with and a 90-day plan Skill used: paid-channel-prioritizer 11. /gooseworks Build Meta audiences, ad sets and copy from my ICP Skill used: meta-ads-campaign-builder 12. /gooseworks Pre-flight my ad copy against Meta policy before I spend Skill used: meta-ad-policy-checker --- MAKE CREATIVES 13. /goose-ads Turn that research into branded static ad creatives for my product Skill used: goose-ads All directly in Claude Code or Cowork. Start by installing npx gooseworks install --claude Comment Goose below and follow, and I'll DM you the full open-source library with 100+ skills to turn Claude into your growth team.

Shiv

106,577 Aufrufe • vor 2 Monaten

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

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

JJ Englert

29,322 Aufrufe • vor 5 Monaten

ANTHROPIC JUST GOT OUTFLANKED AND NOBODY IS TALKING ABOUT IT. DeepSeek V4. Ollama. OpenClaw. Hermes. Claude Code. Five tools. One stack. Completely free. The people who put this together this weekend will have a local AI setup more powerful than what most companies are paying $10,000 a month for in cloud inference. No API bills. No rate limits. No data leaving your machine. Ever. This is not a tutorial for developers. This is a setup any builder can run in under an hour. The gap between people who know this exists and people who do not just got very expensive. Very quietly. This weekend. Follow CyrilXBT for the exact setup, config files, and prompts to make this stack actually work.

ANTHROPIC JUST GOT OUTFLANKED AND NOBODY IS TALKING ABOUT IT. DeepSeek V4. Ollama. OpenClaw. Hermes. Claude Code. Five tools. One stack. Completely free. The people who put this together this weekend will have a local AI setup more powerful than what most companies are paying $10,000 a month for in cloud inference. No API bills. No rate limits. No data leaving your machine. Ever. This is not a tutorial for developers. This is a setup any builder can run in under an hour. The gap between people who know this exists and people who do not just got very expensive. Very quietly. This weekend. Follow CyrilXBT for the exact setup, config files, and prompts to make this stack actually work.

CyrilXBT

32,507 Aufrufe • vor 4 Monaten

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.

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) 🧃

19,532 Aufrufe • vor 27 Tagen

Google Deepmind CEO Demis Hassabis just explained the real AI skill gap: "The next generation will do things that used to take teams of 10, 20, 30, 50 people" Most people hear that and think AI just makes them faster Wrong It changes what one person can become > researcher > designer > developer > marketer > analyst > support > ops All wired into one workflow Agents research Tools write Automations publish Memory compounds This is not prompt engineering This is leverage The next 5 years won't belong to better prompt writers They'll belong to better workflow builders Bookmark and watch the full intreview

Google Deepmind CEO Demis Hassabis just explained the real AI skill gap: "The next generation will do things that used to take teams of 10, 20, 30, 50 people" Most people hear that and think AI just makes them faster Wrong It changes what one person can become > researcher > designer > developer > marketer > analyst > support > ops All wired into one workflow Agents research Tools write Automations publish Memory compounds This is not prompt engineering This is leverage The next 5 years won't belong to better prompt writers They'll belong to better workflow builders Bookmark and watch the full intreview

rari

39,959 Aufrufe • vor 2 Monaten

MASTER CLAUDE FOR MARKETING IN 72 MINUTES, ZERO CODE. ONE FREE COURSE JUST DROPPED. Agencies charge $10K/month to run this stack. This hands you the entire marketing system. Not one line of code. The 72-minute marketing money map, by timestamp: 00:00 - what you'll learn 01:07 - grab the free resource pack 02:32 - install Claude and turn on Cowork 03:17 - set up your workspace (CLAUDE.md + memory) 09:38 - what a skill actually is 11:29 - build your 4 content voice skills 17:12 - the content repurposing skill 20:00 - set up Firecrawl for web scraping 23:10 - generate images and videos with Higgsfield 28:21 - infographic skills 31:49 - product infographic skill 34:17 - product-to-ad UGC video skill 38:11 - find customers and leads with Clay 46:26 - build a live dashboard artifact 48:44 - store data with Supabase 51:42 - build your own content tracker 54:45 - connect any app with Zapier 58:21 - schedule and auto-post with Blotato 1:04:21 - AI SEO with SEMrush 1:11:19 - final words 72 free minutes here replace a $2,000 "AI marketing" cohort. One person + Claude + a weekend = a full marketing team while others still boost posts. Save it, watch today, ship your first skill before the week ends.

MASTER CLAUDE FOR MARKETING IN 72 MINUTES, ZERO CODE. ONE FREE COURSE JUST DROPPED. Agencies charge $10K/month to run this stack. This hands you the entire marketing system. Not one line of code. The 72-minute marketing money map, by timestamp: 00:00 - what you'll learn 01:07 - grab the free resource pack 02:32 - install Claude and turn on Cowork 03:17 - set up your workspace (CLAUDE.md + memory) 09:38 - what a skill actually is 11:29 - build your 4 content voice skills 17:12 - the content repurposing skill 20:00 - set up Firecrawl for web scraping 23:10 - generate images and videos with Higgsfield 28:21 - infographic skills 31:49 - product infographic skill 34:17 - product-to-ad UGC video skill 38:11 - find customers and leads with Clay 46:26 - build a live dashboard artifact 48:44 - store data with Supabase 51:42 - build your own content tracker 54:45 - connect any app with Zapier 58:21 - schedule and auto-post with Blotato 1:04:21 - AI SEO with SEMrush 1:11:19 - final words 72 free minutes here replace a $2,000 "AI marketing" cohort. One person + Claude + a weekend = a full marketing team while others still boost posts. Save it, watch today, ship your first skill before the week ends.

shmidt

15,848 Aufrufe • vor 2 Monaten

540,000 lines of Rails is a brutal way to learn the agent era Garry's List shipped with: > 262,000 lines of app code > 276,000 lines of tests > 127 background jobs > 33 cron jobs > a 1,778-line claim verifier Then GStack hit 105k GitHub stars Do not copy the Rails pattern 1. Finish the task with an agent 2. Say `skillify it` 3. Save the markdown skill 4. Keep TypeScript only for deterministic I/O 5. Add a unit test for the code 6. Add an LLM eval for the skill 7. Add an integration test across both 8. Add a resolver so the agent loads the skill next time A Rails feature serves one app A skill pack can run against the next hackathon, repo, customer inbox, research folder, or QA run Audit your repo this week Cut code that only exists to: > re-check model output > retry the same model call > validate what the model already has context for > schedule work because the agent has no reusable procedure > preserve a one-off prompt in chat history Keep the code that touches files, APIs, auth, billing, devices, databases Move the judgment into markdown Test the markdown Reuse the skill

540,000 lines of Rails is a brutal way to learn the agent era Garry's List shipped with: > 262,000 lines of app code > 276,000 lines of tests > 127 background jobs > 33 cron jobs > a 1,778-line claim verifier Then GStack hit 105k GitHub stars Do not copy the Rails pattern 1. Finish the task with an agent 2. Say `skillify it` 3. Save the markdown skill 4. Keep TypeScript only for deterministic I/O 5. Add a unit test for the code 6. Add an LLM eval for the skill 7. Add an integration test across both 8. Add a resolver so the agent loads the skill next time A Rails feature serves one app A skill pack can run against the next hackathon, repo, customer inbox, research folder, or QA run Audit your repo this week Cut code that only exists to: > re-check model output > retry the same model call > validate what the model already has context for > schedule work because the agent has no reusable procedure > preserve a one-off prompt in chat history Keep the code that touches files, APIs, auth, billing, devices, databases Move the judgment into markdown Test the markdown Reuse the skill

Alpha Batcher

36,878 Aufrufe • vor 3 Monaten

Y Combinator CEO, Garry Tan, took the stage for 42 minutes at Startup School 2026 and explained how to build your own personal AGI better than any paid AI course. This is what he told the room: 1. The leverage is in your context, not the model. Tan watches hundreds of founders use identical models every batch. "There are 2x people and there are 100x people who are using the same Claude. Same weights, same context window size, same API. But the leverage is not in the weights." The gap between users is now bigger than the gap between models. 2. One person's output went up 400x. In 2013 Tan shipped maybe 14 useful lines of code a day as a YC partner, dead on the median for programmer productivity. "I did the math on my output, and I'm at about 400x what I did in 2013." 3. Agents run on a different working memory. Humans hold 7 things in their head at once. Every org chart and checklist ever built is a patch for that limit. "An AI agent holds a million tokens. That's about a thousand pages. Three Harry Potter books sitting open on its head all at once." You're still running your week on tools built for the 7-digit brain. 4. Markdown is code now. Tan's stack is mostly skill files: pages of plain English an agent can execute. "If you can write clear instructions in English, you're a programmer. The compiler is a language model." At YC, finance and events staff who never opened a terminal are building automations. 5. Your history is your moat. Tan's agent runs on a personal wiki: about 220,000 markdown pages covering 25 years of email, meetings, notes and decisions. "When my agent does anything, it does knowing everything I know. And that's the difference between an assistant and a colleague." No frontier model has your context. That's the one asset nobody can replicate. 6. Never do one-off work. Most people run a task with an agent, close the window and throw the learning away. Tan ends every task by having the agent turn what it did into a reusable skill file. "If you have to ask for something twice, you failed." Captured skills compound daily. Amnesia resets you to zero every morning. 7. Own your skill files before your employer does. A skill file is your judgment, extracted and executable. The only question is who controls it. "Own your skills because if you don't, your job becomes a skill file." Files in your repo compound your career. Files in the company's repo run your judgment without you. Watch it, then read the step-by-step guide on becoming an AI engineer.

Y Combinator CEO, Garry Tan, took the stage for 42 minutes at Startup School 2026 and explained how to build your own personal AGI better than any paid AI course. This is what he told the room: 1. The leverage is in your context, not the model. Tan watches hundreds of founders use identical models every batch. "There are 2x people and there are 100x people who are using the same Claude. Same weights, same context window size, same API. But the leverage is not in the weights." The gap between users is now bigger than the gap between models. 2. One person's output went up 400x. In 2013 Tan shipped maybe 14 useful lines of code a day as a YC partner, dead on the median for programmer productivity. "I did the math on my output, and I'm at about 400x what I did in 2013." 3. Agents run on a different working memory. Humans hold 7 things in their head at once. Every org chart and checklist ever built is a patch for that limit. "An AI agent holds a million tokens. That's about a thousand pages. Three Harry Potter books sitting open on its head all at once." You're still running your week on tools built for the 7-digit brain. 4. Markdown is code now. Tan's stack is mostly skill files: pages of plain English an agent can execute. "If you can write clear instructions in English, you're a programmer. The compiler is a language model." At YC, finance and events staff who never opened a terminal are building automations. 5. Your history is your moat. Tan's agent runs on a personal wiki: about 220,000 markdown pages covering 25 years of email, meetings, notes and decisions. "When my agent does anything, it does knowing everything I know. And that's the difference between an assistant and a colleague." No frontier model has your context. That's the one asset nobody can replicate. 6. Never do one-off work. Most people run a task with an agent, close the window and throw the learning away. Tan ends every task by having the agent turn what it did into a reusable skill file. "If you have to ask for something twice, you failed." Captured skills compound daily. Amnesia resets you to zero every morning. 7. Own your skill files before your employer does. A skill file is your judgment, extracted and executable. The only question is who controls it. "Own your skills because if you don't, your job becomes a skill file." Files in your repo compound your career. Files in the company's repo run your judgment without you. Watch it, then read the step-by-step guide on becoming an AI engineer.

Alex Prompter

249,533 Aufrufe • vor 1 Monat

Google DeepMind CEO: "The gap between people who use AI and people who don't will be the largest skill divide in human history" Demis Hassabis spent 50 minutes at Stanford saying things most CEOs would never say publicly this is exactly the kind of conversation people pay $250,000 to be in the room for if you want to stay competitive, understanding AI is no longer optional I wrote a full guide on Claude features 99% of people don't know exist watch this video, then read the article below those two things alone put you ahead of most people using AI right now

Google DeepMind CEO: "The gap between people who use AI and people who don't will be the largest skill divide in human history" Demis Hassabis spent 50 minutes at Stanford saying things most CEOs would never say publicly this is exactly the kind of conversation people pay $250,000 to be in the room for if you want to stay competitive, understanding AI is no longer optional I wrote a full guide on Claude features 99% of people don't know exist watch this video, then read the article below those two things alone put you ahead of most people using AI right now

Anatoli Kopadze

111,031 Aufrufe • vor 3 Monaten

Once you learn these three things, you can build nearly anything yourself. Skills, chains, and plugins. Learn them once and you can automate a real part of your week yourself. Here's the system: A skill is a standard operating procedure. It's one long, reusable prompt that does one thing well, like writing a newsletter, setting up a PPC campaign, triaging your inbox, or drafting a note to the board. You write it once and reuse it forever. The trick is to feed it your real work. For my writing skill, I gave Claude posts I admire and my own exported analytics with the winners marked, so it could see the patterns. Show it what good looks like and it nails your voice. Skip that step and it guesses. A chain connects skills into an automation. One skill's output feeds the next, in order. A copywriting skill writes the messaging, then hands it to a PPC-setup skill that builds the campaign. That's an automation, and you built it without writing code. A plugin is the harness that holds it all. It bundles your skills and chains into one thing you share with your team. Instead of sending 15 separate prompts around, you send one plugin, and it knows when to use each skill on its own. Skill, chain, plugin. It's one step up the ladder, and once you're up there it's easy. Now the worked example. I call it the Daily Driver. It's five skills chained together: email triage, a writer, Slack triage, a thinking partner, and a setup skill that connects my tools and personalizes everything. I chained them into one morning brief and scheduled it to run at 9am and message me the list. Two things made the biggest difference. Give it memory. I made plain docs for About Me, my Brand Voice, and my working preferences. I had Claude interview me and saved each answer as a file. Now every output sounds like me and knows my projects and my team. Connect your tools. The plugin reads my inbox, Slack, and calendar through MCP connectors for Gmail, Slack, and Google Calendar. That's what turns "summarize my morning" into a real brief instead of an empty wish. This is the highest-ROI thing an operator can set up this week. I run my YouTube channel, podcast, community, and newsletter on plugins I built myself, all on the $100 Max plan with no engineer in sight. I made a full walkthrough that shows the whole build start to finish. Want the Daily Driver plugin to start from? Comment PLUGIN below and I'll send it to you. #AI #automation #ClaudeCode

JJ Englert

53,969 Aufrufe • vor 3 Monaten

Most people sell one AI service and cap their income there. Here's the upsell menu that turns a $999 client into an $8K one: - Process redesign: Cut a broken 16-step process down to 7. No automation yet. $3,000–$3,500. - Automation build: A simple Zapier or Make flow for cut-and-dry tasks. ~$1,500. - Knowledge system: Train a custom GPT on their docs. - Custom workflow: Build Claude skills for their proprietary process. Bolt on a monthly retainer to maintain them. - Full implementation: Any combination of the above. ~$8,000. The $999 assessment is just the door. Everything after it is the real money.

Most people sell one AI service and cap their income there. Here's the upsell menu that turns a $999 client into an $8K one: - Process redesign: Cut a broken 16-step process down to 7. No automation yet. $3,000–$3,500. - Automation build: A simple Zapier or Make flow for cut-and-dry tasks. ~$1,500. - Knowledge system: Train a custom GPT on their docs. - Custom workflow: Build Claude skills for their proprietary process. Bolt on a monthly retainer to maintain them. - Full implementation: Any combination of the above. ~$8,000. The $999 assessment is just the door. Everything after it is the real money.

The Startup Ideas Podcast (SIP) 🧃

12,622 Aufrufe • vor 2 Monaten

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

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

Yarchi

54,840 Aufrufe • vor 3 Monaten

Nobody's talking about the Claude trick that fixes every Seedance 2.0 video mistake. A cinematic action scene, an animated sequence, a product ad, and a dialogue scene are completely different types of content. Different camera language, different pacing, different reference logic. Most people try to force all of it through one universal prompt. The fix turns out to be simpler than expected: Claude Skills. It's not some secret hack. It's a file of instructions you load into Claude for one specific type of task. Once it's loaded, Claude stops acting like a general assistant and starts thinking like an expert in that one niche — with its own set of rules for that scene type. Here's what that looks like in practice: ▪ Cinematic skill — generates real camera language: dolly moves, crane shots, rack focus, shot discipline across multiple cuts. Test: a medieval battle between two armies, 15 seconds, dark fantasy. Result — three shots with the shot logic of an actual film, not just "epic battle" typed as text. ▪ Animation skill — locks in style and physics before a single shot is built. One test: a rain-soaked shonen fight in the style of Tokyo Revengers. Another: a quiet Ghibli-style farm scene. Same skill, completely different visual output — because the style gets fixed at the very top of the prompt. ▪ Product ad skill — keeps the product front and center in every shot: clean hero framing, commercial lighting, a full product description built from the reference image before any shots are generated. ▪ Dialogue skill — this is where most people fall apart. Lip sync, emotional direction, shot structure, and audio cues all have to work together. Test: an interrogation scene with a fourth-wall break — and the moment landed exactly as written, down to the pause and tone. The core idea is simple: instead of writing a prompt from scratch every time and hoping for the best, you build one skill per content type — and Claude asks the right setup questions (genre, tone, shot count, camera energy) before generating a fully structured Seedance 2.0 prompt. One prompt template for everything is exactly why 90% of AI videos look the same. This 13-minute video is free, and it's more useful than a $500 course. YouTube: "Skai Generated" - Thank you for sharing this invaluable material with us.

Nobody's talking about the Claude trick that fixes every Seedance 2.0 video mistake. A cinematic action scene, an animated sequence, a product ad, and a dialogue scene are completely different types of content. Different camera language, different pacing, different reference logic. Most people try to force all of it through one universal prompt. The fix turns out to be simpler than expected: Claude Skills. It's not some secret hack. It's a file of instructions you load into Claude for one specific type of task. Once it's loaded, Claude stops acting like a general assistant and starts thinking like an expert in that one niche — with its own set of rules for that scene type. Here's what that looks like in practice: ▪ Cinematic skill — generates real camera language: dolly moves, crane shots, rack focus, shot discipline across multiple cuts. Test: a medieval battle between two armies, 15 seconds, dark fantasy. Result — three shots with the shot logic of an actual film, not just "epic battle" typed as text. ▪ Animation skill — locks in style and physics before a single shot is built. One test: a rain-soaked shonen fight in the style of Tokyo Revengers. Another: a quiet Ghibli-style farm scene. Same skill, completely different visual output — because the style gets fixed at the very top of the prompt. ▪ Product ad skill — keeps the product front and center in every shot: clean hero framing, commercial lighting, a full product description built from the reference image before any shots are generated. ▪ Dialogue skill — this is where most people fall apart. Lip sync, emotional direction, shot structure, and audio cues all have to work together. Test: an interrogation scene with a fourth-wall break — and the moment landed exactly as written, down to the pause and tone. The core idea is simple: instead of writing a prompt from scratch every time and hoping for the best, you build one skill per content type — and Claude asks the right setup questions (genre, tone, shot count, camera energy) before generating a fully structured Seedance 2.0 prompt. One prompt template for everything is exactly why 90% of AI videos look the same. This 13-minute video is free, and it's more useful than a $500 course. YouTube: "Skai Generated" - Thank you for sharing this invaluable material with us.

Zentrix⌚️

45,874 Aufrufe • vor 1 Monat

Nobel Prize winner and Google DeepMind CEO Demis Hassabis just revealed the real AI skill gap: “The next generation will do things that used to take teams of 10, 20, 30, 50 people” Most people heard that and thought: “Cool, AI makes me faster” Wrong. AI does not just make people faster. It changes what one person can become. A startup used to need: > researcher > designer > developer > marketer > analyst > support team > ops manager Now one AI-native person can wire all of that into workflows. > Agents that research. > Tools that write. > Workflows that test. > Automations that publish. > Memory that compounds. This is not prompt engineering. This is leverage. The next 5 years will not belong to people who write better prompts. They will belong to people who build better workflows. Watch the full interview. Bookmark this. It is one of the most important ideas of the decade.

Nobel Prize winner and Google DeepMind CEO Demis Hassabis just revealed the real AI skill gap: “The next generation will do things that used to take teams of 10, 20, 30, 50 people” Most people heard that and thought: “Cool, AI makes me faster” Wrong. AI does not just make people faster. It changes what one person can become. A startup used to need: > researcher > designer > developer > marketer > analyst > support team > ops manager Now one AI-native person can wire all of that into workflows. > Agents that research. > Tools that write. > Workflows that test. > Automations that publish. > Memory that compounds. This is not prompt engineering. This is leverage. The next 5 years will not belong to people who write better prompts. They will belong to people who build better workflows. Watch the full interview. Bookmark this. It is one of the most important ideas of the decade.

spect

132,349 Aufrufe • vor 3 Monaten

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.

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,150 Aufrufe • vor 6 Monaten

I'm making $8,000 a month building Claude skills for other people's businesses. I call it the AI Concierge. I have 5 clients paying $1,200 to $2,000 a month each. My effective rate is about $1,200 an hour. Every engagement runs on one framework I call AOA: Audit, Optimize, Automate. Here's the entire model: 1) Most people skip straight to Automate. That's the fun part. It's also how you end up automating a broken process. 2) Audit first. The client shares their screen and walks the process in painful detail while I take notes in a Google Doc and interrupt with a million questions. 3) Capture the plumbing, not just the steps. Who owns each step, which tool it runs in, where the data lives, and whether that tool can connect to Claude. 4) Hand the audit doc to Claude and ask it to find a better way. Then push back. Claude's first synopsis is usually partly wrong, and the client catches it. 5) Cut the fat. Most processes are 15 steps and only need to be 11. Most clients use 3 tools where 2 would do. 6) One home per fact. One client stored customer data in ClickUp and the CRM. We killed the ClickUp copy. Duplicates are just human error waiting to happen. 7) Have Claude write the build plan. It splits the process into skills, scaffolds each one, and lists next steps. Then you lock the doc. 8) A skill is a markdown file plus reference files. A reference file is just an example of what good looks like. Claude builds all of it. 9) Build one skill at a time from the build plan. If the audit was done right, Claude one shots it. Test on a real run, let Claude interview you, iterate. Version 2 is usually the keeper. 10) Draft first, never auto send. A speed to lead skill drafts replies for review on day one. It earns auto send later. Two things that make this work: 1) Audit and Optimize are 80% of the work. Automate is the 20%. You have to earn the right to build. 2) Skills do one thing well. Split at every point a human or a wait interrupts the chain, then let an orchestrator run them back to back. Full step-by-step playbook for starting a profitable AI Concierge business (free): Full breakdown below. Enjoy!

I'm making $8,000 a month building Claude skills for other people's businesses. I call it the AI Concierge. I have 5 clients paying $1,200 to $2,000 a month each. My effective rate is about $1,200 an hour. Every engagement runs on one framework I call AOA: Audit, Optimize, Automate. Here's the entire model: 1) Most people skip straight to Automate. That's the fun part. It's also how you end up automating a broken process. 2) Audit first. The client shares their screen and walks the process in painful detail while I take notes in a Google Doc and interrupt with a million questions. 3) Capture the plumbing, not just the steps. Who owns each step, which tool it runs in, where the data lives, and whether that tool can connect to Claude. 4) Hand the audit doc to Claude and ask it to find a better way. Then push back. Claude's first synopsis is usually partly wrong, and the client catches it. 5) Cut the fat. Most processes are 15 steps and only need to be 11. Most clients use 3 tools where 2 would do. 6) One home per fact. One client stored customer data in ClickUp and the CRM. We killed the ClickUp copy. Duplicates are just human error waiting to happen. 7) Have Claude write the build plan. It splits the process into skills, scaffolds each one, and lists next steps. Then you lock the doc. 8) A skill is a markdown file plus reference files. A reference file is just an example of what good looks like. Claude builds all of it. 9) Build one skill at a time from the build plan. If the audit was done right, Claude one shots it. Test on a real run, let Claude interview you, iterate. Version 2 is usually the keeper. 10) Draft first, never auto send. A speed to lead skill drafts replies for review on day one. It earns auto send later. Two things that make this work: 1) Audit and Optimize are 80% of the work. Automate is the 20%. You have to earn the right to build. 2) Skills do one thing well. Split at every point a human or a wait interrupts the chain, then let an orchestrator run them back to back. Full step-by-step playbook for starting a profitable AI Concierge business (free): Full breakdown below. Enjoy!

Corey Ganim

64,919 Aufrufe • vor 1 Tag