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.

Here's how I'm running automated content engine in 2 files 1 markdown file = my wiki 1 html file = my dashboard that's the whole stack. [ the architecture, in plain words ]: LLM wiki = a single markdown file holding my audience DNA, 15 tracked creators, every viral... topic from the last 30 days HTML artifact = a single page that reads that markdown file AND can trigger my agents the artifact and the agent talk to each other directly the wiki is the shared brain [ what I actually see when I open it at 9am ]: > 5 trending topics ranked by my audience-DNA fit > 3 KOL posts worth quoting today > last week's saved tweets (so I can ride waves that are still warm) > buttons: [draft tweet] [draft QT] [schedule] [log idea] 1. I click "draft tweet" on a topic 2. the artifact pings my agent 3. agent reads the wiki, drafts in MY voice, returns it to the artifact 4. I edit, schedule, done 15 minutes from morning coffee to 3 scheduled posts [ how to build the same in one evening ]: > step 1: dump your domain knowledge into ONE markdown file (audience profile, KOL list, content rules, voice guide, anything an agent would need to do YOUR job) > step 2: ask claude to build an html artifact that reads from that file ("here's my wiki, build me a dashboard with these views") > step 3: add buttons for the actions you do daily (draft, schedule, log, score, search — your workflow, not mine) > step 4: wire each button to call your agent via tool calls (so the artifact and the agent talk directly) the moment your artifact reads your wiki AND triggers your agents.. most SaaS tools you currently pay for quietly become unnecessary dashboards I used to pay $50/month for now sit in a single html file I can rebuild in 20 minutes every "I'll build a SaaS for this" idea you had last year is a 200-line file you write in an afternoon if you want to get the same content engine, just reply "CONTENT" and will send you in DMs later we're going from buying software to owning it.show more

Ronin

109,866 subscribers

50,083 Aufrufe • vor 3 Monaten •via X (Twitter)

Bildung Nachrichten & Politik Wissenschaft & Technologie

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

