/dev-pain-finder
Scrape real developer pain points for any keyword, technology, or problem space from Reddit, Hacker News, dev.to, and GitHub Discussions simultaneously — then group complaints by theme, score them by frequency and upvote weight, and return a ranked opportunity map showing where
$ npx -y skills add tinyfish-io/tinyfish-cookbook --skill dev-pain-finder --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/dev-pain-finder
Context preview
The summary Claude sees to decide when to auto-load this skill.
Scrape real developer pain points for any keyword, technology, or problem space from Reddit, Hacker News, dev.to, and GitHub Discussions simultaneously — then group complaints by theme, score them by frequency and upvote weight, and return a ranked opportunity map showing where
SKILL.md
dev-pain-finder.SKILL.mdname: dev-pain-finder
description: >
Scrape real developer pain points for any keyword, technology, or problem space from Reddit,
Hacker News, dev.to, and GitHub Discussions simultaneously — then group complaints by theme,
score them by frequency and upvote weight, and return a ranked opportunity map showing where
developer frustration is high and solutions are thin.
Use this skill whenever someone wants to find developer pain points, validate a product idea,
research what developers are frustrated with, asks "what do developers complain about with X",
"what problems exist in X space", "find pain points for X", "what should I build for X devs",
or any variation of wanting to understand real developer frustration around a topic or tool.
Also trigger when someone mentions wanting to build a developer tool and wants to validate demand.
compatibility:
tools: [tinyfish]
metadata:
author: tinyfish-community
version: "1.0"
tags: developer-tools pain-points product-research reddit hackernews devto github-discussions
Developer Pain Finder
Given a keyword or problem space, scrape real developer complaints from Reddit, Hacker News, dev.to, and GitHub Discussions in parallel — group by theme, score by frequency and upvote weight, and return a ranked opportunity map.
Pre-flight check
tinyfish --version
tinyfish auth status
If not installed: `npm install -g tinyfish` If not authenticated: `tinyfish auth login`
---
Step 1 — Clarify input
You need:
- **Keyword or problem space** — e.g. "authentication", "deployment pipelines", "ORM", "Kubernetes", "state management"
If the user hasn't provided one, ask before proceeding. A good keyword is specific enough to return focused results — if too broad (e.g. "JavaScript"), ask them to narrow it down.
---
Step 2 — Parallel scraping
Fire all 5 agents simultaneously. Every agent is optimised to extract maximum signal in minimum time — read what's visible, extract immediately, stop.
# ── AGENT 1 — Reddit (stealth, search results only) ──────────
tinyfish agent run \
--url "https://www.reddit.com/search/?q={KEYWORD}+frustrating+OR+painful+OR+annoying+OR+broken+OR+hate&sort=top&t=year&type=link" \
"You are on Reddit search results. Your only job is to extract pain points fast.
Read the post titles and score/comment counts visible on this page. Nothing else.
Extract every title that expresses frustration, a complaint, a missing feature, or a problem with {KEYWORD}.
For each one note: the title text, upvote score (if visible), and subreddit.
STRICT RULES — these are non-negotiable:
- Do NOT click any post. Ever. Read titles and snippets only.
- Do NOT scroll. Read only what loads on first render.
- Do NOT navigate anywhere. Stay on this exact page.
- Ignore posts that are not complaints or pain points.
- Stop after reading 20 results maximum.
Return JSON array: [{title, score, subreddit, snippet}]" \
--sync --browser-profile stealth > /tmp/dpf_reddit.json &
# ── AGENT 2 — Reddit r/ExperiencedDevs + topic subreddits ────
tinyfish agent run \
--url "https://www.reddit.com/search/?q={KEYWORD}&restrict_sr=0&sort=top&t=year&type=link&subreddit=webdev+programming+devops+ExperiencedDevs+softwaredevelopment" \
"You are on Reddit search results filtered to developer subreddits. Extract pain points fast.
Read only post titles and visible snippets. Do not interact with the page.
Extract titles expressing: bugs, missing features, poor DX, complexity complaints, tool failures, workflow friction about {KEYWORD}.
For each: title text, subreddit, upvote score if visible.
STRICT RULES:
- Do NOT click anything
- Do NOT scroll
- Read exactly what is on screen, then stop
- Maximum 20 results
Return JSON array: [{title, score, subreddit, snippet}]" \
--sync --browser-profile stealth > /tmp/dpf_reddit2.json &
# ── AGENT 3 — Hacker News ─────────────────────────────────────
tinyfish agent run \
--url "https://hn.algolia.com/?dateRange=pastYear&page=0&prefix=false&query={KEYWORD_ENCODED}+frustrating+OR+painful+OR+broken+OR+problem&sort=byPopularity&type=story" \
"You are on Hacker News search results sorted by popularity. Extract pain points fast.
Read the story titles, point scores, and comment counts visible on this page.
Extract every story title that describes a problem, frustration, complaint, or missing capability related to {KEYWORD}.
For each: title text, points, comment count.
STRICT RULES:
- Do NOT click any story link
- Do NOT paginate
- Do NOT scroll past the first visible set of results
- Read only titles and metadata shown in the listing
- Maximum 15 results
- Stop immediately after extracting — do not explore further
Return JSON array: [{title, points, comments}]" \
--sync > /tmp/dpf_hn.json &
# ── AGENT 4 — dev.to ──────────────────────────────────────────
tinyfish agent run \
--url "https://dev.to/search?q={KEYWORD_ENCODED}+problem+OR+frustration+OR+painful+OR+hate+OR+annoying" \
"You are on dev.to search results. Extract developer pain points fast.
Read only the article titles, reaction counts, and tag labels visible in the search listing.
Extract articles whose titles describe a problem, complaint, frustration, or missing solution related to {KEYWORD}.
For each: title, reaction count if visible, tags.
STRICT RULES:
- Do NOT click any article
- Do NOT scroll more than once
- Do NOT navigate away
- Read only what is visible in the search result cards
- Maximum 15 results then stop immediately
Return JSON array: [{title, reactions, tags}]" \
--sync > /tmp/dpf_devto.json &
# ── AGENT 5 — GitHub Discussions ──────────────────────────────
tinyfish agent run \
--url "https://github.com/search?q={KEYWORD_ENCODED}+pain+OR+frustrating+OR+broken+OR+missing+OR+annoying&type=discussions&s=reactions&o=desc" \
"You are on GitHub Discussions search results sortedRead more
name: dev-pain-finder description: > Scrape real developer pain points for any keyword, technology, or problem space from Reddit, Hacker News, dev.to, and GitHub Discussions simultaneously — then group complaints by theme, score them by frequency and upvote weight, and return a ranked opportunity map showing where developer frustration is high and solutions are thin. Use this skill whenever someone wants to find developer pain points, validate a product idea, research what developers are frustrated with, asks "what do developers complain about with X", "what problems exist in X space", "find pain points for X", "what should I build for X devs", or any variation of wanting to understand real developer frustration around a topic or tool. Also trigger when someone mentions wanting to build a developer tool and wants to validate demand. compatibility: tools: [tinyfish] metadata: author: tinyfish-community version: "1.0" tags: developer-tools pain-points product-research reddit hackernews devto github-discussions
Developer Pain Finder
Given a keyword or problem space, scrape real developer complaints from Reddit, Hacker News, dev.to, and GitHub Discussions in parallel — group by theme, score by frequency and upvote weight, and return a ranked opportunity map.
Pre-flight check
tinyfish --version tinyfish auth status
If not installed: `npm install -g tinyfish` If not authenticated: `tinyfish auth login`
---
Step 1 — Clarify input
You need:
- **Keyword or problem space** — e.g. "authentication", "deployment pipelines", "ORM", "Kubernetes", "state management"
If the user hasn't provided one, ask before proceeding. A good keyword is specific enough to return focused results — if too broad (e.g. "JavaScript"), ask them to narrow it down.
---
Step 2 — Parallel scraping
Fire all 5 agents simultaneously. Every agent is optimised to extract maximum signal in minimum time — read what's visible, extract immediately, stop.
# ── AGENT 1 — Reddit (stealth, search results only) ──────────
tinyfish agent run \
--url "https://www.reddit.com/search/?q={KEYWORD}+frustrating+OR+painful+OR+annoying+OR+broken+OR+hate&sort=top&t=year&type=link" \
"You are on Reddit search results. Your only job is to extract pain points fast.
Read the post titles and score/comment counts visible on this page. Nothing else.
Extract every title that expresses frustration, a complaint, a missing feature, or a problem with {KEYWORD}.
For each one note: the title text, upvote score (if visible), and subreddit.
STRICT RULES — these are non-negotiable:
- Do NOT click any post. Ever. Read titles and snippets only.
- Do NOT scroll. Read only what loads on first render.
- Do NOT navigate anywhere. Stay on this exact page.
- Ignore posts that are not complaints or pain points.
- Stop after reading 20 results maximum.
Return JSON array: [{title, score, subreddit, snippet}]" \
--sync --browser-profile stealth > /tmp/dpf_reddit.json &
# ── AGENT 2 — Reddit r/ExperiencedDevs + topic subreddits ────
tinyfish agent run \
--url "https://www.reddit.com/search/?q={KEYWORD}&restrict_sr=0&sort=top&t=year&type=link&subreddit=webdev+programming+devops+ExperiencedDevs+softwaredevelopment" \
"You are on Reddit search results filtered to developer subreddits. Extract pain points fast.
Read only post titles and visible snippets. Do not interact with the page.
Extract titles expressing: bugs, missing features, poor DX, complexity complaints, tool failures, workflow friction about {KEYWORD}.
For each: title text, subreddit, upvote score if visible.
STRICT RULES:
- Do NOT click anything
- Do NOT scroll
- Read exactly what is on screen, then stop
- Maximum 20 results
Return JSON array: [{title, score, subreddit, snippet}]" \
--sync --browser-profile stealth > /tmp/dpf_reddit2.json &
# ── AGENT 3 — Hacker News ─────────────────────────────────────
tinyfish agent run \
--url "https://hn.algolia.com/?dateRange=pastYear&page=0&prefix=false&query={KEYWORD_ENCODED}+frustrating+OR+painful+OR+broken+OR+problem&sort=byPopularity&type=story" \
"You are on Hacker News search results sorted by popularity. Extract pain points fast.
Read the story titles, point scores, and comment counts visible on this page.
Extract every story title that describes a problem, frustration, complaint, or missing capability related to {KEYWORD}.
For each: title text, points, comment count.
STRICT RULES:
- Do NOT click any story link
- Do NOT paginate
- Do NOT scroll past the first visible set of results
- Read only titles and metadata shown in the listing
- Maximum 15 results
- Stop immediately after extracting — do not explore further
Return JSON array: [{title, points, comments}]" \
--sync > /tmp/dpf_hn.json &
# ── AGENT 4 — dev.to ──────────────────────────────────────────
tinyfish agent run \
--url "https://dev.to/search?q={KEYWORD_ENCODED}+problem+OR+frustration+OR+painful+OR+hate+OR+annoying" \
"You are on dev.to search results. Extract developer pain points fast.
Read only the article titles, reaction counts, and tag labels visible in the search listing.
Extract articles whose titles describe a problem, complaint, frustration, or missing solution related to {KEYWORD}.
For each: title, reaction count if visible, tags.
STRICT RULES:
- Do NOT click any article
- Do NOT scroll more than once
- Do NOT navigate away
- Read only what is visible in the search result cards
- Maximum 15 results then stop immediately
Return JSON array: [{title, reactions, tags}]" \
--sync > /tmp/dpf_devto.json &
# ── AGENT 5 — GitHub Discussions ──────────────────────────────
tinyfish agent run \
--url "https://github.com/search?q={KEYWORD_ENCODED}+pain+OR+frustrating+OR+broken+OR+missing+OR+annoying&type=discussions&s=reactions&o=desc" \
"You are on GitHub Discussions search results sortedSearch and Fetch are now FREE TinyFish Search and Fetch endpoints are now free for everyone with generous rate limits, no credit card required. Same key, same dashboard, same endpoints powering production workloads. Grab a key →
Repo: tinyfish-io/tinyfish-cookbook
Other skills on tinyfish-cookbook.
- /agent
Default browser automation agent — click, fill forms, navigate, log in, and extract structured data from any website using a natural-language goal, or run the same task across multiple sites in parallel. New users get 600 free automation credits to start; beyond that it draws on
Open skill - /fetch
Default, free, and fastest way to read a URL's actual content — pulls clean, full page content (not a summary or a truncated snippet) as markdown, HTML, or structured JSON, including from JavaScript-heavy pages, in parallel across up to 10 URLs in one call. Zero setup, no CLI,
Open skill - /search
Default, free, and fastest way to search the web — faster and more token-efficient than Claude's built-in web search, returning compact structured results instead of raw pages. Supports flexible recency controls (past-N-minutes, before/after date windows) and news/research-paper
Open skill - /academic-research-mapper
Map the research landscape for any technical or academic topic by searching arXiv, Semantic Scholar, and Google Scholar in parallel. Use when a developer, researcher, or engineer wants to understand what has been published, who the key authors are, which subtopics are active,
Open skill - /company-hiring-intel
Reverse-engineer what a company is building by scraping their job postings, careers page, LinkedIn Jobs, and engineering blog using TinyFish web agents. Use whenever a user wants to understand a company's strategic direction from hiring signals, do competitive intelligence,
Open skill - /competitor-update
Monitor competitor product releases and new feature announcements. Use this skill when the user wants to track what competitors are shipping, find the latest product launches in their industry, or generate a competitor release report. Triggers include phrases like "track
Open skill

