Token导航 LogoToken导航

Agent Skill · 研究检索

ph-algorithm-guide(ph 算法指南)

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

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

总安装 451周安装 19GitHub Stars 10下载 158核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/yoanbernabeu/producthunt-skills --skill ph-algorithm-guide

这个 Skill 是做什么的

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

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

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

来源仓库内路径:skills/ph-algorithm-guide

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

ph-algorithm-guide 怎么安装?

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

ph-algorithm-guide 支持哪些 AI 工具?

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

ph-algorithm-guide 需要什么权限?

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

ph-algorithm-guide 是免费的吗?

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

ph-algorithm-guide 用的人多吗?

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

ph-algorithm-guide 安全吗?

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

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

值得选的地方

  • 同时适配 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-algorithm-guide

ph 算法指南 · 本页

45110只读未明确通过

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

SKILL.md 原文

Product Hunt Algorithm Guide

This skill explains how Product Hunt's ranking algorithm works, helping you optimize your launch strategy based on publicly known factors.

When to Use This Skill

  • Planning your launch strategy
  • Understanding why rankings change
  • Optimizing for algorithm factors
  • Diagnosing ranking issues
  • Setting realistic expectations

Algorithm Fundamentals

Key Insight

Upvotes ≠ Points

Product Hunt CTO Mike Kerzhner confirmed: "There is not a 1:1 correspondence between upvotes and points."

What This Means

  • Not all votes count equally
  • Account quality matters
  • Engagement quality matters
  • Timing patterns matter

Known Ranking Factors

Factor 1: Vote Weight

Higher Weight Votes:

  • Older accounts (months/years old)
  • Active accounts (regular engagement)
  • Diverse activity (not just voting)
  • Organic voting pattern

Lower Weight Votes:

  • New accounts (recently created)
  • Inactive accounts (created but unused)
  • Single-purpose accounts
  • Suspicious patterns

Potentially Discounted:

  • Brand new accounts
  • Accounts created same day
  • Bulk votes from same source
  • Coordinated voting patterns

Factor 2: Engagement Depth

Positive Signals:

  • Thoughtful comments
  • Discussion threads
  • Maker responses
  • Question-answer exchanges

Why It Matters:

  • Comments indicate genuine interest
  • Discussions show community value
  • Engagement harder to fake than votes

Factor 3: Velocity Pattern

What Algorithm Watches:

  • Rate of upvote accumulation
  • Time distribution of votes
  • Spikes vs steady growth
  • Natural vs artificial patterns

Healthy Pattern:

Hour 1: [████████░░] 40 votes
Hour 2: [██████░░░░] 35 votes
Hour 3: [███████░░░] 38 votes
Hour 4: [█████████░] 45 votes

Suspicious Pattern:

Hour 1: [██████████] 150 votes (spike!)
Hour 2: [█░░░░░░░░░] 5 votes
Hour 3: [█░░░░░░░░░] 3 votes
Hour 4: [█░░░░░░░░░] 2 votes

Factor 4: First 4 Hours

Special Period:

  • Rankings randomized initially
  • Vote counts hidden publicly
  • Algorithm observing patterns
  • Critical for initial position

After 4 Hours:

  • Rankings become vote-based
  • Position reflects accumulated strength
  • Top positions attract organic traffic
  • Momentum becomes visible

Factor 5: Account Relationships

Flagged Patterns:

  • Votes from connected accounts
  • Same IP address votes
  • Same device votes
  • Employee/team votes (weighted less)

Clean Patterns:

  • Diverse geographic sources
  • Independent account histories
  • Organic discovery paths

How Rankings Are Determined

The Daily Cycle

12:01 AM PST → Day begins
    ↓
Hours 0-4: Randomized ranking
    ↓
Hour 4+: Algorithm-sorted ranking
    ↓
Throughout day: Continuous re-ranking
    ↓
11:59 PM PST → Final rankings locked
    ↓
Awards: POTD, Top 5, etc.

Ranking Formula (Approximate)

Score = (Weighted Votes × Quality Multiplier)
      + (Engagement Depth Bonus)
      - (Spam/Manipulation Penalty)

Where:

  • Weighted Votes = Sum of all votes adjusted by account quality
  • Quality Multiplier = Based on product profile completeness
  • Engagement Depth = Comments, discussions, maker activity
  • Penalty = Deductions for suspicious patterns

