skills/producthunt-scan/SKILL.md
--- name: producthunt-scan description: Scan Product Hunt's daily / weekly / all-time rankings via the public Atom feed. Returns product names, taglines, URLs, upvotes (when exposed). No auth required. Use for "what launched today?" or niche topic filtering. category: research argument-hint: [topic] [--since today|week|month] [--limit N] [--category <slug>] allowed-tools: Bash(curl *) Bash(python3 *) Read content-pipeline: - pipeline:scan - platform:agnostic - role:scanner --- # Product H
npx skillsauth add RonanCodes/ronan-skills skills/producthunt-scanInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Three modes:
tech, productivity, ai)Product Hunt's public Atom feed is https://www.producthunt.com/feed — returns the current top products, no auth, atom-XML format.
/ro:producthunt-scan # top 30 launches today
/ro:producthunt-scan "AI agent" # filter today's feed by keyword
/ro:producthunt-scan "markdown" --since week # past week filtered
/ro:producthunt-scan --category ai --limit 50 # AI category, more items
today30# Today / main feed
curl -s "https://www.producthunt.com/feed"
# Category-scoped (replace <slug>)
curl -s "https://www.producthunt.com/feed?category=<slug>"
Common category slugs: tech, ai, productivity, design-tools, developer-tools, marketing, web3, e-commerce.
The feed is Atom not RSS. Use Python's xml.etree.ElementTree with namespace http://www.w3.org/2005/Atom:
import xml.etree.ElementTree as ET
ns = {'a': 'http://www.w3.org/2005/Atom'}
tree = ET.parse('/tmp/ph.xml')
for e in tree.getroot().findall('a:entry', ns):
title = e.findtext('a:title', default='', namespaces=ns)
link = e.find('a:link', ns).get('href')
updated = e.findtext('a:updated', default='', namespaces=ns)
summary = e.findtext('a:summary', default='', namespaces=ns)
# id → product slug
# author → posted by
Note: the public feed does NOT expose upvote counts. If you need upvotes, the product page itself has them in JSON-LD (scrape the product URL), or use the GraphQL API (requires auth token — out of scope).
When a topic is given, fetch the feed and filter entries where title or summary matches the topic (case-insensitive substring). PH titles are often 1-2 words so be lenient — also match the product page content if the topic is broad.
For better matching, fetch each candidate product page and check the tagline + description:
curl -s "https://www.producthunt.com/products/<slug>" | \
python3 -c "
import sys, re
html = sys.stdin.read()
# tagline is in <meta property='og:description'>
m = re.search(r'<meta property=\"og:description\" content=\"([^\"]+)\"', html)
print(m.group(1) if m else '')
"
Rate-limit yourself — don't hammer product pages. Cap at ~20 per scan.
# Product Hunt (since: <today|week>, category: <all|slug>, filter: "<topic or none>")
1. **<Product name>** — <tagline / og:description>
<https://www.producthunt.com/products/<slug>>
Launched: <date> | Category: <inferred from URL path or description>
2. ...
## Themes
- <1-line pattern spotted across today's launches>
- <another>
Called by /ro:trend-scan --discover. Pull the main feed for today, cluster by theme (keyword extraction on titles + summaries), return the top themes with 2+ product mentions.
application/atom+xml before parsing.--since week) automatically and note the fallback.hn-scan, reddit-scan, x-scan, youtube-scan — sibling source scanners.trend-scan — upstream orchestrator.development
Close the loop on a Linear ticket when its work ships - move the status and post a deploy comment with the PR link, what shipped, and a try-it link, mentioning the collaborator. Used as the tail of /ro:linear-nightshift for every merged mirror, or manually after an ad-hoc build. Triggers on "linear update", "update the linear ticket", "mark NUT-x done", "tell eoin it shipped", "/ro:linear-update".
devops
Run a night-shift against a collaborator's Linear board. Pulls the team's Grilled tickets (/ro:linear-grill moves a ticket to Grilled once its questions are answered), VERIFIES the questions were actually answered (unanswered → bounce the ticket to the "Question for <name>" state), mirrors verified tickets to ephemeral GitHub issues with ready-for-agent, then runs the standard /ro:night-shift machinery on GitHub. Tail-calls /ro:linear-update for everything that merged + deployed. Triggers on "linear nightshift", "nightshift linear", "drain the linear board", "run the shift off linear", "/ro:linear-nightshift".
development
Grill a collaborator's Linear tickets and move every processed ticket to where it belongs. Resolves the board from the repo's .ro-linear.json, reads the collaborator's Backlog / Ready-for-agent issues, then per ticket either posts 3-5 decision-extracting questions (state moves to "Question for <name>") or confirms it build-ready (state moves to "Grilled", the gate /ro:linear-nightshift consumes); shipped-and-confirmed tickets close as Done. The async-collaborator counterpart of /ro:day-shift for people who never touch GitHub. Triggers on "grill linear", "grill eoin's tickets", "linear grill", "add questions to the linear tickets", "/ro:linear-grill".
development
--- name: about-page description: Add a standard About page to any web app, what it is, the tech stack, and an FAQ, wired into a footer link with a sticky footer. Built with Spartan + Tailwind (the canonical component layer) and falls back to semantic HTML so it ships reliably. Use whenever building, polishing, or shipping an app, every app should have one. Triggers on "add an about page", "about page", "footer about link", or as a standard step in app build/polish. category: frontend argument-h