Sales

Customization

Before executing, check for user customizations at: ~/.claude/LIFEOS/USER/CUSTOMIZATIONS/SKILLS/Sales/

If this directory exists, load and apply any PREFERENCES.md, configurations, or resources found there. These override default behavior. If the directory does not exist, proceed with skill defaults.

🚨 MANDATORY: Voice Notification (REQUIRED BEFORE ANY ACTION)

You MUST send this notification BEFORE doing anything else when this skill is invoked.

1. Send voice notification:

   curl -s -X POST http://localhost:31337/notify \
     -H "Content-Type: application/json" \
     -d '{"message": "Running the WORKFLOWNAME workflow in the Sales skill to ACTION"}' \
     > /dev/null 2>&1 &
   

2. Output text notification:

   Running the **WorkflowName** workflow in the **Sales** skill to ACTION...
   

This is not optional. Execute this curl command immediately upon skill invocation.

Sales Skill

What It Does

Turns product documentation into a sales-ready package: a story narrative that captures the value proposition, a charcoal gestural sketch that conveys the concept visually, and clear talking points. It reads the real value out of technical docs and reframes it as something a sales team can actually use in a pitch.

The Problem

Product docs explain what a thing does. Sales needs to explain why it matters — and the gap between the two is where most pitches die. Hand a sales team a feature list and they read off bullet points; the buyer feels nothing and forgets it. The translation from "here's what it does" to "here's the story you'll remember" usually takes a writer and a designer and a few days, so it doesn't happen, and the product gets sold flat. This skill does that translation: it pulls the narrative arc out of the docs, finds the emotional register, and generates the narrative plus a matching visual tied directly to what's being sold.

How It Works

The pipeline runs in four steps, from raw docs to a finished package: