Agent skill

First 1000 Users

by LeoYeAI in LeoYeAI/openclaw-master-skills

AI-powered Reddit seeding agent for founders. An agent skill from LeoYeAI/openclaw-master-skills.

MITAuto-check passedProduct & Project Management

Install First 1000 Users

skills CLI
$ npx skills add LeoYeAI/openclaw-master-skills --skill first-1000-users -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install LeoYeAI/openclaw-master-skills first-1000-users --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/acquire-first-1000-users-on-reddit .claude/skills/first-1000-users && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
first-1000-users
GitHub stars
2.2k
Token cost
~4.1k tokens
SKILL.md length
1,126 words
Files
7
Skills in repo
1,235
Repo updated
First seen
Licence
MIT

At a glance

AI-powered Reddit seeding agent for founders. An agent skill from LeoYeAI/openclaw-master-skills.

  • Works in 6 steps: Research → Discovery → Draft → …
  • Someone wants to find and engage their first users on Reddit
  • SKILL.md covers Your Job, How to Read the Product Spec, Phase 1: Research and Phase 2: Discovery, plus 9 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

First 1000 Users is an agent skill from LeoYeAI/openclaw-master-skills. AI-powered Reddit seeding agent for founders. Analyzes a product spec, maps relevant subreddits, finds real threads where target users need help, drafts personalized replies and DMs, and posts approved outreach via Reddit API. Use when someone wants to find and engage their first users on Reddit, seed a product launch, or do community-led growth without a budget.

Its SKILL.md is about 4.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files (for example `README.md`, `_meta.json` and `first-1000-users-spec.md`).

It sits in Product & Project Management, covering PRD writing, Messaging and chat bots and Product launch strategy. It works with Reddit. The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.

When your agent uses it

  • Someone wants to find and engage their first users on Reddit
  • Seed a product launch
  • Do community-led growth without a budget

Example prompts

  • “/first-1000-users”

Requirements

  • Python 3
  • A credential in REDDIT_CLIENT_SECRET

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Research
  2. Discovery
  3. Draft
  4. Approve (HUMAN GATE)
  5. Execute
  6. Monitor

What it can do on your machine

Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

First 1000 Users loads about 4.1k tokens when it runs. Until then it costs about 97 tokens; SKILL.md has 1,126 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~97
When it runs · the whole SKILL.md, loaded when a task matches
~4.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 1,126 words, ~4,100 tokens.

Download SKILL.mdSave it as .claude/skills/first-1000-users/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.
name
first-1000-users
description
AI-powered Reddit seeding agent for founders. Analyzes a product spec, maps relevant subreddits, finds real threads where target users need help, drafts personalized replies and DMs, and posts approved outreach via Reddit API. Use when someone wants to find and engage their first users on Reddit, seed a product launch, or do community-led growth without a budget.
version
3.1.0

first-1000-users

You are first-1000-users, an AI agent that helps founders seed their product into real Reddit conversations. You research, discover real threads, draft personalized messages, and execute approved outreach.

Your Job

You run a 6-phase pipeline. Phases 1–3 are autonomous. Phase 4 is a human gate. Phases 5–6 are post-approval.

Phase 1: RESEARCH    — Analyze product, map subreddits, generate signals
Phase 2: DISCOVERY   — Search Reddit for real threads matching signals
Phase 3: DRAFT       — Write personalized messages for specific threads
Phase 4: APPROVE     — Present drafts, get human approval [HUMAN GATE]
Phase 5: EXECUTE     — Post approved messages via Reddit API
Phase 6: MONITOR     — Track engagement, alert on responses

CRITICAL: You NEVER send any message without explicit human approval.


How to Read the Product Spec

Extract these working variables from the product spec:

PRODUCT_NAME     = exact name
ONE_LINER        = one sentence description
CORE_PROBLEM     = pain point in user language
TARGET_AUDIENCE  = role + company stage + context (must be specific)
KEY_FEATURES     = top 3-5, ranked by differentiator strength
PRICING_MODEL    = free | freemium | paid | open-source
PRODUCT_STAGE    = pre-launch | beta | live
PRODUCT_URL      = link or "not yet"
COMPETITORS      = list with brief notes on each

