Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

CODEX SKILL THAT FINDS YOUR STARTUP’S FIRST CUSTOMERS! I made a Codex skill that analyzes your startup and finds potential customers from real public signals. Paste your startup URL while Codex defines your ideal customer, searches public discussions, qualifies each prospect, and generates a polished report with personalized outreach...

939,998 görüntüleme • 1 ay önce •via X (Twitter)

0 Yorum

Yorum bulunmuyor

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

Benzer Videolar

HERMES AGENT CAN SHARE MEMORY WITH CODEX AND CLAUDE CODE THROUGH HINDSIGHT. ONE MEMORY BANK. ONE AGENT REMEMBERS, EVERY OTHER AGENT KNOWS. the problem: you use Hermes for orchestration. Codex for coding. Claude Code for debugging. each has its own memory. switch between them and you explain the same project three times. Hindsight fixes this. one shared memory bank that every agent reads and writes to. tell Codex: "the test color for this project is purple." switch to Hermes. ask: "what test color did I pick?" Hermes answers: "purple." no copy-paste. no re-explaining. instant recall. HOW IT WORKS: Hindsight runs as a Docker container on your machine. self-hosted. your data stays local. an LLM powers the memory processing (retain, recall, reflect). RETAIN: extracts facts from your conversations. entities, decisions, preferences, project context. saved to the memory bank automatically. RECALL: when you ask a question, Hindsight pulls from semantic search, keywords, graph connections, and temporal data. fused into one answer. REFLECT: deeper reasoning layer. connects memories across sessions. identifies patterns in your work. produces observations that get smarter over time. CONNECT TO HERMES: Desktop app: Settings → Memory and Context → switch provider from Namosin to Hindsight. set API URL to your local Docker container. set bank ID. done. CLI: hermes memory setup → select Hindsight. verify: hermes memory status should show: provider: hindsight, installed, available. CONNECT TO CODEX: npx hindsight-coding-agents install codex \ --self-hosted --server this installs lifecycle hooks: initialize memory on session start. recall context during work. retain the session when done. enable hooks in Codex: Settings → Hooks → trust all three. CONNECT TO CLAUDE CODE (same command): npx hindsight-coding-agents install all "all" connects every detected agent on your machine. Claude Code, Codex, Cursor, and others. one command. every agent shares the same bank. TAGS FOR FILTERING: every memory gets tagged by harness (Hermes, Codex, Claude Code) and optionally by project name. in the Hindsight control plane: filter by harness. see only Hermes memories. or only Codex memories. or search across everything. soft partitions inside one bank. not hard walls. cross-reference when you need to. ONE BANK OR MANY: one global bank: solo dev, related projects. all agents share everything. patterns emerge across projects. per-project banks: unrelated codebases. each project gets its own memory. no cross-contamination. your call. start with one. split when projects diverge. KNOWLEDGE PAGES (v0.9.0): Hindsight auto-generates living summaries from your accumulated memories. components, concepts, conventions, decisions. not static docs. projected from real agent conversations. auto-refresh as new memories land. WHAT TO KNOW: self-hosted via Docker. your data never leaves your machine. backup system built in (admin CLI + scheduled exports). works with any LLM (local Ollama, OpenAI, Codex subscription). memory defense: redact or block sensitive content automatically. 33,000+ memories accumulated in ~10 days of normal use.

YanXbt

29,200 görüntüleme • 22 gün önce

I just built a Reddit research agent in Claude Code that turns real customer complaints into ad angles 🤯 It scrapes the threads where people actually rant about your category, reads every post and comment, and hands you back a dashboard of pain points, exact customer phrases, and ready-to-test ad angles. All inside Claude Code. Perfect for DTC brands and agencies who want ad angles pulled from real customer language, not guessed in a vacuum. Reddit is the most honest focus group on earth. People say things there they'd never put in a survey or a review with a brand watching. So if you're writing hooks off your own assumptions — or digging through Reddit by hand, opening tab after tab, pasting quotes into a doc... This agent runs the entire loop: → Give it a product or category + a couple of subreddits → It searches Reddit for the threads where people actually discuss the problem → Pulls every post and comment → Claude reads all of it and finds the patterns → Builds a dashboard: pain points, desires, objections, and swipe-worthy phrases No manual scrolling. No pasting quotes into docs. No guessing what your customers actually care about. What you get: → Ranked customer pain points, each with a real verbatim quote → The exact language your customers use, ready to drop into ad copy → Objections and buying triggers pulled straight from the threads → 8-10 ready-to-test ad angles built from all of it Built 100% in Claude Code. Want the skill file for free? > Like this post > Comment "REDDIT" And I'll send it over (must be following so I can DM)

Mike Futia

46,020 görüntüleme • 2 ay önce

We open-sourced our entire outbound team. Introducing the GojiberryAI Sales OS for Grok Bot. A full AI sales department. Each agent gets a job. Each gets access to the GojiberryAI MCP. And they work together to find, research, contact, and qualify prospects while you sleep. 🖤 Head of Sales · decides who to target and why 🟢 Signal Hunter · finds prospects showing real buying intent 🟪 ICP Analyst · filters out bad fits before outreach starts 🔷 Account Researcher · researches every company + prospect ⚪️ Lead Enricher · finds emails, phone numbers, and missing data 🔺 Intent Scorer · ranks prospects by likelihood to buy 🔵 LinkedIn Copywriter · writes personalised messages for every lead 🟡 Outreach Operator · launches and manages LinkedIn campaigns 🟥 Reply Agent · reads replies and identifies interested prospects 🟤 Follow-up Agent · makes sure warm opportunities don't disappear 🟩 Meeting Qualifier · qualifies prospects before they reach your calendar 🟣 Pipeline Analyst · tells you which ICPs, signals, and messages actually convert 🔶 Sales Manager · coordinates everything and keeps the pipeline moving And they hand work to each other: Signal Hunter finds someone who engaged with a competitor → ICP Analyst checks if they're a fit → Account Researcher finds the angle → Lead Enricher gets their contact data → Copywriter creates the message → Outreach Operator contacts them → Reply Agent handles the response → Meeting Qualifier moves them toward a demo. All powered by the GojiberryAI MCP. One link. Install it in Grok Bot. Turn Grok into your outbound team. Comment "BOT" and I'll send it to you.