Introducing Wikiwise: an open-source Mac app for managing your own Karpathy-style LLM wiki. Set up a new wiki in a few clicks: all you need is Wikiwise + your agent. It's infinitely customizable, just markdown/html under the hood, and one click to share your wiki publicly. Here's how it works: * Install Wikiwise for mac (it's built in Swift so super minimal and performant). In Karpathy's framework, Wikiwise is your IDE. * Start a new Wiki: it generates a new folder on your machine that's scaffolded in the wiki structure Andrej Karpathy describes (index.md, raw folder, wiki folder, CLAUDE.md/AGENTS.md, although it tries to be as un-opinionated as possible). * Then just point your agent (Codex, Claude Code, Cursor, etc) at the folder and tell it what to import -- files on your machine, connect to your Readwise account, or urls from the web. * Your agent creates wthe wiki for you: Your agent will know how to ingest your raw sources (via the AGENTS.md) and will immediately start writing+linking wiki pages for you. * Go crazy on customization! The rendered wiki pages live as static html/css in your folder too so just tell your agent to change stuff, and if you need any more customization Wikiwise is fully open source :) * Ask questions about your research with your agent, ask it to bring in new sources, write new documents, etc. * (optionally) Hit the Publish button to share your wiki with friends/colleagues at a custom URL === I tried to walk the line on a couple constraints with Wikiwise: 1. I wanted it to be easy to spin up new wikis, especially without chaining together a bunch of different apps. It takes me a few minutes to spin up a new wiki on a topic -- I already have five! 2. Infinitely Customizable: one great aspect of building a wiki as Karpathy described is that you can modify any aspect of your wiki with your agent. Every new wiki styling+structure is self-contained in the local folder, which allows you to preserve this. Wikiwise is just an IDE that makes the setup easier and includes a nice un-opinionated starting state. 3. Minimal: Wikiwise is built mostly in Swift, and the DMG you install to download it is only 2.6MB (!) 4. Easy Publishing: my colleague Eleanor Konik has been building her own LLM wikis for months, but has always really struggled to actually share them with her book club. There are tools to do it, but figuring out hosting is always a huge headache. This seemed like an ideal usecase for a tool like Wikiwise to solve. The process of building wikiwise was also pretty interesting -- I "bootstrapped" the app in a way by first building my own wiki based on Karpathy's tweet and other notes I had, and slowly formed the shape of the project in collaboration with my LLM. This was all done in 3 days over the latest Readwise company hackathon we had. Truly an incredible time to be alive. Anyways, curious what you think! Links in next tweet.

Introducing Wikiwise: an open-source Mac app for managing your own Karpathy-style LLM wiki. Set up a new wiki in a few clicks: all you need is Wikiwise + your agent. It's infinitely customizable, just markdown/html under the hood, and one click to share your wiki publicly. Here's how it works: * Install Wikiwise for mac (it's built in Swift so super minimal and performant). In Karpathy's framework, Wikiwise is your IDE. * Start a new Wiki: it generates a new folder on your machine that's scaffolded in the wiki structure Andrej Karpathy describes (index.md, raw folder, wiki folder, CLAUDE.md/AGENTS.md, although it tries to be as un-opinionated as possible). * Then just point your agent (Codex, Claude Code, Cursor, etc) at the folder and tell it what to import -- files on your machine, connect to your Readwise account, or urls from the web. * Your agent creates wthe wiki for you: Your agent will know how to ingest your raw sources (via the AGENTS.md) and will immediately start writing+linking wiki pages for you. * Go crazy on customization! The rendered wiki pages live as static html/css in your folder too so just tell your agent to change stuff, and if you need any more customization Wikiwise is fully open source :) * Ask questions about your research with your agent, ask it to bring in new sources, write new documents, etc. * (optionally) Hit the Publish button to share your wiki with friends/colleagues at a custom URL === I tried to walk the line on a couple constraints with Wikiwise: 1. I wanted it to be easy to spin up new wikis, especially without chaining together a bunch of different apps. It takes me a few minutes to spin up a new wiki on a topic -- I already have five! 2. Infinitely Customizable: one great aspect of building a wiki as Karpathy described is that you can modify any aspect of your wiki with your agent. Every new wiki styling+structure is self-contained in the local folder, which allows you to preserve this. Wikiwise is just an IDE that makes the setup easier and includes a nice un-opinionated starting state. 3. Minimal: Wikiwise is built mostly in Swift, and the DMG you install to download it is only 2.6MB (!) 4. Easy Publishing: my colleague Eleanor Konik has been building her own LLM wikis for months, but has always really struggled to actually share them with her book club. There are tools to do it, but figuring out hosting is always a huge headache. This seemed like an ideal usecase for a tool like Wikiwise to solve. The process of building wikiwise was also pretty interesting -- I "bootstrapped" the app in a way by first building my own wiki based on Karpathy's tweet and other notes I had, and slowly formed the shape of the project in collaboration with my LLM. This was all done in 3 days over the latest Readwise company hackathon we had. Truly an incredible time to be alive. Anyways, curious what you think! Links in next tweet.

Tristan

96,213 Aufrufe • vor 4 Monaten

HERMES AGENT SHIPS WITH A BUNDLED SKILL FOR ANDREJ KARPATHY'S LLM WIKI PATTERN. A SELF-IMPROVING KNOWLEDGE BASE THAT GROWS EVERY TIME YOU FEED IT. mentioned this briefly in the overnight workflow article. here is the full breakdown. what it is: a self-improving knowledge base built as interlinked markdown files. unlike RAG (which rediscovers knowledge from scratch every query), the wiki compiles knowledge once and keeps it current. cross-references stay linked. contradictions get flagged automatically. synthesis reflects everything ingested so far. why this matters for Hermes memory: Hermes built-in memory knows YOU. it remembers your conversations, your preferences, your business context across sessions. but it doesn't know your inbox. or your meeting transcripts. or that article you saved last week. or the expert framework you want it to learn. the LLM Wiki solves that. THE DIVISION OF LABOR human curates sources and directs analysis. agent summarizes, cross-references, files, and maintains consistency. you drop in articles, transcripts, notes. Hermes indexes them, links related concepts, flags contradictions, updates affected pages. your knowledge base grows itself. SETUP IS ONE COMMAND the skill ships with Hermes. enable it. set WIKI_PATH in ~/.hermes/.env: WIKI_PATH=/Users/you/wiki defaults to ~/wiki if unset. then drop anything into it: "index this article into my wiki: [paste URL or text]" Hermes reads it, builds a source page, updates related entries, flags contradictions. THE OBSIDIAN ANGLE set OBSIDIAN_VAULT_PATH to the same directory. now your wiki is visible in Obsidian's graph view. nodes, links, backlinks. all built by Hermes. for headless servers: install obsidian-headless. syncs vaults without a GUI. agent writes from the server, you read on your laptop. THE COMPOUND EFFECT Hermes knows you. the wiki knows your world. combine them and the agent answers questions using BOTH contexts at once. month 1: you explain things twice. month 3: the agent references the wiki on its own. answers get sharper because the knowledge base got sharper. AUTOMATIONS THAT FEED THE WIKI set cron jobs to ingest automatically: "every day at 9am, check Granola for new meetings. add any new transcripts to my wiki under meeting notes." "every morning, scan my Gmail starred items. add anything worth keeping to the wiki." "every week, check arXiv for new papers in [your niche]. summarize and file." your wiki grows while you sleep. Hermes never forgets what gets indexed. THE LIMITATION TO KNOW unlike Hermes memory (which is conversational and lives across sessions), the wiki is a separate knowledge layer. Hermes won't pull from the wiki automatically unless you reference it or save it as a skill. best setup: build an LLM Wiki personality that tells Hermes to consult the wiki when answering strategy questions or domain-specific queries. full HERMES AGENT OVERNIGHT WORKFLOW👇

HERMES AGENT SHIPS WITH A BUNDLED SKILL FOR ANDREJ KARPATHY'S LLM WIKI PATTERN. A SELF-IMPROVING KNOWLEDGE BASE THAT GROWS EVERY TIME YOU FEED IT. mentioned this briefly in the overnight workflow article. here is the full breakdown. what it is: a self-improving knowledge base built as interlinked markdown files. unlike RAG (which rediscovers knowledge from scratch every query), the wiki compiles knowledge once and keeps it current. cross-references stay linked. contradictions get flagged automatically. synthesis reflects everything ingested so far. why this matters for Hermes memory: Hermes built-in memory knows YOU. it remembers your conversations, your preferences, your business context across sessions. but it doesn't know your inbox. or your meeting transcripts. or that article you saved last week. or the expert framework you want it to learn. the LLM Wiki solves that. THE DIVISION OF LABOR human curates sources and directs analysis. agent summarizes, cross-references, files, and maintains consistency. you drop in articles, transcripts, notes. Hermes indexes them, links related concepts, flags contradictions, updates affected pages. your knowledge base grows itself. SETUP IS ONE COMMAND the skill ships with Hermes. enable it. set WIKI_PATH in ~/.hermes/.env: WIKI_PATH=/Users/you/wiki defaults to ~/wiki if unset. then drop anything into it: "index this article into my wiki: [paste URL or text]" Hermes reads it, builds a source page, updates related entries, flags contradictions. THE OBSIDIAN ANGLE set OBSIDIAN_VAULT_PATH to the same directory. now your wiki is visible in Obsidian's graph view. nodes, links, backlinks. all built by Hermes. for headless servers: install obsidian-headless. syncs vaults without a GUI. agent writes from the server, you read on your laptop. THE COMPOUND EFFECT Hermes knows you. the wiki knows your world. combine them and the agent answers questions using BOTH contexts at once. month 1: you explain things twice. month 3: the agent references the wiki on its own. answers get sharper because the knowledge base got sharper. AUTOMATIONS THAT FEED THE WIKI set cron jobs to ingest automatically: "every day at 9am, check Granola for new meetings. add any new transcripts to my wiki under meeting notes." "every morning, scan my Gmail starred items. add anything worth keeping to the wiki." "every week, check arXiv for new papers in [your niche]. summarize and file." your wiki grows while you sleep. Hermes never forgets what gets indexed. THE LIMITATION TO KNOW unlike Hermes memory (which is conversational and lives across sessions), the wiki is a separate knowledge layer. Hermes won't pull from the wiki automatically unless you reference it or save it as a skill. best setup: build an LLM Wiki personality that tells Hermes to consult the wiki when answering strategy questions or domain-specific queries. full HERMES AGENT OVERNIGHT WORKFLOW👇

YanXbt

30,804 Aufrufe • vor 2 Monaten

LLM Wikis + HTML Artifacts are insanely powerful. You should seriously consider this in your workflows. LLM Wikis captures all the important information that lets you and your agents do meaningful work. HTML artifacts present that information in interesting ways that allow you to take important actions along with your agents. My HTML artifacts sit on top of my LLM wikis. They are dynamic and are easily extended as needs arise. I have hooked my Artifacts to talk to my agents, and similarly, the agents can talk to artifacts. This has allowed me to build powerful artifacts that reduce my inbox to zero, keep me updated on any topic of interest, fast prototyping, do deep research, design/trigger new experiments, generate figures to improve understanding, schedule research, search relevant information, discover topics, and so much more. What you see in the clip is not a website. It's a simple interactive HTML artifact. HTML artifacts are useful for designers, engineers, researchers, students, and anyone working with agents. Lastly, HTML doesn't replace Markdown. They are a much better combination working together.

LLM Wikis + HTML Artifacts are insanely powerful. You should seriously consider this in your workflows. LLM Wikis captures all the important information that lets you and your agents do meaningful work. HTML artifacts present that information in interesting ways that allow you to take important actions along with your agents. My HTML artifacts sit on top of my LLM wikis. They are dynamic and are easily extended as needs arise. I have hooked my Artifacts to talk to my agents, and similarly, the agents can talk to artifacts. This has allowed me to build powerful artifacts that reduce my inbox to zero, keep me updated on any topic of interest, fast prototyping, do deep research, design/trigger new experiments, generate figures to improve understanding, schedule research, search relevant information, discover topics, and so much more. What you see in the clip is not a website. It's a simple interactive HTML artifact. HTML artifacts are useful for designers, engineers, researchers, students, and anyone working with agents. Lastly, HTML doesn't replace Markdown. They are a much better combination working together.

elvis

248,826 Aufrufe • vor 3 Monaten

2 Cursor agents in separate tabs chat and plan the most interesting app ever and build it too! collaboratively All you need is 2 rules, THAT IS IT! here is how: create 2 rule files set to "Manual" agent-1 .mdc: --- You are agent-1 you will be chatting with agent-2 to design and build the most interesting python app ever you will write to agent_1.txt file and read from agent_2.txt file if you are waiting for a new response write a cli command to wait for 5 seconds and check again you will repeat this untill the full app is built you start the conversation --- agent-2 .mdc: --- You are agent-2 you will be chatting with agent-1 to design and build the most interesting python app ever you will write to agent_2.txt file and read from agent_1.txt file if you are waiting for a new response write a cli command to wait for 5 seconds and check again you will repeat this untill the full app is built agent-1 will start the convo --- create a new agent tab, you should have 2 tabs assign agent 1 its rule and agent 2 its rule type "begin" for agent 1 and enter type "begin" for agent 2 and enter That is it! and then watch them go to work! --- Want to level up your Cursor game? I’ve created a 45-chapter course on mastering Cursor. Check it out via the link in my bio! each chapter is short and independent and designed to get your started quickly featuring 26 hours of content where we build interesting apps and ideas from scratch in each chapter. ---

2 Cursor agents in separate tabs chat and plan the most interesting app ever and build it too! collaboratively All you need is 2 rules, THAT IS IT! here is how: create 2 rule files set to "Manual" agent-1 .mdc: --- You are agent-1 you will be chatting with agent-2 to design and build the most interesting python app ever you will write to agent_1.txt file and read from agent_2.txt file if you are waiting for a new response write a cli command to wait for 5 seconds and check again you will repeat this untill the full app is built you start the conversation --- agent-2 .mdc: --- You are agent-2 you will be chatting with agent-1 to design and build the most interesting python app ever you will write to agent_2.txt file and read from agent_1.txt file if you are waiting for a new response write a cli command to wait for 5 seconds and check again you will repeat this untill the full app is built agent-1 will start the convo --- create a new agent tab, you should have 2 tabs assign agent 1 its rule and agent 2 its rule type "begin" for agent 1 and enter type "begin" for agent 2 and enter That is it! and then watch them go to work! --- Want to level up your Cursor game? I’ve created a 45-chapter course on mastering Cursor. Check it out via the link in my bio! each chapter is short and independent and designed to get your started quickly featuring 26 hours of content where we build interesting apps and ideas from scratch in each chapter. ---

echo.hive

88,611 Aufrufe • vor 1 Jahr

YT Podcast → LLM Artifact This is now my favorite way to consume podcasts. Knowledge artifacts generated by agents. The agent (Opus 4.7) spots important insights, does deep analysis, and generates thought-provoking observations that really get me curious to research further. All the research goes into a self-improving wiki for later use by any of my agents. I am using Elevenlabs Scribe for diarization. Skills and scripts to guide the artifact generation. Artifacts are just plain HTML + JS (e.g., chart.js). You can go further on anything by selecting text and components (charts) and doing deeper research, as I show in the clip. I expect more people to use agents in this way.

YT Podcast → LLM Artifact This is now my favorite way to consume podcasts. Knowledge artifacts generated by agents. The agent (Opus 4.7) spots important insights, does deep analysis, and generates thought-provoking observations that really get me curious to research further. All the research goes into a self-improving wiki for later use by any of my agents. I am using Elevenlabs Scribe for diarization. Skills and scripts to guide the artifact generation. Artifacts are just plain HTML + JS (e.g., chart.js). You can go further on anything by selecting text and components (charts) and doing deeper research, as I show in the clip. I expect more people to use agents in this way.

elvis

31,855 Aufrufe • vor 4 Monaten

Markdown was doomed from the start. It's just a format with low information density. HTML is better for humans, and agents can now consume and produce it without issues. But nobody wants to type HTML, so here is an alternative: This is an open-source tool for generating dashboards from data without writing a single HTML tag. You define your dashboard in YAML or TSK, and the tool will serve the HTML file for you. It comes with skills for Claude Code and Codex, so they know how to build these dashboards. And you can connect this to Postgres, MySQL, Snowflake, BigQuery, Redshift, Databricks, and many other databases. Repo link below.

Markdown was doomed from the start. It's just a format with low information density. HTML is better for humans, and agents can now consume and produce it without issues. But nobody wants to type HTML, so here is an alternative: This is an open-source tool for generating dashboards from data without writing a single HTML tag. You define your dashboard in YAML or TSK, and the tool will serve the HTML file for you. It comes with skills for Claude Code and Codex, so they know how to build these dashboards. And you can connect this to Postgres, MySQL, Snowflake, BigQuery, Redshift, Databricks, and many other databases. Repo link below.

Santiago

86,565 Aufrufe • vor 3 Monaten

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.

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,922 Aufrufe • vor 8 Monaten

THIS GUY CONNECTED HIS AI AGENTS TO HIS OBSIDIAN AND BUILT A BRAIN THAT LEARNS ON ITS OWN. HERE'S HOW TO BUILD IT Obsidian is just markdown files sitting in a folder. That turns out to be the perfect memory for an AI agent, because an agent can read and write those files directly. He wired his agents into the vault so they pull context from it, do the work, and write what they learned back. The notes aren't the point. The loop is, and it gets sharper every cycle How to build it: 1. Point an agent at your vault. The fastest way, no plugins, no API keys: open a terminal and run npx obsidian-mcp /path/to/your/vault. That exposes your Obsidian folder to Claude as a tool it can read, search, and write to. Add it to your Claude Code or Cowork config and restart 2. Confirm it can see the brain. Ask it: "list the notes in my vault and summarize what's in them." If it reads them back, the connection is live. Now it starts every task with everything the vault already holds instead of from zero 3. Give each agent one job and a write-back rule. Tell it: "research this, then save what you found as a new note in /brain with links to related notes." One agent researches, one summarizes, one plans. Each writes its output back into the vault 4. Close the loop. Add one line to every agent's instructions: "read /brain before starting, write your result back when done." Now each task leaves the vault richer, and the next run reads that before it works. It compounds instead of resetting 5. You only steer. Review what the brain produces, point it at the next thing. The agents handle the reading, writing, and connecting The edge isn't better notes. It's a brain that feeds itself, so the work gets sharper every cycle instead of starting over Bookmark this

THIS GUY CONNECTED HIS AI AGENTS TO HIS OBSIDIAN AND BUILT A BRAIN THAT LEARNS ON ITS OWN. HERE'S HOW TO BUILD IT Obsidian is just markdown files sitting in a folder. That turns out to be the perfect memory for an AI agent, because an agent can read and write those files directly. He wired his agents into the vault so they pull context from it, do the work, and write what they learned back. The notes aren't the point. The loop is, and it gets sharper every cycle How to build it: 1. Point an agent at your vault. The fastest way, no plugins, no API keys: open a terminal and run npx obsidian-mcp /path/to/your/vault. That exposes your Obsidian folder to Claude as a tool it can read, search, and write to. Add it to your Claude Code or Cowork config and restart 2. Confirm it can see the brain. Ask it: "list the notes in my vault and summarize what's in them." If it reads them back, the connection is live. Now it starts every task with everything the vault already holds instead of from zero 3. Give each agent one job and a write-back rule. Tell it: "research this, then save what you found as a new note in /brain with links to related notes." One agent researches, one summarizes, one plans. Each writes its output back into the vault 4. Close the loop. Add one line to every agent's instructions: "read /brain before starting, write your result back when done." Now each task leaves the vault richer, and the next run reads that before it works. It compounds instead of resetting 5. You only steer. Review what the brain produces, point it at the next thing. The agents handle the reading, writing, and connecting The edge isn't better notes. It's a brain that feeds itself, so the work gets sharper every cycle instead of starting over Bookmark this

Yarchi

58,186 Aufrufe • vor 2 Monaten

I built a Reddit marketing agent that gets your business mentioned by ChatGPT, Gemini and Claude. Not a spam bot. Not the kind that gets banned by mods. An agent that drafts genuinely valuable answers grounded in your company's actual content and slips in a brand mention only when it actually helps. Google is paying Reddit $60M a year just for their data!!! If your business isn't showing up in that data, your competitors are, and ChatGPT is recommending them instead of you. Here's how the system works: → A Claude routine pulls the target subreddit's JSON endpoint every hour for new posts → A Phase 1 checklist filters every post — is it answerable from our wiki, factual, on-brand, mod-safe? → The answer engine queries an LLM Wiki built from our blog, guides, and help center (Firecrawl ingested every page into a raw → wiki → index structure) → Claude drafts a casual, value-first answer that grounds every claim in our content → Every draft lands in Slack for human-in-the-loop review before it posts — no fire-and-forget, no bans I built this in a week for CoinLedger, the crypto tax software I've been running for 8 years. 10% of our new signups already say they found us through ChatGPT. This system is how we push that number a lot higher. If you want the exact Claude skill I built: Like & Comment "AGENT" (must be following so I can dm you) I'll send it over for free.

David Roberts

36,388 Aufrufe • vor 3 Monaten

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 Aufrufe • vor 3 Monaten

Identify Which Sectors Showing Strong Sales Growth I’ve created a simple interactive dashboard that lets you view Screener results using bar charts and pie charts. You can also instantly see which stocks belong to which sector, making your analysis faster and more visual. How to Use the Dashboard 1. Download the CSV file Click the Export button on this Screener link: 2. Convert the CSV to JSON Use this online tool to convert your CSV file into a JSON file: 3. Download the HTML file from the link below and open it in your browser: 4. Upload your JSON file Once uploaded, the dashboard will instantly display industry-wise growth charts.

Identify Which Sectors Showing Strong Sales Growth I’ve created a simple interactive dashboard that lets you view Screener results using bar charts and pie charts. You can also instantly see which stocks belong to which sector, making your analysis faster and more visual. How to Use the Dashboard 1. Download the CSV file Click the Export button on this Screener link: 2. Convert the CSV to JSON Use this online tool to convert your CSV file into a JSON file: 3. Download the HTML file from the link below and open it in your browser: 4. Upload your JSON file Once uploaded, the dashboard will instantly display industry-wise growth charts.

Sneha S

76,325 Aufrufe • vor 9 Monaten

How to create Farcaster mini app without coding - Step 1: > Go to ChatGPT > Just type: "I would like to create a Farcaster mini app, can you give me some ideas?" > Choose any one of the ideas - Note: - You can also type your own idea to ChatGPT and alter it - Step 2: - Go to ChatGPT > Paste the first prompt (shared in my channel) > Include the project you chose and tell ChatGPT to alter the prompt according to the idea below - Step 3 - Go to: > Sign up using Gmail or GitHub > Projects -> New Project -> Type the name of your project >Just paste the prompt we created earlier > It will start creating your app > If you need to alter anything, just go to GPT and type: [ I need a prompt to alter "your issue (like changing colour, etc.)" in my app already created in v0app by Vercel ] > Copy the prompt and paste it in v0 > No need to worry about errors , it will rectify them for you > If your project is finished, just click "Publish" on your top right > It will automatically host your app in Vercel > Click "Visit site" to see your app on another device and copy the website URL - Step 4 - Go to: v0 app > Just paste Prompt 2 from the file I provided > Click Publish once it’s completed - Step 5 - Go to: v0 app > Just paste the prompt 3 from the file I provided - Step 6 (Important) > Just paste Prompt 4 from the file I provided - Step 7 > Just paste Prompt 4 from the file I provided - Step 8 > Just paste Prompt 6 from the file I provided > It’s an important step to do — you need to create a manifest inside your app so that you can host it on Farcaster - Step 9 - Go to: > Sign up or Login > Settings → Developers → Mini Apps → Create Manifest (New) > Paste your website URL (remove https) > It should be like: > If you find any error while doing this, just copy and paste it in the v0 app > Once everything is finished, you need to create Account Association > Scan the QR on your mobile and tap and hold the Yes button > It will show an error — just copy and paste those errors into the v0 app > Click Publish again, and then click Refresh in Manifest > Click Open your app > for the main prompt file check our tg channel link in our bio

How to create Farcaster mini app without coding - Step 1: > Go to ChatGPT > Just type: "I would like to create a Farcaster mini app, can you give me some ideas?" > Choose any one of the ideas - Note: - You can also type your own idea to ChatGPT and alter it - Step 2: - Go to ChatGPT > Paste the first prompt (shared in my channel) > Include the project you chose and tell ChatGPT to alter the prompt according to the idea below - Step 3 - Go to: > Sign up using Gmail or GitHub > Projects -> New Project -> Type the name of your project >Just paste the prompt we created earlier > It will start creating your app > If you need to alter anything, just go to GPT and type: [ I need a prompt to alter "your issue (like changing colour, etc.)" in my app already created in v0app by Vercel ] > Copy the prompt and paste it in v0 > No need to worry about errors , it will rectify them for you > If your project is finished, just click "Publish" on your top right > It will automatically host your app in Vercel > Click "Visit site" to see your app on another device and copy the website URL - Step 4 - Go to: v0 app > Just paste Prompt 2 from the file I provided > Click Publish once it’s completed - Step 5 - Go to: v0 app > Just paste the prompt 3 from the file I provided - Step 6 (Important) > Just paste Prompt 4 from the file I provided - Step 7 > Just paste Prompt 4 from the file I provided - Step 8 > Just paste Prompt 6 from the file I provided > It’s an important step to do — you need to create a manifest inside your app so that you can host it on Farcaster - Step 9 - Go to: > Sign up or Login > Settings → Developers → Mini Apps → Create Manifest (New) > Paste your website URL (remove https) > It should be like: > If you find any error while doing this, just copy and paste it in the v0 app > Once everything is finished, you need to create Account Association > Scan the QR on your mobile and tap and hold the Yes button > It will show an error — just copy and paste those errors into the v0 app > Click Publish again, and then click Refresh in Manifest > Click Open your app > for the main prompt file check our tg channel link in our bio

Maran

48,106 Aufrufe • vor 9 Monaten

This is Farzapedia. I had an LLM take 2,500 entries from my diary, Apple Notes, and some iMessage convos to create a personal Wikipedia for me. It made 400 detailed articles for my friends, my startups, research areas, and even my favorite animes and their impact on me complete with backlinks. But, this Wiki was not built for me! I built it for my agent! The structure of the wiki files and how it's all backlinked is very easily crawlable by any agent + makes it a truly useful knowledge base. I can spin up Claude Code on the wiki and starting at index.md (a catalog of all my articles) the agent does a really good job at drilling into the specific pages on my wiki it needs context on when I have a query. For example, when trying to cook up a new landing page I may ask: "I'm trying to design this landing page for a new idea I have. Please look into the images and films that inspired me recently and give me ideas for new copy and aesthetics". In my diary I kept track of everything from: learnings, people, inspo, interesting links, images. So the agent reads my wiki and pulls up my "Philosophy" articles from notes on a Studio Ghibli documentary, "Competitor" articles with YC companies whose landing pages I screenshotted, and pics of 1970s Beatles merch I saved years ago. And it delivers a great answer. I built a similar system to this a year ago with RAG but it was ass. A knowledge base that lets an agent find what it needs via a file system it actually understands just works better. The most magical thing now is as I add new things to my wiki (articles, images of inspo, meeting notes) the system will likely update 2-3 different articles where it feels that context belongs, or, just creates a new article. It's like this super genius librarian for your brain that's always filing stuff for your perfectly and also let's you easily query the knowledge for tasks useful to you (ex. design, product, writing, etc) and it never gets tired. I might spend next week productizing this, if that's of interest to you DM me + tell me your usecase!

This is Farzapedia. I had an LLM take 2,500 entries from my diary, Apple Notes, and some iMessage convos to create a personal Wikipedia for me. It made 400 detailed articles for my friends, my startups, research areas, and even my favorite animes and their impact on me complete with backlinks. But, this Wiki was not built for me! I built it for my agent! The structure of the wiki files and how it's all backlinked is very easily crawlable by any agent + makes it a truly useful knowledge base. I can spin up Claude Code on the wiki and starting at index.md (a catalog of all my articles) the agent does a really good job at drilling into the specific pages on my wiki it needs context on when I have a query. For example, when trying to cook up a new landing page I may ask: "I'm trying to design this landing page for a new idea I have. Please look into the images and films that inspired me recently and give me ideas for new copy and aesthetics". In my diary I kept track of everything from: learnings, people, inspo, interesting links, images. So the agent reads my wiki and pulls up my "Philosophy" articles from notes on a Studio Ghibli documentary, "Competitor" articles with YC companies whose landing pages I screenshotted, and pics of 1970s Beatles merch I saved years ago. And it delivers a great answer. I built a similar system to this a year ago with RAG but it was ass. A knowledge base that lets an agent find what it needs via a file system it actually understands just works better. The most magical thing now is as I add new things to my wiki (articles, images of inspo, meeting notes) the system will likely update 2-3 different articles where it feels that context belongs, or, just creates a new article. It's like this super genius librarian for your brain that's always filing stuff for your perfectly and also let's you easily query the knowledge for tasks useful to you (ex. design, product, writing, etc) and it never gets tired. I might spend next week productizing this, if that's of interest to you DM me + tell me your usecase!

Farza 🇵🇰🇺🇸

2,107,181 Aufrufe • vor 4 Monaten

The reason your AI gives generic answers isn't the model. It's that your company's knowledge lives in 12 different tools and your agent can't see any of it. So here's how to build a context database your agents can actually use: 1) Pull it in: - Slack, email, meetings, docs, tickets - Auto-collected on a schedule into one place. 2) Clean it up. - An agent files what matters and drops the noise, so your brain doesn't bloat. 3) Store it as memory. - Folders of files your agents read from and write back to as they learn. 4) Point your agents at it. - Now they draft, build, and ship with full context instead of guessing. Same model. Same agent. The difference is whether it can understand your company or not. Build the database once. Everything downstream gets smarter.