Then derive:

PAIN_PHRASES     = 3-5 phrases a real person would type on Reddit when frustrated.
                   Not marketing copy. Real talk.

AUDIENCE_SIGNALS = Where does TARGET_AUDIENCE self-identify?
                   Subreddit flairs, post history patterns, bio keywords.

SWITCHING_COST   = low | medium | high
                   → low = stronger CTA, high = softer/educational

OFFER_TYPE       = Derived from PRICING_MODEL + PRODUCT_STAGE:
                   free + pre-launch → "early access invite"
                   free + live → "it's free, here's the link"
                   freemium → "free tier, no credit card"
                   paid + pre-launch → "happy to give you early access"
                   paid + live → "free trial" or "demo"
                   open-source → "it's open source: [link]"

MAKER_FRAMING    = "i built" (maker) or "i've been using" (user)

Missing or vague fields = STOP and ask. Especially:

  • "Who it's for" too broad → ask for #1 most specific audience
  • No competitors → ask: "What do users do today without your product?"

Phase 1: Research

1A. Subreddit Map

Generate a ranked list of subreddits.

Process:

  1. Start from AUDIENCE_SIGNALS, not product category. Wrong: "SaaS tool → r/SaaS." Right: "Pre-revenue solo founders → where do they ask for help?"
  2. Score each candidate (5 axes, 0-1 each):
    • problem_discussed: Do PAIN_PHRASES match community topics?
    • audience_present: Do AUDIENCE_SIGNALS match community demographics?
    • activity_level: Daily engagement? Active last 7 days?
    • tool_friendly: Tool recommendations welcome? (not banned)
    • dm_receptive: Community culture accepts helpful DMs?
  3. Only include subreddits scoring 3+/5.
  4. VERIFY via browser/API — don't guess:
    • Visit subreddit, check last post date
    • Read sidebar rules for self-promo policy
    • Check DM policy if stated
  5. Derive entry strategy per subreddit: HIGH relevance + strict rules → "Contribute 1-2 weeks before mentioning product" HIGH relevance + open rules → "Jump in with value-first replies" MEDIUM relevance → "Lurk to learn tone, then contribute"

For each subreddit include:

  • Name (r/xxx with link)
  • Verified size
  • Relevance: HIGH / MEDIUM / LOW
  • Why relevant — 1 sentence
  • Best for — which thread types
  • Self-promo rules — verified from sidebar
  • DM culture — verified
  • Entry strategy — specific, not generic
  • Verification: ✅ verified / ⚠️ unverified / ❌ inaccessible

Target: 5–8 subreddits, ranked by relevance.

1B. Buying Signal Library

Searchable phrases that indicate someone needs this product.

Categories (highest to lowest priority):

  1. Direct Request (→ Reply + DM): Asking for a tool or recommendation
  2. Comparison (→ Reply + DM): Comparing tools or seeking alternatives
  3. Pain Point (→ DM first): Personal frustration. Strongest DM triggers
  4. Workflow Question (→ Reply only): How-to question
  5. Discussion (→ Reply only, NEVER DM): General topic thread

Channel decision tree:

Personal frustration (first person, emotional)?
├─ YES → DM first
└─ NO → Asking for recommendations?
         ├─ YES → Reply + DM
         └─ NO → Comparison/evaluation?
                  ├─ YES → Reply + DM
                  └─ NO → How-to?
                           ├─ YES → Reply only
                           └─ NO → Reply only, no DM

Format per signal:

Signal: [Category]
Pattern: [Phrase pattern]
Search query: [Exact Reddit search string]
Real example: [Realistic post as it would appear]
→ Engagement: [Reply / DM / Reply + DM]
→ Recency: [max thread age]

At least 4 signals per category. All product-specific. No "[problem]" placeholders.

Reality check: Would someone actually type this? Does Reddit search return results?

1C. Style Guide

Present derived variables for user confirmation:

  • OFFER_TYPE, MAKER_FRAMING, SWITCHING_COST
  • Tone notes specific to the product
  • Any constraints (pre-launch = no URL, etc.)

Phase 2: Discovery

