anima-marketing

name	anima-marketing
version	1.0.0
description	Mass marketing automation for RobotFlow Labs projects. 8 modes: SUBMIT (awesome lists, GitHub Discussions), SOCIAL (X/Twitter, LinkedIn, Reddit drafts), HN (Hacker News Show HN), REDDIT (browser-post to subreddits), BLOG (Dev.to/Medium), HUNT (ProductHunt), SCAN (find communities), BLITZ (all at once). Use via /anima-marketing [MODE] [project-url-or-path]. Supports browser automation for X.com, Reddit, HN via native Computer Use (embedded) and MCP browser tools as fallback. GitHub submissions via gh CLI.
allowed-tools	["Bash","Read","Write","Edit","Grep","Glob","WebFetch","WebSearch","Agent","AskUserQuestion"]

/anima-marketing — Mass Marketing Automation

Launch any RobotFlow Labs project to maximum visibility. 8 modes, real scripts, browser automation.

IMPORTANT: Read project context FIRST

Before ANY mode, ALWAYS:

1. Read the project's README.md to extract: name, one-liner description, install command, key stats/benchmarks, GitHub URL
2. Read CHANGELOG.md if it exists (for version/features)
3. Store these in variables for use across all modes:
   • PROJECT_NAME — repo name
   • PROJECT_URL — GitHub URL
   • PROJECT_ONELINER — one sentence pitch
   • PROJECT_INSTALL — one-line install command
   • PROJECT_STATS — key numbers (stars, tests, performance, etc.)
   • PROJECT_TOPICS — comma-separated topics for searching

MODE: SCAN — Find submission targets

Usage: /anima-marketing SCAN <project-path-or-url> topics:<comma-separated>

Workflow:

1. Extract topics from the project (from GitHub topics, README keywords, or user-provided)
2. Run the find script for each topic:

bash ~/.ccs/shared/skills/anima-marketing/scripts/find_awesome_lists.sh <topic1> <topic2> ...

3. Also search for:
   • GitHub Discussions on related repos (ml-explore/mlx, docker/docker, etc.)
   • Relevant subreddits via WebSearch: site:reddit.com "<topic>" subreddit
   • Relevant Discord servers via WebSearch
4. Score each target by: audience size (stars/members), relevance, submission difficulty
5. Save results to MARKETING-TARGETS.md:

# Marketing Targets for <PROJECT_NAME>

## Awesome Lists (GitHub PRs)
| Repo | Stars | Section | Difficulty |
|------|-------|---------|------------|
| owner/awesome-topic | 5,000 | Tools | Easy (issue) |

## GitHub Discussions
| Repo | Category | Audience |
|------|----------|----------|

## Reddit
| Subreddit | Members | Best Format |
|-----------|---------|-------------|

## Other
| Platform | Community | Notes |
|----------|-----------|-------|

---

MODE: SUBMIT — Automated GitHub submissions

Usage: /anima-marketing SUBMIT <github-url> [--targets MARKETING-TARGETS.md]

Workflow:

