create-an-asset

Create an Asset

Generate custom sales assets tailored to your prospect, audience, and goals. Supports interactive landing pages, presentation decks, executive one-pagers, and workflow/architecture demos.

Triggers

Invoke this skill when:

• User says /create-an-asset or /create-an-asset [CompanyName]
• User asks to "create an asset", "build a demo", "make a landing page", "mock up a workflow"
• User needs a customer-facing deliverable for a sales conversation

Overview

This skill creates professional sales assets by gathering context about:

• (a) The Prospect — company, contacts, conversations, pain points
• (b) The Audience — who's viewing, what they care about
• (c) The Purpose — goal of the asset, desired next action
• (d) The Format — landing page, deck, one-pager, or workflow demo

The skill then researches, structures, and builds a polished, branded asset ready to share with customers.

Phase 0: Context Detection & Input Collection

Step 0.1: Detect Seller Context

From the user's email domain, identify what company they work for.

Actions:

1. Extract domain from user's email
2. Search: "[domain]" company products services site:linkedin.com OR site:crunchbase.com
3. Determine seller context:

Store seller context:

seller:
  company: "[Company Name]"
  product: "[Product/Service]"
  value_props:
    - "[Key value prop 1]"
    - "[Key value prop 2]"
    - "[Key value prop 3]"
  differentiators:
    - "[Differentiator 1]"

Persist to knowledge base for future sessions. On subsequent invocations, confirm: "I have your seller context from last time — still selling [Product] at [Company]?"

Step 0.2: Collect Prospect Context (a)

Ask the user:

Deal stage options:

• Intro / First meeting
• Discovery
• Evaluation / Technical review
• POC / Pilot
• Negotiation
• Close

Step 0.3: Collect Audience Context (b)

Ask the user:

Audience type options:

• Executive (C-suite, VPs)
• Technical (Architects, Engineers, Developers)
• Operations (Ops, IT, Procurement)
• Mixed / Cross-functional

Primary concern options:

• ROI / Business impact
• Technical depth / Architecture
• Strategic alignment
• Risk mitigation / Security
• Implementation / Timeline

Step 0.4: Collect Purpose Context (c)

Ask the user:

Goal options:

• Intro / First impression
• Discovery follow-up
• Technical deep-dive
• Executive alignment / Business case
• POC proposal
• Deal close

Step 0.5: Select Format (d)

Ask the user: "What format works best for this?"

Step 0.6: Format-Specific Inputs

If "Workflow / Architecture demo" selected:

First, parse from user's description. Look for:

• Systems and components mentioned
• Data flows described
• Human interaction points
• Example scenarios

Then ask for any gaps:

Phase 1: Research (Adaptive)

Assess Context Richness

Always Research:

1. Prospect basics

   • Search: "[Company]" annual report investor presentation 2025 2026
   • Search: "[Company]" CEO strategy priorities 2025 2026
   • Extract: Revenue, employees, key metrics, strategic priorities

2. Leadership

   • Search: "[Company]" CEO CTO CIO 2025
   • Extract: Names, titles, recent quotes on strategy/technology

3. Brand colors

   • Search: "[Company]" brand guidelines
   • Or extract from company website
   • Store: Primary color, secondary color, accent

If Moderate/Sparse Context, Also Research:

4. Industry context

   • Search: "[Industry]" trends challenges 2025 2026
   • Extract: Common pain points, market dynamics

5. Technology landscape

   • Search: "[Company]" technology stack tools platforms
   • Extract: Current solutions, potential integration points