Romàn

56,678 görüntüleme • 8 gün önce

EVERYTHING YOU NEED TO KNOW ABOUT CHATGPT'S "LOVABLE KILLER" CODEX SITES (in 25 mins): TLDR; the coolest part is that apps you build can update themselves autonomously 1. Codex Sites is not Replit or Lovable or Bolt. Those are great for one-prompting a full app. Codex Sites is for building apps that the agent keeps improving without you touching them. 2. Your personal website can update its own stats. Your internal dashboard can refresh its own data. Your product can add features while you sleep. The app is alive. 3. Start by invoking at-sites. Use realistic sample data. Always say "save for review, do not deploy." This unlocks building a real product, not a homepage. 4. Add persistent storage so the app remembers everything between visits. Without this it resets every time. Ask Codex to show you the data model before it builds. 5. Create safe actions. These are the specific things the agent is allowed to do to your app: add data, update cards, move things, score things. You define the boundaries. The agent operates within them. 6. Build skills so any future Codex chat knows how to interact with your app. The skill is basically a manual for the agent. Without it, every new chat starts from zero. 7. Save gate like a video game. Codex doesn't auto-save. Create checkpoints before you deploy so you can roll back if something breaks. 8. Close the autonomous loop. This is the magic. Once memory, safe actions, and skills are set up, the agent can update your app from any chat, any context, without you switching tabs. 9. Use the plugins most people are sleeping on. Figma, Canva, HeyGen for avatar videos, Game Studio for interactive experiences, FAL for image generation, Hugging Face for open source models. Worth adding a few. 10. The big picture: we went from building apps to raising apps. You set up the structure, the guardrails, and the skills. The agent does the rest. That's autonomous product building and it's here right now. Tbh, Codex sites isn't perfect. Still a lot to be desired like domains, db, authentication etc. But it's a glimpse into this idea that apps can be updated/improved upon automonously. And Codex Sites is REALLY good if you live in Codex everyday. Which more and more of are. And that's really cool. Will be interesting to see how Lovable, Bolt, Replit etc react to this. full tutorial on The Startup Ideas Podcast (SIP) 🧃 where you get your pods watch share with a friend i'm rooting for you What do you think of Codex and Codex sites?

GREG ISENBERG

69,219 görüntüleme • 3 ay önce

Three skills I use every day in Claude Code and Codex to solve my hardest problems: 1️⃣ /agent-watchdog When I have one agent like Codex working on a task and I don't fully trust it's going to do everything right, I'll open up another one like Claude Code and tell it to watchdog the Codex thread. You can copy the Codex deep link into Claude Code and it'll look at the prompt you sent, watch the Codex thread until it's done, then compare the Codex solution to how it was planning to solve it and automatically fix anything that Codex missed. It can also test the work of the other agent end-to-end. Similar to the idea of OpenRouter's new Fusion feature, I've definitely found that two models thinking through a problem and checking each other's work can be wildly more impactful than just one. 2️⃣ /plan-arbiter Similar ideas as /agent-watchdog - but with this one you have both make plans, compare plans, negotiate the differences, and make a final plan to execute. I find Claude Code is better at writing plans, but Codex is faster and cheaper to execute on them. Then I usually have Claude Code watchdog the Codex work and fix anything that was missed. 3️⃣ /read-the-damn-docs One thing that drives me crazy with coding agents is they're so reluctant to look up docs. They'll just guess and guess and guess at the right API surface for things, or the right solution to an integration of two things. Once I explicitly tell it to look up the docs, it says "Oh, I see the answer," and it fixes the problem. So I made the /read-the-damn-docs skill. Add it and your agents will know when and how to do efficient web searches to look up docs for the types of problems you really should look up docs for. All of these are totally open source over on my GitHub. If you try them, let me know your feedback. Will link to them below:

Steve (Builder.io)

43,089 görüntüleme • 2 ay önce

Send this to ANYONE on your team using AI agents with Claude/Codex skills: If I were you, I'd put your BEST AI skills in a GitHub repo, turn that repo into a PLUGIN, and have your team INSTALL it in Claude/Codex with auto update on. Why? 1. Everyone gets the same AI SOPs instead of 10 versions floating around Slack 2. When one person improves a skill, the whole team gets the better version. 3. New hires can start with your best workflows instead of a blank AI setup (this is a BIG deal). 4. If someone breaks a skill, you can roll it back with version control. 5. Personal skills can stay personal, while team skills become shared company infrastructure (and an asset!). 6. Your best AI processes stay with the company when someone leaves. 7. You can chain skills together for bigger workflows, like titles -> thumbnails -> descriptions -> YouTube publish. 8. You can track which skills are actually being used and delete the ones collecting dust. 9. You get less slop because the agent has real instructions, examples, taste, and process. 10. Your team moves from single-player AI to multiplayer AI. (thanks to AI with Remy | Learn AI for coming onto The Startup Ideas Podcast (SIP) 🧃) Watch full breakdown here (clearly explained): I don't know why I didn't do this before. The more I think about it, the more obvious it feels: your AI workflows should be version controlled company assets. It kinda feels like the difference between “we use AI” and “we actually operate with AI". Enjoy.

GREG ISENBERG

79,539 görüntüleme • 21 gün önce