The reason your AI gives generic answers isn't the model. It's that your company's knowledge lives in 12 different tools and your agent can't see any of it. So here's how to build a context database your agents can actually use: 1) Pull it in: - Slack, email, meetings, docs, tickets - Auto-collected on a schedule into one place. 2) Clean it up. - An agent files what matters and drops the noise, so your brain doesn't bloat. 3) Store it as memory. - Folders of files your agents read from and write back to as they learn. 4) Point your agents at it. - Now they draft, build, and ship with full context instead of guessing. Same model. Same agent. The difference is whether it can understand your company or not. Build the database once. Everything downstream gets smarter.

The Startup Ideas Podcast (SIP) 🧃

13,598 Aufrufe • vor 2 Monaten

I just built a Claude skill that acts as a second brain for DTC brands 🤯 Drop your ad exports, customer reviews, competitor screenshots, and brand docs into a folder → Claude compiles it all into an organized wiki you can ask questions against. All inside Claude Cowork. Perfect for DTC brands and agencies whose knowledge is scattered across Google Drive, Notion, Meta Ads Manager, Figma, and 47 spreadsheets nobody has opened in 3 months. If every strategic question takes 2 hours to answer because the data lives in 8 different places ... This skill eliminates the entire loop: → Claude scaffolds a DTC folder structure: ads, customers, competitors, brand, performance, notes → You drop every file you have into those folders — messy, unorganized, exactly how you have them now → Claude reads everything and compiles a wiki: hooks-that-work, customer-pains, competitor-angles, brand-voice, performance-patterns, creative-brief-library → Every article is cross-linked and traceable back to the source file → You ask questions against the wiki — "what hooks are actually working?" "what objections come up most?" "where are my competitors weak?" → Claude answers, grounded entirely in your own data → Save the answers back in and the system gets smarter every time you use it No more hunting through 12 tools. No more "where did I save that brief?" No more answering the same question twice. What you get: → A complete DTC brand brain scaffold in 60 seconds → Six core wiki articles Claude populates automatically from your raw files → A schema file that tells Claude exactly how to maintain the wiki for DTC use cases → Monthly health checks that catch contradictions and flag gaps before errors compound → A knowledge base that compounds — every question you ask makes the next answer better Built on a methodology Andrej Karpathy shared for personal knowledge bases, I rebuilt the entire thing for DTC operators: folder structure, schema rules, wiki articles, and question frameworks all tuned for brands and agencies. I put together the full skill file plus a playbook walking through the exact setup and 5 real questions to ask your brand brain. Want it for free? > Like this post > Comment "BRAIN" And I'll send it over (must be following so I can DM)

