惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

MongoDB | Blog
MongoDB | Blog
B
Blog RSS Feed
MyScale Blog
MyScale Blog
M
MIT News - Artificial intelligence
H
Hackread – Cybersecurity News, Data Breaches, AI and More
J
Java Code Geeks
U
Unit 42
Blog — PlanetScale
Blog — PlanetScale
L
LangChain Blog
C
Check Point Blog
WordPress大学
WordPress大学
Last Week in AI
Last Week in AI
人人都是产品经理
人人都是产品经理
T
Tailwind CSS Blog
Vercel News
Vercel News
腾讯CDC
GbyAI
GbyAI
有赞技术团队
有赞技术团队
S
SegmentFault 最新的问题
H
Help Net Security
博客园 - 三生石上(FineUI控件)
D
DataBreaches.Net
Microsoft Security Blog
Microsoft Security Blog
小众软件
小众软件

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
An outreach kit for solo founders whose drafts can't hall...
Randy Rockwe · 2026-05-25 · via DEV Community

Randy Rockwell

An outreach kit for solo founders whose drafts can't hallucinate

Short version: five Claude skills, a canonical state file template, and a Python inbox agent that watches Gmail, GitHub, and dev.to for replies. End-to-end pipeline from discovery through logged sends. Self-hosted. $5/mo subscription.

The thing that's different about this kit isn't the automation. It's the discipline the automation enforces.

Every send requires a verified specific hook

The drafting skill asks for the personalization detail before it'll write the message. If the detail is vague, it asks again. Generic openers are blocked at the input layer.

Required inputs:
- candidate_name
- product_summary
- specific_detail  <- the verified hook from the actual source
- channel
- send_type (FIRST_CONTACT or CHASE_1)

Enter fullscreen mode Exit fullscreen mode

No specific_detail → no draft. The skill won't fabricate one.

Every claim runs through a hallucination filter

You write your allowed claims and forbidden claims patterns at setup. The drafter scans every output against them. The first hallucinated metric flags the whole draft and proposes a fix using only allowed claims.

This is Claude's hallucination guardrail. The LLM is the author of every draft and could fabricate metrics that sound plausible. The filter prevents that. Drafts can only use facts you've verified.

Example output when the filter trips:

=== BLUFF FILTER REPORT ===
Status: FLAGGED

Violation: "we've seen agents pay $X per query for this kind of data"

Rules triggered:
  - Forbidden phrase: "we've seen" (implies customer data you don't have)
  - Fabricated price: $X is not in allowed_claims
  - Fabricated volume: implies a customer base you aren't operating

Proposed replacement (uses only allowed claims):
  "[your verified price] — volume's still low, but the rails work"

Enter fullscreen mode Exit fullscreen mode

The replacement is shorter and weaker-sounding than the bluff. That's the point. A bluff that breaks your credibility costs more than a true claim that lands flat.

Every action goes through a Python script with preservation checks

The state file (validation_state.md) is append-only. Structured sections: Sent Log, Active Conversations, Pattern Notes, Closed-loop. Every send, reply, chase, and close-loop is mediated by a script that verifies the file grew the way it should and aborts before writing if anything looks wrong.

  • Verifies the file size increased for append-only events
  • Verifies the previous tail anchor line is still present
  • Verifies all existing Pattern Note subsections survived
  • Verifies the row delta matches the event type
  • Aborts on any failure — file on disk is unchanged

Built after watching a naive LLM Edit silently truncate the trailing section of a long markdown file. Never again.

The inbox agent: multi-channel approval handshake

Watches Gmail (via OAuth send), GitHub (via PAT), and dev.to (via API key). Polls each channel on a configurable cadence. New reply comes in → drafts a response → pushes to Telegram with Send/Edit/Skip buttons.

You tap Send: the reply goes out through the channel's real API.
You tap Edit: type your version, it sends as-is.
You tap Skip: nothing happens.

Telegram is the v1 approval surface. The architecture is built to accept other surfaces.

What this is not

This is not Apollo. There is no contact database. There is no "give me 50 founders matching X." Discovery runs against live public posts at runtime, not a cached DB.

It is not marketing automation. It does not blast. It does not "scale personalization" by templating someone's first name.

If you're a solo founder running cold outreach to other founders or operators and you want the discipline of an institutional sales motion without the institutional headcount, this is for you.

If you want to send 1000 emails a day to a scraped list, this kit will actively work against you.

Pricing

$5.00 USD per month. Founding 100 subscribers are locked at $5/mo for life as long as their subscription stays active.

Each subsequent 100 active subscribers, the price goes up $5/mo for new sign-ups. Next cohort $10, then $15, etc. Founding members keep their lock.

No refunds. Once you have access to the code, you have access. We can't un-show it.

How to subscribe

  1. Pay via the Stripe payment link below.
  2. Email me your GitHub username (randyrockwell05@gmail.com or reply to your Stripe confirmation).
  3. You'll receive a GitHub invitation to collaborate on the private repo within 24 hours.
  4. Accept the invitation, clone the repo, drop the skills into your Claude environment.

Full setup walkthrough lives in the repo's README.

Try it

If you try it and have thoughts, tell me. Especially if there's a feature you'd pay more for — that's the signal I'm watching for in the first 30 days.