Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问许可证需确认审计通过

ph-community-outreachPH 社区外展

Agent Skill

ph-community-outreach 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

442

周安装

19

GitHub Stars

40

下载量

155
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:ph-community-outreach(PH 社区外展)
来源仓库:https://github.com/manojbajaj95/gtm-skills
仓库路径:skills/ph-community-outreach
安装命令:
npx skills add https://github.com/manojbajaj95/gtm-skills --skill ph-community-outreach
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/manojbajaj95/gtm-skills --skill ph-community-outreach

简介

PH 社区外展技能用于联系技术社群与开发者群体。

  • 适用于研究检索任务,支持 Meetup、论坛等平台线索挖掘。
  • 可通过 npx 安装并运行于 Gemini CLI、Cursor 等环境。
  • 使用前请验证联系方式有效性,防止无效投递。ph-community-outreach 属于研究检索类 Skill,可作为该场景下的辅助能力补充。
  • 建议核对原始 README 中的礼貌模板与频率控制建议。

SKILL.md

Product Hunt Community Outreach

This skill helps you leverage online communities to amplify your Product Hunt launch while maintaining authenticity and following community guidelines.

When to Use This Skill

  • Identifying communities relevant to your product
  • Crafting community-appropriate posts
  • Timing cross-platform promotion
  • Building relationships before launch
  • Avoiding spam flags and bans

The Golden Rules

Rule 1: Be a Member First

  • Participate for 2-4 weeks before launch
  • Add value through comments and discussions
  • Build karma/reputation organically
  • Never cold-post your launch

Rule 2: Provide Value, Not Just Promotion

  • Share learnings, not just links
  • Answer questions in your domain
  • Help others with their launches
  • Make posts interesting standalone

Rule 3: Follow Each Community's Rules

  • Read sidebar/rules before posting
  • Check if self-promotion is allowed
  • Note any format requirements
  • Respect moderators

Platform-by-Platform Guide

Reddit

Relevant Subreddits

General Startup/Product:

  • r/SideProject (253k) - Very friendly to makers
  • r/startups (960k) - Broader startup discussion
  • r/Entrepreneur (2.4M) - Business-focused
  • r/smallbusiness (1.3M) - SMB audience
  • r/InternetIsBeautiful (17M) - Cool web things

Tech/Development:

  • r/webdev (1.7M) - Web development
  • r/programming (5.6M) - General programming
  • r/learnprogramming (3.5M) - Beginners
  • r/opensource (400k) - Open source projects
  • r/selfhosted (280k) - Self-hosted solutions

Specific Niches:

  • r/SaaS (44k) - SaaS products
  • r/nocode (120k) - No-code tools
  • r/artificial (1.4M) - AI products
  • r/productivity (1.1M) - Productivity tools
  • r/design (470k) - Design tools

Product Hunt Specific:

  • r/ProductHunters (small but targeted)

Reddit Posting Strategy

Pre-Launch (2-4 weeks before):

  1. Join relevant subreddits
  2. Comment helpfully on 10-20 posts
  3. Build karma organically
  4. Observe what content works

Launch Day Post Template:

Title: I built [Product] to solve [specific problem] -
       launching on Product Hunt today

Hey r/[subreddit]!

After [X months] of building, I'm finally launching
[Product] on Product Hunt today.

**The Problem:**
[2-3 sentences about the problem]

**What I Built:**
[2-3 sentences about your solution]

**What Makes It Different:**
[Your unique angle]

**Current Status:**
- [Key metric or milestone]
- [Another relevant detail]

**Looking For:**
- Honest feedback on the concept
- Suggestions for improvement
- [Specific question for community]

Product Hunt link: [URL]

Happy to answer any questions about the build,
the tech stack, or the journey!

Reddit Best Practices

  • ✓ Post during active hours (9 AM - 5 PM local)
  • ✓ Respond to every comment
  • ✓ Be humble and open to criticism
  • ✓ Share actual value/learnings
  • ✓ Use authentic language

Reddit Avoid

  • ❌ Posting in 10+ subreddits at once (spam)
  • ❌ Using the same text everywhere
  • ❌ Just dropping a link
  • ❌ Ignoring negative feedback
  • ❌ Posting in large subreddits without karma

Indie Hackers

Why Indie Hackers Works

  • Community of makers/founders
  • Celebrate launches and milestones
  • Value transparency and learning
  • Often reciprocal support

Indie Hackers Post Template

Title: Just launched [Product] on Product Hunt -
       here's what I learned building it

