Sales Skill Runner

Run a single sales skill.

Arguments: <skill-name> [url-or-context]

Parse $ARGUMENTS to extract the skill name (first word) and optional URL or context (remaining words).

Server: http://localhost:3500

Instructions

Read the skill definition from packs/sales/skills/<skill-name>.md to understand what this skill does and what events to emit.

Setup (for pipeline-check)

If running pipeline-check, source .env.local to load STRIPE_API_KEY:

source .env.local 2>/dev/null

Use with curl (trailing colon is required): curl -s https://api.stripe.com/v1/endpoint -u "$STRIPE_API_KEY:"

Execution

1. POST a "running" status event:

curl -s -X POST http://localhost:3500/api/packs/sales/events -H 'Content-Type: application/json' -d '{"skill":"<skill-name>","component":"generic","props":{"title":"Running <skill-name>...","data":"Working on it"},"status":"running"}'

2. Do the work using Stripe API (pipeline-check), WebFetch (outreach-gen, sales-enablement), and WebSearch (cold-email, sales-enablement)

3. DELETE the running event:

curl -s -X DELETE "http://localhost:3500/api/packs/sales/events?skill=<skill-name>"

4. POST completed events with real data to http://localhost:3500/api/packs/sales/events

Refer to the full pipeline command at .claude/commands/sales.md for detailed steps for each skill (pipeline-check, cold-email, outreach-gen, sales-enablement).

Use real data from Stripe, WebFetch, and WebSearch. Never hardcode data. POST events progressively so the UI updates in real-time.