Token导航 LogoToken导航

Agent Skill · 待分类

ph-content-recycling(pH 值回收)

用于辅助文档、README、Markdown、说明文和内容稿件的整理与改写。它适合让 Agent 提炼结构、补齐章节、统一术语、检查链接或把零散材料整理成可读文档。使用时应保留项目已有事实、命令和路径,不要把未确认的信息写成确定结论;涉及对外文案时,还需要控制语气,避免过度营销或夸大能力。

ph-content-recycling 是待分类类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描已通过,按安装量在待分类类的 11,209 个 Skill 里排第 5,519。

总安装 558周安装 23GitHub Stars 10下载 182核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/yoanbernabeu/producthunt-skills --skill ph-content-recycling

这个 Skill 是做什么的

这个 Skill 的分类还没最终确定,用法以来源仓库的说明为准。

用于辅助文档、README 和 Markdown 内容的整理与改写。适合提炼结构、补齐章节、统一术语或整合零散材料。使用时应保留项目已有事实、命令和路径。ph-content-recycling 属于待分类类 Skill,可作为该场景下的辅助能力补充。不要把未确认的信息写成确定结论;对外文案需控制语气。

避免过度营销或夸大能力,保持客观准确。

来源仓库内路径:skills/ph-content-recycling

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

ph-content-recycling 怎么安装?

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

ph-content-recycling 支持哪些 AI 工具?

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

ph-content-recycling 需要什么权限?

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

ph-content-recycling 是免费的吗?

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

ph-content-recycling 用的人多吗?

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

ph-content-recycling 安全吗?

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

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

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

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理待分类类任务、又不想每次都手写提示词的人。

不太适合

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

待分类类 Skill 对比

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

infsh CLI · Codex、Claude

4,374,576382权限未标注未明确未收录
ai-video-generation

AI 视频生成 · Codex、Claude

4,313,376382调用外部服务未明确有提醒
lark-openapi-explorer

云雀 OpenAPI 浏览器 · Codex、Claude

2,064,1209,011需要联网未明确有提醒
lark-workflow-standup-report

Lark 工作流程站立报告 · Codex、Claude

2,041,6328,978需要联网未明确通过
use-my-browser

使用我的浏览器 · Codex、Claude

1,848,49140操作浏览器未明确未通过
ph-content-recycling

pH 值回收 · 本页

55810需要联网未明确通过

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

SKILL.md 原文

Product Hunt Content Recycling

This skill helps you repurpose Product Hunt launch content across multiple channels to extend your launch impact.

When to Use This Skill

  • After your PH launch
  • Maximizing content ROI
  • Building your content library
  • Extending launch visibility
  • Creating evergreen materials

The Content Recycling Framework

What You Created for PH

LAUNCH ASSETS:
├── Tagline
├── Description (short + long)
├── Maker comment
├── Gallery images (4-6)
├── Video demo
├── Thumbnail/GIF
├── Email templates
├── Social posts
└── Supporter materials

Where to Repurpose

DESTINATION CHANNELS:
├── Website (landing page, about, features)
├── Blog (launch story, learnings, how-to)
├── Documentation (README, quickstart)
├── Social media (ongoing posts)
├── Email marketing (sequences)
├── Other platforms (directories, communities)
├── Sales materials (decks, one-pagers)
└── PR/Media (press releases, pitches)

Channel-by-Channel Guide

1. Website Updates

Landing Page:

  • Tagline → Headline
  • Description → Value proposition section
  • Gallery images → Feature screenshots
  • Video → Hero or features section
  • Maker comment → About section

Features Page:

  • Gallery images → Feature highlights
  • Demo video → Embedded walkthrough
  • Description points → Feature list

About Page:

  • Origin story from maker comment
  • Mission/vision from description
  • Team info (if mentioned)

Homepage Badge:

<!-- Product Hunt Badge -->
<a href="https://www.producthunt.com/posts/your-product">
  <img src="https://api.producthunt.com/widgets/embed-image/v1/top-post-badge.svg?post_id=YOUR_ID" />
</a>

2. Blog Content

Launch Announcement Post:

Title: "Introducing [Product]: [Tagline]"

Contents:
- What we launched (description)
- Why we built it (maker comment story)
- Key features (from gallery)
- Getting started (CTA)

Launch Retrospective:

Title: "What We Learned Launching on Product Hunt"

Contents:
- Our results (numbers)
- What worked
- What didn't
- Advice for others

Feature Deep-Dive (from each gallery image):

Title: "How [Feature] Helps You [Benefit]"

Contents:
- The problem (from description)
- Our solution (from demo)
- How to use it (new content)
- Results/examples

3. Documentation

README.md:

# [Product Name]

> [Tagline]

[Description - first paragraph]

![Product Screenshot](gallery-image-1.png)

## Features

- [Feature 1 from gallery]
- [Feature 2 from gallery]
- [Feature 3 from gallery]

## Getting Started

[Adapted from demo script]

## Support

[From maker comment closing]

---

🏆 Featured on Product Hunt: [Badge/Link]

Quick Start Guide:

  • Adapted from demo video script
  • Screenshots from gallery
  • Step-by-step from description

4. Social Media (Ongoing)

Thread Formats:

*Origin Story Thread:*

1/ Just launched [Product] on Product Hunt! 🚀

Here's the story of why we built it...

[Maker comment story, broken into tweets]

n/ Try it here: [link]

*Lessons Learned Thread:*

1/ We launched on Product Hunt and got [X upvotes].

Here are [X] things we learned:

[List of lessons]

n/ Full details: [blog link]

*Feature Highlight Posts:*

[Gallery image]

[Feature name] makes [benefit] easy.

Here's how:
[Demo or explanation]

Try it: [link]

5. Email Marketing

Welcome Sequence:

  • Email 1: Welcome (adapted maker comment)
  • Email 2: Feature 1 (gallery image 1)
  • Email 3: Feature 2 (gallery image 2)
  • Email 4: Success story
  • Email 5: CTA

Newsletter:

  • Launch announcement
  • Feature highlights
  • User stories

6. Other Directories

Platforms to List:

  • BetaList
  • SaaSHub
  • AlternativeTo
  • Capterra/G2
  • AppSumo (if applicable)
  • Indie Hackers
  • Hacker News (Show HN)

Adapted Content: Each platform needs slightly different format, but core content stays same:

  • Tagline (may need length adjustment)
  • Description (platform-specific)
  • Screenshots (gallery images)
  • Links

7. Sales Materials

One-Pager:

[LOGO]

[Tagline]

THE PROBLEM
[From description]

THE SOLUTION
[From description + demo]

KEY FEATURES
[From gallery]

RESULTS
[From launch metrics or testimonials]

GET STARTED
[CTA]

Pitch Deck Slides:

  • Slide 2: Problem (from description)
  • Slide 3: Solution (tagline + demo)
  • Slide 4-6: Features (gallery images)
  • Slide 7: Traction (PH results + users)

8. PR/Media

Press Release:

FOR IMMEDIATE RELEASE

[Tagline] — [Company] Launches [Product]

[City, Date] — [First paragraph of description]

[Key features and benefits]

"[Quote from maker comment]" — [Founder Name], [Title]

[Availability and pricing]

About [Company]:
[Brief company description]

Contact:
[Media contact info]

Content Transformation Matrix

Original AssetBlogSocialEmailDocsPR
TaglineTitleHookSubjectHeaderHeadline
DescriptionBodyThreadsBodyOverviewBody
GalleryImagesPostsImagesScreenshotsAttachments
VideoEmbedClipGIFTutorialAsset
Maker CommentStoryThreadIntroAboutQuote

Recycling Workflow

Step 1: Inventory

List all assets created for launch:

  • Tagline
  • Short description
  • Long description
  • Maker comment
  • Gallery image 1
  • Gallery image 2
  • Gallery image 3
  • Gallery image 4
  • Video demo
  • Thumbnail
  • Email templates
  • Social templates

Step 2: Prioritize Channels

Rank by impact:

  1. [Channel] - [Why important]
  2. [Channel] - [Why important]
  3. [Channel] - [Why important]

Step 3: Adapt

For each priority channel:

  • Review format requirements
  • Adapt content to fit
  • Maintain core message
  • Optimize for platform

Step 4: Schedule

Create content calendar:

DateChannelContentAsset Used
[Date]BlogLaunch postAll
[Date]TwitterThreadStory
[Date]LinkedInFeature postGallery 1

Quick Win Templates

Twitter Thread from Maker Comment

  1. Take maker comment
  2. Split into 5-7 logical chunks
  3. Add hook as tweet 1
  4. Add CTA as final tweet

Blog Post from Description

  1. Use tagline as title
  2. Expand each sentence of description into paragraph
  3. Add gallery images as illustrations
  4. Add demo video embed

Email from Social Posts

  1. Combine 3-4 social posts
  2. Add personal greeting
  3. Add CTA
  4. Send!

Recycling Checklist

Week 1 After Launch

  • PH badge added to website
  • Landing page updated with launch assets
  • Blog launch post published
  • README updated

Week 2-4

  • Feature posts scheduled
  • Email sequence created
  • Other directories submitted
  • Sales materials updated

Ongoing

  • Social posts from old assets
  • Blog posts from features
  • Email content from results

Output Format

CONTENT RECYCLING PLAN: [Product Name]

ASSETS AVAILABLE:
- [List all launch assets]

PRIORITY CHANNELS:
1. [Channel] - [Reason]
2. [Channel] - [Reason]
3. [Channel] - [Reason]

CONTENT CALENDAR:

Week 1:
- [Date]: [Content] → [Channel]
- [Date]: [Content] → [Channel]

Week 2:
- [Date]: [Content] → [Channel]
- [Date]: [Content] → [Channel]

ADAPTATIONS NEEDED:
- [Asset] → [Channel]: [Changes needed]
- [Asset] → [Channel]: [Changes needed]

QUICK WINS:
- [ ] [Easy recycling task]
- [ ] [Easy recycling task]
- [ ] [Easy recycling task]

平台分布

Codex

37.07%
按下载量换算67

Claude

28.43%
按下载量换算52

Cursor

16.12%
按下载量换算29

Gemini CLI

9.52%
按下载量换算17

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

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

安装前确认

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

继续浏览同类 Skills