Mike Futia

15,223 Aufrufe • vor 4 Monaten

i spent 40 minutes explaining to Claude who i am. my niche. my voice. my audience. what i never say. generic output. every single time. turns out the problem wasn't Claude. it was me giving it nothing to work with. the fix: a knowledge layer. 20 minutes to set up. your notes, tweets, articles dumped into one folder. agent reads it overnight and builds 200+ wiki pages from your own thinking. next morning your AI finally sounds like you. 90% of people skip this. they just prompt → accept → ship. and wonder why everything sounds the same. and if you learn to set this up for others? 10 clients = $56,800/year. full guide below 👇

i spent 40 minutes explaining to Claude who i am. my niche. my voice. my audience. what i never say. generic output. every single time. turns out the problem wasn't Claude. it was me giving it nothing to work with. the fix: a knowledge layer. 20 minutes to set up. your notes, tweets, articles dumped into one folder. agent reads it overnight and builds 200+ wiki pages from your own thinking. next morning your AI finally sounds like you. 90% of people skip this. they just prompt → accept → ship. and wonder why everything sounds the same. and if you learn to set this up for others? 10 clients = $56,800/year. full guide below 👇

Crypto Mavka

10,742 Aufrufe • vor 3 Monaten

happy friday. sneak peek at some new features i'm building for the bankr agent: > sandboxed filesystem (your agent gets its own secure file system in the browser. you control what it can access. no agent running loose on your actual computer) > skill uploads (plugin new capabilities so your agent learns new things) > cli download & access > secure environment variables for api keys > github integration (connect your repo for reads and writes directly from your agent) all of this runs in a secure browser environment. no desktop app. no messy configuration. no downloading agent harnesses from the terminal. just a sandbox you control. in the video: i download an audit skill, run it against a smart contract, and save the report straight to the filesystem. then i ask the agent to pull all my 2026 transactions and write a csv for my accountant.