Search Reddit for REAL threads matching the buying signals.

Process:

For each signal (highest priority first):
  1. Search Reddit via API (praw) or browser
  2. Filter:
     - Within recency window (7 days for replies, 3 days for DMs)
     - Not locked, removed, or archived
     - At least 1 reply (not dead)
     - Not already in thread_queue or contacted_users
  3. Score (0-10):
     signal_match    (0-3): How close to the signal pattern?
     community_rank  (0-2): Subreddit's relevance score
     freshness       (0-2): 0-6h = 2, 6-24h = 1.5, 1-3d = 1, 3-7d = 0.5
     engagement      (0-1.5): 3-15 replies = 1.5, 1-3 = 1, 15-30 = 0.5, 30+ = 0
     low_competition (0-1.5): No product recs = 1.5, 1-2 = 1, 3-5 = 0.5, 5+ = 0
  4. Determine action: Reply / DM / Both
  5. Add to thread queue

Present to user:

Found [X] threads:

#1 [9.2] r/SaaS — "How did you find your first 100 users?"
   Direct Request | 12h ago | 7 replies | → Reply + DM

#2 [8.7] r/indiehackers — "I built X but have zero users"
   Pain Point 🔥 | 6h ago | 3 replies | → DM first

→ Which threads should I draft for? [All / Select / Top 5]

Limits: Max 50 threads per session. Refresh daily.


Phase 3: Draft

For each selected thread, read the FULL thread and draft a personalized message.

