.claude/skills/fb-finder/SKILL.md
Find the next batch of Facebook Business Page URLs for HVAC/local service leads using Serper.dev. Trigger this skill when the user says "podaj mi 30 linkow", "nastepna partia leadow", "znajdz kolejne linki FB", "podaj kolejne 30", "kolejna partia", "/fb-finder", or any variant asking for the next batch of Facebook leads.
npx skillsauth add cbbkrd-tech/jl-finishes fb-finderInstall 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.
Runs the Serper.dev scraper to find 30 clean Facebook Business Page URLs from the HVAC leads list, then presents them in blocks of 10 ready to paste into "Open Multiple URLs" or any tab opener.
cd /workspaces/ZeroKlik && python3 run_fb_finder_serper.py
The script:
hvac_leads_final.csv (7,775 HVAC leads)fb-dm-done.txtfb-dm-results.csv and progress to fb-dm-done.txtWait for it to finish -- takes 5-10 minutes.
After the script finishes, read the last 40 rows of fb-dm-results.csv and extract rows with status=found from the latest batch.
Before presenting, flag these as suspicious (exclude from main list, note separately):
facebook.com/100071691850608/ -- no business name in URLfacebook.com/firstname.lastname/ -- e.g. pete.murad, les.levy.1/photo.php, /photos/, /posts/, /videos//p/Business-Name-123456/ style URLs are OK.
Present clean URLs exactly as plain text, one URL per line, with absolutely NO numbers, no bullet points, and no extra characters before the URLs.
Insert a blank line after every 10th URL to create distinct blocks. Do NOT use code blocks (```).
Format exactly like this: https://www.facebook.com/example1/ https://www.facebook.com/example2/ ... (up to 10) https://www.facebook.com/example10/
https://www.facebook.com/example11/ ... (up to 20) https://www.facebook.com/example20/
https://www.facebook.com/example21/ ...
Then summary line at the very bottom:
Znaleziono X czystych linkow. Pominieto Y podejrzanych (powod). Przetworzono Z firm lacznie.
Flagged ones listed separately at bottom: business name + reason.
testing
When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," or "content planning." For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit.
development
When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' or 'competitive landing pages.' Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. Emphasizes deep research, modular content architecture, and varied section types beyond feature tables.
development
Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Covers subject lines, opening lines, body copy, CTAs, personalization, and multi-touch follow-up sequences.
development
When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' or 'involuntary churn.' This skill covers voluntary churn (cancel flows, save offers, exit surveys) and involuntary churn (dunning, payment recovery). For post-cancel win-back email sequences, see email-sequence. For in-app upgrade paywalls, see paywall-upgrade-cro.