create-an-asset

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

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

在以下场景调用此Skill:
  • 用户输入
    /create-an-asset
    /create-an-asset [CompanyName]
  • 用户提出“创建资产”“制作演示”“生成着陆页”“制作工作流原型”等需求
  • 用户需要为销售对话准备面向客户的交付物

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.

此Skill通过收集以下维度的信息来创建专业销售资产:
  • (a) 潜在客户 — 公司、联系人、沟通记录、痛点
  • (b) 受众群体 — 查看对象、核心关注点
  • (c) 创建目标 — 资产用途、期望的后续行动
  • (d) 资产格式 — 着陆页、演示文稿、单页资料或工作流演示
随后,该Skill会开展调研、搭建结构并制作出精美的、带有品牌标识的资产,随时可与客户分享。

Phase 0: Context Detection & Input Collection

阶段0:上下文检测与信息收集

Step 0.1: Detect Seller Context

步骤0.1:识别销售方上下文

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:
ScenarioAction
Single-product companyAuto-populate seller context
Multi-product companyAsk: "Which product or solution is this asset for?"
Consultant/agency/generic domainAsk: "What company or product are you representing?"
Unknown/startupAsk: "Briefly, what are you selling?"
Store seller context:
yaml
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]?"

从用户的邮箱域名识别其所属公司。
操作步骤:
  1. 从用户邮箱提取域名
  2. 搜索:
    "[domain]" company products services site:linkedin.com OR site:crunchbase.com
  3. 确定销售方上下文:
场景操作
单一产品公司自动填充销售方上下文
多产品公司询问:“此资产是为哪款产品或解决方案制作的?”
顾问/代理机构/通用域名询问:“您代表哪家公司或产品?”
未知/初创公司询问:“简单说明一下您销售的产品是什么?”
存储销售方上下文:
yaml
seller:
  company: "[公司名称]"
  product: "[产品/服务]"
  value_props:
    - "[核心价值主张1]"
    - "[核心价值主张2]"
    - "[核心价值主张3]"
  differentiators:
    - "[差异化优势1]"
    - "[差异化优势2]"
  pricing_model: "[若公开可查]"
持久化到知识库以便后续会话使用。后续调用时,确认:“我已保留您上次的销售方上下文 — 您仍在[公司名称]销售[产品]吗?”

Step 0.2: Collect Prospect Context (a)

步骤0.2:收集潜在客户上下文 (a)

Ask the user:
FieldPromptRequired
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)

步骤0.3:收集受众群体上下文 (b)

Ask the user:
FieldPromptRequired
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

询问用户:
字段提示语是否必填
受众类型“谁会查看此资产?”✓ 是
具体职位“是否需要针对特定职位定制?(例如:CTO、工程副总裁、CFO)”
核心关注点“他们最关心什么?”✓ 是
异议“是否有需要解决的顾虑或异议?”
受众类型选项:
  • 高管(C-suite、副总裁)
  • 技术人员(架构师、工程师、开发人员)
  • 运营人员(运维、IT、采购)
  • 混合 / 跨职能
核心关注点选项:
  • 投资回报率 / 业务影响
  • 技术深度 / 架构
  • 战略对齐
  • 风险缓解 / 安全
  • 实施 / 时间线

Step 0.4: Collect Purpose Context (c)

步骤0.4:收集创建目标上下文 (c)

Ask the user:
FieldPromptRequired
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)

步骤0.5:选择格式 (d)

Ask the user: "What format works best for this?"
FormatDescriptionBest For
Interactive landing pageMulti-tab page with demos, metrics, calculatorsExec alignment, intros, value prop
Deck-styleLinear slides, presentation-readyFormal meetings, large audiences
One-pagerSingle-scroll executive summaryLeave-behinds, quick summaries
Workflow / Architecture demoInteractive diagram with animated flowTechnical deep-dives, POC demos, integrations

询问用户:“哪种格式最适合此需求?”
格式描述最佳适用场景
交互式着陆页多标签页面,包含演示、指标、计算器高管对齐、介绍、价值主张传递
演示文稿格式线性幻灯片,可直接用于演示正式会议、大规模受众
单页资料单屏滚动的高管摘要留档资料、快速概述
工作流 / 架构演示带有动画流程的交互式图表技术深度讲解、概念验证演示、集成展示

Step 0.6: Format-Specific Inputs

步骤0.6:格式专属输入

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?"

首先,解析用户描述,查找以下信息:
  • 提及的系统和组件
  • 描述的数据流
  • 人工交互点
  • 示例场景
然后,询问缺失的信息:
若缺失...询问...
组件不明确“涉及哪些系统或组件?(数据库、API、AI、中间件等)”
流程不明确“请逐步讲解整个流程”
人工交互点不明确“在工作流的哪个环节有人工交互?”
场景模糊“请提供一个具体的演示场景示例”
集成细节不明确“是否有需要重点展示的特定工具或平台?”

Phase 1: Research (Adaptive)

阶段1:调研(自适应)

Assess Context Richness

评估上下文丰富度

LevelIndicatorsResearch Depth
RichTranscripts uploaded, detailed pain points, clear requirementsLight — fill gaps only
ModerateSome context, no transcriptsMedium — company + industry
SparseJust company nameDeep — full research pass
等级指标调研深度
丰富已上传对话记录、详细痛点、明确需求轻度 — 仅补充缺失信息
中等有部分上下文,无对话记录中度 — 公司 + 行业调研
稀疏仅提供公司名称深度 — 全面调研

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
  1. 潜在客户基础信息
    • 搜索:
      "[Company]" annual report investor presentation 2025 2026
    • 搜索:
      "[Company]" CEO strategy priorities 2025 2026
    • 提取:收入、员工数、关键指标、战略优先事项
  2. 领导层信息
    • 搜索:
      "[Company]" CEO CTO CIO 2025
    • 提取:姓名、职位、近期关于战略/技术的言论
  3. 品牌色彩
    • 搜索:
      "[Company]" brand guidelines
    • 或从公司官网提取
    • 存储:主色、辅助色、强调色

If Moderate/Sparse Context, Also Research:

