Menu
Scour the internet for people asking about family/financial planning apps — find potential pilot users for beanies.family and log opportunities to Notion
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Auto-approved commit, push, CI monitor, and deploy to production
Auto-approved commit, push, and deploy to production — skips the CI/Security gate for fast, locally-verified deploys. Classifies what changed and deploys the Vue app and/or the Astro marketing site as needed (same target-classification as deploy-prod-auto, minus the remote-CI wait).
Turn a scattered, half-formed idea, bug report, or feature request into a complete, well-researched row in the "Beanies Main Issue Tracker" Notion DB — researching the codebase, recent commits, docs, and the web to fill every field, asking only about genuine gaps, checking for duplicates, showing the full proposed issue for approval, and then creating it as a "Not started" row that /beanies-pre-plan can pick up. Use this WHENEVER the user wants to capture, log, file, raise, open, add, or jot down an issue / bug / feature / idea / ticket / tracker item / TODO for beanies — even when they just describe a problem or wish ("the calendar feels cramped on mobile", "we should let users export their data", "remember to fix the flaky sync toast") without saying the word "issue". It is the front door to the tracker and the step BEFORE /beanies-pre-plan.
Standardized requirements-intake step that runs BEFORE beanies-plan. Collects complete, well-structured intent (via a copy/paste template or a Notion issue row), reviews EVERY field, asks the user to resolve anything missing/unclear/TBC (writing resolved values back to the tracker) before building, and — when a mockup is requested — generates a CIG-clamped UI mockup via the frontend-design skill, gets it approved, and stores it on the tracker. Only after explicit user approval does it hand a fully-populated initial prompt (plus any approved mockup) to beanies-plan. Use when the user says "pre-plan this", "intake this issue", "prep a plan for X", or invokes /beanies-pre-plan.
Create standardized plans (and optionally GitHub issues) using a mandatory 4-pass review discipline — initial draft, DRY/error-handling, sustainability/maintainability, and fresh-eyes final sweep — with full context preservation.
Review, prepare and publish a beanies.family "beanstalk" blog post that lives in the Notion Blog Posts database. Use this skill whenever greg mentions the blog, the beanstalk, a Friday post, publishing or reviewing a post, a post ID or Notion blog row, blog images, Substack cross-posting, or says anything like "it's blog day", "review my post", "is post 12 ready", "ship the blog", or "time for this week's post" — even if he doesn't name the skill. Also use it when asked to check a draft's tone, grammar, SEO, or images before publication, or to sync a Notion post into the repo.
| name | pilot-scout |
| description | Scour the internet for people asking about family/financial planning apps — find potential pilot users for beanies.family and log opportunities to Notion |
Scour the internet across multiple platforms for people actively looking for family finance, budgeting, or family planning apps. Find 5-8 of the best opportunities where greg can introduce beanies.family, get feedback, and recruit early users. Log everything to the Notion Pilot Scouting DB.
/pilot-scoutUse WebSearch to run targeted queries across multiple platforms. Run ALL search groups in parallel for speed.
Search query templates (adapt and combine — run at least 8-10 searches):
# Reddit — direct app requests
"looking for" family budget app site:reddit.com
"recommend" family finance app site:reddit.com
"alternative to" YNAB OR Mint OR Monarch site:reddit.com
"need an app" family budget OR household budget site:reddit.com
"best app for" couples budget OR family finances site:reddit.com 2026
"self-hosted" budget OR finance app site:reddit.com
"privacy" budget app OR finance app site:reddit.com
# Hacker News — builders and early adopters
"Ask HN" budget app OR family finance site:news.ycombinator.com
"Show HN" budget OR family finance site:news.ycombinator.com
family finance app site:news.ycombinator.com 2026
# Product Hunt — app discovery
family budget OR family finance site:producthunt.com 2026
budgeting app launch site:producthunt.com
# Twitter/X — real-time requests
"looking for" family budget app site:twitter.com OR site:x.com
"anyone know" budget app family site:twitter.com OR site:x.com
"need a" budgeting app site:twitter.com OR site:x.com 2026
# Indie Hackers — founder community
family finance OR budget app site:indiehackers.com
personal finance app feedback site:indiehackers.com
# Quora — question-based
best family budgeting app site:quora.com
family finance planning app recommendation site:quora.com
# Ask MetaFilter — high-quality Q&A
budget app OR finance app site:ask.metafilter.com
# Facebook — groups (limited external search but try)
"family budget" app recommendation site:facebook.com
# BetaList / AlternativeTo — app seekers
family budget site:betalist.com OR site:alternativeto.net
alternative to YNAB OR Mint site:alternativeto.net
# Niche forums & blogs
"looking for" family budget app forum OR community
"switched from" YNAB OR Mint "looking for" alternative 2026
"local first" OR "offline" budget app OR finance app
"privacy focused" family finance app
Target subreddits (if using Reddit JSON API as fallback):
From all search results, identify the 5-8 best opportunities.
Ideal opportunity characteristics:
beanies.family strengths to match against (filter for these pain points):
Scoring heuristic:
Platform priority order:
For each of the top 5-8 opportunities, present:
### 1. [Platform] — "Post/Question Title"
**[Engagement stats, Age, Platform-specific metrics]**
Link: <clickable URL>
**What they're asking for:** [1-2 sentences — what this person needs]
**Why beanies fits:** [1 sentence — which beanies.family feature directly addresses their need]
**Reply angle:** [2-3 sentences — how greg should frame the introduction. Should feel genuine, helpful, not spammy. Lead with empathy or humor, mention beanies naturally.]
Reply angle guidelines:
End with a prioritization recommendation: which 2-3 to reply to first (freshest + highest engagement + best fit).
After presenting the opportunities, add each one to the Notion Pilot Scouting database.
Database details:
339247d9-a99f-80d7-a617-e449fb26bf62Use mcp__notion__API-post-page to create each entry with:
{
"parent": { "database_id": "339247d9-a99f-80d7-a617-e449fb26bf62" },
"properties": {
"Post Title": { "title": [{ "text": { "content": "<platform: post title truncated to 80 chars>" } }] },
"Sub": { "select": { "name": "<platform name>" } },
"Post Link": { "url": "<full URL>" },
"Post Detail": { "rich_text": [{ "text": { "content": "<what they need + reply angle suggestion>" } }] },
"Notes": { "rich_text": [{ "text": { "content": "<fit score + notes>" } }] },
"Status": { "select": { "name": "Found" } },
"Posted?": { "checkbox": false },
"Date": { "date": { "start": "<YYYY-MM-DD>" } },
"Type": { "select": { "name": "Opportunity" } }
}
}
Platform (Sub) select options: Reddit, Hacker News, Twitter/X, Product Hunt, Indie Hackers, Quora, Ask MetaFilter, Facebook, AlternativeTo, BetaList, MoneySavingExpert, Other
Fit Score (in Notes field):
End with:
339247d9-a99f-80d7-a617-e449fb26bf62) for existing entries. Query with mcp__notion__API-query-data-source or mcp__notion__API-post-search to see what's already been logged. Skip any URL that already appears in the database. This is a hard rule — greg has likely already seen and acted on (or dismissed) previous entries.curl with the Reddit JSON API (old.reddit.com/.../.json) for Reddit searches.