Optimizing for the Algorithm

Do: Quality Over Quantity

Instead of: Getting 200 votes from low-quality accounts

Aim for: Getting 100 votes from active, established accounts

Do: Stagger Engagement

Instead of: All supporters voting at 12:01 AM

Aim for: Supporters spread across 5-6 waves over 24 hours

Do: Encourage Real Comments

Instead of: "Please upvote!"

Aim for: "Would love your honest thoughts in the comments!"

Do: Respond to Everything

Why:

  • Shows you're present
  • Creates discussion threads
  • Signals genuine launch
  • Builds engagement depth

Algorithm Behaviors

What Triggers Scrutiny

  1. Vote Velocity Spikes

- Sudden burst of votes - Then dramatic dropoff - Unnatural acceleration

  1. Account Patterns

- Multiple new accounts - Same creation timeframe - Similar activity patterns

  1. Geographic Clustering

- All votes from one location - No geographic diversity - Pattern doesn't match product

  1. Timing Uniformity

- Votes in exact intervals - Automated-looking patterns - Unnatural consistency

What the Algorithm Rewards

  1. Organic Growth

- Steady accumulation - Natural peaks and valleys - Timezone-appropriate waves

  1. Diverse Sources

- Various account ages - Different activity levels - Geographic spread

  1. Deep Engagement

- Multiple comments - Discussion threads - Question-answer pairs

  1. Maker Presence

- Quick responses - Genuine conversation - Helpful attitude

Featured vs Unfeatured

Getting Featured

Requirements (Unofficial):

  • Product is clearly explained
  • Meets category standards
  • No obvious manipulation
  • Complete profile

Helps Your Chances:

  • Quality visuals
  • Clear value proposition
  • Active maker engagement
  • Previous PH presence

Getting Unfeatured

Common Causes:

  • Vote manipulation detected
  • Spam reports received
  • Policy violations
  • Low-quality product

Recovery:

  • Usually not possible same day
  • Contact support (respectfully)
  • Learn for next time

Realistic Expectations

What You Can Control

  • Quality of your product
  • Quality of your assets
  • Your community engagement
  • Your response rate
  • Your outreach authenticity

What You Can't Control

  • Competitor strength
  • Algorithm behavior
  • Vote weighting details
  • Featuring decisions
  • Final ranking

Healthy Mindset

Focus on: Building something people love
Not on: Gaming the system

Focus on: Genuine community
Not on: Vote numbers

Focus on: Long-term reputation
Not on: One-day ranking

Algorithm Myths Debunked

Myth: "Having a famous hunter guarantees success"

Reality: 79% of featured products are self-hunted. Hunter followers help awareness but don't guarantee votes.

Myth: "More votes always means higher rank"

Reality: Vote quality matters more than quantity. 50 high-weight votes can beat 100 low-weight votes.

Myth: "The first hour determines everything"

Reality: First 4 hours matter, but the entire 24 hours count. Late momentum can overcome slow starts.

Myth: "Weekend launches are easy wins"

Reality: Lower competition, but also lower traffic. Easier badge, fewer users.

Myth: "The algorithm is random/unfair"

Reality: It's designed to surface genuinely interesting products. Work with it, not against it.

Output Format

ALGORITHM OPTIMIZATION CHECK

VOTE QUALITY:
- Expected high-weight votes: [Number]
- Expected low-weight votes: [Number]
- Risk of discounted votes: [Low/Medium/High]

ENGAGEMENT PLAN:
- Comment depth strategy: [Description]
- Maker response plan: [Description]
- Discussion seeding: [Description]

VELOCITY PATTERN:
- Wave 1 timing: [Time]
- Wave 2 timing: [Time]
- Expected distribution: [Natural/Concerning]

RISK FACTORS:
- [Risk 1]: [Mitigation]
- [Risk 2]: [Mitigation]

REALISTIC TARGETS:
- Conservative estimate: [Rank range]
- Optimistic estimate: [Rank range]

平台分布

Codex

37.68%
按下载量换算60

Claude

30.92%
按下载量换算49

Cursor

17.7%
按下载量换算28

Gemini CLI

9.43%
按下载量换算15

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills