Token导航 LogoToken导航

Agent Skill · 研究检索

ph-community-outreach(PH 社区外展)

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

ph-community-outreach 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 40,499。

总安装 1,283周安装 54GitHub Stars 10下载 449核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/yoanbernabeu/producthunt-skills --skill ph-community-outreach

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

用于查找、检索和筛选相关信息。ph-community-outreach 属于研究检索类 Skill,可作为该场景下的辅助能力补充。适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。可结合来源仓库、安装命令和原始 README 核验具体用法。

安装前建议确认权限范围、维护状态及是否触发联网或文件读写。确保操作合规且不越权访问敏感资源。

来源仓库内路径:skills/ph-community-outreach

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/yoanbernabeu/producthunt-skills --skill ph-com…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

ph-community-outreach 怎么安装?

在终端执行 npx skills add https://github.com/yoanbernabeu/producthunt-skills --skill ph-community-out…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

ph-community-outreach 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

ph-community-outreach 需要什么权限?

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

ph-community-outreach 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

ph-community-outreach 用的人多吗?

公开数据是累计安装 1,283 次,近一周安装 54 次,下载 449 次,GitHub 10 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

ph-community-outreach 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
ph-community-outreach

PH 社区外展 · 本页

1,28310只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

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]

平台分布

Codex

32.63%
按下载量换算147

Claude

32.03%
按下载量换算144

Cursor

16.37%
按下载量换算74

Gemini CLI

9.3%
按下载量换算42

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills