Create An Asset
This skill generates custom sales assets tailored to specific prospects and goals
Install
npx promptshop add create-an-assetDetails
What This Skill Does
This skill generates custom sales assets tailored to specific prospects and goals. It supports various formats including landing pages, presentation decks, and executive one-pagers. The skill gathers context about the prospect, audience, purpose, and desired format to create a polished, branded asset.
When to Use
- Creating a landing page for a specific prospect.
- Generating a presentation deck for a sales pitch.
- Building an executive one-pager for a key decision-maker.
- Mocking up a workflow demo for a potential customer.
- Tailoring assets to a specific audience.
- Creating customer-facing deliverables.
Key Features
- Detects seller context from email domain.
- Gathers information about the prospect and audience.
- Supports multiple asset formats.
- Researches and structures content.
- Builds a polished, branded asset.
- Customizes assets based on the purpose and desired action.
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: Extract domain from user's email Search: "[domain]" company products services site:linkedin. com OR site:crunchbase. com Determine seller context:
| Scenario | Action |
|---|---|
| Single-product company | Auto-populate seller context |
| Multi-product company | Ask: "Which product or solution is this asset for?" |
| Consultant/agency/generic domain | Ask: "What company or product are you representing?" |
| Unknown/startup | Ask: "Briefly, what are you selling?" |
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]" - "[Differentiator 2]" pricing_model: "[If publicly known]"
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:
| Field | Prompt | Required |
|---|---|---|
| Company | "Which company is this asset for?" | ✓ Yes |
| Key contacts | "Who are the key contacts? (names, roles)" | No |
| Deal stage | "What stage is this deal?" | ✓ Yes |
| Pain points | "What pain points or priorities have they shared?" | No |
| Past materials | "Upload any conversation materials (transcripts, emails, notes, call recordings)" | No |
Deal stage options: Intro / First meeting Discovery Evaluation / Technical review POC / Pilot Negotiation Close
Step 0.3: Collect Audience Context (b)
Ask the user:
| Field | Prompt | Required |
|---|---|---|
| Audience type | "Who's viewing this?" | ✓ Yes |
| Specific roles | "Any specific titles to tailor for? (e.g., CTO, VP Engineering, CFO)" | No |
| Primary concern | "What do they care most about?" | ✓ Yes |
| Objections | "Any concerns or objections to address?" | No |
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:
| Field | Prompt | Required |
|---|---|---|
| Goal | "What's the goal of this asset?" | ✓ Yes |
| Desired action | "What should the viewer do after seeing this?" | ✓ Yes |
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?"
| Format | Description | Best For |
|---|---|---|
| Interactive landing page | Multi-tab page with demos, metrics, calculators | Exec alignment, intros, value prop |
| Deck-style | Linear slides, presentation-ready | Formal meetings, large audiences |
| One-pager | Single-scroll executive summary | Leave-behinds, quick summaries |
| Workflow / Architecture demo | Interactive diagram with animated flow | Technical deep-dives, POC demos, integrations |
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:
| If Missing... | Ask... |
|---|---|
| Components unclear | "What systems or components are involved? (databases, APIs, AI, middleware, etc.)" |
| Flow unclear | "Walk me through the step-by-step flow" |
| Human touchpoints unclear | "Where does a human interact in this workflow?" |
| Scenario vague | "What's a concrete example scenario to demo?" |
| Integration specifics | "Any specific tools or platforms to highlight?" |
Phase 1: Research (Adaptive)
Assess Context Richness
| Level | Indicators | Research Depth |
|---|---|---|
| Rich | Transcripts uploaded, detailed pain points, clear requirements | Light — fill gaps only |
| Moderate | Some context, no transcripts | Medium — company + industry |
| Sparse | Just company name | Deep — full research pass |
Always Research:
Prospect basics
- Search: "[Company]" annual report investor presentation 2025 2026
- Search: "[Company]" CEO strategy priorities 2025 2026
- Extract: Revenue, employees, key metrics, strategic priorities
Leadership
- Search: "[Company]" CEO CTO CIO 2025
- Extract: Names, titles, recent quotes on strategy/technology
Brand colors
- Search: "[Company]" brand guidelines
- Or extract from company website
- Store: Primary color, secondary color, accent
If Moderate/Sparse Context, Also Research:
Industry context
- Search: "[Industry]" trends challenges 2025 2026
- Extract: Common pain points, market dynamics
Technology landscape
- Search: "[Company]" technology stack tools platforms
- Extract: Current solutions, potential integration points
Competitive context
- Search: "[Company]" vs [seller's competitors]
- Extract: Current solutions, switching signals
If Transcripts/Materials Uploaded:
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
| Purpose | Recommended Sections |
|---|---|
| Intro | Company Fit → Solution Overview → Key Use Cases → Why Us → Next Steps |
| Discovery follow-up | Their Priorities → How We Help → Relevant Examples → ROI Framework → Next Steps |
| Technical deep-dive | Architecture → Security & Compliance → Integration → Performance → Support |
| Exec alignment | Strategic Fit → Business Im |