Build-in-Public with Hermes
Use Hermes as an autonomous build-in-public engine — ship code, post about it, grow an audience, build a community. Reference models: @levelsio (Pieter Levels), @marc_louvion, @tdinh_me, @outsource_.
When to Use
- Setting up Hermes as an autonomous social media presence
- Designing a "social media manager" Hermes profile
- Deploying Hermes on a VPS for always-on posting
- Choosing X Premium tiers for growth
- Planning a build-in-public content strategy
Prerequisites
- xurl CLI installed and authenticated (see
xurl skill)
- gh CLI authenticated (for GitHub integration)
- Hermes running (local or VPS)
X Premium Tier Recommendation
For build-in-public growth, Premium ($8/mo) is the right tier:
| Feature |
Why it matters for BIP |
| Blue checkmark |
Credibility at 0 followers; higher click-through on profile |
| Reply prioritization |
Your replies show higher in threads of bigger accounts — #1 growth lever under 5K followers |
| Creator monetization |
Revenue sharing + subscriptions unlock at Premium |
| 50% fewer ads |
Followers see more of your content |
Premium+ ($40/mo) is NOT worth it because:
- Hermes replaces Grok (higher Grok limits irrelevant)
- xurl + web_search replaces Radar Search
- Articles → link to GitHub/blog instead
- $32/mo difference funds VPS + API costs
Cost breakdown for the full stack:
- X Premium: $8/mo
- VPS (Hetzner CX22 / DO): ~$5/mo
- Hermes API (Nous): ~$5-15/mo
- Total: ~$18-28/mo (less than Premium+ alone)
Social Media Manager Profile Design
Profile Config
# ~/.hermes/profiles/social/config.yaml
model:
provider: nous
default: qwen/qwen3.6-flash
base_url: https://inference-api.nousresearch.com/v1
tools:
enabled: [web, terminal, file, x_search]
disabled: [delegation, computer_use]
plugins:
enabled: [disk-cleanup, icarus]
terminal:
timeout: 120
Model choice rationale: Posting is high-volume, low-reasoning. Flash-tier ($0.19/$1.13 per 1M) is 3-5x cheaper than reasoning models with no quality loss for short-form content.
SOUL.md Traits
The social profile's SOUL should encode:
- Concise, punchy copy (280-char default, use 25k when needed)
- Technical but not jargon-heavy
- Transparent: share failures alongside wins
- Never generic AI-isms ("game-changer", "leverage", "unlock")
- Authentic voice — first person, specific details
- Engagement-first: replies and conversations > broadcast
Skills to Attach
xurl — posting, replying, searching, engagement
draft-post — execution layer for drafting individual posts/threads
brand-review-content — quality gate before posting (AI-ism detection, voice check)
reply-research — research-first reply drafting (the engagement growth lever)
github-pr-workflow — detect new pushes/PRs for content triggers
youtube-content — if doing video content
Content Strategy
Daily Cadence (3-4 posts/day)
| Time (ET) |
Type |
Example |
| 9 AM |
Morning intention |
"Building X feature today — here's the approach" |
| 12 PM |
Progress update |
Screenshot/GIF of what's working |
| 5 PM |
Wrap-up |
"Shipped X. Y broke. Tomorrow: fix Y." |
| Varies |
Reply engagement |
15-30 min replying to larger accounts |
Content Types (rotate)
- "Built this today" — feature, screenshot, GIF, demo
- "Debugging hell" — honest failure story (gets MORE engagement than wins)
- "Lesson learned" — actionable insight from the trenches
- "Revenue/metrics update" — transparent numbers, even $0
- Thread — deep-dive on a technical decision (hook → 5-7 value tweets → CTA)
- Question — specific question to drive engagement
Weekly Cadence
- Friday: Progress thread (like @levelsio's weekly summaries)
- Monthly: Revenue/metrics transparency post
Peak Posting Times (2026 data)
- Primary: Wed–Fri, 9–11 AM ET
- Secondary: Mon–Tue ~10 AM; Sat 8–10 AM; Sun 9 AM–12 PM
- Experiment: Late-night (10 PM–12 AM) for international audiences
Engagement Strategy (the growth lever)
Reply prioritization is the #1 growth mechanic for accounts under 5K followers:
- Search #buildinpublic, #indiehacker via
xurl search
- Reply to accounts 2-10x your size with genuine value
- Target: 10-15 quality replies/day
- Never pitch in replies — add insight, ask questions, share related experience
VPS Deployment Architecture
┌─────────────────────────────────────────────┐
│ Linux VPS (always-on) │
│ ├── Hermes installed headlessly │
│ ├── Senna profile (orchestrator) │
│ ├── Social profile (posting agent) │
│ ├── Cron jobs (posting schedule) │
│ ├── xurl (X API) │
│ ├── gh CLI (GitHub) │
│ └── Gateway (connects to user's devices) │
└─────────────────────────────────────────────┘
Content Pipeline Flow
You code (local Mac)
→ git push to GitHub
→ VPS Hermes detects push (cron poll or webhook)
→ Social profile drafts post about what changed
→ Posts at next peak-time window via xurl
→ Monitors replies via xurl mentions
→ Notifies you (Telegram/Discord) if reply needs personal response
→ Weekly: generates progress thread
Cron Job Setup
# Morning post — what we're building today
hermes cronjob create \
--name "bip-morning" \
--schedule "0 9 * * *" \
--profile social \
--skills xurl \
--prompt "Draft and post a build-in-public morning update. Check recent git commits for context on what's being worked on. Keep it concise, specific, authentic. Post via xurl." \
--deliver origin
# Midday update — progress check
hermes cronjob create \
--name "bip-midday" \
--schedule "0 12 * * *" \
--profile social \
--skills xurl \
--prompt "Draft a midday progress update. Check git log for today's commits. If nothing new, skip silently (don't post filler). If progress exists, post a concise update with specifics." \
--deliver origin
# Evening wrap-up
hermes cronjob create \
--name "bip-evening" \
--schedule "0 17 * * *" \
--profile social \
--skills xurl \
--prompt "Draft an end-of-day wrap-up. What shipped, what broke, what's next. Be honest about failures — they get more engagement than wins. Post via xurl." \
--deliver origin
# Friday thread
hermes cronjob create \
--name "bip-weekly-thread" \
--schedule "0 10 * * 5" \
--profile social \
--skills xurl \
--prompt "Draft a weekly progress thread (5-7 tweets). Hook tweet → what was built → challenges → lessons → what's next → CTA. Post as a thread via xurl." \
--deliver origin
Engagement Cron (replies)
# Daily engagement — reply to build-in-public community
hermes cronjob create \
--name "bip-engagement" \
--schedule "0 14 * * *" \
--profile social \
--skills xurl \
--prompt "Search X for recent #buildinpublic and #indiehacker posts. Find 5-10 posts from accounts with 1K-100K followers. Reply to each with genuine value — insight, related experience, or a thoughtful question. Never pitch. Never generic. Be specific." \
--deliver origin
Pitfalls
Don't post filler. If nothing happened, skip silently. "Working on stuff" posts kill engagement. The cron prompts above check git activity before posting.
Don't automate replies blindly. The engagement cron should draft replies for review, not post autonomously, until the voice is calibrated. Start with --deliver origin so you see what's being posted.
Don't start with automation. Post manually for the first 200-500 followers to calibrate the voice, learn what resonates, and build authentic relationships. Then hand off to Hermes.
Don't ignore replies. The algorithm rewards fast reply engagement. If Hermes posts, you should still check replies personally within 1 hour for the first few months.
Don't use Premium+. The $32/mo savings over Premium+ funds your entire VPS + API stack.
Don't post only wins. Failure stories get 2-3x more engagement than success stories. Authenticity is the build-in-public moat.
VPS credential management. xurl credentials (~/.xurl) and GitHub tokens need to be set up on the VPS separately from your Mac. Don't copy them — run xurl auth oauth2 and gh auth login on the VPS directly.
Cron timezone. VPS crons run in UTC. Convert peak ET times: 9 AM ET = 14:00 UTC (EST) or 13:00 UTC (EDT). Adjust seasonally.
Growth Timeline (realistic expectations)
| Phase |
Followers |
Focus |
| Foundation (0-200) |
Manual posting, voice calibration |
Daily updates, engage manually |
| Consistency (200-500) |
Reply guy strategy, weekly threads |
Start automating posts |
| Momentum (500-1200) |
Collaborate, share milestones |
Full Hermes automation active |
| Acceleration (1200-2500) |
Algorithm boost, inbound DMs |
Community building |
| Pre-launch (2500-4000) |
Announce products, early access |
Monetization begins |
Related Skills
draft-post — execution layer: draft individual posts, threads, blog posts, emails
Execution Layer Skills
This skill is the strategy layer — what to post, when, and why. The actual writing and quality-checking lives in dedicated execution skills:
| Skill |
Purpose |
draft-post |
Write a single piece of content (X post, thread, LinkedIn, blog, email). Channel-specific structure, hook patterns, voice defaults. |
brand-review-content |
Quality gate before posting. AI-ism detection, specificity check, voice consistency, authenticity flags. |
reply-research |
Research an X account, then draft a value-add reply. The #1 growth lever under 5K followers. |
Workflow: Strategy (this skill) → Draft (draft-post) → Review (brand-review-content) → Post (xurl). For engagement: Research (reply-research) → Review → Reply (xurl).
These skills were adapted from Anthropic's knowledge-work-plugins (marketing/skills/draft-content, marketing/skills/brand-review, sales/skills/draft-outreach), stripped of enterprise/CRM framing and rewritten for indie-hacker voice.
Related Skills
draft-post — content execution layer (writing the actual posts)
brand-review-content — quality gate (checking posts before shipping)
reply-research — engagement execution (research + draft replies)
xurl — X API posting mechanics (post, reply, search, media)
github-pr-workflow — GitHub integration for content triggers
hermes-agent — Hermes config, profiles, cron setup
foreman-orchestration — Multi-agent orchestration for complex pipelines
1---
2name: build-in-public
3description: Build-in-public X (Twitter) growth strategy using Hermes as an autonomous content engine — profile design, VPS deployment, content pipeline, engagement cadence, and X Premium tier guidance for indie hackers.
4version: 1.0.0
5author: senna
6triggers:
7 - "build in public"
8 - "grow on X"
9 - "social media manager profile"
10 - "autonomous posting"
11 - "indie hacker twitter"
12 - "X growth strategy"
13 - "VPS hermes"
14metadata:
15 source: https://skillmd.com/skills/theheavenlyd3mon/build-in-public
16 hermes:
17 tags: [social-media, x, twitter, build-in-public, growth, indie-hacker, vps, autonomous]
18 related_skills: [xurl, github-pr-workflow, hermes-agent, draft-post, brand-review-content, reply-research]
19---
20
21# Build-in-Public with Hermes
22
23Use Hermes as an autonomous build-in-public engine — ship code, post about it, grow an audience, build a community. Reference models: @levelsio (Pieter Levels), @marc_louvion, @tdinh_me, @outsource_.
24
25## When to Use
26
27- Setting up Hermes as an autonomous social media presence
28- Designing a "social media manager" Hermes profile
29- Deploying Hermes on a VPS for always-on posting
30- Choosing X Premium tiers for growth
31- Planning a build-in-public content strategy
32
33## Prerequisites
34
35- xurl CLI installed and authenticated (see `xurl` skill)
36- gh CLI authenticated (for GitHub integration)
37- Hermes running (local or VPS)
38
39## X Premium Tier Recommendation
40
41For build-in-public growth, **Premium ($8/mo)** is the right tier:
42
43| Feature | Why it matters for BIP |
44|---------|----------------------|
45| Blue checkmark | Credibility at 0 followers; higher click-through on profile |
46| Reply prioritization | Your replies show higher in threads of bigger accounts — #1 growth lever under 5K followers |
47| Creator monetization | Revenue sharing + subscriptions unlock at Premium |
48| 50% fewer ads | Followers see more of your content |
49
50**Premium+ ($40/mo) is NOT worth it** because:
51- Hermes replaces Grok (higher Grok limits irrelevant)
52- xurl + web_search replaces Radar Search
53- Articles → link to GitHub/blog instead
54- $32/mo difference funds VPS + API costs
55
56**Cost breakdown for the full stack:**
57- X Premium: $8/mo
58- VPS (Hetzner CX22 / DO): ~$5/mo
59- Hermes API (Nous): ~$5-15/mo
60- Total: ~$18-28/mo (less than Premium+ alone)
61
62## Social Media Manager Profile Design
63
64### Profile Config
65
66```yaml
67# ~/.hermes/profiles/social/config.yaml
68model:
69 provider: nous
70 default: qwen/qwen3.6-flash
71 base_url: https://inference-api.nousresearch.com/v1
72
73tools:
74 enabled: [web, terminal, file, x_search]
75 disabled: [delegation, computer_use]
76
77plugins:
78 enabled: [disk-cleanup, icarus]
79
80terminal:
81 timeout: 120
82```
83
84**Model choice rationale:** Posting is high-volume, low-reasoning. Flash-tier ($0.19/$1.13 per 1M) is 3-5x cheaper than reasoning models with no quality loss for short-form content.
85
86### SOUL.md Traits
87
88The social profile's SOUL should encode:
89- Concise, punchy copy (280-char default, use 25k when needed)
90- Technical but not jargon-heavy
91- Transparent: share failures alongside wins
92- Never generic AI-isms ("game-changer", "leverage", "unlock")
93- Authentic voice — first person, specific details
94- Engagement-first: replies and conversations > broadcast
95
96### Skills to Attach
97
98- `xurl` — posting, replying, searching, engagement
99- `draft-post` — execution layer for drafting individual posts/threads
100- `brand-review-content` — quality gate before posting (AI-ism detection, voice check)
101- `reply-research` — research-first reply drafting (the engagement growth lever)
102- `github-pr-workflow` — detect new pushes/PRs for content triggers
103- `youtube-content` — if doing video content
104
105## Content Strategy
106
107### Daily Cadence (3-4 posts/day)
108
109| Time (ET) | Type | Example |
110|-----------|------|---------|
111| 9 AM | Morning intention | "Building X feature today — here's the approach" |
112| 12 PM | Progress update | Screenshot/GIF of what's working |
113| 5 PM | Wrap-up | "Shipped X. Y broke. Tomorrow: fix Y." |
114| Varies | Reply engagement | 15-30 min replying to larger accounts |
115
116### Content Types (rotate)
117
1181. **"Built this today"** — feature, screenshot, GIF, demo
1192. **"Debugging hell"** — honest failure story (gets MORE engagement than wins)
1203. **"Lesson learned"** — actionable insight from the trenches
1214. **"Revenue/metrics update"** — transparent numbers, even $0
1225. **Thread** — deep-dive on a technical decision (hook → 5-7 value tweets → CTA)
1236. **Question** — specific question to drive engagement
124
125### Weekly Cadence
126
127- **Friday:** Progress thread (like @levelsio's weekly summaries)
128- **Monthly:** Revenue/metrics transparency post
129
130### Peak Posting Times (2026 data)
131
132- Primary: Wed–Fri, 9–11 AM ET
133- Secondary: Mon–Tue ~10 AM; Sat 8–10 AM; Sun 9 AM–12 PM
134- Experiment: Late-night (10 PM–12 AM) for international audiences
135
136### Engagement Strategy (the growth lever)
137
138Reply prioritization is the #1 growth mechanic for accounts under 5K followers:
139- Search #buildinpublic, #indiehacker via `xurl search`
140- Reply to accounts 2-10x your size with genuine value
141- Target: 10-15 quality replies/day
142- Never pitch in replies — add insight, ask questions, share related experience
143
144## VPS Deployment Architecture
145
146```
147┌─────────────────────────────────────────────┐
148│ Linux VPS (always-on) │
149│ ├── Hermes installed headlessly │
150│ ├── Senna profile (orchestrator) │
151│ ├── Social profile (posting agent) │
152│ ├── Cron jobs (posting schedule) │
153│ ├── xurl (X API) │
154│ ├── gh CLI (GitHub) │
155│ └── Gateway (connects to user's devices) │
156└─────────────────────────────────────────────┘
157```
158
159### Content Pipeline Flow
160
161```
162You code (local Mac)
163 → git push to GitHub
164 → VPS Hermes detects push (cron poll or webhook)
165 → Social profile drafts post about what changed
166 → Posts at next peak-time window via xurl
167 → Monitors replies via xurl mentions
168 → Notifies you (Telegram/Discord) if reply needs personal response
169 → Weekly: generates progress thread
170```
171
172### Cron Job Setup
173
174```bash
175# Morning post — what we're building today
176hermes cronjob create \
177 --name "bip-morning" \
178 --schedule "0 9 * * *" \
179 --profile social \
180 --skills xurl \
181 --prompt "Draft and post a build-in-public morning update. Check recent git commits for context on what's being worked on. Keep it concise, specific, authentic. Post via xurl." \
182 --deliver origin
183
184# Midday update — progress check
185hermes cronjob create \
186 --name "bip-midday" \
187 --schedule "0 12 * * *" \
188 --profile social \
189 --skills xurl \
190 --prompt "Draft a midday progress update. Check git log for today's commits. If nothing new, skip silently (don't post filler). If progress exists, post a concise update with specifics." \
191 --deliver origin
192
193# Evening wrap-up
194hermes cronjob create \
195 --name "bip-evening" \
196 --schedule "0 17 * * *" \
197 --profile social \
198 --skills xurl \
199 --prompt "Draft an end-of-day wrap-up. What shipped, what broke, what's next. Be honest about failures — they get more engagement than wins. Post via xurl." \
200 --deliver origin
201
202# Friday thread
203hermes cronjob create \
204 --name "bip-weekly-thread" \
205 --schedule "0 10 * * 5" \
206 --profile social \
207 --skills xurl \
208 --prompt "Draft a weekly progress thread (5-7 tweets). Hook tweet → what was built → challenges → lessons → what's next → CTA. Post as a thread via xurl." \
209 --deliver origin
210```
211
212### Engagement Cron (replies)
213
214```bash
215# Daily engagement — reply to build-in-public community
216hermes cronjob create \
217 --name "bip-engagement" \
218 --schedule "0 14 * * *" \
219 --profile social \
220 --skills xurl \
221 --prompt "Search X for recent #buildinpublic and #indiehacker posts. Find 5-10 posts from accounts with 1K-100K followers. Reply to each with genuine value — insight, related experience, or a thoughtful question. Never pitch. Never generic. Be specific." \
222 --deliver origin
223```
224
225## Pitfalls
226
2271. **Don't post filler.** If nothing happened, skip silently. "Working on stuff" posts kill engagement. The cron prompts above check git activity before posting.
228
2292. **Don't automate replies blindly.** The engagement cron should draft replies for review, not post autonomously, until the voice is calibrated. Start with `--deliver origin` so you see what's being posted.
230
2313. **Don't start with automation.** Post manually for the first 200-500 followers to calibrate the voice, learn what resonates, and build authentic relationships. Then hand off to Hermes.
232
2334. **Don't ignore replies.** The algorithm rewards fast reply engagement. If Hermes posts, you should still check replies personally within 1 hour for the first few months.
234
2355. **Don't use Premium+.** The $32/mo savings over Premium+ funds your entire VPS + API stack.
236
2376. **Don't post only wins.** Failure stories get 2-3x more engagement than success stories. Authenticity is the build-in-public moat.
238
2397. **VPS credential management.** xurl credentials (`~/.xurl`) and GitHub tokens need to be set up on the VPS separately from your Mac. Don't copy them — run `xurl auth oauth2` and `gh auth login` on the VPS directly.
240
2418. **Cron timezone.** VPS crons run in UTC. Convert peak ET times: 9 AM ET = 14:00 UTC (EST) or 13:00 UTC (EDT). Adjust seasonally.
242
243## Growth Timeline (realistic expectations)
244
245| Phase | Followers | Focus |
246|-------|-----------|-------|
247| Foundation (0-200) | Manual posting, voice calibration | Daily updates, engage manually |
248| Consistency (200-500) | Reply guy strategy, weekly threads | Start automating posts |
249| Momentum (500-1200) | Collaborate, share milestones | Full Hermes automation active |
250| Acceleration (1200-2500) | Algorithm boost, inbound DMs | Community building |
251| Pre-launch (2500-4000) | Announce products, early access | Monetization begins |
252
253## Related Skills
254
255- `draft-post` — execution layer: draft individual posts, threads, blog posts, emails
256## Execution Layer Skills
257
258This skill is the **strategy layer** — what to post, when, and why. The actual writing and quality-checking lives in dedicated execution skills:
259
260| Skill | Purpose |
261|-------|---------|
262| `draft-post` | Write a single piece of content (X post, thread, LinkedIn, blog, email). Channel-specific structure, hook patterns, voice defaults. |
263| `brand-review-content` | Quality gate before posting. AI-ism detection, specificity check, voice consistency, authenticity flags. |
264| `reply-research` | Research an X account, then draft a value-add reply. The #1 growth lever under 5K followers. |
265
266**Workflow:** Strategy (this skill) → Draft (`draft-post`) → Review (`brand-review-content`) → Post (`xurl`). For engagement: Research (`reply-research`) → Review → Reply (`xurl`).
267
268These skills were adapted from [Anthropic's knowledge-work-plugins](https://github.com/anthropics/knowledge-work-plugins) (marketing/skills/draft-content, marketing/skills/brand-review, sales/skills/draft-outreach), stripped of enterprise/CRM framing and rewritten for indie-hacker voice.
269
270## Related Skills
271
272- `draft-post` — content execution layer (writing the actual posts)
273- `brand-review-content` — quality gate (checking posts before shipping)
274- `reply-research` — engagement execution (research + draft replies)
275- `xurl` — X API posting mechanics (post, reply, search, media)
276- `github-pr-workflow` — GitHub integration for content triggers
277- `hermes-agent` — Hermes config, profiles, cron setup
278- `foreman-orchestration` — Multi-agent orchestration for complex pipelines