openclaw 网盘下载
OpenClaw

技能详情(站内镜像,无评论)

首页 > 技能库 > Funnel Helper

Diagnose and optimize full conversion funnels for paid traffic from Meta (Facebook/Instagram), Google Ads, TikTok Ads, YouTube Ads, Amazon Ads, and Shopify A...

开发与 DevOps

作者:danyangliu @danyangliu-sandwichlab

许可证:MIT-0

MIT-0 ·免费使用、修改和重新分发。无需归因。

版本:v1.0.0

统计:⭐ 0 · 167 · 1 current installs · 1 all-time installs

0

安装量(当前) 1

🛡 VirusTotal :良性 · OpenClaw :良性

Package:danyangliu-sandwichlab/funnel-ads-helper

安全扫描(ClawHub)

  • VirusTotal :良性
  • OpenClaw :良性

OpenClaw 评估

The skill is an instruction-only funnel analysis assistant that only requires user-supplied metrics and does not request credentials, installs, or perform external operations — its declared purpose matches its instructions.

目的

Name/description (funnel diagnosis and optimization for paid channels) aligns with the inputs and outputs declared in SKILL.md; no unexpected credentials, binaries, or platform installs are requested.

说明范围

Runtime instructions limited to analyzing user-provided funnel metrics, producing scorecards, bottleneck maps, and experiment plans. It does not instruct accessing system files, environment variables, or external endpoints. Note: optional inputs (session replay notes, logs) may contain sensitive user data but are explicitly user-supplied.

安装机制

No install spec and no code files (instruction-only). This minimizes on-disk execution and is the lowest-risk install model.

证书

No environment variables, credentials, or config paths are required. Requested inputs are application metrics and logs, which are proportionate to a funnel diagnosis skill.

持久

Flags show no always:true, no install-time persistence, and the skill does not request system-wide changes or elevated privileges.

综合结论

This skill appears coherent and low-risk because it only operates on data you supply. Before using it, avoid sharing raw logs or session replays that contain PII, auth tokens, or customer identifiers — prefer aggregated or anonymized metrics. If you want automated fetching from ad/analytics platforms, require an explicit connector that limits scopes (avoid pasting API keys into free-text prompts). Validate any recommended experiments in a stag…

安装(复制给龙虾 AI)

将下方整段复制到龙虾中文库对话中,由龙虾按 SKILL.md 完成安装。

请把本段交给龙虾中文库(龙虾 AI)执行:为本机安装 OpenClaw 技能「Funnel Helper」。简介:Diagnose and optimize full conversion funnels for paid traffic from Meta (Faceb…。
请 fetch 以下地址读取 SKILL.md 并按文档完成安装:https://raw.githubusercontent.com/openclaw/skills/refs/heads/main/skills/danyangliu-sandwichlab/funnel-ads-helper/SKILL.md
(来源:yingzhi8.cn 技能库)

SKILL.md

打开原始 SKILL.md(GitHub raw)

---
name: funnel-ads-helper
description: Diagnose and optimize full conversion funnels for paid traffic from Meta (Facebook/Instagram), Google Ads, TikTok Ads, YouTube Ads, Amazon Ads, and Shopify Ads campaigns.
---

# Funnel Helper

## Purpose
Core mission:
- Analyze conversion funnel drop-off by stage.
- Identify bottlenecks from ad click to checkout or lead submit.
- Recommend stage-specific optimization actions.
- Define funnel experiment roadmap and expected impact.

## When To Trigger
Use this skill when the user asks for:
- conversion funnel diagnosis
- CVR optimization planning
- landing page and checkout improvement sequence
- funnel experiment design tied to ROAS/CPA goals

High-signal keywords:
- conversion, funnel, checkout, cvr
- cpa, roas, traffic, landing page
- campaign, optimize, retarget

## Input Contract
Required:
- funnel_stage_metrics
- traffic_source_breakdown
- conversion_goal
- observation_window

Optional:
- session_replay_notes
- form_or_checkout_logs
- segment_breakdowns
- experiment_history

## Output Contract
1. Funnel Stage Health Scorecard
2. Bottleneck Priority Ranking
3. Optimization Actions by Stage
4. Experiment Roadmap with KPI impact
5. Monitoring and Iteration Rules

## Workflow
1. Normalize funnel definitions and stage metrics.
2. Rank drop-off severity and opportunity size.
3. Map root causes (message mismatch, UX friction, trust gap, etc.).
4. Recommend stage-specific actions and experiments.
5. Define monitoring thresholds and iteration cadence.

## Decision Rules
- If top-funnel CTR is strong but CVR is weak, prioritize LP and checkout fixes.
- If add-to-cart is strong but purchase is weak, prioritize trust/payment friction fixes.
- If retargeting conversion is low, review audience freshness and offer relevance.
- If funnel data is sparse, run diagnostic experiments before major redesign.

## Platform Notes
Primary scope:
- Meta (Facebook/Instagram), Google Ads, TikTok Ads, YouTube Ads, Amazon Ads, Shopify Ads

Platform behavior guidance:
- Keep funnel interpretation tied to traffic intent by channel.
- Distinguish ad-side and on-site bottlenecks before action.

## Constraints And Guardrails
- Do not infer funnel causes without stage-level evidence.
- Keep test queue prioritized by expected impact and effort.
- Avoid simultaneous high-impact changes that break attribution clarity.

## Failure Handling And Escalation
- If stage definitions are inconsistent, output a canonical funnel mapping first.
- If missing checkout data blocks diagnosis, request minimum event payload.
- If conversion drops sharply during active changes, trigger rollback review.

## Code Examples
### Funnel Health Schema

    stages:
      - impression_to_click
      - click_to_viewcontent
      - viewcontent_to_addtocart
      - addtocart_to_checkout
      - checkout_to_purchase
    primary_metric: stage_cvr

### Bottleneck Prioritization Rule

    impact_score = dropoff_pct * traffic_volume * margin_weight
    sort_by: impact_score_desc

## Examples
### Example 1: CVR collapse
Input:
- Click volume stable, purchases down

Output focus:
- stage bottleneck map
- immediate fixes
- monitor plan

### Example 2: Checkout friction
Input:
- Add-to-cart high, checkout completion low

Output focus:
- checkout friction hypotheses
- test sequence
- expected lift range

### Example 3: Funnel rebuild plan
Input:
- Multi-channel traffic with inconsistent landing paths

Output focus:
- canonical funnel design
- stage KPI definitions
- experiment roadmap

## 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