Founder pain miner

Skill lexthirteen-ai/founder-survival-kit/skills/founder-pain-miner

Claude skills for the hard parts of building, now that ai made the building easy

Install

npx -y skills add lexthirteen-ai/founder-survival-kit --skill founder-pain-miner

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

28 days oldThe repository was created 28 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Weekly sensor that reads founder communities and ranks the problems founders actually have. Reads a set of subreddits (defaults: r/vibecoding, r/SaaS, r/AI_Agents), pulls the past 7 days of top and rising posts, clusters them into recurring pain themes, ranks by frequency plus recency plus cross-community recurrence, and returns a ranked report of 5-8 themes. Each theme gets a disposition (content angle, keyword idea, promote-your-own-thing, or propose-a-new-skill) and a drafted artifact. Use when you want a fresh read on what founders are struggling with, or on a weekly cadence. Read-only, never posts.

SKILL.md

4.9 KB, as published. Nobody here has run it

Founder Pain Miner

The sensor of the kit. Every week it reads where founders talk, finds the pains that keep recurring, and turns them into things you can act on: angles to write about and keywords worth a page. It produces a ranked report, not raw data, and it never posts anywhere.

When to use

A weekly research pass, or any time you want to know what founders are actually stuck on.
Best run before you plan content or decide what to build next, so its output feeds those decisions.

Configure it first (once)

Open references/config.md and set:

the communities to read (defaults are r/vibecoding, r/SaaS, r/AI_Agents),
your voice, if you have one (otherwise it drafts in a plain, no-hype default),
your own products, if any, so the promote disposition can point at them (off and empty by default).

Process

Ingest. For each community, pull the past 7 days of top and rising posts plus their top comments. Retrieval order is in references/retrieval.md: try direct fetch of the public listing first, and use a browser connector (Chrome, Brave, any Chromium) as the fallback for pages that block plain fetching. Capture title, permalink, upvotes, comments, date, and one or two representative quotes per post.
Extract. For each post, write the underlying problem in one line (the pain, not the topic), and record its frequency signal: upvotes, comments, and whether the same pain shows up in more than one community.
Cluster. Group posts into recurring pain themes. A theme is a pain that shows up more than once, not a single viral post. Merge near-duplicates, discard one-offs.
Rank. Score each theme by frequency plus recency plus cross-community recurrence, using the rubric in references/scoring.md. Check data/theme-history.md: a theme that appeared in prior weeks gets a recurrence bonus. Keep the top 5-8.
Map a disposition for each theme using references/dispositions.md: content angle (default), keyword idea, promote-your-own-thing (only if you configured your own products), or propose-a-new-skill (only when a high-scoring pain keeps recurring and nothing in tier 2 or 3 covers it).
Draft the artifact each disposition calls for: a content angle, a keyword row, a promote note, or a skill proposal appended to data/skill-proposals.md. Write hooks in your voice (see config), never hype.
Write the report using the template in references/dispositions.md, and save it to data/reports/founder-pain-report-<YYYY-MM-DD>.md.
Append keyword rows to data/keyword-tracker.csv so recurring searchable pains accumulate over time.
Update history. Append this week's themes to data/theme-history.md with their scores, so next week can measure recurrence.

Output

One weekly report. For each of the top 5-8 themes: the pain in one line, 2-3 representative quotes with their links, a frequency score with a one-line reason, a disposition, and the drafted artifact. Plus a header (week, communities read, post count) and a closing one-line recommendation for what to write about this week.

Guardrails

Require recurrence. Do not over-trust a single viral post. A theme ranks high only when the pain recurs across posts or communities. One loud thread is a candidate, not a theme.
Read-only and rule-respecting. No voting, commenting, posting, or logging in. Respect each community's rules and terms. Direct fetch first, browser only as a fallback, modest request volume.
Honest evidence. Every theme carries real links. If a claimed pain has no traceable source, it does not go in the report.
No hype in drafts. Lead with the concrete incident, not an abstract claim. If a line could sit on a generic homepage, rewrite it.
Value first. This informs your own work. If you take any theme into a community yourself, keep it heavily value-first with anything you promote trailing softly. The skill never posts for you.

Feeds the rest of the kit: content angles feed build-in-public-engine, and the pains it surfaces are what the tier 2 and tier 3 skills solve. When it keeps finding a pain nothing in tier 2 or 3 covers, it proposes the kit's next skill in data/skill-proposals.md, which is how the kit grows.