# Visual Research Skills — Task List

## Status Key
- [ ] Not started
- [~] In progress  
- [x] Done
- [!] Blocked

---

## Phase 1: Prepare for Open Source

### Strip & Generalize
- [ ] Fork `creative-visual-research/SKILL.md` → remove CE/eToro-specific references
- [ ] Fork `visual-competitive-analysis/SKILL.md` → extract style system into `references/style-system.md` with configurable variables
- [ ] Fork `visual-benchmarking/SKILL.md` → remove internal references (Kittoro, channel IDs)
- [ ] Replace all hardcoded paths (`work/pitches/`, `public/etoro-competition/`) with relative paths
- [ ] Remove team/agent references (Gerri, Kittoro, Anton, etc.)
- [ ] Make Typekit ID configurable (or remove font dependency for generic use)

### Create Foundation Skill
- [ ] Write `visual-research-context/SKILL.md` — project config, brand schema, style preferences
- [ ] Define the brand config JSON schema (brand, website, social handles, agencies, campaigns)
- [ ] Add "when to use" triggers in description

### Bundle Scripts
- [ ] Clean up `extract-images.sh` for open source (remove internal paths)
- [ ] Clean up `compress-images.js` for open source
- [ ] Clean up `section-audit.py` for open source (remove internal staging URLs)
- [ ] Create `init-brand.sh` — scaffolds a new brand research directory
- [ ] Create `instagram-fetch.py` — standalone Instagram API image fetcher
- [ ] Test all scripts in a clean environment
- [ ] Add dependency list (Playwright, Node.js, Python, ImageMagick)

### Validate Against Spec
- [ ] Audit each SKILL.md — frontmatter only `name` + `description`
- [ ] Check all SKILL.md bodies are under 500 lines
- [ ] Move excess content to `references/` files
- [ ] Ensure all reference files are linked from SKILL.md with usage context
- [ ] Remove any extraneous docs (no README inside skill folders)

### Autoresearch Evals
- [ ] Write binary evals for `creative-visual-research`
- [ ] Write binary evals for `visual-competitive-analysis`
- [ ] Write binary evals for `visual-benchmarking`
- [ ] Test eval loop on at least one brand

---

## Phase 2: Repo & README

### Repo Setup
- [ ] Create GitHub repo
- [ ] Choose license (MIT recommended)
- [ ] Set up directory structure per PLAN.md
- [ ] Write CONTRIBUTING.md (PR guidelines, skill standards)
- [ ] Create `install.sh` one-command setup script

### README
- [ ] Write hero section with one-sentence pitch
- [ ] Create pipeline ASCII diagram
- [ ] Add live example screenshots (anonymized if needed)
- [ ] Write Quick Start section
- [ ] Write compatibility section (Claude Code, OpenClaw, AgentSkills)
- [ ] Write skill descriptions section
- [ ] Write Contributing section
- [ ] Final review pass for polish

### Example Output
- [ ] Decide: include real brand pages or create fictional examples?
- [ ] Prepare 2-3 example pages for `examples/` directory
- [ ] Take screenshots for README

---

## Phase 3: Launch Prep

### Content
- [ ] Draft launch tweet (main)
- [ ] Draft thread (5-7 tweets)
- [ ] Record 60-second demo video
- [ ] Write companion blog post outline
- [ ] Prepare before/after comparison images

### Distribution
- [ ] Identify 10-15 people to DM (agent skills community, marketing folks)
- [ ] Draft DM template
- [ ] Prepare r/ClaudeAI post
- [ ] Prepare Hacker News submission
- [ ] Prepare ClawHub submission

### Timing
- [ ] Set launch date
- [ ] Coordinate across platforms (tweet, reddit, HN same day)

---

## Phase 4: Launch & Post-Launch

### Launch Day
- [ ] Publish tweet + thread
- [ ] Send DMs to identified people
- [ ] Post to Reddit
- [ ] Submit to HN
- [ ] Submit to ClawHub
- [ ] Monitor GitHub issues

### Week 1 Post-Launch
- [ ] Respond to all issues within 24h
- [ ] Respond to all PRs within 48h
- [ ] Share user results/testimonials
- [ ] Publish companion blog post
- [ ] Collect and address feedback
- [ ] Track GitHub stars / forks / traffic

---

## Decisions Needed (from Assaf/Dan)
1. GitHub org name?
2. Include CE styleguide as default or fully generic?
3. Include real brand example pages or anonymize?
4. Ship fast (this week) or polish (next week)?
5. Value ladder: link to CE services from README?
6. Who owns ongoing maintenance / PR reviews?

---

*Last updated: 2026-03-20*