← ClaudeAtlas

setuplisted

Short auto-detection tour of what ProductLab can use in this project, then optional setup of PRODUCT.md, notifications and connectors. Use when the user runs /productlab:setup.
hitrich/productlab · ★ 0 · AI & Automation · score 75
Install: claude install-skill hitrich/productlab
# ProductLab setup ProductLab works the moment it is installed, with web search and fetch alone. Setup only shows what it found and lets the user add extras. Never block a lab run on setup. ## Step 0: detection tour (always first, no questions) Check silently, then print the summary below. ```bash [ -f PRODUCT.md ] && echo "PRODUCT.md found" || echo "PRODUCT.md missing" ls -d lab/*/ 2>/dev/null | head -20 # earlier lab runs grep -sE '^(NTFY_TOPIC|SLACK_WEBHOOK_URL|NOTIFICATION_EMAIL)=' .env | cut -d= -f1 ``` Connectors: look at the tools available in this session (do not call them). Note which of these exist, by tool or server name: Bright Data (reviews, forums, scraping at scale), Ahrefs or Semrush (search demand), Similarweb (rival traffic), Amplitude or Mixpanel (usage), Intercom or Zendesk (support tickets), HubSpot or Salesforce (deal notes), Linear, Jira or Notion (feedback and roadmap). A server that exists but needs sign-in counts as "needs sign-in". ``` ProductLab detected: Product context: PRODUCT.md found | missing (lab runs work, but briefs will ask more) Earlier runs: <n> in lab/: <slugs> Web research: web search and fetch (always on) Connectors: <name: ready | needs sign-in>, ... | none Notifications: <ntfy | Slack | email> | off Set up extras? 1) PRODUCT.md 2) notifications 3) connector tips [skip] ``` If the user skips, stop here. ## Step 1: PRODUCT.md (if chosen) Copy [assets/PRODUCT.md](assets/PRODUCT.md) (at `${CLAU