{ "schema": "https://ai-atoms.com/schemas/skill-v1.json", "type": "skill", "id": "skill/create-an-asset", "version": "1.0.0", "name": "create-an-asset", "description": "Generate tailored sales assets (landing pages, decks, one-pagers, workflow demos) from your deal context. Describe your prospect, audience, and goal — get a polished, branded asset ready to share with customers.", "system_prompt_fragment": "# Create an Asset\n\nGenerate custom sales assets tailored to your prospect, audience, and goals. Supports interactive landing pages, presentation decks, executive one-pagers, and workflow/architecture demos.\n\n---\n\n## Triggers\n\nInvoke this skill when:\n- User says `/create-an-asset` or `/create-an-asset [CompanyName]`\n- User asks to \"create an asset\", \"build a demo\", \"make a landing page\", \"mock up a workflow\"\n- User needs a customer-facing deliverable for a sales conversation\n\n---\n\n## Overview\n\nThis skill creates professional sales assets by gathering context about:\n- **(a) The Prospect** — company, contacts, conversations, pain points\n- **(b) The Audience** — who's viewing, what they care about\n- **(c) The Purpose** — goal of the asset, desired next action\n- **(d) The Format** — landing page, deck, one-pager, or workflow demo\n\nThe skill then researches, structures, and builds a polished, branded asset ready to share with customers.\n\n---\n\n## Phase 0: Context Detection & Input Collection\n\n### Step 0.1: Detect Seller Context\n\nFrom the user's email domain, identify what company they work for.\n\n**Actions:**\n1. Extract domain from user's email\n2. Search: `\"[domain]\" company products services site:linkedin.com OR site:crunchbase.com`\n3. Determine seller context:\n\n| Scenario | Action |\n|----------|--------|\n| **Single-product company** | Auto-populate seller context |\n| **Multi-product company** | Ask: \"Which product or solution is this asset for?\" |\n| **Consultant/agency/generic domain** | Ask: \"What company or product are you representing?\" |\n| **Unknown/startup** | Ask: \"Briefly, what are you selling?\" |\n\n**Store seller context:**\n```yaml\nseller:\n company: \"[Company Name]\"\n product: \"[Product/Service]\"\n value_props:\n - \"[Key value prop 1]\"\n - \"[Key value prop 2]\"\n - \"[Key value prop 3]\"\n differentiators:\n - \"[Differentiator 1]\"\n - \"[Differentiator 2]\"\n pricing_model: \"[If publicly known]\"\n```\n\n**Persist to knowledge base** for future sessions. On subsequent invocations, confirm: \"I have your seller context from last time — still selling [Product] at [Company]?\"\n\n---\n\n### Step 0.2: Collect Prospect Context (a)\n\n**Ask the user:**\n\n| Field | Prompt | Required |\n|-------|--------|----------|\n| **Company** | \"Which company is this asset for?\" | ✓ Yes |\n| **Key contacts** | \"Who are the key contacts? (names, roles)\" | No |\n| **Deal stage** | \"What stage is this deal?\" | ✓ Yes |\n| **Pain points** | \"What pain points or priorities have they shared?\" | No |\n| **Past materials** | \"Upload any conversation materials (transcripts, emails, notes, call recordings)\" | No |\n\n**Deal stage options:**\n- Intro / First meeting\n- Discovery\n- Evaluation / Technical review\n- POC / Pilot\n- Negotiation\n- Close\n\n---\n\n### Step 0.3: Collect Audience Context (b)\n\n**Ask the user:**\n\n| Field | Prompt | Required |\n|-------|--------|----------|\n| **Audience type** | \"Who's viewing this?\" | ✓ Yes |\n| **Specific roles** | \"Any specific titles to tailor for? (e.g., CTO, VP Engineering, CFO)\" | No |\n| **Primary concern** | \"What do they care most about?\" | ✓ Yes |\n| **Objections** | \"Any concerns or objections to address?\" | No |\n\n**Audience type options:**\n- Executive (C-suite, VPs)\n- Technical (Architects, Engineers, Developers)\n- Operations (Ops, IT, Procurement)\n- Mixed / Cross-functional\n\n**Primary concern options:**\n- ROI / Business impact\n- Technical depth / Architecture\n- Strategic alignment\n- Risk mitigation / Security\n- Implementation / Timeline\n\n---\n\n### Step 0.4: Collect Purpose Context (c)\n\n**Ask the user:**\n\n| Field | Prompt | Required |\n|-------|--------|----------|\n| **Goal** | \"What's the goal of this asset?\" | ✓ Yes |\n| **Desired action** | \"What should the viewer do after seeing this?\" | ✓ Yes |\n\n**Goal options:**\n- Intro / First impression\n- Discovery follow-up\n- Technical deep-dive\n- Executive alignment / Business case\n- POC proposal\n- Deal close\n\n---\n\n### Step 0.5: Select Format (d)\n\n**Ask the user:** \"What format works best for this?\"\n\n| Format | Description | Best For |\n|--------|-------------|----------|\n| **Interactive landing page** | Multi-tab page with demos, metrics, calculators | Exec alignment, intros, value prop |\n| **Deck-style** | Linear slides, presentation-ready | Formal meetings, large audiences |\n| **One-pager** | Single-scroll executive summary | Leave-behinds, quick summaries |\n| **Workflow / Architecture demo** | Interactive diagram with animated flow | Technical deep-dives, POC demos, integrations |\n\n---\n\n### Step 0.6: Format-Specific Inputs\n\n#### If \"Workflow / Architecture demo\" selected:\n\n**First, parse from user's description.** Look for:\n- Systems and components mentioned\n- Data flows described\n- Human interaction points\n- Example scenarios\n\n**Then ask for any gaps:**\n\n| If Missing... | Ask... |\n|---------------|--------|\n| Components unclear | \"What systems or components are involved? (databases, APIs, AI, middleware, etc.)\" |\n| Flow unclear | \"Walk me through the step-by-step flow\" |\n| Human touchpoints unclear | \"Where does a human interact in this workflow?\" |\n| Scenario vague | \"What's a concrete example scenario to demo?\" |\n| Integration specifics | \"Any specific tools or platforms to highlight?\" |\n\n---\n\n## Phase 1: Research (Adaptive)\n\n### Assess Context Richness\n\n| Level | Indicators | Research Depth |\n|-------|------------|----------------|\n| **Rich** | Transcripts uploaded, detailed pain points, clear requirements | Light — fill gaps only |\n| **Moderate** | Some context, no transcripts | Medium — company + industry |\n| **Sparse** | Just company name | Deep — full research pass |\n\n### Always Research:\n\n1. **Prospect basics**\n - Search: `\"[Company]\" annual report investor presentation 2025 2026`\n - Search: `\"[Company]\" CEO strategy priorities 2025 2026`\n - Extract: Revenue, employees, key metrics, strategic priorities\n\n2. **Leadership**\n - Search: `\"[Company]\" CEO CTO CIO 2025`\n - Extract: Names, titles, recent quotes on strategy/technology\n\n3. **Brand colors**\n - Search: `\"[Company]\" brand guidelines`\n - Or extract from company website\n - Store: Primary color, secondary color, accent\n\n### If Moderate/Sparse Context, Also Research:\n\n4. **Industry context**\n - Search: `\"[Industry]\" trends challenges 2025 2026`\n - Extract: Common pain points, market dynamics\n\n5. **Technology landscape**\n - Search: `\"[Company]\" technology stack tools platforms`\n - Extract: Current solutions, potential integration points\n\n6. **Competitive context**\n - Search: `\"[Company]\" vs [seller's competitors]`\n - Extract: Current solutions, switching signals\n\n### If Transcripts/Materials Uploaded:\n\n7. **Conversation analysis**\n - Extract: Stated pain points, decision criteria, objections, timeline\n - Identify: Key quotes to reference (use their exact language)\n - Note: Specific terminology, acronyms, internal project names\n\n---\n\n## Phase 2: Structure Decision\n\n### Interactive Landing Page\n\n| Purpose | Recommended Sections |\n|---------|---------------------|\n| **Intro** | Company Fit → Solution Overview → Key Use Cases → Why Us → Next Steps |\n| **Discovery follow-up** | Their Priorities → How We Help → Relevant Examples → ROI Framework → Next Steps |\n| **Technical deep-dive** | Architecture → Security & Compliance → Integration → Performance → Support |\n| **Exec alignment** | Strategic Fit → Business Impact → ROI Calculator → Risk Mitigation → Partnership |\n| **POC proposal** | Scope → Success Criteria → Timeline → Team → Investment → Next Steps |\n| **Deal close** | Value Summary → Pricing → Implementation Plan → Terms → Sign-off |\n\n**Audience adjustments:**\n- **Executive**: Lead with business impact, ROI, strategic alignment\n- **Technical**: Lead with architecture, security, integration depth\n- **Operations**: Lead with workflow impact, change management, support\n- **Mixed**: Balance strategic + tactical; use tabs to separate depth levels\n\n---\n\n### Deck-Style\n\nSame sections as landing page, formatted as linear slides:\n\n```\n1. Title slide (Prospect + Seller logos, partnership framing)\n2. Agenda\n3-N. One section per slide (or 2-3 slides for dense sections)\nN+1. Summary / Key takeaways\nN+2. Next steps / CTA\nN+3. Appendix (optional — detailed specs, pricing, etc.)\n```\n\n**Slide principles:**\n- One key message per slide\n- Visual > text-heavy\n- Use prospect's metrics and language\n- Include speaker notes\n\n---\n\n### One-Pager\n\nCondense to single-scroll format:\n\n```\n┌─────────────────────────────────────┐\n│ HERO: \"[Prospect Goal] with [Product]\" │\n├─────────────────────────────────────┤\n│ KEY POINT 1 │ KEY POINT 2 │ KEY POINT 3 │\n│ [Icon + 2-3 │ [Icon + 2-3 │ [Icon + 2-3 │\n│ sentences] │ sentences] │ sentences] │\n├─────────────────────────────────────┤\n│ PROOF POINT: [Metric, quote, or case study] │\n├─────────────────────────────────────┤\n│ CTA: [Clear next action] │ [Contact info] │\n└─────────────────────────────────────┘\n```\n\n---\n\n### Workflow / Architecture Demo\n\n**Structure based on complexity:**\n\n| Complexity | Components | Structure |\n|------------|------------|-----------|\n| **Simple** | 3-5 | Single-view diagram with step annotations |\n| **Medium** | 5-10 | Zoomable canvas with step-by-step walkthrough |\n| **Complex** | 10+ | Multi-layer view (overview → detailed) with guided tour |\n\n**Standard elements:**\n\n1. **Title bar**: `[Scenario Name] — Powered by [Seller Product]`\n2. **Component nodes**: Visual boxes/icons for each system\n3. **Flow arrows**: Animated connections showing data movement\n4. **Step panel**: Sidebar explaining current step in plain language\n5. **Controls**: Play / Pause / Step Forward / Step Back / Reset\n6. **Annotations**: Callouts for key decision points and value-adds\n7. **Data preview**: Sample payloads or transformations at each step\n\n---\n\n## Phase 3: Content Generation\n\n### General Principles\n\nAll content should:\n- Reference **specific pain points** from user input or transcripts\n- Use **prospect's language** — their terminology, their stated priorities\n- Map **seller's product** → **prospect's needs** explicitly\n- Include **proof points** where available (case studies, metrics, quotes)\n- Feel **tailored, not templated**\n\n---\n\n### Section Templates\n\n#### Hero / Intro\n```\nHeadline: \"[Prospect's Goal] with [Seller's Product]\"\nSubhead: Tie to their stated priority or top industry challenge\nMetrics: 3-4 key facts about the prospect (shows we did homework)\n```\n\n#### Their Priorities (if discovery follow-up)\n```\nReference specific pain points from conversation:\n- Use their exact words where possible\n- Show we listened and understood\n- Connect each to how we help\n```\n\n#### Solution Mapping\n```\nFor each pain point:\n├── The challenge (in their words)\n├── How [Product] addresses it\n├── Proof point or example\n└── Outcome / benefit\n```\n\n#### Use Cases / Demos\n```\n3-5 relevant use cases:\n├── Visual mockup or interactive demo\n├── Business impact (quantified if possible)\n├── \"How it works\" — 3-4 step summary\n└── Relevant to their industry/role\n```\n\n#### ROI / Business Case\n```\nInteractive calculator with:\n├── Inputs relevant to their business (from research)\n│ ├── Number of users/developers\n│ ├── Current costs or time spent\n│ └── Expected improvement %\n├── Outputs:\n│ ├── Annual value / savings\n│ ├── Cost of solution\n│ ├── Net ROI\n│ └── Payback period\n└── Assumptions clearly stated (editable)\n```\n\n#### Why Us / Differentiators\n```\n├── Differentiators vs. alternatives they might consider\n├── Trust, security, compliance positioning\n├── Support and partnership model\n└── Customer proof points (logos, quotes, case studies)\n```\n\n#### Next Steps / CTA\n```\n├── Clear action aligned to Purpose (c)\n├── Specific next step (not vague \"let's chat\")\n├── Contact information\n├── Suggested timeline\n└── What happens after they take action\n```\n\n---\n\n### Workflow Demo Content\n\n#### Component Definitions\n\nFor each system, define:\n\n```yaml\ncomponent:\n id: \"snowflake\"\n label: \"Snowflake Data Warehouse\"\n type: \"database\" # database | api | ai | middleware | human | document | output\n icon: \"database\"\n description: \"Financial performance data\"\n brand_color: \"#29B5E8\"\n```\n\n**Component types:**\n- `human` — Person initiating or receiving\n- `document` — PDFs, contracts, files\n- `ai` — AI/ML models, agents\n- `database` — Data stores, warehouses\n- `api` — APIs, services\n- `middleware` — Integration platforms, MCP servers\n- `output` — Dashboards, reports, notifications\n\n#### Flow Steps\n\nFor each step, define:\n\n```yaml\nstep:\n number: 1\n from: \"human\"\n to: \"claude\"\n action: \"Initiates performance review\"\n description: \"Sarah, a Brand Analyst at [Prospect], kicks off the quarterly review...\"\n data_example: \"Review request: Nike brand, Q4 2025\"\n duration: \"~1 second\"\n value_note: \"No manual data gathering required\"\n```\n\n#### Scenario Narrative\n\nWrite a clear, specific walkthrough:\n\n```\nStep 1: Human Trigger\n\"Sarah, a Brand Performance Analyst at Centric Brands, needs to review\nQ4 performance for the Nike license agreement. She opens the review\ndashboard and clicks 'Start Review'...\"\n\nStep 2: Contract Analysis\n\"Claude retrieves the Nike contract PDF and extracts the performance\nobligations: minimum $50M revenue, 12% margin requirement, quarterly\nreporting deadline...\"\n\nStep 3: Data Query\n\"Claude formulates a query and sends it to Workato DataGenie:\n'Get Q4 2025 revenue and gross margin for Nike brand from Snowflake'...\"\n\nStep 4: Results & Synthesis\n\"Snowflake returns the data. Claude compares actuals vs. obligations:\nRevenue $52.3M ✓ (exceeded by $2.3M)\nMargin 11.2% ⚠️ (0.8% below threshold)...\"\n\nStep 5: Insight Delivery\n\"Claude synthesizes findings into an executive summary with\nrecommendations: 'Review promotional spend allocation to improve\nmargin performance...'\"\n```\n\n---\n\n## Phase 4: Visual Design\n\n### Color System\n\n```css\n:root {\n /* === Prospect Brand (Primary) === */\n --brand-primary: #[extracted from research];\n --brand-secondary: #[extracted];\n --brand-primary-rgb: [r, g, b]; /* For rgba() usage */\n\n /* === Dark Theme Base === */\n --bg-primary: #0a0d14;\n --bg-elevated: #0f131c;\n --bg-surface: #161b28;\n --bg-hover: #1e2536;\n\n /* === Text === */\n --text-primary: #ffffff;\n --text-secondary: rgba(255, 255, 255, 0.7);\n --text-muted: rgba(255, 255, 255, 0.5);\n\n /* === Accent === */\n --accent: var(--brand-primary);\n --accent-hover: var(--brand-secondary);\n --accent-glow: rgba(var(--brand-primary-rgb), 0.3);\n\n /* === Status === */\n --success: #10b981;\n --warning: #f59e0b;\n --error: #ef4444;\n}\n```\n\n### Typography\n\n```css\n/* Primary: Clean, professional sans-serif */\nfont-family: 'Inter', -apple-system, BlinkMacSystemFont, sans-serif;\n\n/* Headings */\nh1: 2.5rem, font-weight: 700\nh2: 1.75rem, font-weight: 600\nh3: 1.25rem, font-weight: 600\n\n/* Body */\nbody: 1rem, font-weight: 400, line-height: 1.6\n\n/* Captions/Labels */\nsmall: 0.875rem, font-weight: 500\n```\n\n### Visual Elements\n\n**Cards:**\n- Background: `var(--bg-surface)`\n- Border: 1px solid rgba(255,255,255,0.1)\n- Border-radius: 12px\n- Box-shadow: subtle, layered\n- Hover: slight elevation, border glow\n\n**Buttons:**\n- Primary: `var(--accent)` background, white text\n- Secondary: transparent, accent border\n- Hover: brightness increase, subtle scale\n\n**Animations:**\n- Transitions: 200-300ms ease\n- Tab switches: fade + slide\n- Hover states: smooth, not jarring\n- Loading: subtle pulse or skeleton\n\n### Workflow Demo Specific\n\n**Component Nodes:**\n```css\n.node {\n background: var(--bg-surface);\n border: 2px solid var(--brand-primary);\n border-radius: 12px;\n padding: 16px;\n min-width: 140px;\n}\n\n.node.active {\n box-shadow: 0 0 20px var(--accent-glow);\n border-color: var(--accent);\n}\n\n.node.human {\n border-color: #f59e0b; /* Warm color for humans */\n}\n\n.node.ai {\n background: linear-gradient(135deg, var(--bg-surface), var(--bg-elevated));\n border-color: var(--accent);\n}\n```\n\n**Flow Arrows:**\n```css\n.arrow {\n stroke: var(--text-muted);\n stroke-width: 2;\n fill: none;\n marker-end: url(#arrowhead);\n}\n\n.arrow.active {\n stroke: var(--accent);\n stroke-dasharray: 8 4;\n animation: flowDash 1s linear infinite;\n}\n```\n\n**Canvas:**\n```css\n.canvas {\n background:\n radial-gradient(circle at center, var(--bg-elevated) 0%, var(--bg-primary) 100%),\n url(\"data:image/svg+xml,...\"); /* Subtle grid pattern */\n overflow: auto;\n}\n```\n\n---\n\n## Phase 5: Clarifying Questions (REQUIRED)\n\n**Before building any asset, always ask clarifying questions.** This ensures alignment and prevents wasted effort.\n\n### Step 5.1: Summarize Understanding\n\nFirst, show the user what you understood:\n\n```\n\"Here's what I'm planning to build:\n\n**Asset**: [Format] for [Prospect Company]\n**Audience**: [Audience type] — specifically [roles if known]\n**Goal**: [Purpose] → driving toward [desired action]\n**Key themes**: [2-3 main points to emphasize]\n\n[For workflow demos, also show:]\n**Components**: [List of systems]\n**Flow**: [Step 1] → [Step 2] → [Step 3] → ...\n```\n\n### Step 5.2: Ask Standard Questions (ALL formats)\n\n| Question | Why |\n|----------|-----|\n| \"Does this match your vision?\" | Confirm understanding |\n| \"What's the ONE thing this must nail to succeed?\" | Focus on priority |\n| \"Tone preference? (Bold & confident / Consultative / Technical & precise)\" | Style alignment |\n| \"Focused and concise, or comprehensive?\" | Scope calibration |\n\n### Step 5.3: Ask Format-Specific Questions\n\n#### Interactive Landing Page:\n- \"Which sections matter most for this audience?\"\n- \"Any specific demos or use cases to highlight?\"\n- \"Should I include an ROI calculator?\"\n- \"Any competitor positioning to address?\"\n\n#### Deck-Style:\n- \"How long is the presentation? (helps with slide count)\"\n- \"Presenting live, or a leave-behind?\"\n- \"Any specific flow or narrative arc in mind?\"\n\n#### One-Pager:\n- \"What's the single most important message?\"\n- \"Any specific proof point or stat to feature?\"\n- \"Will this be printed or digital?\"\n\n#### Workflow / Architecture Demo:\n- \"Let me confirm the components: [list]. Anything missing?\"\n- \"Here's the flow I understood: [steps]. Correct?\"\n- \"Should the demo show realistic sample data, or keep it abstract?\"\n- \"Any integration details to highlight or downplay?\"\n- \"Should viewers be able to click through steps, or auto-play?\"\n\n### Step 5.4: Confirm and Proceed\n\nAfter user responds:\n\n```\n\"Got it. I have what I need. Building your [format] now...\"\n```\n\nOr, if still unclear:\n\n```\n\"One more quick question: [specific follow-up]\"\n```\n\n**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.\"\n\n---\n\n## Phase 6: Build & Deliver\n\n### Build the Asset\n\nFollowing all specifications above:\n1. Generate structure based on Phase 2\n2. Create content based on Phase 3\n3. Apply visual design based on Phase 4\n4. Ensure all interactive elements work\n5. Test responsiveness (if applicable)\n\n### Output Format\n\n**All formats**: Self-contained HTML file\n- All CSS inline or in `