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.testing
--- name: linear-pipeline description: The Fable orchestrator for a single dispatched Linear ticket. Holds almost no context itself; it receives `--issue <ID> --detached`, decides the stage sequence, and fans out a sub-agent per stage, passing forward only each stage's artifact (never re-derived, never inlined into its own context). Step zero, before any planning or stage routing, is a boundary triage against `canon/security-boundary.md` (#199): a match tags Ronan Connolly and stops the run, no
development
--- name: in-your-face description: Capture a chat-only answer into a durable artifact (markdown + HTML, PDF when cheap) and launch it automatically so the user cannot miss it. Use when user says "in your face", "don't let me lose this", "save that answer", "make that durable", or right after answering a substantive side question (a recipe, comparison, how-to, or generated prompt) that would otherwise die with the context. category: workflow argument-hint: [--no-open] [--vault <short>] [hint of
tools
One-shot headless OpenAI Codex CLI calls for background/admin AI tasks — summaries, classification, extraction, admin glue. The default engine for anything that runs AI constantly in the background (daemon-driven, per-event), because it bills the flat ChatGPT subscription instead of Claude usage or per-token API spend, and it keeps working while Claude is rate-limited. NEVER for coding — coding stays Claude. Use when a skill or daemon needs a cheap always-on AI call, when the user says "use codex", "ask codex", "codex as backup", or when building a background summarizer/classifier into a listener or loop. Reads auth from ~/.codex/auth.json (ChatGPT account, no API key).
research
Turn a warranty rejection, repair quote, or RMA email into a cited decision brief — legal read (NL/EU consumer law), is the part user-serviceable, live part and new-unit prices, repair-vs-DIY-vs-new economics, before-you-send-it checklist, deadlines. Use when the user pastes or screenshots a repair quote, warranty rejection, "not covered" email, onderzoekskosten fee, or asks "should I repair or replace this".