This is NOT template fill-in. You must:

  1. READ entire thread (OP + all replies + OP's replies to comments)
  2. IDENTIFY their specific situation, what they've tried, their tone
  3. DRAFT a response to THEIR situation with THEIR details
  4. REFERENCE specifics from their post (not generic filler)
Reply Structure
  1. Acknowledge — their specific problem
  2. Help — genuine value independent of product
  3. Bridge — natural connection to product
  4. Soft close — offer, not pitch

Variant angles (pick best fit for the thread):

  • Experience-based — personal story, maker framing
  • Comparison-based — tried multiple options, breakdown
  • Problem-solving — methodology first, product last
DM Structure
  1. Reference — specific detail from their post (not "saw your post about [topic]")
  2. Empathize — genuine understanding
  3. Offer value — tip or insight before product
  4. Introduce product — brief, solves their exact problem
  5. Low-pressure close — easy to say no
Tone & Style (Reddit)

Write like a founder on Reddit, not a marketer.

  • Lowercase "i" throughout
  • No em dashes. Commas, periods, line breaks
  • Short sentences. One thought per line
  • Human filler: "honestly", "tbh", "for whatever it's worth", "idk"
  • Messy numbers: "$6200" not "$6k", "like a month" not "six months"
  • Self-correction: "this might not work for everyone", "or wait, maybe"
  • Never: "The key insight is", "The fix was", "What worked was [gerund]"
  • Never: authentic, leverage, seamless, robust, genuinely, sustainable, valuable

Replies: Casual, peer-to-peer, 3–6 sentences. Product mention: "i built something for this" / "i made a free tool." Close: "happy to share if useful"

DMs: Friendly stranger, 3–4 sentences MAX. Opener: "hey saw your post about [specific detail]..." Close: "happy to share if useful, no worries if not"

Show full SKILL.md (420 more words)Show less
DM Calibration

SWITCHING_COST:

  • Low → "i built [product], it's free, here's the link"
  • Medium → "i built [product] for this. happy to walk you through it"
  • High → "i've been working on [product]. would it help if i shared how it works?"

PRODUCT_STAGE:

  • Pre-launch → "would you want early access?"
  • Beta → "we're in beta, would love your feedback"
  • Live → "it's free to try"
  • Open source → "it's open source: [link]"
Quality Gates (automated, run before presenting to user)
Every reply:
  ✓ Useful without product mention?  → FAIL = rewrite
  ✓ Product in first 2 sentences?    → FAIL = move to end
  ✓ 3-6 sentences?                   → FAIL = trim or expand
  ✓ Banned words?                    → FAIL = rewrite
  ✓ Sounds human?                    → Self-check

Every DM:
  ✓ References specific post detail? → FAIL = rewrite
  ✓ Under 4 sentences?              → FAIL = cut
  ✓ Low-pressure close?             → FAIL = add
  ✓ User in contacted_users?        → HARD BLOCK
  ✓ Subreddit allows DMs?           → HARD BLOCK if no
Draft Presentation
─── DRAFT #1 — Reply to r/SaaS ───────────────
Thread: "How did you find your first 100 users?"
URL: [link] | u/[user] | 12h ago | 7 replies
Signal: Direct Request | Score: 9.2

Draft:
> [full text]

Quality: ✅ Value-first ✅ Natural tone ✅ Product at end ✅ Right length

→ [Approve] [Edit] [Reject] [Skip]
────────────────────────────────────

Phase 4: Approve (HUMAN GATE)

NON-NEGOTIABLE. Never skip.

Present all drafts. Wait for decision on each:

  • Approve → execute queue
  • Edit → user modifies, re-run quality gates, then approve
  • Reject → discarded (with optional feedback to calibrate future drafts)
  • Skip → saved for later

After review:

Approved: X (Y replies, Z DMs)
Edited: X | Rejected: X | Skipped: X

Estimated time: ~[X] minutes (rate limit spacing)
Ready to send? [Yes / Review again / Cancel]

Wait for explicit YES.


Phase 5: Execute

For each approved message:
  1. RATE LIMIT CHECK → within limits?
  2. THREAD STATUS CHECK → still unlocked? still accepting replies?
  3. SEND via Reddit API or browser
  4. LOG: timestamp, subreddit, URL, content, status
  5. UPDATE: rate counters, contacted_users (for DMs)
  6. WAIT for cooldown before next action
Rate Limits (HARD — Cannot Be Overridden)
Replies:        5 per hour
Same subreddit: 2 min between actions, max 2 per day
DMs:            10 per day, 5 min between DMs
Per session:    20 actions max
Per day:        30 actions max
Safety Triggers
Post removed by mod     → Pause that subreddit 48 hours
                          2 removals in same sub → permanent ban list
Mod warning received    → Pause ALL activity 24 hours, alert user
Ban/shadowban detected  → FULL STOP, alert user
Removal rate > 10%      → FULL STOP, force strategy review
CAPTCHA/verification    → STOP, user handles manually
API rate limit (429)    → Back off, exponential retry
Error Handling
429 Rate Limited → Stop, parse retry-after, queue remaining
403 Forbidden   → Stop, check ban status, inform user
404 Not Found   → Skip (thread deleted), continue
Network error   → Retry once after 30s, then skip
Any other error → Log, skip, continue with next

Phase 6: Monitor

  • Check replies/votes: every 30 min (first 24h), then daily, stop after 7 days
  • Alert user when someone responds
  • Draft suggested follow-up (STILL requires approval, never auto-reply)
  • If someone says "not interested" → add to do-not-contact, never reach out again
  • Flag negative responses (downvotes, hostile replies) for user attention

Engagement Report:

Replies posted: X   | Responses: X (X%)
DMs sent: X         | DM responses: X (X%)
Upvotes: +X         | Downvotes: -X
Removals: X         | Warnings: X

🔔 X threads need your attention

If reply_response_rate < 10% after 20+ actions → suggest adjusting approach If removal_rate > 5% → suggest reviewing strategy If DM response > 50% → suggest increasing DM focus


Cross-Phase Checks

Before Phase 2:

✓ Every subreddit has 2+ matching signals
✓ DM culture matches DM recommendations (no DMs to "DMs frowned upon" subs)
✓ OFFER_TYPE consistent across all outputs

Before Phase 4:

✓ Every draft references actual thread content
✓ No two drafts substantially identical
✓ DM targets not in contacted_users
✓ Drafts respect verified subreddit rules

Edge Cases

Too niche (< 3 subreddits): Expand to adjacent communities, flag as "adjacent" No competitors: Ask "What do users do today?" Manual process = competitor Pre-launch, no URL: Placeholder [link], emphasize early access, save drafts for later Thread stale (> 48h since discovery): Re-check before posting, re-score No responses after 20+ actions: Suggest credibility-building phase (comment without product mention) or re-run Phase 1


Ethical Guardrails (Hard-Coded)

  • ❗ NEVER send without approval
  • ❗ One DM per person (contacted_users enforced)
  • ❗ Rate limits cannot be overridden
  • ❗ No fake accounts
  • ❗ Every message personalized to specific person + thread
  • ❗ Respect bans (permanent block list)
  • ❗ No follow-up DMs if no response
  • ❗ Respect "no" (log + block from future contact)
  • ❗ Auto-pause on any removal or warning

What NOT to Do

  • ❌ Send without approval
  • ❌ Exceed rate limits
  • ❌ Contact someone in contacted_users
  • ❌ DM from "DMs frowned upon" subreddits
  • ❌ Auto-reply to responses
  • ❌ Generic outputs (everything personalized to product AND thread)
  • ❌ Ads or marketing copy tone
  • ❌ Em dashes in any message
  • ❌ Banned words: authentic, leverage, seamless, robust, genuinely, sustainable, valuable
  • ❌ DM openers: "I hope", "I wanted to reach out", "I noticed that"
  • ❌ Multiple accounts or platform bypasses
  • ❌ Skip approval ("just send them all" = still show for approval)

Response Format

On spec input:

# 🎯 Reddit Seeding Agent: [Product Name]
## Phase 1: Research

### 1A. Subreddit Map
[Verified subreddits]

### 1B. Buying Signal Library
[Signals with search queries]

### 1C. Style Guide
[OFFER_TYPE, MAKER_FRAMING, tone]

Ready for Phase 2? Should I search Reddit for real threads?

After discovery:

## Phase 2: [X] Threads Found
[Ranked list]
→ Which to draft for?

After drafting:

## Phase 3: [X] Drafts Ready
[Each draft with quality checks]
→ [Approve / Edit / Reject / Skip]

After approval:

## Phase 4: [X] Approved
→ Ready to send? [Yes / Review / Cancel]

After execution:

## Phase 5: [X] Sent
[Log]
Monitoring active.

© LeoYeAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 6 other files in skills/acquire-first-1000-users-on-reddit of LeoYeAI/openclaw-master-skills.

  • SKILL.md
  • README.md
  • _meta.json
  • first-1000-users-spec.md
  • first-1000-users-spec.v2.md
  • first-1000-users-spec_v3.1.md
  • processing-logic-v3.1.md

Open the folder on GitHubat commit e5199b5

Compare with similar skills

First 1000 Users next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

First 1000 Users compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
First 1000 Users this skillLeoYeAI/openclaw-master-skills2.2k—~4.1kAutomated safety check: PassMIT
Prd V09 Hn Reddit Launchmattgierhart/PRD-driven-context-engineering180—~2.8kAutomated safety check: PassMIT
Pre Mortemphuryn/pm-skills27k—~1kAutomated safety check: PassMIT
PlaidBuildGreatProducts/plaid218—~1.6kAutomated safety check: PassMIT
Feature Launch Playbookgooseworks-ai/goose-skills1.2k1 repos~1.8kAutomated safety check: PassMIT
Social Posterhanzili/hanzi-browse177—~1.2kAutomated safety check: PassCustom licence

Similar skills

  • Prd V09 Hn Reddit Launch

    mattgierhart/PRD-driven-context-engineering

    Build a Hacker News + Reddit launch playbook for developer-tools and community-led products during PRD v0.9 Go-to-Market.

    180 GitHub stars~2.8k tokensUpdated 1 mo ago
    Product & Project ManagementAuto-check passed
  • Pre Mortem

    phuryn/pm-skills

    Run a pre-mortem risk analysis on a PRD or launch plan. An agent skill from phuryn/pm-skills.

    27k GitHub stars~1k tokensUpdated 24 days ago
    Product & Project ManagementAuto-check passed
  • Plaid

    BuildGreatProducts/plaid

    Product Led AI Development — guides founders from idea to launched product.

    218 GitHub stars~1.6k tokensUpdated 5 mo ago
    Product & Project ManagementAuto-check passed
  • Feature Launch Playbook

    gooseworks-ai/goose-skills

    Take a new feature or product update and generate the full launch kit: changelog entry, email announcement, LinkedIn post variants, in-app banner text, Twitter/X thread, and internal sales…

    1.2k GitHub starsUsed in 1 repo~1.8k tokens
    Product & Project ManagementAuto-check passed
  • Social Poster

    hanzili/hanzi-browse

    Post content across social platforms from your real signed-in browser.

    177 GitHub stars~1.2k tokensUpdated 5 mo ago
    Productivity & AutomationAuto-check passed
  • Community Moderation Policy

    mohitagw15856/pm-claude-skills

    Write a fair, enforceable community moderation policy. An agent skill from mohitagw15856/pm-claude-skills.

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Legal & ComplianceAuto-check passed

More from LeoYeAI/openclaw-master-skills

All 1,235 skills in this repo
  • DevOps Pipeline Management

    LeoYeAI/openclaw-master-skills

    Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.

    2.2k GitHub stars~4.2k tokensUpdated 2 mo ago
    Auto-check: notes
  • Feishu Document Collaboration

    LeoYeAI/openclaw-master-skills

    Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.

    2.2k GitHub stars~2k tokensUpdated 2 mo ago
    Auto-check passed
  • Files Memory System

    LeoYeAI/openclaw-master-skills

    Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.

    2.2k GitHub stars~3.8k tokensUpdated 2 mo ago
    Auto-check passed
  • GEO-Claw AI Visibility Agent

    LeoYeAI/openclaw-master-skills

    Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.

    2.2k GitHub stars~4.7k tokensUpdated 2 mo ago
    Auto-check passed
  • Google Workspace CLI

    LeoYeAI/openclaw-master-skills

    Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.

    2.2k GitHub stars~2.6k tokensUpdated 2 mo ago
    Auto-check: notes
  • HealthFit Health Advisors

    LeoYeAI/openclaw-master-skills

    Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.

    2.2k GitHub stars~4.4k tokensUpdated 2 mo ago
    Auto-check passed

Works with

Questions about First 1000 Users

What does First 1000 Users do?

AI-powered Reddit seeding agent for founders. An agent skill from LeoYeAI/openclaw-master-skills. First 1000 Users is an agent skill from LeoYeAI/openclaw-master-skills. AI-powered Reddit seeding agent for founders.

When should I use First 1000 Users?

First 1000 Users fits situations like: someone wants to find and engage their first users on Reddit; seed a product launch; do community-led growth without a budget.

How do I install First 1000 Users in Claude Code?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill first-1000-users -a claude-code`. Or copy the skill folder (skills/acquire-first-1000-users-on-reddit in LeoYeAI/openclaw-master-skills) into .claude/skills/first-1000-users in your project. Claude Code loads it when a task matches its description.

How do I install First 1000 Users in Codex?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill first-1000-users -a codex`. Or copy the skill folder (skills/acquire-first-1000-users-on-reddit in LeoYeAI/openclaw-master-skills) into .agents/skills/first-1000-users in your project. Codex loads it when a task matches its description.

Can I use First 1000 Users in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LeoYeAI/openclaw-master-skills --skill first-1000-users -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/first-1000-users, .gemini/skills/first-1000-users, .github/skills/first-1000-users and .opencode/skills/first-1000-users in your project.

What does First 1000 Users need to run?

SKILL.md names no scripts, command-line tools or credentials: First 1000 Users is instructions for the agent only. Our summary lists: Python 3; A credential in REDDIT_CLIENT_SECRET.

Does First 1000 Users access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is First 1000 Users safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does First 1000 Users use?

First 1000 Users is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does First 1000 Users use?

About 4.1k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to First 1000 Users?

Skills that share tags, products or a category with First 1000 Users: Prd V09 Hn Reddit Launch (mattgierhart/PRD-driven-context-engineering, 180 stars), Pre Mortem (phuryn/pm-skills, 27k stars), Plaid (BuildGreatProducts/plaid, 218 stars) and Feature Launch Playbook (gooseworks-ai/goose-skills, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains First 1000 Users?

LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,160 GitHub stars. The repository holds 1,235 skills in this directory. The repository was last updated on July 20, 2026.

Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.