Gingiris commited on
Commit
baa5412
·
1 Parent(s): 936cd9f

Add ClawHub install CTA + 30-Second Preview block to dataset card

Browse files
Files changed (1) hide show
  1. README.md +46 -0
README.md CHANGED
@@ -34,6 +34,52 @@ size_categories:
34
 
35
  ---
36
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
37
  ## English
38
 
39
  ### What Is This?
 
34
 
35
  ---
36
 
37
+ ## 📦 Install on ClawHub
38
+
39
+ ```bash
40
+ clawhub install gingiris-opensource
41
+ ```
42
+
43
+ Then ask your AI agent:
44
+
45
+ > "I just open-sourced my AI agent framework, plan my 30-day push to 1k GitHub stars" or "Draft a Show HN post for my repo"
46
+
47
+ Installs the **complete OSS launch playbook** that drove AFFiNE 0 → 60K stars in 24 months — README optimization, HackerNews Show HN strategy, Reddit community seeding, Discord/Slack outreach, sustained-growth content rhythm.
48
+
49
+ 🔗 [View on ClawHub](https://clawhub.ai/gingiris/gingiris-opensource) · [Sustained growth follow-up: gingiris-github-star-growth](https://clawhub.ai/gingiris/gingiris-github-star-growth) · [All 39 Gingiris skills](https://clawhub.ai/user/gingiris)
50
+
51
+ ## 🚀 30-Second Preview
52
+
53
+ ```
54
+ You: I open-sourced my AI agent framework yesterday. Plan 30-day → 1k stars.
55
+ Agent (with gingiris-opensource):
56
+
57
+ Day 1-3 — README + repo readiness (must-fix before any promo):
58
+ • README cover image + 3-line "what + why + try" intro
59
+ • 30-second demo GIF (Loom or asciinema)
60
+ • Issues labeled "good first issue" × 5 pre-created
61
+ • Contributing.md + Code of Conduct + license badges
62
+
63
+ Day 4-7 — Soft launch in 3 niche communities:
64
+ • r/<niche> (NOT r/programming) — post as discussion, not promo
65
+ • Discord servers where target users hang out — DM 5 contributors first
66
+ • dev.to + Hashnode cross-post with canonical → repo
67
+
68
+ Day 8-10 — Show HN (Tuesday/Thursday morning UTC, NEVER Monday):
69
+ • Title format: "Show HN: <verb> <what> <unique twist>"
70
+ • First comment: technical explanation, not marketing
71
+ • Reply to every comment within 2h for first 6h
72
+
73
+ Day 11-30 — Sustained content + Trending push:
74
+ • 2 dev.to long-form posts per week (canonical to repo)
75
+ • Twitter/X build-in-public daily (numbers + screenshots)
76
+ • Aim for GitHub Trending in week 3-4 via consistent star velocity
77
+ ```
78
+
79
+ Specific timings, specific templates — not "post on HN and pray."
80
+
81
+ ---
82
+
83
  ## English
84
 
85
  ### What Is This?