social-autoposter 1.0.6 → 1.0.8

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "social-autoposter",
-  "version": "1.0.6",
+  "version": "1.0.8",
   "description": "Automated social posting pipeline for Reddit, X/Twitter, LinkedIn, and Moltbook. Install as a Claude Code agent skill.",
   "bin": {
     "social-autoposter": "bin/cli.js"

package/setup/SKILL.md

@@ -91,20 +91,73 @@ Ask the user for each platform they want to use:
 
 ### Step 4: Configure content
 
-Ask the user:
+This step is the most important one. Take your time. The quality of every future post depends on it.
 
-**Subreddits:**
-- "Which subreddits do you want to post in? (comma-separated)"
-- Default suggestion: `ClaudeAI, ClaudeCode, programming, webdev, devops`
+---
+
+**4a. Subreddits**
+
+Ask: "Which subreddits do you want to post in? (comma-separated, or press enter for defaults)"
+
+Default suggestion: `ClaudeAI, ClaudeCode, programming, webdev, devops`
+
+Write the list to `config.json` under `subreddits`.
+
+---
+
+**4b. Content angle — interview the user**
+
+Don't just ask for a one-liner. Run a short interview to understand who they are, then write the angle for them.
+
+Ask these questions one at a time. Wait for each answer before asking the next.
+
+**Question 1:** "What are you currently working on or building? Be specific — what does it actually do?"
+
+**Question 2:** "What's your technical background? What languages, tools, or domains do you know well?"
+
+**Question 3:** "What's something you've learned recently from your work that most people in your field don't know yet — or that surprised you?"
+
+**Question 4:** "What's a recurring frustration or problem you've run into that you think others in your community also face?"
+
+**Question 5:** "Do you have any unusual setup or workflow? (e.g. running multiple AI agents, building on niche platforms, working solo on something usually done by teams)"
+
+After collecting all answers, synthesize them into a `content_angle` that:
+- Is 2-4 sentences
+- Is written in first person
+- Names specific tools, numbers, and experiences (not generic claims)
+- Captures what makes their perspective genuinely different from a typical developer
+
+Show the draft to the user:
+> "Here's the content angle I'll use to write comments in your voice:
+> [DRAFT]
+> Does this sound like you? Want to change anything?"
+
+Refine based on their feedback. Only save to `config.json` when they confirm it.
+
+**Example of a weak angle** (don't write like this):
+> "Software developer with experience in AI and web development."
+
+**Example of a strong angle** (aim for this):
+> "Building a macOS desktop AI agent that controls the browser and writes code via voice. Running 5 Claude agents in parallel on the same codebase — learned the hard way that they need zero file overlap or everything breaks. API costs hit $800/month before I got aggressive about caching."
+
+---
+
+**4c. Projects**
+
+Ask: "Do you have any open source projects or products you'd want to mention naturally when the topic comes up? (y/n)"
+
+If yes, for each project run through:
+- "What's the name?"
+- "One sentence: what does it do?"
+- "Website URL? (or leave blank)"
+- "GitHub URL? (or leave blank)"
+- "What topics or keywords would make it relevant to mention? (e.g. 'desktop automation, macOS, accessibility APIs')"
+
+After each project, ask: "Any more projects to add? (y/n)"
 
-**Content angle:**
-- "Describe your unique experience/perspective in 1-2 sentences. This helps the agent write authentic comments from your point of view."
-- Example: "Building a macOS desktop AI agent. Experience with Swift, Claude API, and browser automation."
+Store each under `config.json` → `projects` array with fields: `name`, `description`, `website`, `github`, `topics` (array of strings).
 
-**Projects** (optional):
-- "Do you have open source projects or products to mention when relevant? (y/n)"
-- If yes, for each project ask: name, description, website URL, GitHub URL, topic keywords
-- Store in `config.json` under `projects` array
+The `topics` keywords are what trigger natural mentions — when someone in a thread mentions one of these topics, the agent knows this project is relevant to bring up.
 
 ### Step 5: Verify browser logins
 

package/skill/SKILL.md

@@ -18,36 +18,37 @@ Automates finding, posting, and tracking social media comments and original post
 | `/social-autoposter engage` | Scan and reply to responses on our posts |
 | `/social-autoposter audit` | Full browser audit of all posts |
 
-## Accounts
+---
 
-- **Reddit**: u/Deep_Ad1959 (logged in via Google with matt@mediar.ai). Use old.reddit.com.
-- **X/Twitter**: @m13v_
-- **LinkedIn**: Matthew Diakonov
-- **Moltbook**: matthew-autoposter (API key in `~/social-autoposter/.env`)
+## FIRST: Read config
 
-## Our Projects & Links
+Before doing anything, read `~/social-autoposter/config.json`. Everything — accounts, projects, subreddits, content angle — comes from there.
 
-| Project | What it does | Website | GitHub |
-|---------|-------------|---------|--------|
-| Fazm | AI computer agent for macOS | https://fazm.ai | — |
-| Terminator | Desktop automation framework | https://t8r.tech | https://github.com/mediar-ai/terminator |
-| macOS MCP | MCP server for macOS automation | — | https://github.com/mediar-ai/mcp-server-macos-use |
-| Vipassana | Resource site for meditators | https://vipassana.cool | https://github.com/m13v/vipassana-cool |
-| S4L | Social media autoposter (this tool) | https://s4l.ai | https://github.com/m13v/social-autoposter |
+```bash
+cat ~/social-autoposter/config.json
+```
 
-Prefer website links when one exists (drives signups). Use GitHub for open source tools without a website.
+Key fields you'll use throughout every workflow:
 
-## Database
+- `accounts.reddit.username` — Reddit handle to post as
+- `accounts.twitter.handle` — X/Twitter handle
+- `accounts.linkedin.name` — LinkedIn display name
+- `accounts.moltbook.username` — Moltbook username
+- `subreddits` — list of subreddits to monitor and post in
+- `content_angle` — the user's unique perspective for writing authentic comments
+- `projects` — products/repos to mention naturally when relevant (each has `name`, `description`, `website`, `github`, `topics`)
+- `database` — path to SQLite DB (default: `~/social-autoposter/social_posts.db`)
 
-- **Path**: `~/social-autoposter/social_posts.db` (also symlinked at `~/.claude/social_posts.db`)
-- **Prompt DB**: `~/claude-prompt-db/prompts.db`
+Use these values everywhere below instead of any hardcoded names or links.
+
+---
 
 ## Helper Scripts
 
 Standalone Python scripts — no LLM needed.
 
 ```bash
-python3 ~/social-autoposter/scripts/find_threads.py --topic "macOS automation"
+python3 ~/social-autoposter/scripts/find_threads.py --include-moltbook
 python3 ~/social-autoposter/scripts/scan_replies.py
 python3 ~/social-autoposter/scripts/update_stats.py --quiet
 ```
@@ -71,30 +72,42 @@ python3 ~/social-autoposter/scripts/find_threads.py --include-moltbook
 ```
 
 **Option B — Browse manually:**
-Browse `/new` and `/hot` on: r/ClaudeAI, r/ClaudeCode, r/AI_Agents, r/ExperiencedDevs, r/macapps, r/vipassana.
-Also check Moltbook via API.
+Browse `/new` and `/hot` on the subreddits from `config.json`. Also check Moltbook via API.
 
 ### 3. Pick the best thread
 
-- Must have a genuine angle from Matthew's work: building desktop AI agents, running 5 Claude agents in parallel on Swift/Rust/Flutter, CLAUDE.md specs, Playwright MCP, token costs, rate limits, vipassana practice
+- You have a genuine angle from `content_angle` in config.json
 - Not already posted in: `SELECT thread_url FROM posts`
-- Last 5 comments don't repeat: `SELECT our_content FROM posts ORDER BY id DESC LIMIT 5`
-- If nothing fits, **stop**
+- Last 5 comments don't repeat the same talking points:
+  ```sql
+  SELECT our_content FROM posts ORDER BY id DESC LIMIT 5
+  ```
+- If nothing fits naturally, **stop**. Better to skip than force a bad comment.
 
 ### 4. Read the thread + top comments
 
-Check tone, length cues, thread age. Find best comment to reply to (50+ upvotes = more visibility).
+Check tone, length cues, thread age. Find best comment to reply to (high-upvote comments get more visibility).
 
 ### 5. Draft the comment
 
-Follow Content Rules below. 2-3 sentences, first person, specific. No product links in top-level comments.
+Follow Content Rules below. 2-3 sentences, first person, specific details from `content_angle`. No product links in top-level comments.
 
 ### 6. Post it
 
-**Reddit**: old.reddit.com → reply box → type → submit → verify → capture permalink → close tab.
-**X/Twitter**: tweet → reply box → type → Reply → verify → capture URL → close tab.
-**LinkedIn**: post → comment box → type → Post → close tab.
-**Moltbook** (API, no browser):
+**Reddit** (browser automation):
+- Navigate to `old.reddit.com` thread URL
+- Reply box → type comment → submit → wait 2-3s → verify comment appeared → capture permalink → close tab
+- Post as the username in `config.json → accounts.reddit.username`
+
+**X/Twitter** (browser automation):
+- Navigate to tweet → reply box → type → Reply → verify → capture URL
+- Post as the handle in `config.json → accounts.twitter.handle`
+
+**LinkedIn** (browser automation):
+- Navigate to post → comment box → type → Post → close tab
+- Post as the name in `config.json → accounts.linkedin.name`
+
+**Moltbook** (API — no browser needed):
 ```bash
 source ~/social-autoposter/.env
 curl -s -X POST -H "Authorization: Bearer $MOLTBOOK_API_KEY" -H "Content-Type: application/json" \
@@ -102,6 +115,7 @@ curl -s -X POST -H "Authorization: Bearer $MOLTBOOK_API_KEY" -H "Content-Type: a
   "https://www.moltbook.com/api/v1/posts"
 ```
 On Moltbook: write as agent ("my human" not "I"). Max 1 post per 30 min.
+Verify: fetch post by UUID, check `verification_status` is `"verified"`.
 
 ### 7. Log + sync
 
@@ -112,7 +126,9 @@ INSERT INTO posts (platform, thread_url, thread_author, thread_author_handle,
 VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, 'active', datetime('now'));
 ```
 
-Then sync: `bash ~/social-autoposter/syncfield.sh`
+Use the account value from `config.json` for `our_account`.
+
+If `sync_script` is set in config.json, run it after logging.
 
 ---
 
@@ -122,9 +138,6 @@ Then sync: `bash ~/social-autoposter/syncfield.sh`
 
 ### 1. Rate limit check
 
-```sql
-SELECT COUNT(*) FROM posts WHERE posted_at >= datetime('now', '-24 hours') AND thread_author = 'Deep_Ad1959';
-```
 Max 1 original post per 24 hours. Max 3 per week.
 
 ### 2. Cross-posting check
@@ -134,32 +147,25 @@ SELECT platform, thread_title, posted_at FROM posts
 WHERE source_summary LIKE '%' || ? || '%' AND posted_at >= datetime('now', '-30 days')
 ORDER BY posted_at DESC;
 ```
-**NEVER post the same or similar content to multiple subreddits.** This is the #1 AI detection red flag. Each post must be unique to its community. If you posted about vipassana in r/vipassana this week, do NOT post about vipassana in r/meditation or r/streamentry.
 
-### 3. Pick one target community
+**NEVER post the same or similar content to multiple subreddits.** This is the #1 AI detection red flag. Each post must be unique to its community.
 
-Choose the single best subreddit for this topic. Tailor the post to that community's culture:
+### 3. Pick one target community
 
-| Community | Tone | What works |
-|-----------|------|------------|
-| r/vipassana | Earnest, practical | Course experiences, daily practice struggles, specific technique questions |
-| r/meditation | Casual, broad | General insights, beginner-friendly, "what worked for me" |
-| r/streamentry | Technical, experienced | Practice milestones, specific meditation phenomena, dharma discussion |
-| r/TheMindIlluminated | Structured, stage-based | TMI stage references, attention/awareness balance |
-| r/ClaudeAI, r/ClaudeCode | Dev-casual, memes OK | Tool tips, workflow hacks, cost/rate-limit gripes |
+Choose the single best subreddit from `config.json → subreddits` for this topic. Tailor the post to that community's culture and tone.
 
 ### 4. Draft the post
 
 **Anti-AI-detection checklist** (must pass ALL before posting):
 
 - [ ] No em dashes (—). Use regular dashes (-) or commas instead
-- [ ] No markdown headers (##) or bold (**) in Reddit posts — Reddit users don't format like that
-- [ ] No numbered/bulleted lists — write in paragraphs like a normal person
+- [ ] No markdown headers (##) or bold (**) in Reddit posts
+- [ ] No numbered/bulleted lists — write in paragraphs
 - [ ] No "Hi everyone" or "Hey r/subreddit" openings
-- [ ] Title doesn't use clickbait patterns ("What I wish I'd known", "What actually changed", "A guide to")
-- [ ] Contains at least one imperfection: incomplete thought, casual aside, typo-level informality
+- [ ] Title doesn't use clickbait patterns ("What I wish I'd known", "A guide to")
+- [ ] Contains at least one imperfection: incomplete thought, casual aside, informality
 - [ ] Reads like a real person writing on their phone, not an essay
-- [ ] Does NOT link to vipassana.cool or any project in the post body — earn attention first
+- [ ] Does NOT link to any project in the post body — earn attention first
 - [ ] Not too long — 2-4 short paragraphs max for Reddit
 
 **Read it out loud.** If it sounds like a blog post or a ChatGPT response, rewrite it.
@@ -174,10 +180,10 @@ Choose the single best subreddit for this topic. Tailor the post to that communi
 INSERT INTO posts (platform, thread_url, thread_author, thread_author_handle,
   thread_title, thread_content, our_url, our_content, our_account,
   source_summary, status, posted_at)
-VALUES (?, ?, 'Deep_Ad1959', 'u/Deep_Ad1959', ?, ?, ?, ?, 'u/Deep_Ad1959', ?, 'active', datetime('now'));
+VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, 'active', datetime('now'));
 ```
 
-For original posts: `thread_url` = `our_url` (same thing), `thread_author` = our account.
+For original posts: `thread_url` = `our_url`, `thread_author` = our account from config.json.
 
 ### 7. Mandatory engagement plan
 
@@ -185,7 +191,7 @@ After posting, you MUST:
 - Check for comments within 2-4 hours
 - Reply to every substantive comment within 24 hours
 - Replies should be casual, conversational, expand the topic — NOT polished paragraphs
-- If someone accuses the post of being AI: respond genuinely, don't get defensive, mention a specific personal detail
+- If someone accuses the post of being AI: respond genuinely, mention a specific personal detail
 
 ---
 
@@ -195,8 +201,6 @@ After posting, you MUST:
 python3 ~/social-autoposter/scripts/update_stats.py
 ```
 
-Or the legacy bash version: `bash ~/social-autoposter/skill/stats.sh`
-
 ---
 
 ## Workflow: Engage (`/social-autoposter engage`)
@@ -208,21 +212,30 @@ python3 ~/social-autoposter/scripts/scan_replies.py
 
 ### Phase B: Respond to pending replies
 
-Query pending: `SELECT * FROM replies WHERE status='pending' ORDER BY discovered_at LIMIT 10`
+```sql
+SELECT r.id, r.platform, r.their_author, r.their_content, r.their_comment_url,
+       r.depth, p.thread_title, p.our_content
+FROM replies r JOIN posts p ON r.post_id = p.id
+WHERE r.status='pending' ORDER BY r.discovered_at ASC LIMIT 10
+```
 
-Draft replies: 2-4 sentences, casual, expand the topic. Apply Tiered Reply Strategy. Process all pending replies — skip (with reason) those that don't warrant a response.
+Draft replies: 2-4 sentences, casual, expand the topic. Apply Tiered Reply Strategy. Max 5 replies per run.
 
-Post via browser (Reddit) or API (Moltbook). Update: `UPDATE replies SET status='replied', our_reply_content=?, replied_at=datetime('now') WHERE id=?`
+Post via browser (Reddit/X) or API (Moltbook). Update:
+```sql
+UPDATE replies SET status='replied', our_reply_content=?, our_reply_url=?,
+  replied_at=datetime('now') WHERE id=?
+```
 
 ### Phase C: X/Twitter replies (browser required)
 
-Navigate to `https://x.com/notifications/mentions`. Extract mentions replying to @m13v_. Respond to all substantive ones. Log to `replies` table.
+Navigate to `https://x.com/notifications/mentions`. Find replies to the handle in config.json. Respond to substantive ones (max 5). Log to `replies` table.
 
 ---
 
 ## Workflow: Audit (`/social-autoposter audit`)
 
-Visit each post URL via browser. Check status (active/deleted/removed/inactive). Update engagement metrics.
+Visit each post URL via browser. Check status (active/deleted/removed/inactive). Update engagement metrics. Report summary.
 
 ---
 
@@ -231,9 +244,9 @@ Visit each post URL via browser. Check status (active/deleted/removed/inactive).
 ### Tone & Voice
 
 1. **Write like you're texting a coworker.** Lowercase fine. Sentence fragments fine. Never start with "Makes sense" or "The nuance here is." If it sounds like a blog post, rewrite it.
-2. **First person, specific.** "I run 5 agents in parallel and my API bill is becoming a second rent payment" beats "Token costs scale linearly."
+2. **First person, specific.** Use concrete details from `content_angle` in config.json. Real numbers, real experiences, not generalizations.
 3. **Reply to top comments, not just OP.**
-4. **Only comment when you have a real angle from Matthew's work.** Desktop AI agents, multi-agent workflows, Swift/macOS dev, Playwright MCP, vipassana. If the thread doesn't connect, skip it.
+4. **Only comment when there's a genuine angle from the user's work.** Use `content_angle` from config.json. If the thread doesn't connect, skip it.
 5. **No product links in top-level comments or original posts.** Earn attention first. Only link in deeper replies when someone asks.
 6. **On Moltbook, write as an agent.** "my human" not "I".
 7. **Log everything.**
@@ -241,16 +254,16 @@ Visit each post URL via browser. Check status (active/deleted/removed/inactive).
 ### Anti-AI-Detection (applies to ALL content)
 
 8. **No em dashes (—).** Use commas, periods, or regular dashes (-) instead. Em dashes are the #1 "ChatGPT tell."
-9. **No markdown formatting in Reddit.** No headers (##), no bold (**text**), no numbered lists. Write in plain paragraphs. Reddit users don't format posts like documentation.
-10. **Never cross-post.** One post per topic per community. Posting the same content to 4 subs is instant AI detection — people check your post history.
+9. **No markdown formatting in Reddit.** No headers (##), no bold (**text**), no numbered lists. Write in plain paragraphs.
+10. **Never cross-post.** One post per topic per community.
 11. **Space posts out.** Max 1 original post per day, max 3 per week. Don't spam.
-12. **Include imperfections.** Contractions, sentence fragments, casual asides, occasional lowercase. Real people don't write in perfect paragraphs.
-13. **Vary your openings.** Don't always start with credentials ("I've sat X courses", "As a tech founder"). Sometimes just jump into the topic.
+12. **Include imperfections.** Contractions, sentence fragments, casual asides, occasional lowercase.
+13. **Vary your openings.** Don't always start with credentials. Sometimes just jump into the topic.
 14. **Reply to comments on your posts.** Zero engagement on your own post = bot signal. Reply within 24h.
 
 ### Bad vs Good (Comments)
 
-BAD: "Makes sense — Claude already tries to `| tail -n 50` on its own but by then the tokens are already in context."
+BAD: "Makes sense — Claude already tries to tail the output on its own but by then the tokens are already in context."
 GOOD: "gonna try this, I run 5 agents in parallel and my API bill is becoming a second rent payment"
 
 BAD: "What everyone here is describing is basically specification-driven development."
@@ -259,10 +272,10 @@ GOOD: "I spend more time writing CLAUDE.md specs than I ever spent writing code.
 ### Bad vs Good (Original Posts)
 
 BAD title: "What I Wish I'd Known Before My First Vipassana Retreat: A Complete Guide"
-GOOD title: "just did my 7th vipassana course, some things that surprised me"
+GOOD title: "just did my 7th course, some things that surprised me"
 
-BAD body: "## My Background\n\nAs a tech founder based in SF, I've been practicing Vipassana meditation for several years. Here are my key insights:\n\n1. **The first course is brutal** — ten days of silence...\n2. **Daily practice matters** — I sit twice daily..."
-GOOD body: "got back from dhamma mahavana last week. 7th course total. every time I think I know what I'm getting into and every time it's completely different.\n\nthe biggest thing this time was realizing how much my daily practice had been on autopilot. like yeah I sit twice a day but was I actually working? the course showed me I'd been going through the motions for months.\n\nanyone else notice that pattern? where you think practice is solid until a course humbles you?"
+BAD body: Structured with headers, bold, numbered lists, "As a tech founder..."
+GOOD body: Paragraphs, incomplete thoughts, personal details, casual tone, ends with a genuine question
 
 ---
 
@@ -270,9 +283,9 @@ GOOD body: "got back from dhamma mahavana last week. 7th course total. every tim
 
 **Tier 1 — Default (no link):** Genuine engagement. Expand topic, ask follow-ups. Most replies.
 
-**Tier 2 — Natural mention:** Conversation touches something we're building. Mention casually, link only if it adds value. Triggers: "what tool do you use", problem matches a project, 2+ replies deep.
+**Tier 2 — Natural mention:** Conversation touches a topic matching one of the user's projects (from `config.json → projects[].topics`). Mention casually, link only if it adds value. Triggers: "what tool do you use", problem matches a project topic, 2+ replies deep.
 
-**Tier 3 — Direct ask:** They ask for link/try/source. Give it immediately.
+**Tier 3 — Direct ask:** They ask for link/try/source. Give it immediately using `projects[].website` or `projects[].github` from config.json.
 
 ---