happy friday. sneak peek at some new features i'm building for the bankr agent: > sandboxed filesystem (your agent gets its own secure file system in the browser. you control what it can access. no agent running loose on your actual computer) > skill uploads (plugin new capabilities so your agent learns new things) > cli download & access > secure environment variables for api keys > github integration (connect your repo for reads and writes directly from your agent) all of this runs in a secure browser environment. no desktop app. no messy configuration. no downloading agent harnesses from the terminal. just a sandbox you control. in the video: i download an audit skill, run it against a smart contract, and save the report straight to the filesystem. then i ask the agent to pull all my 2026 transactions and write a csv for my accountant.

deployer

45,638 Aufrufe • vor 4 Monaten

Right now, I have a few dozen tools to automate my life. Every single thing that I do more than once every week is now a tool: either a Claude Code skill, a scheduled workflow, or an application. • I spend the time doing this once. • I schedule it. • I forget about it (or at least, try to) CREAO is one of the platforms I've used extensively for building some of these automations. They are partnering with me on this post. They are one of the only platforms where you can go from a conversation to a scheduled agent that quickly. This is how it works: 1. You describe the problem you want to solve 2. CREAO's agent builds the logic and executes it 3. You can iterate with the agent to improve the solution 4. When you are done, you turn that solution into a mini app 5. You can schedule that app to run any time you need it Something important: These agents are deterministic. They don't use an LLM to generate answers, so they will always return the same output given the same input. This is critical: when you're automating something that runs every Monday at 9 am, you need it to return the same result every time, not a "creative" answer.