若上下文为中等/稀疏,额外调研:

  1. Industry context
    • Search:
      "[Industry]" trends challenges 2025 2026
    • Extract: Common pain points, market dynamics
  2. Technology landscape
    • Search:
      "[Company]" technology stack tools platforms
    • Extract: Current solutions, potential integration points
  3. Competitive context
    • Search:
      "[Company]" vs [seller's competitors]
    • Extract: Current solutions, switching signals
  1. 行业上下文
    • 搜索:
      "[Industry]" trends challenges 2025 2026
    • 提取:常见痛点、市场动态
  2. 技术格局
    • 搜索:
      "[Company]" technology stack tools platforms
    • 提取:当前解决方案、潜在集成点
  3. 竞争上下文
    • 搜索:
      "[Company]" vs [seller's competitors]
    • 提取:当前解决方案、转换信号

If Transcripts/Materials Uploaded:

若已上传对话记录/资料:

  1. 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

  1. 对话分析
    • 提取:明确的痛点、决策标准、异议、时间线
    • 识别:可引用的关键语句(使用其原话)
    • 记录:特定术语、缩写、内部项目名称

Phase 2: Structure Decision

阶段2:结构决策

Interactive Landing Page

交互式着陆页

PurposeRecommended Sections
IntroCompany Fit → Solution Overview → Key Use Cases → Why Us → Next Steps
Discovery follow-upTheir Priorities → How We Help → Relevant Examples → ROI Framework → Next Steps
Technical deep-diveArchitecture → Security & Compliance → Integration → Performance → Support
Exec alignmentStrategic Fit → Business Impact → ROI Calculator → Risk Mitigation → Partnership
POC proposalScope → Success Criteria → Timeline → Team → Investment → Next Steps
Deal closeValue Summary → Pricing → Implementation Plan → Terms → Sign-off
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:
1. Title slide (Prospect + Seller logos, partnership framing)
2. Agenda
3-N. One section per slide (or 2-3 slides for dense sections)
N+1. Summary / Key takeaways
N+2. Next steps / CTA
N+3. Appendix (optional — detailed specs, pricing, etc.)
Slide principles:
  • One key message per slide
  • Visual > text-heavy
  • Use prospect's metrics and language
  • Include speaker notes

章节与着陆页相同,格式为线性幻灯片:
1. 标题页(潜在客户 + 销售方logo,合作定位)
2. 议程
3-N. 每章节对应1张幻灯片(内容密集的章节可占2-3张)
N+1. 总结 / 核心要点
N+2. 下一步行动 / 号召性用语
N+3. 附录(可选 — 详细规格、定价等)
幻灯片原则:
  • 每张幻灯片仅传递一个核心信息
  • 优先使用视觉元素,避免文字堆砌
  • 使用潜在客户的指标和语言
  • 包含演讲者备注

One-Pager

单页资料

Condense to single-scroll format:
┌─────────────────────────────────────┐
│ HERO: "[Prospect Goal] with [Product]" │
├─────────────────────────────────────┤
│ KEY POINT 1     │ KEY POINT 2     │ KEY POINT 3     │
│ [Icon + 2-3     │ [Icon + 2-3     │ [Icon + 2-3     │
│  sentences]     │  sentences]     │  sentences]     │
├─────────────────────────────────────┤
│ PROOF POINT: [Metric, quote, or case study] │
├─────────────────────────────────────┤
│ CTA: [Clear next action] │ [Contact info] │
└─────────────────────────────────────┘

浓缩为单屏滚动格式:
┌─────────────────────────────────────┐
│ 标题区:"[潜在客户目标] 借助 [产品]" │
├─────────────────────────────────────┤
│ 核心要点1     │ 核心要点2     │ 核心要点3     │
│ [图标 + 2-3     │ [图标 + 2-3     │ [图标 + 2-3     │
│  句话]     │  句话]     │  句话]     │
├─────────────────────────────────────┤
│ 证明点:[指标、引用或案例研究] │
├─────────────────────────────────────┤
│ 号召性用语:[明确的下一步行动] │ [联系方式] │
└─────────────────────────────────────┘

Workflow / Architecture Demo

工作流 / 架构演示

Structure based on complexity:
ComplexityComponentsStructure
Simple3-5Single-view diagram with step annotations
Medium5-10Zoomable canvas with step-by-step walkthrough
Complex10+Multi-layer view (overview → detailed) with guided tour
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

根据复杂度选择结构:
复杂度组件数量结构
简单3-5个带步骤注释的单视图图表
中等5-10个可缩放画布 + 逐步讲解
复杂10个以上多层视图(概览 → 详情)+ 引导式游览
标准元素:
  1. 标题栏
    [场景名称] — 由 [销售方产品] 提供支持
  2. 组件节点:每个系统对应的可视化方框/图标
  3. 流程箭头:显示数据流动的动画连接
  4. 步骤面板:侧边栏用通俗语言解释当前步骤
  5. 控制按钮:播放 / 暂停 / 前进 / 后退 / 重置
  6. 注释:关键决策点和增值点的标注
  7. 数据预览:每个步骤的示例负载或转换结果

Phase 3: Content Generation

阶段3:内容生成

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 productprospect's needs explicitly
  • Include proof points where available (case studies, metrics, quotes)
  • Feel tailored, not templated

所有内容应:
  • 引用用户输入或对话记录中的具体痛点
  • 使用潜在客户的语言 — 他们的术语、明确的优先事项
  • 明确将销售方产品与潜在客户需求对应起来
  • 尽可能包含证明点(案例研究、指标、引用)
  • 给人定制化而非模板化的感觉

Section Templates

章节模板

Hero / Intro

标题区 / 介绍

Headline: "[Prospect's Goal] with [Seller's Product]"
Subhead: Tie to their stated priority or top industry challenge
Metrics: 3-4 key facts about the prospect (shows we did homework)
标题:"[潜在客户目标] 借助 [销售方产品]"
副标题:关联其明确的优先事项或行业顶级挑战
指标:3-4个关于潜在客户的关键事实(展示我们做了功课)

Their Priorities (if discovery follow-up)

他们的优先事项(若为需求探索跟进)

Reference specific pain points from conversation:
- Use their exact words where possible
- Show we listened and understood
- Connect each to how we help
引用对话中的具体痛点:
- 尽可能使用他们的原话
- 展示我们认真倾听并理解了需求
- 将每个痛点与我们的帮助方式关联起来

Solution Mapping

解决方案映射

For each pain point:
├── The challenge (in their words)
├── How [Product] addresses it
├── Proof point or example
└── Outcome / benefit
针对每个痛点:
├── 挑战(用他们的语言表述)
├── [产品] 如何解决该挑战
├── 证明点或示例
└── 成果 / 收益

Use Cases / Demos

用例 / 演示

3-5 relevant use cases:
├── Visual mockup or interactive demo
├── Business impact (quantified if possible)
├── "How it works" — 3-4 step summary
└── Relevant to their industry/role
3-5个相关用例:
├── 可视化原型或交互式演示
├── 业务影响(尽可能量化)
├── “工作原理” — 3-4步总结
└── 与其行业/职位相关

ROI / Business Case

投资回报率 / 业务案例

Interactive calculator with:
├── Inputs relevant to their business (from research)
│   ├── Number of users/developers
│   ├── Current costs or time spent
│   └── Expected improvement %
├── Outputs:
│   ├── Annual value / savings
│   ├── Cost of solution
│   ├── Net ROI
│   └── Payback period
└── Assumptions clearly stated (editable)
交互式计算器包含:
├── 与其业务相关的输入项(来自调研)
│   ├── 用户/开发人员数量
│   ├── 当前成本或耗时
│   └── 预期改进百分比
├── 输出项:
│   ├── 年度价值 / 节省金额
│   ├── 解决方案成本
│   ├── 净投资回报率
│   └── 回收期
└── 明确说明假设条件(可编辑)

Why Us / Differentiators

选择我们的理由 / 差异化优势

├── Differentiators vs. alternatives they might consider
├── Trust, security, compliance positioning
├── Support and partnership model
└── Customer proof points (logos, quotes, case studies)
├── 与他们可能考虑的替代方案相比的差异化优势
├── 信任、安全、合规定位
├── 支持与合作模式
└── 客户证明点(logo、引用、案例研究)

Next Steps / CTA

下一步行动 / 号召性用语

├── Clear action aligned to Purpose (c)
├── Specific next step (not vague "let's chat")
├── Contact information
├── Suggested timeline
└── What happens after they take action

├── 与创建目标(c)对齐的明确行动
├── 具体的下一步(而非模糊的“聊聊”)
├── 联系方式
├── 建议时间线
└── 采取行动后的后续安排

Workflow Demo Content

工作流演示内容

Component Definitions

组件定义

For each system, define:
yaml
component:
  id: "snowflake"
  label: "Snowflake Data Warehouse"
  type: "database"  # database | api | ai | middleware | human | document | output
  icon: "database"
  description: "Financial performance data"
  brand_color: "#29B5E8"
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
针对每个系统,定义:
yaml
component:
  id: "snowflake"
  label: "Snowflake 数据仓库"
  type: "database"  # database | api | ai | middleware | human | document | output
  icon: "database"
  description: "财务绩效数据"
  brand_color: "#29B5E8"
组件类型:
  • human
    — 发起或接收的人员
  • document
    — PDF、合同、文件
  • ai
    — AI/ML模型、Agent
  • database
    — 数据存储、数据仓库
  • api
    — API、服务
  • middleware
    — 集成平台、MCP服务器
  • output
    — 仪表板、报告、通知

Flow Steps

流程步骤

For each step, define:
yaml
step:
  number: 1
  from: "human"
  to: "claude"
  action: "Initiates performance review"
  description: "Sarah, a Brand Analyst at [Prospect], kicks off the quarterly review..."
  data_example: "Review request: Nike brand, Q4 2025"
  duration: "~1 second"
  value_note: "No manual data gathering required"
针对每个步骤,定义:
yaml
step:
  number: 1
  from: "human"
  to: "claude"
  action: "启动绩效评估"
  description: "Sarah是[潜在客户]的品牌分析师,她启动了季度评估..."
  data_example: "评估请求:Nike品牌,2025年第四季度"
  duration: "~1秒"
  value_note: "无需手动收集数据"

Scenario Narrative

场景叙事

Write a clear, specific walkthrough:
Step 1: Human Trigger
"Sarah, a Brand Performance Analyst at Centric Brands, needs to review
Q4 performance for the Nike license agreement. She opens the review
dashboard and clicks 'Start Review'..."

Step 2: Contract Analysis
"Claude retrieves the Nike contract PDF and extracts the performance
obligations: minimum $50M revenue, 12% margin requirement, quarterly
reporting deadline..."

Step 3: Data Query
"Claude formulates a query and sends it to Workato DataGenie:
'Get Q4 2025 revenue and gross margin for Nike brand from Snowflake'..."

Step 4: Results & Synthesis
"Snowflake returns the data. Claude compares actuals vs. obligations:
Revenue $52.3M ✓ (exceeded by $2.3M)
Margin 11.2% ⚠️ (0.8% below threshold)..."

Step 5: Insight Delivery
"Claude synthesizes findings into an executive summary with
recommendations: 'Review promotional spend allocation to improve
margin performance...'"

撰写清晰、具体的讲解内容:
步骤1:人工触发
"Sarah是Centric Brands的品牌绩效分析师,她需要评估Nike授权协议的2025年第四季度绩效。她打开评估仪表板并点击‘开始评估’..."

步骤2:合同分析
"Claude获取Nike合同PDF并提取绩效要求:最低5000万美元收入、12%利润率要求、季度报告截止日期..."

步骤3:数据查询
"Claude生成查询语句并发送给Workato DataGenie:‘从Snowflake获取Nike品牌2025年第四季度的收入和毛利率’..."

步骤4:结果与合成
"Snowflake返回数据。Claude将实际数据与要求对比:
收入5230万美元 ✓(超出230万美元)
毛利率11.2% ⚠️(低于阈值0.8%)..."

步骤5:洞察交付
"Claude将发现整理为高管摘要并给出建议:‘审查促销支出分配以提高毛利率表现...’"

Phase 4: Visual Design

阶段4:视觉设计

Color System

色彩系统

css
:root {
    /* === Prospect Brand (Primary) === */
    --brand-primary: #[extracted from research];
    --brand-secondary: #[extracted];
    --brand-primary-rgb: [r, g, b]; /* For rgba() usage */

    /* === Dark Theme Base === */
    --bg-primary: #0a0d14;
    --bg-elevated: #0f131c;
    --bg-surface: #161b28;
    --bg-hover: #1e2536;

    /* === Text === */
    --text-primary: #ffffff;
    --text-secondary: rgba(255, 255, 255, 0.7);
    --text-muted: rgba(255, 255, 255, 0.5);

    /* === Accent === */
    --accent: var(--brand-primary);
    --accent-hover: var(--brand-secondary);
    --accent-glow: rgba(var(--brand-primary-rgb), 0.3);

    /* === Status === */
    --success: #10b981;
    --warning: #f59e0b;
    --error: #ef4444;
}
css
:root {
    /* === 潜在客户品牌(主色)=== */
    --brand-primary: #[从调研中提取];
    --brand-secondary: #[从调研中提取];
    --brand-primary-rgb: [r, g, b]; /* 用于rgba() */

    /* === 深色主题基础 === */
    --bg-primary: #0a0d14;
    --bg-elevated: #0f131c;
    --bg-surface: #161b28;
    --bg-hover: #1e2536;

    /* === 文本 === */
    --text-primary: #ffffff;
    --text-secondary: rgba(255, 255, 255, 0.7);
    --text-muted: rgba(255, 255, 255, 0.5);

    /* === 强调色 === */
    --accent: var(--brand-primary);
    --accent-hover: var(--brand-secondary);
    --accent-glow: rgba(var(--brand-primary-rgb), 0.3);

    /* === 状态色 === */
    --success: #10b981;
    --warning: #f59e0b;
    --error: #ef4444;
}

Typography

排版

css
/* Primary: Clean, professional sans-serif */
font-family: 'Inter', -apple-system, BlinkMacSystemFont, sans-serif;

/* Headings */
h1: 2.5rem, font-weight: 700
h2: 1.75rem, font-weight: 600
h3: 1.25rem, font-weight: 600

/* Body */
body: 1rem, font-weight: 400, line-height: 1.6

/* Captions/Labels */
small: 0.875rem, font-weight: 500
css
/* 主字体:简洁、专业的无衬线字体 */
font-family: 'Inter', -apple-system, BlinkMacSystemFont, sans-serif;

/* 标题 */
h1: 2.5rem, font-weight: 700
h2: 1.75rem, font-weight: 600
h3: 1.25rem, font-weight: 600

/* 正文 */
body: 1rem, font-weight: 400, line-height: 1.6

/* 说明文字/标签 */
small: 0.875rem, font-weight: 500

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
卡片:
  • 背景:
    var(--bg-surface)
  • 边框:1px solid rgba(255,255,255,0.1)
  • 圆角:12px
  • 阴影:柔和的分层阴影
  • 悬停状态:轻微抬升效果、边框发光
按钮:
  • 主按钮:
    var(--accent)
    背景,白色文字
  • 次按钮:透明背景,强调色边框
  • 悬停状态:亮度提升、轻微缩放
动画:
  • 过渡效果:200-300ms 缓动
  • 标签页切换:淡入 + 滑动
  • 悬停状态:平滑过渡,不突兀
  • 加载状态:轻微脉冲或骨架屏

Workflow Demo Specific

工作流演示专属样式

Component Nodes:
css
.node {
    background: var(--bg-surface);
    border: 2px solid var(--brand-primary);
    border-radius: 12px;
    padding: 16px;
    min-width: 140px;
}

.node.active {
    box-shadow: 0 0 20px var(--accent-glow);
    border-color: var(--accent);
}

.node.human {
    border-color: #f59e0b; /* Warm color for humans */
}

.node.ai {
    background: linear-gradient(135deg, var(--bg-surface), var(--bg-elevated));
    border-color: var(--accent);
}
Flow Arrows:
css
.arrow {
    stroke: var(--text-muted);
    stroke-width: 2;
    fill: none;
    marker-end: url(#arrowhead);
}

.arrow.active {
    stroke: var(--accent);
    stroke-dasharray: 8 4;
    animation: flowDash 1s linear infinite;
}
Canvas:
css
.canvas {
    background:
        radial-gradient(circle at center, var(--bg-elevated) 0%, var(--bg-primary) 100%),
        url("data:image/svg+xml,..."); /* Subtle grid pattern */
    overflow: auto;
}

组件节点:
css
.node {
    background: var(--bg-surface);
    border: 2px solid var(--brand-primary);
    border-radius: 12px;
    padding: 16px;
    min-width: 140px;
}

.node.active {
    box-shadow: 0 0 20px var(--accent-glow);
    border-color: var(--accent);
}

.node.human {
    border-color: #f59e0b; /* 人员使用暖色调 */
}

.node.ai {
    background: linear-gradient(135deg, var(--bg-surface), var(--bg-elevated));
    border-color: var(--accent);
}
流程箭头:
css
.arrow {
    stroke: var(--text-muted);
    stroke-width: 2;
    fill: none;
    marker-end: url(#arrowhead);
}

.arrow.active {
    stroke: var(--accent);
    stroke-dasharray: 8 4;
    animation: flowDash 1s linear infinite;
}
画布:
css
.canvas {
    background:
        radial-gradient(circle at center, var(--bg-elevated) 0%, var(--bg-primary) 100%),
        url("data:image/svg+xml,..."); /* 细微网格图案 */
    overflow: auto;
}

Phase 5: Clarifying Questions (REQUIRED)

阶段5:确认问题(必填)

Before building any asset, always ask clarifying questions. This ensures alignment and prevents wasted effort.
在制作任何资产之前,务必提出确认问题,确保对齐需求,避免无效工作。

Step 5.1: Summarize Understanding

步骤5.1:总结理解内容

First, show the user what you understood:
"Here's what I'm planning to build:

**Asset**: [Format] for [Prospect Company]
**Audience**: [Audience type] — specifically [roles if known]
**Goal**: [Purpose] → driving toward [desired action]
**Key themes**: [2-3 main points to emphasize]

[For workflow demos, also show:]
**Components**: [List of systems]
**Flow**: [Step 1] → [Step 2] → [Step 3] → ...
首先,向用户展示您的理解:
"以下是我计划制作的内容:

**资产**:[格式] 为 [潜在客户公司]
**受众**:[受众类型] — 具体为[已知职位]
**目标**:[用途] → 推动受众采取[期望行动]
**核心主题**:[2-3个重点强调的要点]

[若为工作流演示,还需展示:]
**组件**:[系统列表]
**流程**:[步骤1] → [步骤2] → [步骤3] → ...

Step 5.2: Ask Standard Questions (ALL formats)

步骤5.2:提出通用问题(所有格式)

QuestionWhy
"Does this match your vision?"Confirm understanding
"What's the ONE thing this must nail to succeed?"Focus on priority
"Tone preference? (Bold & confident / Consultative / Technical & precise)"Style alignment
"Focused and concise, or comprehensive?"Scope calibration
问题原因
“这符合您的预期吗?”确认理解正确
“此资产必须做好的一件事是什么?”聚焦优先级
语气偏好?(大胆自信 / 咨询式 / 技术精准)风格对齐
希望内容简洁聚焦还是全面详尽?范围校准

Step 5.3: Ask Format-Specific Questions

步骤5.3:提出格式专属问题

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

步骤5.4:确认并推进

After user responds:
"Got it. I have what I need. Building your [format] now..."
Or, if still unclear:
"One more quick question: [specific follow-up]"
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."

用户回复后:
“明白了。我已获取所需信息。正在为您制作[格式]资产...”
若仍有不明确之处:
“还有一个小问题:[具体跟进问题]”
最多进行2轮问题确认。若仍存在歧义,做出合理选择并备注:“我选择了X方案 — 若您偏好Y方案,可随时调整。”

Phase 6: Build & Deliver

阶段6:制作与交付

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)
遵循上述所有规范:
  1. 根据阶段2生成结构
  2. 根据阶段3创建内容
  3. 根据阶段4应用视觉设计
  4. 确保所有交互元素正常工作
  5. 测试响应性(若适用)

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
所有格式:独立HTML文件
  • 所有CSS内联或放在
    <style>
    标签中
  • 所有JS内联或放在
    <script>
    标签中
  • 无外部依赖(Google Fonts除外)
  • 单一文件便于分享
文件命名
[潜在客户名称]-[格式]-[日期].html
  • 示例:
    CentricBrands-workflow-demo-2026-01-28.html

Delivery Message

交付消息

markdown
undefined
markdown
undefined

✓ Asset Created: [Prospect Name]

✓ 资产已创建:[潜在客户名称]

View your asset

Summary
  • Format: [Interactive Page / Deck / One-Pager / Workflow Demo]
  • Audience: [Type and roles]
  • Purpose: [Goal] → [Desired action]
  • Sections/Steps: [Count and list]

Deployment Options
To share this with your customer:
  • Static hosting: Upload to Netlify, Vercel, GitHub Pages, AWS S3, or any static host
  • Password protection: Most hosts offer this (e.g., Netlify site protection)
  • Direct share: Send the HTML file directly — it's fully self-contained
  • Embed: The file can be iframed into other pages if needed

Customization
Let me know if you'd like to:
  • Adjust colors or styling
  • Add, remove, or reorder sections
  • Refine any messaging or copy
  • Change the flow or architecture (for workflow demos)
  • Add more interactive elements
  • Export as PDF or static images

---
查看您的资产

摘要
  • 格式:[交互式页面 / 演示文稿 / 单页资料 / 工作流演示]
  • 受众:[类型和职位]
  • 用途:[目标] → [期望行动]
  • 章节/步骤:[数量和列表]

部署选项
与客户分享此资产的方式:
  • 静态托管:上传至Netlify、Vercel、GitHub Pages、AWS S3或任意静态托管平台
  • 密码保护:大多数托管平台支持此功能(例如Netlify站点保护)
  • 直接分享:直接发送HTML文件 — 它是完全独立的
  • 嵌入:该文件可嵌入到其他页面中(若需要)

定制化调整
若您需要以下调整,请告知:
  • 调整颜色或样式
  • 添加、删除或重新排序章节
  • 优化任何文案或信息
  • 修改工作流或架构(针对工作流演示)
  • 添加更多交互元素
  • 导出为PDF或静态图片

---

Phase 7: Iteration Support

阶段7:迭代支持

After delivery, be ready to iterate:
User RequestAction
"Change the colors"Regenerate with new palette, keep content
"Add a section on X"Insert new section, maintain flow
"Make it shorter"Condense, prioritize key points
"The flow is wrong"Rebuild architecture based on correction
"Use our brand instead"Switch from prospect brand to seller brand
"Add more detail on step 3"Expand that section specifically
"Can I get this as a PDF?"Provide print-optimized version
Remember: Default to prospect's brand colors, but seller can adjust to their own brand or a neutral palette after initial build.

交付后,随时准备进行迭代:
用户请求操作
“更改颜色”使用新调色板重新生成,保留内容
“添加关于X的章节”插入新章节,保持流程连贯
“缩短内容”浓缩内容,优先展示核心要点
“流程有误”根据修正重新构建架构
“使用我们的品牌”将潜在客户品牌切换为销售方品牌
“详细说明步骤3”专门扩展该章节
“能否导出为PDF?”提供优化的打印版本
注意:默认使用潜在客户的品牌颜色,但销售方可在初始制作完成后调整为自身品牌或中性调色板。

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

示例1:高管着陆页

Input:
  • Prospect: Acme Corp (manufacturing)
  • Audience: C-suite
  • Purpose: Exec alignment after discovery
  • Format: Interactive landing page
Output structure:
[Tabs]
Strategic Fit | Business Impact | ROI Calculator | Security & Trust | Next Steps

[Strategic Fit tab]
- Acme's stated priorities (from discovery call)
- How [Product] aligns
- Relevant manufacturing customers
输入:
  • 潜在客户:Acme Corp(制造业)
  • 受众:C-suite高管
  • 用途:需求探索后的高管对齐
  • 格式:交互式着陆页
输出结构:
[标签页]
战略适配 | 业务影响 | 投资回报率计算器 | 安全与信任 | 下一步行动

[战略适配标签页]
- Acme在需求探索会议中提出的优先事项
- [产品] 如何与之对齐
- 相关制造业客户案例

Example 2: Technical Workflow Demo

示例2:技术工作流演示

Input:
  • Prospect: Centric Brands
  • Audience: IT architects
  • Purpose: POC proposal
  • Format: Workflow demo
  • Components: Claude, Workato DataGenie, Snowflake, PDF contracts
Output structure:
[Interactive canvas with 5 nodes]
Human → Claude → PDF Contracts → Workato → Snowflake
    [Results back to Human]

[Step-by-step walkthrough with sample data]
[Controls: Play | Pause | Step | Reset]
输入:
  • 潜在客户:Centric Brands
  • 受众:IT架构师
  • 用途:概念验证提案
  • 格式:工作流演示
  • 组件:Claude、Workato DataGenie、Snowflake、PDF合同
输出结构:
[包含5个节点的交互式画布]
人工 → Claude → PDF合同 → Workato → Snowflake
    [结果返回给人工]

[带样本数据的逐步讲解]
[控制按钮:播放 | 暂停 | 步进 | 重置]

Example 3: Sales One-Pager

示例3:销售单页资料

Input:
  • Prospect: TechStart Inc
  • Audience: VP Engineering
  • Purpose: Leave-behind after first meeting
  • Format: One-pager
Output structure:
Hero: "Accelerate TechStart's Product Velocity"
Point 1: [Dev productivity]
Point 2: [Code quality]
Point 3: [Time to market]
Proof: "Similar companies saw 40% faster releases"
CTA: "Schedule technical deep-dive"

输入:
  • 潜在客户:TechStart Inc
  • 受众:工程副总裁
  • 用途:首次会议后的留档资料
  • 格式:单页资料
输出结构:
标题区:“加速TechStart的产品交付速度”
要点1:[开发人员生产力]
要点2:[代码质量]
要点3:[上市时间]
证明点:“类似公司实现了40%的发布速度提升”
号召性用语:“安排技术深度讲解”

Appendix: Component Icons

附录:组件图标

For workflow demos, use these icon mappings:
TypeIconExample
human👤 or person SVGUser, Analyst, Admin
document📄 or file SVGPDF, Contract, Report
ai🤖 or brain SVGClaude, AI Agent
database🗄️ or cylinder SVGSnowflake, Postgres
api🔌 or plug SVGREST API, GraphQL
middleware⚡ or hub SVGWorkato, MCP Server
output📊 or screen SVGDashboard, Report

针对工作流演示,使用以下图标映射:
类型图标示例
human👤 或人物SVG用户、分析师、管理员
document📄 或文件SVGPDF、合同、报告
ai🤖 或大脑SVGClaude、AI Agent
database🗄️ 或圆柱SVGSnowflake、Postgres
api🔌 或插头SVGREST API、GraphQL
middleware⚡ 或枢纽SVGWorkato、MCP服务器
output📊 或屏幕SVG仪表板、报告

Appendix: Brand Color Fallbacks

附录:品牌色备选方案

If brand colors cannot be extracted:
IndustryPrimarySecondary
Technology#2563eb#7c3aed
Finance#0f172a#3b82f6
Healthcare#0891b2#06b6d4
Manufacturing#ea580c#f97316
Retail#db2777#ec4899
Energy#16a34a#22c55e
Default#3b82f6#8b5cf6

Skill created for generalized sales asset generation. Works for any seller, any product, any prospect.
若无法提取品牌颜色:
行业主色辅助色
科技#2563eb#7c3aed
金融#0f172a#3b82f6
医疗#0891b2#06b6d4
制造#ea580c#f97316
零售#db2777#ec4899
能源#16a34a#22c55e
默认#3b82f6#8b5cf6

本Skill用于通用销售资产生成,适用于任意销售方、任意产品、任意潜在客户。