1. Read MARKETING-TARGETS.md (or SCAN first if it doesn't exist)
2. For each awesome list target:

bash ~/.ccs/shared/skills/anima-marketing/scripts/submit_awesome.sh \
  "owner/awesome-repo" \
  "- [project](url): description" \
  "Tools"

3. For each GitHub Discussion target:

bash ~/.ccs/shared/skills/anima-marketing/scripts/submit_discussion.sh \
  "owner" "repo" "Title" "body"

4. For repos that don't accept PRs, create issues:

bash ~/.ccs/shared/skills/anima-marketing/scripts/submit_issue.sh \
  "owner/repo" "Add project — description" "body"

5. Track ALL submissions in MARKETING-SUBMISSIONS.md:

# Submissions for <PROJECT_NAME>

| Target | Type | URL | Status | Date |
|--------|------|-----|--------|------|
| awesome-mlx | PR | github.com/.../pull/5 | Open | 2026-04-01 |

---

MODE: SOCIAL — Generate social media content

Usage: /anima-marketing SOCIAL <project-path-or-url>

Workflow:

1. Read project README, extract key messaging
2. Generate ALL of these in one file SOCIAL-POSTS.md:

Twitter/X Thread (5-7 tweets)

Tweet 1 (Hook): Bold claim or question. Must stop the scroll.
  "We just open-sourced the NVIDIA Container Toolkit for Mac."

Tweet 2 (Problem): What's broken today.
  "Docker on Mac = no GPU. Every ML workload falls back to CPU inside containers."

Tweet 3 (Solution): What we built.
  "docker_mlx_cpp: any container gets Metal GPU access. 107 ops. One line install."

Tweet 4 (Proof): Numbers/benchmarks.
  "Tested on M5: 95 TFLOPS matmul, Flash Attention 1.6ms, 107/108 ops passing."

Tweet 5 (How): Technical detail.
  "Architecture: host-side MLX daemon → Docker gateway → your container. Zero CUDA."

Tweet 6 (CTA): Link to repo.
  "One line: curl -fsSL https://raw.githubusercontent.com/... | bash

  GitHub: github.com/RobotFlow-Labs/docker_mlx_cpp"

LinkedIn Post (professional tone, 1300 chars max)

Professional tone. Lead with the problem. Include: what it is, why it matters, benchmarks, link.

Reddit Posts (one per subreddit, adapted tone)

• r/LocalLLaMA: Focus on local inference, model support, benchmarks
• r/MachineLearning: Focus on architecture, technical contribution
• r/docker: Focus on Docker ecosystem integration
• r/apple: Focus on Apple Silicon, Metal GPU
• r/selfhosted: Focus on self-hosting, privacy

HN Backstory Comment

First-person narrative: "Why I built this, what problem it solves, what I learned."

---

MODE: HN — Hacker News Show HN

Usage: /anima-marketing HN <github-url> [--post]

Workflow:

1. Draft title: Show HN: <project> – <one-liner under 80 chars>
2. Draft backstory comment (500-800 words, first person)
3. Save to HN-SUBMISSION.md
4. If --post flag: use Chrome DevTools to submit:

BROWSER AUTOMATION — Use NATIVE COMPUTER USE (embedded in Claude Code):

Computer Use is the PRIMARY method. It can see the screen, move the mouse,
click, type, and take screenshots — no MCP tools needed.

WORKFLOW:
1. Take screenshot → see the current browser state
2. Navigate to https://news.ycombinator.com/submit (click address bar, type URL, press Enter)
3. Take screenshot → verify the submit page loaded
4. Click the title input field → type the Show HN title
5. Click the URL input field → type the GitHub URL
6. Take screenshot → verify fields are filled correctly
7. ASK USER: "Ready to submit to HN? Screenshot shows the filled form. [y/n]"
8. If yes: click the Submit button
9. Take screenshot → verify submission went through
10. Navigate to the posted story → click the comment box
11. Type the backstory comment
12. Click "add comment"
13. Take screenshot → verify comment posted

FALLBACK (if Computer Use not available, use MCP browser tools):
  - mcp__playwright-server__browser_navigate/click/snapshot
  - mcp__browsermcp__browser_navigate/click/snapshot
  - mcp__automatalabs-playwright-server__browser_navigate/fill/click

Timing guidance: Post Tuesday or Wednesday, 9-11 AM Pacific. Monitor and reply to first 5 comments within 30 minutes.

---

MODE: REDDIT — Post to subreddits

Usage: /anima-marketing REDDIT <github-url> [--subreddits r/LocalLLaMA,r/docker] [--post]

Workflow:

1. Read SOCIAL-POSTS.md for Reddit drafts (or generate if missing)
2. For each subreddit, adapt the post:
   • Adjust title for subreddit culture
   • Adjust body length and tone
   • Include relevant benchmarks/stats
3. Save to REDDIT-POSTS.md
4. If --post flag: use Chrome DevTools to submit to each:

BROWSER AUTOMATION — Use NATIVE COMPUTER USE (embedded in Claude Code):

For each subreddit:
1. Take screenshot → see current browser state
2. Navigate to https://www.reddit.com/r/{subreddit}/submit
3. Take screenshot → verify submit page loaded
4. Click the "Text" post tab (if link post tab is default)
5. Click the title input → type the post title
6. Click the body text area → type the post body (markdown)
7. Take screenshot → verify form is filled correctly
8. ASK USER: "Ready to post to r/{subreddit}? Screenshot shows the filled form. [y/n]"
9. If yes: click the Post button
10. Take screenshot → verify posted successfully

FALLBACK: Use MCP browser tools (playwright-server, browsermcp, etc.)

IMPORTANT: Always ask user confirmation before actually posting. Draft mode is default.

---

MODE: X — Post to X.com (Twitter)

Usage: /anima-marketing X <project-path> [--post]

Workflow:

1. Read SOCIAL-POSTS.md for X thread (or generate if missing)
2. Save thread to X-THREAD.md
3. If --post flag: use Chrome DevTools to post thread:

BROWSER AUTOMATION — Use NATIVE COMPUTER USE (embedded in Claude Code):

Posting a thread to X.com:
1. Take screenshot → see current browser state
2. Navigate to https://x.com/compose/post
3. Take screenshot → verify compose box is open
4. Click the compose text area → type Tweet 1 text
5. Take screenshot → verify text entered
6. ASK USER: "Ready to post first tweet? Screenshot shows the text. [y/n]"
7. Click the Post button
8. Take screenshot → verify posted
9. For remaining thread tweets:
   - Click "Reply" or "Add another tweet"
   - Type next tweet text
   - Take screenshot → show user what will be posted
   - ASK USER: "Post next tweet? [y/n]"
   - Click Post
10. Final screenshot → verify full thread

IMPORTANT: Always ask user before each post. Never auto-post without confirmation.

FALLBACK: Use MCP browser tools (playwright-server, browsermcp, etc.)

---

MODE: BLOG — Generate blog post

Usage: /anima-marketing BLOG <project-path>

Workflow:

1. Read ALL project docs (README, CHANGELOG, architecture docs, SHIPPING guide)
2. Generate 2000-3000 word blog post with this structure:

---
title: "<catchy title>"
published: false
description: "<meta description for SEO>"
tags: <topic1>, <topic2>, <topic3>, <topic4>
cover_image: <hero.png URL>
---

## The Problem (hook — 200 words)
On Linux, nvidia-docker gives containers --gpus all. On Mac, nothing. Until now.

## Why Existing Solutions Don't Work (300 words)
Docker Model Runner is inference-only. Podman Vulkan is 75% speed. Native MLX can't run in containers.

## What We Built (500 words)
Architecture explanation with diagram. Host daemon + gateway + container SDK.

## How It Works (500 words)
Code examples: install, start daemon, run from container, GPU compute.

## Benchmarks (300 words)
Performance table. Comparison with alternatives.

## Getting Started (300 words)
Step-by-step with code blocks.

## What's Next (200 words)
Roadmap, community, how to contribute.

3. Save to BLOG-POST.md (Dev.to frontmatter format)

---

MODE: HUNT — ProductHunt preparation

Usage: /anima-marketing HUNT <project-path>

Workflow:

1. Generate all ProductHunt materials:
   • Tagline (under 60 chars): "Docker with GPU support for Mac"
   • Description (2-3 paragraphs, problem-first)
   • Maker comment (backstory, 200-400 words)
   • First comment (for the thread, value-add)
   • Screenshots needed (list of 5 screenshots to take)
   • Categories to submit under
   • Launch timing recommendation
2. Save to PRODUCTHUNT-LAUNCH.md

---

MODE: BLITZ — Full launch sequence

Usage: /anima-marketing BLITZ <github-url>

Workflow:

1. SCAN — Find all targets
2. SUBMIT — Submit to all awesome lists + discussions
3. SOCIAL — Generate all social content
4. HN — Draft HN submission
5. BLOG — Generate blog post
6. HUNT — Prepare ProductHunt
7. Create MARKETING-BLITZ/ directory with all output files
8. Generate MARKETING-BLITZ/LAUNCH-CHECKLIST.md:

# Launch Checklist for <PROJECT_NAME>

## Pre-Launch (done by BLITZ)
- [x] Submitted to N awesome lists
- [x] Posted to M GitHub Discussions
- [x] Social content drafted for 5 platforms
- [x] HN Show HN drafted
- [x] Blog post drafted
- [x] ProductHunt materials ready

## Launch Day
- [ ] Post HN Show HN (Tuesday/Wednesday 9-11 AM PST)
- [ ] Post Twitter/X thread (same day, after HN)
- [ ] Post Reddit (r/LocalLLaMA first, then others 1-2 hours apart)
- [ ] Post LinkedIn
- [ ] Monitor HN comments (reply within 30 min)

## Post-Launch (Week 1)
- [ ] ProductHunt launch (1 week after HN)
- [ ] Publish Dev.to blog post
- [ ] Follow up on awesome list PRs
- [ ] Engage with GitHub issues/discussions
- [ ] Post YouTube tutorial (if recorded)

## Submissions Tracker
<paste MARKETING-SUBMISSIONS.md content>

---

RULES

1. ALWAYS ask before posting — Draft mode is default. Browser automation requires explicit --post flag AND user confirmation per post.
2. Never spam — Adapt tone per community. No copy-paste across subreddits.
3. Lead with value — Every post must provide value (benchmarks, how-to, architecture) not just "check out our tool."
4. Track everything — Every submission goes in MARKETING-SUBMISSIONS.md with URL and date.
5. Respect rate limits — Space Reddit posts 1-2 hours apart. One HN post per project.
6. Browser automation safety — Always take screenshots before and after posting. Always confirm with user.

SCRIPTS

All scripts are at: ~/.ccs/shared/skills/anima-marketing/scripts/

• find_awesome_lists.sh — Search GitHub for awesome-* repos by topic
• submit_awesome.sh — Fork → branch → add entry → PR (full automation)
• submit_discussion.sh — Create GitHub Discussion via GraphQL
• submit_issue.sh — Create GitHub issue on target repo