Right now, I have a few dozen tools to automate my life. Every single thing that I do more than once every week is now a tool: either a Claude Code skill, a scheduled workflow, or an application. • I spend the time doing this once. • I schedule it. • I forget about it (or at least, try to) CREAO is one of the platforms I've used extensively for building some of these automations. They are partnering with me on this post. They are one of the only platforms where you can go from a conversation to a scheduled agent that quickly. This is how it works: 1. You describe the problem you want to solve 2. CREAO's agent builds the logic and executes it 3. You can iterate with the agent to improve the solution 4. When you are done, you turn that solution into a mini app 5. You can schedule that app to run any time you need it Something important: These agents are deterministic. They don't use an LLM to generate answers, so they will always return the same output given the same input. This is critical: when you're automating something that runs every Monday at 9 am, you need it to return the same result every time, not a "creative" answer.

Santiago

13,712 Aufrufe • vor 4 Monaten

HERMES AGENT SUPPORTS 7 TYPES OF AI AGENTS. EACH ONE TAKES LESS THAN 90 SECONDS TO SET UP. MOST PEOPLE ONLY BUILD THE FIRST ONE. HERE ARE ALL SEVEN AND WHEN TO USE EACH. 1. BASIC AGENT WITH TOOLS your agent with access to terminal, browser, file system, web search, and calendar. it plans and executes tasks on its own. this is what you get on day one. "find flights to Lisbon under $400" "check my calendar and flag conflicts" "search the web for competitor pricing" set in Desktop app / Dashboard: Tools → enable what you need. when to use: single tasks that need tool access. 2. AGENT WITH MCP SERVERS connect your agent to external services. Notion, Google Drive, GitHub, Slack, databases, APIs, any MCP-compatible service. the agent doesn't scrape these services. it interacts through structured APIs. reads your Notion pages. creates GitHub issues. queries your database. sends Slack messages. set in Desktop app / Dashboard: MCP → Add Server. when to use: your workflow lives across multiple platforms. 3. SEQUENTIAL AGENTS (pipeline) one agent finishes. passes output to the next. assembly line for AI. agent 1: scans inbox for leads. agent 2: qualifies leads against criteria. agent 3: drafts outreach emails. in Hermes: cron jobs with wakeAgent gates. agent 1 writes output to a file. agent 2 wakes only when that file has new data. agent 3 wakes when agent 2 is done. each agent = a separate profile with its own model. when to use: multi-step workflows where each step depends on the previous one finishing. 4. PARALLEL EXECUTION AGENTS multiple agents working at the same time. results merge when all finish. "research these 5 competitors in parallel" in Hermes: delegate_task with batch mode. up to 3 sub-agents running in parallel by default. each gets its own clean context. only summaries return to the parent. delegation: model: "deepseek/deepseek-v4" children run cheap. parent synthesizes. when to use: independent tasks that don't depend on each other. research, data gathering, analysis. 5. AGENTS WITH ROUTERS conditions that send tasks down different paths based on the input. "if sales email → SDR profile. if support ticket → support profile. if calendar invite → EA profile." in Hermes: Kanban decompose. the decomposer reads profile descriptions and routes each task to the best-fit agent. or: Chief of Staff profile that triages and assigns to other profiles. when to use: incoming work that needs different specialists based on type. 6. HUMAN IN THE LOOP the agent does the work. asks for your approval before executing. "I drafted this email. approve before I send?" "this command will delete 3 files. proceed?" in Hermes: approvals.mode: manual (default). every dangerous action needs your confirmation. 60-second timeout. fails closed. or smart mode: LLM assesses risk. safe actions auto-approved. dangerous ones ask you. uncertain ones escalate. when to use: tasks where a mistake has real consequences. emails, deployments, financial transactions, public posts. 7. DYNAMIC SUB-AGENT SPAWNING your main agent realizes it needs help and spawns specialized sub-agents on the fly. "build this feature" → parent delegates: → sub-agent 1: research the API docs → sub-agent 2: write the code → sub-agent 3: write the tests in Hermes: delegate_task with role: orchestrator. raise max_spawn_depth for nested delegation. delegation: max_spawn_depth: 2 orchestrator_enabled: true depth 2 with concurrency 3 = up to 9 parallel workers. each level multiplies the spend. raise depth only when you need multi-level trees. when to use: complex tasks where the agent discovers what help it needs during execution. THE PROGRESSION: start with 1 (tools) and 6 (approvals). add 2 (MCP) when you need external services. add 4 (parallel) when tasks take too long one at a time. add 3 (sequential) when you build multi-step pipelines. add 5 (routing) when you run multiple profiles. add 7 (dynamic) when single-agent reasoning falls short. seven types. each under 90 seconds to configure. the value compounds as you stack them. comment AGENTS and I'll send you 3 ready-to-build agent setups that combine these types into real workflows.

YanXbt

17,312 Aufrufe • vor 1 Monat