plugins/development/skills/inbox/SKILL.md
Fetches and processes items queued from mobile via email (articles, GitHub repos, links, newsletters). Use when user says "inbox", "zkontroluj inbox", "check inbox", "co je noveho", or at session start to review new items. NOT for general email management or reading unrelated emails.
npx skillsauth add petrogurcak/skills inboxInstall 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.
Process items sent from mobile via email. Articles, GitHub repos, links, newsletters — anything worth reviewing.
python3 ~/.claude/scripts/inbox-fetch.py
Read ~/.claude/inbox/queue.json and show summary:
Inbox: X novych polozek (Y articles, Z newsletters)
1. [subject] — 2 URLs
2. [subject] — newsletter (15 URLs)
3. [subject] — 1 URL + poznamka
Before processing, classify each item:
Newsletter detection — item is a newsletter if ANY of:
Regular items — everything else (single article, repo, pasted text, note)
Newsletters do NOT use the interactive per-item flow. Instead:
~/.claude/NOW.md for current projects, interests, and queueNewsletter: [name/subject]
Relevantni:
- [Title](url) — 1-2 sentence why it matters for us
- [Title](url) — 1-2 sentence why it matters for us
Zbytek (X items): skip — [one-line reason, e.g. "generic AI news, nothing actionable"]
For each non-newsletter item, based on content type:
URL to article/blog:
GitHub repo:
Pasted text (paywalled article):
URL + user note (subject line):
Ask user what to do:
Update item status in queue.json to "processed" when done.
After all items processed:
python3 ~/.claude/scripts/inbox-fetch.py --clear
{
"id": "abc12345",
"date": "2026-02-20T21:30:00",
"subject": "User's note or email subject",
"from": "[email protected]",
"urls": ["https://..."],
"body": "Full text content (max 5000 chars)",
"status": "new|processed|skipped"
}
~/.claude/inbox/config.json:
{
"email": "[email protected]",
"app_password": "xxxx xxxx xxxx xxxx",
"imap_server": "imap.gmail.com",
"imap_port": 993
}
python3 ~/.claude/scripts/inbox-fetch.py[email protected]inbox / zkontroluj inbox — fetch + process queueinbox --list — just show what's in queue without fetchingdevelopment
Builds a pre-launch social proof strategy through structured beta programs using D'Souza Brain Audit interviews. Use when launching new products/services and need compelling testimonials, planning a beta cohort, designing interview questions to harvest objection-busting social proof, improving video testimonials for landing pages, or designing case studies with metrics. Trigger phrases include "beta tester program for testimonials", "pre-launch social proof", "Brain Audit testimonial framework", "case study harvest", "reverse testimonial", "video testimonial mechanics", "social proof landing page", "sběr referencí", "beta tester program", "testimonial pro landing page", "social proof před launchem", "rozhovor s klientem", "case study sběr", "reference před spuštěním". NOT for ongoing case study production (use growth-hacking case-study approach), offer design (use offer-creation), or conversion optimization (use ux-optimization).
development
Use when planning a product launch and the product type is unclear or could be either generic (SaaS/app/physical) or info-product. Routes between marketing:launch-strategy (generic launches) and marketing:info-product-launch (courses, memberships, ebooks, cohorts, communities). Trigger phrases - "launch", "spuštění", "go-to-market", "product launch", "release strategy", "uvedení na trh", "launch plan", "spuštění produktu", "launch sequence", "launch strategy". Do NOT trigger when product type is already clear (use specific skill directly).
testing
Specialized 8-week launch cadence for info-products — online courses, cohort programs, memberships, communities, ebooks, masterminds. Combines Jeff Walker's Product Launch Formula (Seed/Internal/JV variants, PLC sequence, open-cart day-by-day) with Stu McLaren's membership mechanics (closed cart, Success Path) and Hormozi Grand Slam Offer stacking. Use when planning "launch online kurzu", "info-product launch", "PLF launch", "course launch", "membership launch", "cohort launch", "ebook launch", "open cart close cart", "8-week launch of online course", "beta cohort to launch sequence", "spuštění kurzu", "launch členské sekce", "open cart strategie". Differentiates from marketing:launch-strategy (generic SaaS/app launches) — info-product-specific. NOT for SaaS launches, physical products, or services.
development
Use when releasing an Expo/React Native mobile app to App Store and Google Play - covers eas submit, ASC "Submit for Review", Play promote Internal→Production, OTA update, and decoding common silent failures (Apple agreement expiry, missing English locale, Background Location declaration, web bundle failure on react-native-maps).