Shipped · Product builder · Personal project · 2026

How I automated LinkedIn growth without sounding like a bot

LinkedIn Tools is a private monorepo for posting, golden-hour replies, feed comments, and hiring outreach: Cursor-agent skills plus always-on Linux cron, with copy gates so it keeps a human voice.

  • Agentic ops
  • LinkedIn
  • Notion
  • Buffer
  • Python

Problem

I needed to automate LinkedIn engagement and growth (posting, replies, outreach) without sounding like a bot. Growth work was a pile of one-off scripts: posting from Notion, replying in the first 90 minutes, commenting on other people's posts, and finding hiring threads. I needed a system a Cursor agent could run, with a human voice, on an always-on host.

Metrics

  • One monorepo for content posting, engagement, messaging, and outreach instead of scattered scripts
  • Publish-day flow: Notion Content Library to Buffer schedule to go-live sync to golden-hour replies
  • Outreach stops at drafts (Gmail queue). No auto-send of cold mail or DMs

Decisions

  1. Treat content, engagement, and outreach as modules with skills, not a single chatbot that posts unsupervised.
  2. Prefer an always-on Linux host for live ticks. macOS launchd is fallback only so two daemons never double-comment.
  3. Keep the repo private. It holds session cookies, Buffer tokens, and outreach drafts. This page is the public write-up; there is no live demo.

Outcomes

  • Shipped a Cursor-agent catalog (content posting, golden hour, feed engage, messaging, hiring discover, cold outreach) with specs and a test script.
  • Golden hour replies only on my posts; feed engage comments on others via a rate-limited daemon (baseline plus a hot boost while a slot is armed).
  • Hiring posts land in a Notion Opening database. Cold outreach produces drafts, not sends.

I needed to automate LinkedIn engagement and growth (posting, replies, outreach) without sounding like a bot. LinkedIn Tools is how I run that as operations: a Python/Cursor monorepo that drafts and schedules from a Notion Content Library via Buffer, replies in the 90-minute golden hour on my own posts, comments on other people’s posts from a Linux daemon, reads DMs on demand, and turns hiring posts into Notion rows plus outreach drafts.

Live demo: none. The GitHub repo is private (cookies, tokens, outreach). I do not publish unlisted outreach endpoints or Agent HQ URLs. This mini-case is the public artifact.

What it is

Lane What ships
Content Notion Ready rows to Buffer; confirm go-live; sync Posted back to Notion
Golden hour Auto-replies on comments on my posts during the first 90 minutes
Feed engage Proactive comments on others’ posts, always-on Linux cron
Outreach Hiring-post discovery into Notion; cold drafts into Gmail. No auto-send

The product bet: agentic ops should keep a human voice. Copy gates and draft queues exist so the system does not spray bot comments or mail. I am happy to walk a hiring manager through the publish-day flowchart without opening the private repo.

← All projects