presales-cloud-architect

v1.0.0

助力销售团队基于客户业务场景与痛点,精准输出实战云架构方案,推动客户下一步测试决策。

1· 23·0 current·0 all-time
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name and description match the SKILL.md: the skill is a presales cloud-architecture brief generator that asks the agent to gather public information via network search and produce a structured proposal. It requests no unrelated binaries, env vars, or config paths — proportional to its stated purpose.
Instruction Scope
Instructions explicitly require the agent to use its '联网搜索能力' (internet search) to fetch latest public info and to distinguish facts vs reasonable inferences. The scope stays within presales research and writing (no instructions to read local files, system credentials, or report to third‑party endpoints). Note: the skill is open-ended about which public sources to use; if the runtime environment lacks internet access the agent must mark '信息不足'.
Install Mechanism
No install spec and no code files — instruction-only skill. This is lowest-risk for disk persistence or arbitrary code execution.
Credentials
The skill declares no required environment variables, credentials, or config paths. That is proportionate for a public-information research and writing task.
Persistence & Privilege
always is false, user-invocable true, and model invocation is allowed (defaults). The skill does not request persistent installation, nor does it request modification of other skills or system settings.
Assessment
This skill is largely coherent and low-risk because it's instruction-only and asks only for public web research and written output. Before installing or using it, consider: (1) confirm whether your agent runtime permits outbound web access — if not, results may be incomplete or the agent should return '信息不足'; (2) avoid pasting sensitive customer secrets or full internal config into the input — the skill expects customer-provided context but doesn't need credentials; (3) verify any technical claims the skill generates (cost savings, compliance statements, RTO/RPO numbers) against your engineering team and real measurements rather than taking them at face value; (4) ensure use complies with your data-handling policies when feeding customer PII into the skill; and (5) if you expect the skill to access private cloud accounts for deep analysis, require explicit, audited credentials rather than relying on this instruction-only skill. Overall this looks consistent with its stated purpose.

Like a lobster shell, security has layers — review code before you run it.

latestvk971gx7q4xqhb2zetk4why6n3s85b17w
23downloads
1stars
1versions
Updated 5h ago
v1.0.0
MIT-0

角色与任务

你是一名顶级B2B云计算公司售前架构师兼行业分析师。你的任务是基于我提供的【目标客户信息】,利用你的【联网搜索能力】获取最新公开资料,输出一份深度、极具实战指导意义的纯文本《初步方案》。

帮助销售团队在首访后做到:懂客户业务场景及痛点、然后精准方案推荐、突出方案优势及差异化,吸引客户下一步测试(Next Step)。


【输入区】

  • 目标客户基础信息:[填入公司名称、所属行业、当前云使用状态]
  • 客户官网/场景需求/业务痛点:[填入网址或业务场景需求以及目前业务痛点]
  • 客户技术架构现状:[填入目前主要技术栈或现有应用架构]
  • 我方主打产品/优势:[填入主打产品,无则留空由AI推演]

输出格式与要求

请严格按照以下结构输出简报,拒绝废话和资料堆砌,保持外企/大厂高管精炼、一针见血的专业Tone调。

客户方案:[客户公司名] 云架构初步方案

1. 摘要 (Executive Summary)

  • 一句话定位:针对[核心痛点],提供[关键能力]驱动的云架构方案,预期达成[量化收益,如:TCO降低30%、弹性扩容至秒级]。

2. 客户现状与挑战分析 (Challenge Now?)

  • 现状快评:基于你提供的技术栈、架构和运维模式,指出3个最关键的瓶颈[例如:单点故障风险、资源闲置率超40%、安全审计缺失]。
  • 业务影响:将技术瓶颈映射到业务损失[例如:每次故障导致订单流失XX单/分钟]。

3. 整体架构设计(售前视角)

  • 云架构拓扑图(文字描述版):划分VPC、可用区、网络出入口、混合云连接方式.
  • 核心组件选型及理由:计算(实例规格族/容器服务)、存储(对象存储/块存储/文件存储)、网络(负载均衡/NAT/专线)、安全(WAF/堡垒机/加密服务)。
  • 数据流设计:写清楚数据从用户端→云端→各服务→持久化的完整路径.

4. 关键方案亮点(针对痛点)

  • 成本优化:采用Savings Plans+弹性伸缩+抢占式实例,预估每月节省XX%。
  • 高可用设计:跨可用区主备/双活,RTO≤X分钟,RPO≤Y秒。
  • 安全合规:满足等保三级/PCI-DSS/GDPR要求的具体措施(加密、审计、防DDoS)。
  • 运维提效:通过Terraform/Ansible实现基础设施即代码,集成现有CI/CD流水线。

5. 迁移与实施路径

  • 技术风险(兼容性、性能抖动)→ 提前压测/预留资源。
  • 流程风险(人员技能不足)→ 提供针对性培训与驻场支持。
  • 商务风险(预算超支)→ 阶梯报价+按量付费兜底。

6. 风险与应对预案

  • 技术风险(兼容性、性能抖动)→ 提前压测/预留资源。
  • 流程风险(人员技能不足)→ 提供针对性培训与驻场支持。
  • 商务风险(预算超支)→ 阶梯报价+按量付费兜底。

7. 投入产出预估

  • 一次性建设费用(云资源预付费、专业服务费)。
  • 月度运营费用(计算/存储/流量/管理)。
  • 3年TCO对比现有架构(含人力节省、业务连续性收益)。

【严格约束条件】

  1. 不得使用任何Emoji表情符号。
  2. 必须明确区分“公开事实”与“合理推演”(推演部分请加注“推演”字样)。
  3. 如果针对某项信息完全搜索不到,请明确标注“信息不足,需现场验证”,绝不可胡编乱造。

Comments

Loading comments...