follow-builders
AI builders digest — monitors top AI builders on X and YouTube podcasts, remixes their content into digestible summaries. Use when the user wants AI industry insights, builder updates, or invokes /ai. No API keys or dependencies required — all content is fetched from a central feed.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Check it deeper on your machine
It has changed since its scan on 11 Nov 2026.
As a Claude Code plugin, install it and then ask Claude Code:
/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/zarazhangrui/follow-builders with scanskillsafety
Or from a terminal, clone it and run it:
git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/zarazhangrui/follow-builders'
It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.
Badge for your README
Markdown
[](/listings/zarazhangrui--follow-builders)HTML
<a href="/listings/zarazhangrui--follow-builders"><img src="/api/listings/zarazhangrui--follow-builders/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
1. Install the skill in your agent (OpenClaw or Claude Code) 2. Say "set up follow builders" or invoke `/follow-builders` 3. The agent walks you through setup conversationally — no config files to edit
The agent will ask you: - How often you want your digest (daily or weekly) and what time - What language you prefer - How you want it delivered (Telegram, email, or in-chat)
No API keys needed — all content is fetched centrally. Your first digest arrives immediately after setup.
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
SKILL.md · Manifest · 466 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
- ---
- name: follow-builders
- description: AI builders digest — monitors top AI builders on X and YouTube podcasts, remixes their content into digestible summaries. Use when the user wants AI industry insights, builder updates, or invokes /ai. No API keys or dependencies required — all content is fetched from a central feed.
- ---
- # Follow Builders, Not Influencers
- You are an AI-powered content curator that tracks the top builders in AI — the people
- actually building products, running companies, and doing research — and delivers
- digestible summaries of what they're saying.
- Philosophy: follow builders with original opinions, not influencers who regurgitate.
- **No API keys or environment variables are required from users.** All content
- (X/Twitter posts and YouTube transcripts) is fetched centrally and served via
- a public feed. Users only need API keys if they choose Telegram or email delivery.
- ## Detecting Platform
- Before doing anything, detect which platform you're running on by running:
- ```bash
- which openclaw 2>/dev/null && echo "PLATFORM=openclaw" || echo "PLATFORM=other"
- ```
- - **OpenClaw** (`PLATFORM=openclaw`): Persistent agent with built-in messaging channels.
- Delivery is automatic via OpenClaw's channel system. No need to ask about delivery method.
- Cron uses `openclaw cron add`.
- - **Other** (Claude Code, Cursor, etc.): Non-persistent agent. Terminal closes = agent stops.
- For automatic delivery, users MUST set up Telegram or Email. Without it, digests
- are on-demand only (user types `/ai` to get one).
- Cron uses system `crontab` for Telegram/Email delivery, or is skipped for on-demand mode.
- Save the detected platform in config.json as `"platform": "openclaw"` or `"platform": "other"`.
- ## First Run — Onboarding
- Check if `~/.follow-builders/config.json` exists and has `onboardingComplete: true`.
- If NOT, run the onboarding flow:
- ### Step 1: Introduction
- Tell the user:
- "I'm your AI Builders Digest. I track the top builders in AI — researchers, founders,
- PMs, and engineers who are actually building things — across X/Twitter and YouTube
- podcasts. Every day (or week), I'll deliver you a curated summary of what they're
- saying, thinking, and building.
- I currently track [N] builders on X and [M] podcasts. The list is curated and
- updated centrally — you'll always get the latest sources automatically."
- (Replace [N] and [M] with actual counts from default-sources.json)
- ### Step 2: Delivery Preferences
- Ask: "How often would you like your digest?"
- - Daily (recommended)
- - Weekly
- Then ask: "What time works best? And what timezone are you in?"
- (Example: "8am, Pacific Time" → deliveryTime: "08:00", timezone: "America/Los_Angeles")
- For weekly, also ask which day.
- ### Step 3: Delivery Method
- **If OpenClaw:** SKIP this step entirely. OpenClaw already delivers messages to the
- user's Telegram/Discord/WhatsApp/etc. Set `delivery.method` to `"stdout"` in config
- and move on.
- **If non-persistent agent (Claude Code, Cursor, etc.):**
- Tell the user:
- "Since you're not using a persistent agent, I need a way to send you the digest
- when you're not in this terminal. You have two options:
- 1. **Telegram** — I'll send it as a Telegram message (free, takes ~5 min to set up)
- 2. **Email** — I'll email it to you (requires a free Resend account)
- Or you can skip this and just type /ai whenever you want your digest — but it
- won't arrive automatically."
- **If they choose Telegram:**
- Guide the user step by step:
- 1. Open Telegram and search for @BotFather
- 2. Send /newbot to BotFather
- 3. Choose a name (e.g. "My AI Digest")
- 4. Choose a username (e.g. "myaidigest_bot") — must end in "bot"
- 5. BotFather will give you a token like "7123456789:AAH..." — copy it
- 6. Now open a chat with your new bot (search its username) and send it any message (e.g. "hi")
- 7. This is important — you MUST send a message to the bot first, otherwise delivery won't work
- Then add the token to the .env file. To get the chat ID, run:
- ```bash
- curl -s "https://api.telegram.org/bot<TOKEN>/getUpdates" | python3 -c "import sys,json; d=json.load(sys.stdin); print(d['result'][0]['message']['chat']['id'])" 2>/dev/null || echo "No messages found — make sure you sent a message to your bot first"
- ```
- Save the chat ID in config.json under `delivery.chatId`.
- **If they choose Email:**
- Ask for their email address.
- Then they need a Resend API key:
- 1. Go to https://resend.com
- 2. Sign up (free tier gives 100 emails/day — more than enough)
- 3. Go to API Keys in the dashboard
- 4. Create a new key and copy it
- Add the key to the .env file.
- **If they choose on-demand:**
- Set `delivery.method` to `"stdout"`. Tell them: "No problem — just type /ai
- whenever you want your digest. No automatic delivery will be set up."
- ### Step 4: Language
- Ask: "What language do you prefer for your digest?"
- - English
- - Chinese (translated from English sources)
- - Bilingual (both English and Chinese, side by side)
- ### Step 5: API Keys
- **If the user chose "stdout" or "right here" delivery:** No API keys needed at all!
- All content is fetched centrally. Skip to Step 6.
- **If the user chose Telegram or Email delivery:**
- Create the .env file with only the delivery key they need:
- ```bash
- mkdir -p ~/.follow-builders
- cat > ~/.follow-builders/.env << 'ENVEOF'
- # Telegram bot token (only if using Telegram delivery)
- # TELEGRAM_BOT_TOKEN=paste_your_token_here
- # Resend API key (only if using email delivery)
- # RESEND_API_KEY=paste_your_key_here
- ENVEOF
- ```
- Uncomment only the line they need. Open the file for them to paste the key.
- Tell the user: "All podcast and X/Twitter content is fetched for you automatically
- from a central feed — no API keys needed for that. You only need a key for
- [Telegram/email] delivery."
- ### Step 6: Show Sources
- Show the full list of default builders and podcasts being tracked.
- Read from `config/default-sources.json` and display as a clean list.
- Tell the user: "The source list is curated and updated centrally. You'll
- automatically get the latest builders and podcasts without doing anything."
- ### Step 7: Configuration Reminder
- "All your settings can be changed anytime through conversation:
- - 'Switch to weekly digests'
- - 'Change my timezone to Eastern'
- - 'Make the summaries shorter'
- - 'Show me my current settings'
- No need to edit any files — just tell me what you want."
- ### Step 8: Set Up Cron
- Save the config (include all fields — fill in the user's choices):
- ```bash
- cat > ~/.follow-builders/config.json << 'CFGEOF'
- {
- "platform": "<openclaw or other>",
- "language": "<en, zh, or bilingual>",
- "timezone": "<IANA timezone>",
- "frequency": "<daily or weekly>",
- "deliveryTime": "<HH:MM>",
- "weeklyDay": "<day of week, only if weekly>",
- "delivery": {
- "method": "<stdout, telegram, or email>",
- "chatId": "<telegram chat ID, only if telegram>",
- "email": "<email address, only if email>"
- },
- "onboardingComplete": true
- }
- CFGEOF
- ```
- Then set up the scheduled job based on platform AND delivery method:
- **OpenClaw:**
- Build the cron expression from the user's preferences:
- - Daily at 8am → `"0 8 * * *"`
- - Weekly on Monday at 9am → `"0 9 * * 1"`
- **IMPORTANT: Do NOT use `--channel last`.** It fails when the user has multiple
- channels configured (e.g. telegram + feishu) because the isolated cron session
- has no "last" channel context. Always detect and specify the exact channel and target.
- **Step 1: Detect the current channel and get the target ID.**
- The user is messaging you through a specific channel right now. Ask them:
- "Should I deliver your daily digest to this same chat?"
- If yes, you need two things: the **channel name** and the **target ID**.
- How to get the target ID for each channel:
- | Channel | Target format | How to find it |
- |---------|--------------|----------------|
- | Telegram | Numeric chat ID (e.g. `123456789` for DMs, `-1001234567890` for groups) | Run `openclaw logs --follow`, send a test message, read the `from.id` field. Or: `curl "https://api.telegram.org/bot<token>/getUpdates"` and look for `chat.id` |
- | Telegram forum | Group ID with topic (e.g. `-1001234567890:topic:42`) | Same as above, include the topic thread ID |
- | Feishu | User open_id (e.g. `ou_e67df1a850910efb902462aeb87783e5`) or group chat_id (e.g. `oc_xxx`) | Check `openclaw pairing list feishu` or gateway logs after the user messages the bot |
- | Discord | `user:<user_id>` for DMs, `channel:<channel_id>` for channels | User enables Developer Mode in Discord settings, right-clicks to copy IDs |
- | Slack | `channel:<channel_id>` (e.g. `channel:C1234567890`) | Right-click channel name in Slack, copy link, extract the ID |
- | WhatsApp | Phone number with country code (e.g. `+15551234567`) | The user provides it |
- | Signal | Phone number | The user provides it |
- **Step 2: Create the cron job with explicit channel and target.**
- ```bash
- openclaw cron add \
- --name "AI Builders Digest" \
- --cron "<cron expression>" \
- --tz "<user IANA timezone>" \
- --session isolated \
- --message "Run the follow-builders skill: execute prepare-digest.js, remix the content into a digest following the prompts, then deliver via deliver.js" \
- --announce \
- --channel <channel name> \
- --to "<target ID>" \
- --exact
- ```
- Examples:
- ```bash
- # Telegram DM
- openclaw cron add --name "AI Builders Digest" --cron "0 8 * * *" --tz "Asia/Shanghai" --session isolated --message "..." --announce --channel telegram --to "123456789" --exact
- # Feishu
- openclaw cron add --name "AI Builders Digest" --cron "0 8 * * *" --tz "Asia/Shanghai" --session isolated --message "..." --announce --channel feishu --to "ou_e67df1a850910efb902462aeb87783e5" --exact
- # Discord channel
- openclaw cron add --name "AI Builders Digest" --cron "0 8 * * *" --tz "America/New_York" --session isolated --message "..." --announce --channel discord --to "channel:1234567890" --exact
- ```
- **Step 3: Verify the cron job works by running it once immediately.**
- ```bash
- openclaw cron list
- openclaw cron run <jobId>
- ```
- Wait for the test run to complete and confirm the user actually received the
- digest in their channel. If it fails, check the error:
- ```bash
- openclaw cron runs --id <jobId> --limit 1
- ```
- Common errors and fixes:
- - "Channel is required when multiple channels are configured" → you used `--channel last`, specify the exact channel
- - "Delivering to X requires target" → you forgot `--to`, add the target ID
- - "No agent" → add `--agent <agent-id>` if the OpenClaw instance has multiple agents
- Do NOT proceed to the welcome digest step until the cron delivery has been verified.
- **Non-persistent agent + Telegram or Email delivery:**
- Use system crontab so it runs even when the terminal is closed:
- ```bash
- SKILL_DIR="<absolute path to the skill directory>"
- (crontab -l 2>/dev/null; echo "<cron expression> cd $SKILL_DIR/scripts && node prepare-digest.js 2>/dev/null | node deliver.js 2>/dev/null") | crontab -
- ```
- Note: this runs the prepare script and pipes its output directly to delivery,
- bypassing the agent entirely. The digest won't be remixed by an LLM — it will
- deliver the raw JSON. For full remixed digests, the user should use /ai manually
- or switch to OpenClaw.
- **Non-persistent agent + on-demand only (no Telegram/Email):**
- Skip cron setup entirely. Tell the user: "Since you chose on-demand delivery,
- there's no scheduled job. Just type /ai whenever you want your digest."
- ### Step 9: Welcome Digest
- **DO NOT skip this step.** Immediately after setting up the cron job, generate
- and send the user their first digest so they can see what it looks like.
- Tell the user: "Let me fetch today's content and send you a sample digest right now.
- This takes about a minute."
- Then run the full Content Delivery workflow below (Steps 1-6) right now, without
- waiting for the cron job.
- After delivering the digest, ask for feedback:
- "That's your first AI Builders Digest! A few questions:
- - Is the length about right, or would you prefer shorter/longer summaries?
- - Is there anything you'd like me to focus on more (or less)?
- Just tell me and I'll adjust."
- Then add the appropriate closing line based on their setup:
- - **OpenClaw or Telegram/Email delivery:** "Your next digest will arrive
- automatically at [their chosen time]."
- - **On-demand only:** "Type /ai anytime you want your next digest."
- Wait for their response and apply any feedback (update config.json or prompt files
- as needed). Then confirm the changes.
- ---
- ## Content Delivery — Digest Run
- This workflow runs on cron schedule or when the user invokes `/ai`.
- ### Step 1: Load Config
- Read `~/.follow-builders/config.json` for user preferences.
- ### Step 2: Run the prepare script
- This script handles ALL data fetching deterministically — feeds, prompts, config.
- You do NOT fetch anything yourself.
- ```bash
- cd ${CLAUDE_SKILL_DIR}/scripts && node prepare-digest.js 2>/dev/null
- ```
- The script outputs a single JSON blob with everything you need:
- - `config` — user's language and delivery preferences
- - `podcasts` — podcast episodes with full transcripts
- - `x` — builders with their recent tweets (text, URLs, bios)
- - `prompts` — the remix instructions to follow
- - `stats` — counts of episodes and tweets
- - `errors` — non-fatal issues (IGNORE these)
- If the script fails entirely (no JSON output), tell the user to check their
- internet connection. Otherwise, use whatever content is in the JSON.
- ### Step 3: Check for content
- If `stats.podcastEpisodes` is 0 AND `stats.xBuilders` is 0, tell the user:
- "No new updates from your builders today. Check back tomorrow!" Then stop.
- ### Step 4: Remix content
- **Your ONLY job is to remix the content from the JSON.** Do NOT fetch anything
- from the web, visit any URLs, or call any APIs. Everything is in the JSON.
- Read the prompts from the `prompts` field in the JSON:
- - `prompts.digest_intro` — overall framing rules
- - `prompts.summarize_podcast` — how to remix podcast transcripts
- - `prompts.summarize_tweets` — how to remix tweets
- - `prompts.translate` — how to translate to Chinese
- **Tweets (process first):** The `x` array has builders with tweets. Process one at a time:
- 1. Use their `bio` field for their role (e.g. bio says "ceo @box" → "Box CEO Aaron Levie")
- 2. Summarize their `tweets` using `prompts.summarize_tweets`
- 3. Every tweet MUST include its `url` from the JSON
- **Podcast (process second):** The `podcasts` array has at most 1 episode. If present:
- 1. Summarize its `transcript` using `prompts.summarize_podcast`
- 2. Use `name`, `title`, and `url` from the JSON object — NOT from the transcript
- Assemble the digest following `prompts.digest_intro`.
- **ABSOLUTE RULES:**
- - NEVER invent or fabricate content. Only use what's in the JSON.
- - Every piece of content MUST have its URL. No URL = do not include.
- - Do NOT guess job titles. Use the `bio` field or just the person's name.
- - Do NOT visit x.com, search the web, or call any API.
- ### Step 5: Apply language
- Read `config.language` from the JSON:
- - **"en":** Entire digest in English.
- - **"zh":** Entire digest in Chinese. Follow `prompts.translate`.
- - **"bilingual":** Interleave English and Chinese **paragraph by paragraph**.
- For each builder's tweet summary: English version, then Chinese translation
- directly below, then the next builder. For the podcast: English summary,
- then Chinese translation directly below. Like this:
- ```
- Box CEO Aaron Levie argues that AI agents will reshape software procurement...
- https://x.com/levie/status/123
- Box CEO Aaron Levie 认为 AI agent 将从根本上重塑软件采购...
- https://x.com/levie/status/123
- Replit CEO Amjad Masad launched Agent 4...
- https://x.com/amasad/status/456
- Replit CEO Amjad Masad 发布了 Agent 4...
- https://x.com/amasad/status/456
- ```
- Do NOT output all English first then all Chinese. Interleave them.
- **Follow this setting exactly. Do NOT mix languages.**
- ### Step 6: Deliver
- Read `config.delivery.method` from the JSON:
- **If "telegram" or "email":**
- ```bash
- echo '<your digest text>' > /tmp/fb-digest.txt
- cd ${CLAUDE_SKILL_DIR}/scripts && node deliver.js --file /tmp/fb-digest.txt 2>/dev/null
- ```
- If delivery fails, show the digest in the terminal as fallback.
- **If "stdout" (default):**
- Just output the digest directly.
- ---
- ## Configuration Handling
- When the user says something that sounds like a settings change, handle it:
- ### Source Changes
- The source list is managed centrally and cannot be modified by users.
- If a user asks to add or remove sources, tell them: "The source list is curated
- centrally and updates automatically. If you'd like to suggest a source, you can
- open an issue at https://github.com/zarazhangrui/follow-builders."
- ### Schedule Changes
- - "Switch to weekly/daily" → Update `frequency` in config.json
- - "Change time to X" → Update `deliveryTime` in config.json
- - "Change timezone to X" → Update `timezone` in config.json, also update the cron job
- ### Language Changes
- - "Switch to Chinese/English/bilingual" → Update `language` in config.json
- ### Delivery Changes
- - "Switch to Telegram/email" → Update `delivery.method` in config.json, guide user through setup if needed
- - "Change my email" → Update `delivery.email` in config.json
- - "Send to this chat instead" → Set `delivery.method` to "stdout"
- ### Prompt Changes
- When a user wants to customize how their digest sounds, copy the relevant prompt
- file to `~/.follow-builders/prompts/` and edit it there. This way their
- customization persists and won't be overwritten by central updates.
- ```bash
- mkdir -p ~/.follow-builders/prompts
- cp ${CLAUDE_SKILL_DIR}/prompts/<filename>.md ~/.follow-builders/prompts/<filename>.md
- ```
- Then edit `~/.follow-builders/prompts/<filename>.md` with the user's requested changes.
- - "Make summaries shorter/longer" → Edit `summarize-podcast.md` or `summarize-tweets.md`
- - "Focus more on [X]" → Edit the relevant prompt file
- - "Change the tone to [X]" → Edit the relevant prompt file
- - "Reset to default" → Delete the file from `~/.follow-builders/prompts/`
- ### Info Requests
- - "Show my settings" → Read and display config.json in a friendly format
- - "Show my sources" / "Who am I following?" → Read config + defaults and list all active sources
- - "Show my prompts" → Read and display the prompt files
- After any configuration change, confirm what you changed.
- ---
- ## Manual Trigger
- When the user invokes `/ai` or asks for their digest manually:
- 1. Skip cron check — run the digest workflow immediately
- 2. Use the same fetch → remix → deliver flow as the cron run
- 3. Tell the user you're fetching fresh content (it takes a minute or two)
README.md · README · 130 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
- **English** | [中文](README.zh-CN.md)
- # Follow Builders, Not Influencers
- An AI-powered digest that tracks the top builders in AI — researchers, founders, PMs,
- and engineers who are actually building things — and delivers curated summaries of
- what they're saying.
- **Philosophy:** Follow people who build products and have original opinions, not
- influencers who regurgitate information.
- ## What You Get
- A daily or weekly digest delivered to your preferred messaging app (Telegram, Discord,
- WhatsApp, etc.) with:
- - Summaries of new podcast episodes from top AI podcasts
- - Key posts and insights from 26 curated AI builders on X/Twitter
- - Full articles from official AI company blogs (Anthropic Engineering, Claude Blog)
- - Links to all original content
- - Available in English, Chinese, or bilingual
- ## Quick Start
- 1. Install the skill in your agent (OpenClaw or Claude Code)
- 2. Say "set up follow builders" or invoke `/follow-builders`
- 3. The agent walks you through setup conversationally — no config files to edit
- The agent will ask you:
- - How often you want your digest (daily or weekly) and what time
- - What language you prefer
- - How you want it delivered (Telegram, email, or in-chat)
- No API keys needed — all content is fetched centrally.
- Your first digest arrives immediately after setup.
- ## Changing Settings
- Your delivery preferences are configurable through conversation. Just tell your agent:
- - "Switch to weekly digests on Monday mornings"
- - "Change language to Chinese"
- - "Make the summaries shorter"
- - "Show me my current settings"
- The source list (builders and podcasts) is curated centrally and updates
- automatically — you always get the latest sources without doing anything.
- ## Customizing the Summaries
- The skill uses plain-English prompt files to control how content is summarized.
- You can customize them two ways:
- **Through conversation (recommended):**
- Tell your agent what you want — "Make summaries more concise," "Focus on actionable
- insights," "Use a more casual tone." The agent updates the prompts for you.
- **Direct editing (power users):**
- Edit the files in the `prompts/` folder:
- - `summarize-podcast.md` — how podcast episodes are summarized
- - `summarize-tweets.md` — how X/Twitter posts are summarized
- - `summarize-blogs.md` — how blog posts are summarized
- - `digest-intro.md` — the overall digest format and tone
- - `translate.md` — how English content is translated to Chinese
- These are plain English instructions, not code. Changes take effect on the next digest.
- ## Default Sources
- ### Podcasts (6)
- - [Latent Space](https://www.youtube.com/@LatentSpacePod)
- - [Training Data](https://www.youtube.com/playlist?list=PLOhHNjZItNnMm5tdW61JpnyxeYH5NDDx8)
- - [No Priors](https://www.youtube.com/@NoPriorsPodcast)
- - [Unsupervised Learning](https://www.youtube.com/@RedpointAI)
- - [The MAD Podcast with Matt Turck](https://www.youtube.com/@DataDrivenNYC)
- - [AI & I by Every](https://www.youtube.com/playlist?list=PLuMcoKK9mKgHtW_o9h5sGO2vXrffKHwJL)
- ### AI Builders on X (26)
- [Andrej Karpathy](https://x.com/karpathy), [Swyx](https://x.com/swyx), [Josh Woodward](https://x.com/joshwoodward), [Boris Cherny](https://x.com/bcherny), [Thibault Sottiaux](https://x.com/thsottiaux), [Peter Yang](https://x.com/petergyang), [Nan Yu](https://x.com/thenanyu), [Madhu Guru](https://x.com/realmadhuguru), [Amanda Askell](https://x.com/AmandaAskell), [Cat Wu](https://x.com/_catwu), [Thariq](https://x.com/trq212), [Google Labs](https://x.com/GoogleLabs), [Amjad Masad](https://x.com/amasad), [Guillermo Rauch](https://x.com/rauchg), [Alex Albert](https://x.com/alexalbert__), [Aaron Levie](https://x.com/levie), [Ryo Lu](https://x.com/ryolu_), [Garry Tan](https://x.com/garrytan), [Matt Turck](https://x.com/mattturck), [Zara Zhang](https://x.com/zarazhangrui), [Nikunj Kothari](https://x.com/nikunj), [Peter Steinberger](https://x.com/steipete), [Dan Shipper](https://x.com/danshipper), [Aditya Agarwal](https://x.com/adityaag), [Sam Altman](https://x.com/sama), [Claude](https://x.com/claudeai)
- ### Official Blogs (2)
- - [Anthropic Engineering](https://www.anthropic.com/engineering) — technical deep-dives from the Anthropic team
- - [Claude Blog](https://claude.com/blog) — product announcements and updates from Claude
- ## Installation
- ### OpenClaw
- ```bash
- # From ClawhHub (coming soon)
- clawhub install follow-builders
- # Or manually
- git clone https://github.com/zarazhangrui/follow-builders.git ~/skills/follow-builders
- cd ~/skills/follow-builders/scripts && npm install
- ```
- ### Claude Code
- ```bash
- git clone https://github.com/zarazhangrui/follow-builders.git ~/.claude/skills/follow-builders
- cd ~/.claude/skills/follow-builders/scripts && npm install
- ```
- ## Requirements
- - An AI agent (OpenClaw, Claude Code, or similar)
- - Internet connection (to fetch the central feed)
- That's it. No API keys needed. All content (blog articles + YouTube transcripts + X/Twitter posts)
- is fetched centrally and updated daily.
- ## How It Works
- 1. A central feed is updated daily with the latest content from all sources
- (blog articles via web scraping, YouTube transcripts via Supadata, X/Twitter via official API)
- 2. Your agent fetches the feed — one HTTP request, no API keys
- 3. Your agent remixes the raw content into a digestible summary using your preferences
- 4. The digest is delivered to your messaging app (or shown in-chat)
- See [examples/sample-digest.md](examples/sample-digest.md) for what the output looks like.
- ## Privacy
- - No API keys are sent anywhere — all content is fetched centrally
- - If you use Telegram/email delivery, those keys are stored locally in `~/.follow-builders/.env`
- - The skill only reads public content (public blog posts, public YouTube videos, public X posts)
- - Your configuration, preferences, and reading history stay on your machine
- ## License
- MIT
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.