Token导航 LogoToken导航TokenDH.com
待分类需要联网github未标认证来源可访问许可证需确认审计通过

ph-timing-optimizerph 时间优化器

Agent Skill

ph-timing-optimizer 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

465

周安装

19

GitHub Stars

10

下载量

149
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/yoanbernabeu/producthunt-skills --skill ph-timing-optimizer

简介

用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息。

  • 适合围绕仓库状态、代码变更或协作事项进行整理。
  • 通过 npx skills add 命令从 GitHub 仓库安装使用。
  • 安装前需确认权限范围、维护状态及是否触发联网或文件操作。
  • ph-timing-optimizer 属于待分类类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Product Hunt Timing Optimizer

This skill helps you choose the optimal launch timing based on your goals, available resources, and competitive landscape.

When to Use This Skill

  • Deciding which day of the week to launch
  • Understanding timezone implications
  • Planning for specific audience targeting
  • Balancing competition vs. traffic trade-offs
  • Coordinating global team availability

The Golden Rule

Launch at 12:01 AM Pacific Standard Time (PST)

Product Hunt's daily cycle resets at midnight PST. Launching at 12:01 AM gives you the full 24 hours of visibility.

Timezone Conversions

TimezoneLaunch Time
PST (San Francisco)12:01 AM
EST (New York)3:01 AM
GMT (London)8:01 AM
CET (Paris/Berlin)9:01 AM
IST (Mumbai)1:31 PM
CST (Beijing)4:01 PM
JST (Tokyo)5:01 PM
AEST (Sydney)7:01 PM

Day-by-Day Analysis

WEEKDAYS (Higher Traffic, Higher Competition)

Tuesday

Best For: Maximum exposure, B2B products

  • Traffic Level: ★★★★★
  • Competition: ★★★★★
  • Badge Difficulty: Very Hard
  • Newsletter: Individual daily feature

Pros:

  • Highest overall engagement
  • Decision-makers are active
  • Maximum newsletter exposure

Cons:

  • Brutal competition (often VC-backed products)
  • Requires 600-900+ upvotes for #1
  • Need large support network

Ideal For: Well-funded startups, products with large existing audience


Wednesday

Best For: Serious launches with strong preparation

  • Traffic Level: ★★★★★
  • Competition: ★★★★★
  • Badge Difficulty: Very Hard
  • Newsletter: Individual daily feature

Pros:

  • Peak mid-week attention
  • Strong B2B engagement
  • High-quality comments

Cons:

  • Highest competition day
  • Often 700-1000+ upvotes needed for #1
  • Exhausting for small teams

Ideal For: Products with viral potential, well-prepared teams


Thursday

Best For: Strong launches with slightly less competition

  • Traffic Level: ★★★★☆
  • Competition: ★★★★☆
  • Badge Difficulty: Hard
  • Newsletter: Individual daily feature

Pros:

  • Still high traffic
  • Slightly less competition than Tue/Wed
  • Good B2B engagement

Cons:

  • Still very competitive
  • 600-800+ upvotes often needed for #1

Ideal For: Solid products, teams with good support network


Monday

Best For: Starting the week strong

  • Traffic Level: ★★★★☆
  • Competition: ★★★☆☆
  • Badge Difficulty: Medium-Hard
  • Newsletter: Individual daily feature

Pros:

  • Fresh week, high attention
  • Less competition than mid-week
  • People catching up on new products

Cons:

  • Some decision-makers busy with meetings
  • 500-700 upvotes typically needed for #1

Ideal For: B2B tools, productivity products


Friday

Best For: Balanced approach

  • Traffic Level: ★★★☆☆
  • Competition: ★★★☆☆
  • Badge Difficulty: Medium
  • Newsletter: Grouped in Monday newsletter

Pros:

  • Lower competition
  • More casual browsing
  • 400-600 upvotes can win

Cons:

  • Lower overall traffic
  • Newsletter exposure diluted (grouped with weekend)
  • Some users checked out for weekend

Ideal For: Consumer products, creative tools, side projects


WEEKENDS (Lower Traffic, Easier Badges)

Saturday

Best For: Winning a badge with limited resources

  • Traffic Level: ★★☆☆☆
  • Competition: ★★☆☆☆
  • Badge Difficulty: Easy
  • Newsletter: Grouped in Monday newsletter

Pros:

  • Much lower competition
  • 300-500 upvotes can win #1
  • Indie hackers very active
  • Great for solo makers

Cons:

  • Lower total traffic
  • Less B2B engagement
  • Newsletter grouped (diluted exposure)

Ideal For: Indie projects, MVP validation, first-time launchers


Sunday

Best For: Minimal competition launch

  • Traffic Level: ★★☆☆☆
  • Competition: ★☆☆☆☆
  • Badge Difficulty: Very Easy
  • Newsletter: Grouped in Monday newsletter

Pros:

  • Lowest competition
  • 300-400 upvotes often enough for #1
  • Relaxed community vibe
  • Good for testing

Cons:

  • Lowest traffic
  • Minimal B2B presence
  • Newsletter exposure very diluted

Ideal For: Side projects, experiments, products not needing B2B

Decision Matrix

Choose WEEKDAY (Tue-Thu) if:

  • Primary goal is customer acquisition
  • You have 50+ active supporters ready
  • Product appeals to B2B/enterprise
  • You have team capacity for 24-hour push
  • Marketing budget for promotion
  • Product is polished and market-ready

Choose WEEKEND (Sat-Sun) if:

  • Primary goal is winning a badge
  • Limited support network (<30 people)
  • First Product Hunt launch
  • Solo maker or tiny team
  • MVP seeking validation
  • Consumer/indie product

Choose FRIDAY if:

  • Want balance of traffic and competition
  • Consumer-focused product
  • Creative or fun tool
  • Moderate support network (30-50)

Critical 4-Hour Window

Regardless of day, the first 4 hours after launch are crucial:

Hour 0-1: Aim for 30-50 upvotes

  • Activate your closest supporters
  • Post on social media
  • Send first email wave

Hour 1-2: Aim for 50-100 upvotes

  • Second wave of outreach
  • Respond to all comments
  • Monitor ranking position

Hour 2-4: Aim for 100-200 upvotes

  • Continue engagement
  • Share progress updates
  • Activate next timezone supporters

Why First 4 Hours Matter:

  • Rankings are randomized initially
  • Algorithm watches early momentum
  • Top 3 position attracts organic traffic
  • Most users only see top products

Timing Optimization Checklist

  • Confirmed launch at 12:01 AM PST
  • Calculated timezone for your location
  • Assessed competition for chosen day
  • Verified team availability for first 4 hours
  • Scheduled email/social for optimal times
  • Planned supporter activation by timezone
  • Set up monitoring for launch time

Output Format

TIMING RECOMMENDATION

Selected Day: [Day]
Launch Time: 12:01 AM PST ([Local Time] your timezone)

Rationale:
- Primary goal: [Goal] → [Why this day fits]
- Support network size: [#] → [Sufficient/Needs work]
- Expected competition: [Level]
- Upvote target for Top 5: [#]

Timezone Coverage Plan:
- Wave 1 (Hour 0-1): [Region] supporters
- Wave 2 (Hour 1-2): [Region] supporters
- Wave 3 (Hour 2-4): [Region] supporters

Team Availability:
- [Person]: [Time range] - [Role]
- [Person]: [Time range] - [Role]

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

36.12%
按下载量换算54

Claude

28.47%
按下载量换算42

Cursor

20.07%
按下载量换算30

Gemini CLI

9.36%
按下载量换算14

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

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

来源信息

继续浏览同类 Skills