Transforms product documentation into sales-ready narrative packages combining story explanation, charcoal gestural sketch art, and talking points.
Technical documentation describes what a product does. Sales materials need to show why it matters — to a specific person, in a specific situation, with a specific fear or ambition in play. A generic AI asked to 'turn this doc into a pitch' produces a reformatted feature list. The features are still features, the voice is still technical, and nothing lands emotionally. Good sales materials aren't summaries of specs; they're stories with a protagonist who has a problem.
The pipeline runs in four steps: extract the narrative arc from the documentation (what's the real value, not what the product does), determine the emotional register that fits the arc — wonder, determination, hope — then derive a visual scene from that, and generate both assets together. CreateSalesPackage runs the full pipeline: a story explanation via the _STORYEXPLANATION skill, a charcoal gestural sketch generated through the Art essay-art workflow, and key talking points. The visual style is locked to charcoal gestural sketches — minimalist, breathing space, no corporate stock-photo aesthetic. CreateNarrative produces the story alone, 8-24 numbered points in first-person voice, built to be read as a script or dropped into a deck. CreateVisual produces the sketch for an existing narrative. The output is always tied tightly to what's actually being sold — there's no generic 'here are the benefits' filler.
What you say to your DA, and what the Sales skill actually does.
The thinking, frameworks, and architecture that distinguish this skill from a generic version of the same task.
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.
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.
The pipeline runs in four steps, from raw docs to a finished package:
PRODUCT DOCUMENTATION
↓
[1] STORY EXPLANATION — Extract the narrative arc (what's the real value?)
↓
[2] EMOTIONAL REGISTER — What feeling should this evoke? (wonder, determination, hope, etc.)
↓
[3] VISUAL CONCEPT — Derive scene from narrative + emotion
↓
[4] GENERATE ASSETS — Create visual + narrative package
↓
SALES-READY OUTPUT
It produces three things: sales narratives (story explanations that capture the value proposition), visual assets (charcoal sketch art that conveys the concept), and scripts (clear, succinct messaging tied to what you're selling). Internally it leans on the story-explanation narrative engine and the Art essay-art workflow for the visual.
Workflows/CreateSalesPackage.mdThe complete pipeline. Takes product docs and produces:
Workflows/CreateNarrative.mdJust the story. Converts technical docs into compelling narrative.
Workflows/CreateVisual.mdJust the visual. Creates charcoal sketch art for existing narrative.
Input: Technical documentation about AI code review tool
Output:
This skill combines:
The goal: Sales teams get materials that are highly tied to what they're selling, clear, succinct, and effective.
Example 1: Full sales package from docs
User: "create a sales package for this product" [provides docs]
→ Extracts narrative arc using storyexplanation
→ Determines emotional register (wonder, determination, hope)
→ Generates charcoal sketch visual + narrative + talking points
Example 2: Sales narrative only
User: "turn this technical doc into a sales pitch"
→ Reads documentation and extracts value proposition
→ Creates 8-24 point story explanation in first person
→ Returns conversational narrative ready for sales scripts
Example 3: Visual asset for existing narrative
User: "create a visual for this sales story"
→ Analyzes narrative for emotional core
→ Derives scene concept from story + emotion
→ Generates charcoal gestural sketch with transparent background
Workflows/CreateNarrative.md Workflows/CreateSalesPackage.md Workflows/CreateVisual.md Say any of these to your DA and PAI activates the Sales skill automatically:
Or invoke explicitly:
Skill("Sales")Install PAI on your machine — your DA gets the Sales skill plus 44 others, all hooked into one Life OS.