Product Hunt
v1.0.0Launch, hunt, and research products on Product Hunt with timing, assets, engagement, and anti-manipulation practices.
⭐ 2· 1.4k·8 current·9 all-time
byIván@ivangdavila
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description describe launching, hunting, and researching on Product Hunt. The skill has no install, no environment variables, and no binaries — all of which align with a pure guidance/playbook skill. Nothing requested appears unrelated to Product Hunt workflows.
Instruction Scope
SKILL.md and the companion docs stay focused on Product Hunt timing, assets, comment strategy, and research signals. They do not instruct reading local files, accessing unrelated environment variables, calling external endpoints, or collecting credentials. The instructions are procedural guidance rather than automation commands.
Install Mechanism
No install spec and no code files are included (instruction-only). That minimizes on-disk risk — nothing is downloaded or executed by the skill itself.
Credentials
The skill declares no required environment variables, no primary credential, and no config paths. That is proportionate for a documentation/playbook-only skill.
Persistence & Privilege
always is false (default). The skill does not request persistent system presence or elevated privileges and does not modify other skills or system config.
Assessment
This skill is essentially a best-practices playbook for Product Hunt and appears low technical risk because it has no code, no installs, and asks for no credentials. Before using it: (1) remember these are behavioral recommendations — following aggressive or automated outreach can violate Product Hunt's rules and lead to bans, so avoid bots, bought upvotes, or coordinated vote exchanges; (2) if you plan to automate posting or give any tool your PH credentials, those credentials are not requested by this skill and you should treat them as sensitive — only provide them to trusted, audited integrations; (3) confirm you have the maker's consent before hunting their product (the docs emphasize coordination); (4) review Product Hunt's Terms of Service/community guidelines to ensure the tactics you use comply; and (5) because this is instruction-only, the main risk is human misuse of the advice (ethical/policy risk), not technical exfiltration — proceed if you accept those behavioral responsibilities.Like a lobster shell, security has layers — review code before you run it.
latestvk97eraqwf151g9kf34qd4kjq6d817f8z
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🚀 Clawdis
OSLinux · macOS · Windows