Hey IH community!

Today I launched [Product] on Product Hunt and wanted
to share the journey.

**📝 The Backstory**
[How you got the idea, why you built it]

**🔨 What I Built**
[Product] is [description]. It helps [audience]
[achieve outcome].

**📊 Key Numbers**
- Time to build: [X months]
- Lines of code: [X] (or tech stack)
- Beta users before launch: [X]
- Current MRR: [X or "pre-revenue"]

**💡 Lessons Learned**
1. [Key lesson]
2. [Key lesson]
3. [Key lesson]

**🎯 What's Next**
[Your roadmap or next steps]

**🙏 The Ask**
Would love feedback from this community:
- [Specific question]
- [Specific question]

Product Hunt: [Link]
Website: [Link]

AMA about the build!

Indie Hackers Best Practices

  • ✓ Share real numbers (transparency wins)
  • ✓ Focus on the journey, not just the product
  • ✓ Engage with other launches too
  • ✓ Join relevant IH groups
  • ✓ Follow up with results post

Hacker News

Hacker News Reality Check

  • Very high bar for quality
  • Community can be harsh
  • Not for every product
  • Best for: Dev tools, technical products, novel tech

HN Post Strategy

Show HN Format:

Title: Show HN: [Product Name] – [Brief description]

[Link to product]

Then in comments, add context:

Hey HN! I built [Product] because [reason].

Technical details:
- Built with [tech stack]
- [Interesting technical challenge]
- [Performance/scale info]

I'd appreciate any feedback, especially on:
- [Technical question]
- [UX question]

Happy to discuss the implementation!

HN Best Practices

  • ✓ Technical substance required
  • ✓ Be ready for tough questions
  • ✓ Respond thoughtfully to criticism
  • ✓ Don't ask for upvotes (ever)
  • ✓ Time it well (morning US)

HN Avoid

  • ❌ Marketing speak
  • ❌ "AI-powered" without substance
  • ❌ Voting rings (will get you banned)
  • ❌ Complaining about downvotes

Other Communities

Discord Servers

  • Find servers related to your niche
  • Participate genuinely first
  • Check if #self-promotion channels exist
  • Don't DM spam

Slack Communities

  • Many industries have Slack groups
  • Similar rules as Discord
  • Often more professional

Facebook Groups

  • Still relevant for certain niches
  • B2B groups can be valuable
  • Follow group rules strictly

Product-Specific Communities

  • Dev.to (developers)
  • Hashnode (developers)
  • Lobste.rs (tech)
  • Designer News (designers)
  • Growth Hackers (marketing)

Timing Strategy

Pre-Launch (2-4 weeks)

  • Join all relevant communities
  • Comment on 20+ posts
  • Build relationships
  • Save posts where you can share later

Launch Week

  • Soft mentions in comments
  • Help others, mention your launch naturally
  • Prepare posts for each platform

Launch Day

  • Space out community posts (not all at once)
  • Different post for each community
  • Monitor and respond quickly

Post-Launch

  • Share results and learnings
  • Thank communities
  • Continue participating

Community Post Checklist

Before Posting

  • Am I a recognized member of this community?
  • Have I read the rules?
  • Is self-promotion allowed?
  • Does my post provide value beyond promotion?
  • Is my post format appropriate?

After Posting

  • Monitoring for comments
  • Responding to all feedback
  • Thanking people for support
  • Not getting defensive about criticism

Output Format

COMMUNITY OUTREACH PLAN FOR: [Product Name]

TARGET COMMUNITIES:

1. Reddit
   Subreddits: [List with member counts]
   Pre-launch activity: [Status]
   Post timing: [When]

2. Indie Hackers
   Groups: [Relevant groups]
   Pre-launch activity: [Status]
   Post timing: [When]

3. Hacker News
   Suitable: [Yes/No and why]
   Post timing: [When]

4. Other
   [List other communities]

POSTING SCHEDULE:
- [Time]: [Platform] - [Subreddit/community]
- [Time]: [Platform] - [Subreddit/community]
- [Time]: [Platform] - [Subreddit/community]

PRE-LAUNCH CHECKLIST:
- [ ] [Community]: [X] comments, [X] karma
- [ ] [Community]: [Status]
- [ ] [Community]: [Status]

POST DRAFTS:
[Include customized drafts for each community]

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

33.7%
按下载量换算52

Claude

31.91%
按下载量换算49

Cursor

18.72%
按下载量换算29

Gemini CLI

10.86%
按下载量换算17

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills