first-1000-users
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.
89
88%
Does it follow best practices?
Impact
97%
1.76xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly articulates specific capabilities (product spec analysis, subreddit mapping, thread discovery, reply/DM drafting, Reddit API posting) and provides explicit trigger guidance for when to use it. The description is well-structured, uses third person voice, includes natural keywords, and occupies a distinct niche that would be easy to differentiate from other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: analyzes a product spec, maps relevant subreddits, finds real threads, drafts personalized replies and DMs, and posts approved outreach via Reddit API. | 3 / 3 |
Completeness | Clearly answers both what (analyzes product spec, maps subreddits, finds threads, drafts replies/DMs, posts via Reddit API) and when ('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'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Reddit', 'subreddits', 'product launch', 'first users', 'community-led growth', 'seeding', 'outreach', 'DMs', 'founders'. These cover a good range of how users would naturally describe this need. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche combining Reddit-specific outreach with product seeding for founders. The combination of Reddit API, subreddit mapping, product spec analysis, and community-led growth creates a very clear and unique trigger profile unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a highly actionable and well-structured skill with an impressive level of operational detail—scoring rubrics, decision trees, rate limits, quality gates, and safety triggers are all concrete and executable. Its main weakness is length: at 400+ lines in a single file, it could benefit from progressive disclosure via sub-documents, and some redundancy between sections (ethical guardrails vs. what-not-to-do) adds unnecessary tokens. The workflow clarity is excellent with explicit human gates and validation checkpoints throughout.
Suggestions
Extract the Buying Signal Library format, Style/Tone Guide, and Rate Limits into separate reference files (e.g., SIGNALS.md, STYLE.md, LIMITS.md) and link from the main skill to reduce monolithic length.
Consolidate the 'Ethical Guardrails' and 'What NOT to Do' sections into a single constraints section to eliminate redundancy and save ~30 lines.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive and mostly earns its tokens with specific, actionable details (scoring rubrics, rate limits, decision trees). However, it's quite long (~400+ lines) and includes some redundancy—the 'What NOT to Do' section largely repeats constraints already stated in 'Ethical Guardrails' and throughout the phases. Some sections like the tone guide could be tighter. | 2 / 3 |
Actionability | Extremely actionable throughout: concrete scoring formulas (0-10 thread scoring), exact rate limits (5 per hour, 2 min between actions), specific decision trees for DM vs reply, quality gate checklists with pass/fail criteria, exact message structures, and banned word lists. Every phase has executable steps rather than vague guidance. | 3 / 3 |
Workflow Clarity | The 6-phase pipeline is clearly sequenced with explicit validation checkpoints: cross-phase checks before Phase 2 and Phase 4, quality gates before presenting drafts, a mandatory human approval gate (Phase 4), safety triggers with specific escalation paths, and error handling with retry logic. Feedback loops are well-defined (removal rate triggers, response rate thresholds). | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and phases, but it's entirely monolithic—everything lives in one large file with no references to external documents. Given the length and complexity (rate limits, style guides, signal libraries could each be separate reference files), this would benefit from splitting into sub-documents with a concise overview in the main skill file. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
63%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 7 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (525 lines); consider splitting into references/ and linking | Warning |
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 7 / 11 Passed | |
- Repository
- openclaw/skills
- Commit
48238dd
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.