6. Competitive context

   • Search: "[Company]" vs [seller's competitors]
   • Extract: Current solutions, switching signals

If Transcripts/Materials Uploaded:

7. Conversation analysis
   • Extract: Stated pain points, decision criteria, objections, timeline
   • Identify: Key quotes to reference (use their exact language)
   • Note: Specific terminology, acronyms, internal project names

Phase 2: Structure Decision

Interactive Landing Page

Audience adjustments:

• Executive: Lead with business impact, ROI, strategic alignment
• Technical: Lead with architecture, security, integration depth
• Operations: Lead with workflow impact, change management, support
• Mixed: Balance strategic + tactical; use tabs to separate depth levels

Deck-Style

Same sections as landing page, formatted as linear slides:

Slide principles:

• One key message per slide
• Visual > text-heavy
• Use prospect's metrics and language
• Include speaker notes

One-Pager

Condense to single-scroll format:

Workflow / Architecture Demo

Structure based on complexity:

Standard elements:

1. Title bar: [Scenario Name] — Powered by [Seller Product]
2. Component nodes: Visual boxes/icons for each system
3. Flow arrows: Animated connections showing data movement
4. Step panel: Sidebar explaining current step in plain language
5. Controls: Play / Pause / Step Forward / Step Back / Reset
6. Annotations: Callouts for key decision points and value-adds
7. Data preview: Sample payloads or transformations at each step

Phase 3: Content Generation

General Principles

All content should:

• Reference specific pain points from user input or transcripts
• Use prospect's language — their terminology, their stated priorities
• Map seller's product → prospect's needs explicitly
• Include proof points where available (case studies, metrics, quotes)
• Feel tailored, not templated

Section Templates

Hero / Intro

Their Priorities (if discovery follow-up)

Solution Mapping

Use Cases / Demos

ROI / Business Case

Why Us / Differentiators

Next Steps / CTA

Workflow Demo Content

Component Definitions

For each system, define:

Component types:

• human — Person initiating or receiving
• document — PDFs, contracts, files
• ai — AI/ML models, agents
• database — Data stores, warehouses
• api — APIs, services
• middleware — Integration platforms, MCP servers
• output — Dashboards, reports, notifications

Flow Steps

For each step, define:

Scenario Narrative

Write a clear, specific walkthrough:

Phase 4: Visual Design

Color System

Typography

Visual Elements

Cards:

• Background: var(--bg-surface)
• Border: 1px solid rgba(255,255,255,0.1)
• Border-radius: 12px
• Box-shadow: subtle, layered
• Hover: slight elevation, border glow

Buttons:

• Primary: var(--accent) background, white text
• Secondary: transparent, accent border
• Hover: brightness increase, subtle scale

Animations:

• Transitions: 200-300ms ease
• Tab switches: fade + slide
• Hover states: smooth, not jarring
• Loading: subtle pulse or skeleton

Workflow Demo Specific

Component Nodes:

Flow Arrows:

Canvas:

Phase 5: Clarifying Questions (REQUIRED)

Before building any asset, always ask clarifying questions. This ensures alignment and prevents wasted effort.

Step 5.1: Summarize Understanding

First, show the user what you understood:

Step 5.2: Ask Standard Questions (ALL formats)

Step 5.3: Ask Format-Specific Questions

Interactive Landing Page:

• "Which sections matter most for this audience?"
• "Any specific demos or use cases to highlight?"
• "Should I include an ROI calculator?"
• "Any competitor positioning to address?"

Deck-Style:

• "How long is the presentation? (helps with slide count)"
• "Presenting live, or a leave-behind?"
• "Any specific flow or narrative arc in mind?"

One-Pager:

• "What's the single most important message?"
• "Any specific proof point or stat to feature?"
• "Will this be printed or digital?"

Workflow / Architecture Demo:

• "Let me confirm the components: [list]. Anything missing?"
• "Here's the flow I understood: [steps]. Correct?"
• "Should the demo show realistic sample data, or keep it abstract?"
• "Any integration details to highlight or downplay?"
• "Should viewers be able to click through steps, or auto-play?"

Step 5.4: Confirm and Proceed

After user responds:

Or, if still unclear:

Max 2 rounds of questions. If still ambiguous, make a reasonable choice and note: "I went with X — easy to adjust if you prefer Y."

Phase 6: Build & Deliver

Build the Asset

Following all specifications above:

1. Generate structure based on Phase 2
2. Create content based on Phase 3
3. Apply visual design based on Phase 4
4. Ensure all interactive elements work
5. Test responsiveness (if applicable)

Output Format

All formats: Self-contained HTML file

• All CSS inline or in <style> tags
• All JS inline or in <script> tags
• No external dependencies (except Google Fonts)
• Single file for easy sharing

File naming: [ProspectName]-[format]-[date].html

• Example: CentricBrands-workflow-demo-2026-01-28.html

Delivery Message

Phase 7: Iteration Support

After delivery, be ready to iterate:

Remember: Default to prospect's brand colors, but seller can adjust to their own brand or a neutral palette after initial build.

Quality Checklist

Before delivering, verify:

Content

• Prospect company name spelled correctly throughout
• Leadership names are current (not outdated)
• Pain points accurately reflect input/transcripts
• Seller's product accurately represented
• No placeholder text remaining
• Proof points are accurate and sourced

Visual

• Brand colors applied correctly
• All text readable (contrast)
• Animations smooth, not distracting
• Mobile responsive (if interactive page)
• Dark theme looks polished

Functional

• All tabs/sections load correctly
• Interactive elements work (calculators, demos)
• Workflow steps animate properly (if applicable)
• Navigation is intuitive
• CTA is clear and clickable

Professional

• Tone matches audience
• Appropriate level of detail for purpose
• No typos or grammatical errors
• Feels tailored, not templated

Examples

Example 1: Executive Landing Page

Input:

• Prospect: Acme Corp (manufacturing)
• Audience: C-suite
• Purpose: Exec alignment after discovery
• Format: Interactive landing page

Output structure:

Example 2: Technical Workflow Demo

Input:

• Prospect: Centric Brands
• Audience: IT architects
• Purpose: POC proposal
• Format: Workflow demo
• Components: Claude, Workato DataGenie, Snowflake, PDF contracts

Output structure:

Example 3: Sales One-Pager

Input:

• Prospect: TechStart Inc
• Audience: VP Engineering
• Purpose: Leave-behind after first meeting
• Format: One-pager

Output structure:

Appendix: Component Icons

For workflow demos, use these icon mappings:

Appendix: Brand Color Fallbacks

If brand colors cannot be extracted:

Skill created for generalized sales asset generation. Works for any seller, any product, any prospect.