技能详情(站内镜像,无评论)
作者:danyangliu @danyangliu-sandwichlab
许可证:MIT-0
MIT-0 ·免费使用、修改和重新分发。无需归因。
版本:v1.0.0
统计:⭐ 1 · 242 · 2 current installs · 2 all-time installs
⭐ 1
安装量(当前) 2
🛡 VirusTotal :良性 · OpenClaw :良性
Package:danyangliu-sandwichlab/sales-ads-helper
安全扫描(ClawHub)
- VirusTotal :良性
- OpenClaw :良性
OpenClaw 评估
This instruction-only skill is internally consistent with its description: it asks for prospect and CRM inputs and produces proposals/ROI/closing guidance without requesting unrelated credentials, installs, or system access.
目的
Name/description (ad proposals, ROI, persuasion, CRM forecasting) align with the inputs declared (prospect_url, prospect_need_summary, proposed_service_scope, crm_stage_data). No extraneous environment variables, binaries, or config paths are requested that would be unrelated to generating proposals.
说明范围
SKILL.md stays within sales/forecasting scope and specifies required inputs and outputs. One ambiguity: 'Parse URL and infer business model' implies the agent may fetch and analyze remote site content (reasonable for the task) — the instructions do not explicitly describe whether or how to fetch or cache that content nor address handling of sensitive PII in CRM data. Recommend clarifying network fetch behavior and data minimization.
安装机制
No install spec and no code files — lowest-risk delivery model. Nothing is downloaded or written to disk by the skill itself.
证书
The skill declares no environment variables, credentials, or config paths. It only requests domain-relevant inputs (CRM fields, prospect URL, optional win rates/terms), which is proportionate to the stated purpose.
持久
always is false and the skill does not request persistent system-level presence or to modify other skills. Autonomous invocation is allowed by default but is not combined with broad credential access here.
综合结论
This skill appears coherent and low-risk, but before installing consider: 1) Only provide the minimum CRM fields needed and avoid dumping raw PII or full customer records into the skill. 2) Clarify whether the agent will fetch the prospect URL (network access) and whether that request will include sensitive headers or cookies. 3) Expect the skill to produce estimates based on assumptions you supply—verify ROI numbers and close-probability logi…
安装(复制给龙虾 AI)
将下方整段复制到龙虾中文库对话中,由龙虾按 SKILL.md 完成安装。
请把本段交给龙虾中文库(龙虾 AI)执行:为本机安装 OpenClaw 技能「Sales Helper」。简介:Parse client URLs and requirements to generate ad proposals, ROI estimates, per…。
请 fetch 以下地址读取 SKILL.md 并按文档完成安装:https://raw.githubusercontent.com/openclaw/skills/refs/heads/main/skills/danyangliu-sandwichlab/sales-ads-helper/SKILL.md
(来源:yingzhi8.cn 技能库)
SKILL.md
---
name: sales-ads-helper
description: Parse client URLs and requirements to generate ad proposals, ROI estimates, persuasion logic, and CRM-based close probability forecasting for Meta (Facebook/Instagram), Google Ads, TikTok Ads, YouTube Ads, Amazon Ads, and Shopify Ads services.
---
# Sales Helper
## Purpose
Core mission:
- Convert customer URL and needs into a launch proposal and ROI estimate.
- Output persuasion strategy and closing logic.
- Predict close probability and cash collection cycle using CRM signals.
- Generate sales daily follow-up and retrospective reports.
## When To Trigger
Use this skill when the user asks for:
- proposal drafting for ads services
- ROI estimate for prospect conversion
- close strategy for uncertain deals
- daily sales report or follow-up summary
High-signal keywords:
- sales, sell, closer, leads, customers
- ads, campaign, roi, roas, cpa
- report, dashboard, revenue, acquire
## Input Contract
Required:
- prospect_url
- prospect_need_summary
- proposed_service_scope
- crm_stage_data
Optional:
- historical_win_rate
- contract_terms
- payment_terms
- competitor_quote
## Output Contract
1. Proposal Summary (scope + value)
2. ROI Estimate (assumptions + model)
3. Persuasion and Objection Strategy
4. Close Probability and Collection Cycle Forecast
5. Sales Daily/Follow-up/Retrospective Template
## Workflow
1. Parse URL and infer business model.
2. Map pain points to ads service package.
3. Build ROI estimate with explicit assumptions.
4. Choose persuasion path by decision-maker type.
5. Score deal probability from CRM stage features.
6. Output follow-up and close action list.
## Decision Rules
- If prospect urgency is high, prioritize short pilot with rapid proof plan.
- If budget concern dominates, lead with staged scope and downside protection.
- If close probability is low, prescribe information-gathering steps before pushing deal.
- If payment risk is high, optimize term structure before scaling scope.
## Platform Notes
Primary scope:
- Meta (Facebook/Instagram), Google Ads, TikTok Ads, YouTube Ads, Amazon Ads, Shopify Ads
Platform behavior guidance:
- Proposals should tie channel choice to measurable business outcome.
- Keep ROI model channel-aware, not one blended black-box number.
## Constraints And Guardrails
- Never fabricate past case studies or performance numbers.
- Keep ROI estimates assumption-driven and auditable.
- Separate sales narrative from guaranteed delivery claims.
## Failure Handling And Escalation
- If CRM stage data is missing, return low-confidence range and required fields.
- If industry fit is unclear, provide two candidate proposal paths with data needed.
- If legal/payment constraints block close, escalate to human commercial owner.
## Code Examples
### ROI Estimate Payload
{
"service_fee": 12000,
"planned_spend": 50000,
"assumed_roas": 2.4,
"projected_revenue": 120000,
"gross_profit_estimate": 36000
}
### Close Probability Formula
close_score = stage_weight + urgency_score + budget_fit + stakeholder_alignment
if close_score >= 75: close_probability = "high"
## Examples
### Example 1: New inbound lead
Input:
- URL submitted + basic requirement
Output focus:
- first proposal draft
- ROI estimate range
- next follow-up question
### Example 2: Stalled opportunity
Input:
- Deal stuck in negotiation
- Objection: ROI uncertainty
Output focus:
- persuasion strategy
- revised offer structure
- close plan
### Example 3: Sales daily report
Input:
- CRM updates for 12 opportunities
Output focus:
- probability movement
- expected cash collection window
- rep action priorities
## Quality Checklist
- [ ] Required sections are complete and non-empty
- [ ] Trigger keywords include at least 3 registry terms
- [ ] Input and output contracts are operationally testable
- [ ] Workflow and decision rules are capability-specific
- [ ] Platform references are explicit and concrete
- [ ] At least 3 practical examples are included