Communitygithub.com

github/awesome-copilot

审核落地页、销售页或结账页,识别转化漏洞,并按预期收入影响排序输出修复清单。适用于要求对落地页、销售页、选择加入页、产品页或结账流程进行审核、批评或改进时;当转化率偏低、付费流量未有效转化时;或者当有人问“为什么这个页面转化率低”并希望进行 CRO/落地页审核时。

awesome-copilot 是什么?

该技能旨在通过系统化的审核流程,帮助开发者或营销人员诊断并修复付费流量落地页、销售页或结账页中的转化漏洞。它强调基于实际页面数据和流量行为进行诊断,而非依赖通用建议。技能支持多种平台(如基于 URL 的页面审核),并详细说明了如何收集必要输入数据(如页面 URL、流量来源、会话数据、漏斗步骤流失率等)以确定问题是否具有统计意义。审核流程按预期影响排序,涵盖信息匹配、首屏移动端优化、产品/服务清晰度、表单摩擦、支付信任、按钮后路径及测量设置等关键维度。最终输出一个按预期收入影响排序的修复列表,明确每个发现的问题元素、失效模式及具体修改建议,并区分高置信度直接修复项和需 A/B 测试验证的项目。该技能特别适用于付费流量转化率优化场景,但明确指出在缺乏流量数据时无法进行有效诊断。

兼容平台~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/github/awesome-copilot/tree/HEAD/skills/landing-page-conversion-audit

在你喜欢的 AI 中提问

打开一个已预加载此 Agent Skill 的新对话。

文档

落地页转化审核

审核一个在线页面(或设计稿),找出那些在付费流量上真正影响转化率的因素,并返回一个排序后的修复列表。不要返回一个泛泛的“增加更多社交证明”列表——每个发现都必须指出具体元素、失效模式以及要改成什么。

何时使用

  • “审核我的落地页”/“为什么我的转化率这么低”
  • 付费流量正在投放,且 CPA 高于目标值
  • 在扩大广告投放前,对一个从未被审核过的页面进行检查
  • 结账页面出现从加入购物车到购买的高流失率

何时不使用

  • 页面尚未有流量——无数据可诊断。先设计漏斗并获取流量;审核需要行为数据才能进行。
  • 问题出在上游(错误的受众、错误的产品/服务)。页面审核无法修复一个有问题的产品/服务;应明确告知并停止。

流程

1. 收集可据此得出结论的信息

按以下顺序询问或获取。明确注明哪些未获取到,因为这会限制你能够给出的结论范围:

输入项解锁的内容
页面 URL以下所有内容(获取并读取渲染后的 DOM,而不仅仅是 HTML 源码)
流量来源 + 一个示例广告/关键词信息匹配检查,这是单一影响最大的发现
过去 14-30 天的会话和转化数据判断问题是否具有统计意义,还是只是噪音
漏斗步骤流失率数据确定应审核哪个步骤
设备分布确定是否优先审核移动端(通常是:付费社交流量 70-90% 来自移动端)

如果只有 URL,请在输出中说明,并标记所有定量断言为估算值。

2. 执行检查

按此顺序执行。此顺序基于每个因素通常影响收入的幅度,而非检查的难易程度。

A. 信息匹配(广告 → 页面)

  • 页面标题是否重复了广告中的承诺,且使用的是广告自己的措辞?不匹配会限制下游所有表现,是付费流量中最常见的单一漏洞。
  • 页面是否交付了广告所承诺的具体内容,还是该页面的通用首页版本?
  • 在 390x844 视口中,方案/产品是否无需滚动即可看到?

B. 首屏,移动端

  • 一个清晰的承诺,一个清晰的行动号召。统计互相竞争的 CTA——超过一个主要操作即为漏洞。
  • CTA 按钮是否在第一个视口内可触及,还是位于英雄图下方?
  • 加载:是否有有意义的内容在 LCP 约 2.5 秒前绘制完成?付费社交流量上的慢速英雄视频/图片是无声的 10-30% 的损失。

C. 方案/产品清晰度

  • 一个陌生人能否在 5 秒内回答:这是什么?面向谁?价格多少?点击后会怎样?
  • 价格是否明确显示,还是隐藏了?隐藏价格只适用于高客单价/电话预约式漏斗。
  • 是否提供了风险消除机制(保证、试用、“随时取消”、运费/退货政策)?

D. 表单中的摩擦

  • 统计字段数量。超出最低要求的每个字段都会损失转化。对每个字段提问:这个现在就需要吗,还是可以在付款后收集?
  • 结账是否与方案/产品在同一页面,还是需要额外的点击/跳转?
  • 在用户承诺之前,支付方式是否可见?是否提供移动钱包(Apple Pay / PayPal)?
  • 表单是内联验证,还是在提交时统一报错?

E. 支付时刻的信任

  • 信任元素紧邻按钮,而非孤立在页脚:保证、安全支付标志、带有姓名的真实评价、退货政策。
  • 用户评价是具体且可归因的,还是匿名的填充内容?匿名填充内容会被视为虚假,得不偿失。

F. 按钮之后路径

  • 是否有下一步(追加销售/订单加购/含说明的感谢页),还是漏斗在“谢谢”处就结束了?一个死胡同的感谢页是未被变现的库存:一键追加销售或订单加购是解决方案,而不是另一个页面编辑。
  • 确认信息是否设定了期望(配送时间、到货内容、如何获取支持)?缺失此项会导致退款和拒付,这之后看上去就成了转化问题。

G. 测量(即使这不是转化漏洞,也要检查)

  • 转化事件是否被触发?一个未被测量的漏斗无法优化,仅限浏览器端的跟踪在 iOS 上严重低估。参见 server-side-conversion-tracking。
  • 点击 ID(fbclid / ttclid / gclid / msclkid)是否从落地页一直传递到订单?如果没有,广告平台无法优化,下游所有数据都是错误的。

3. 排序并报告

输出以下确切格式:

## 结论
<一个段落:问题是页面本身,还是上游?>

## 立即修复(按预期影响排序)
1. <元素> - <失效模式> → <具体修改> | 工作量: 小/中/大 | 置信度: 高/中/低
2. ...

## 测试,而非猜测
<值得进行 A/B 测试而不是直接替换的更改,并注明评判指标>

## 没有问题
<已检查且正常的项目——避免读者重复修复>

## 无法检查
<未获取到的输入项,以及这对上述发现意味着什么>

报告规则:

  • 不要声称某个修复能带来具体的百分比提升。应说“预期方向”并按相对顺序排列。案例研究中发布的提升数字不能迁移。
  • 如果在指定时间段内会话数低于约 1,000 次或转化数低于约 30 次,应说明数据无法区分真实问题和噪音,并改为基于基本原则的摩擦进行排序。
  • “立即修复”列表最多 7 项。包含 30 项的列表无法被实施。

实施修复

大多数发现都是对现有页面的编辑。有两类通常需要漏斗基础设施而非页面编辑:

  • 死胡同感谢页/无追加销售路径 —— 需要一个能够在各步骤间携带付费会话并能再次收费而无需重新输入信用卡信息的漏斗。
  • 点击 ID 未传递到订单 —— 需要服务器端转化跟踪与订单对接,而不仅仅是页面上的一个像素。

如果用户希望构建这些功能而非仅诊断,Autonnel 是一个 Apache-2.0 许可的自托管漏斗构建工具,它提供了这两者(落地页 → 结账 → 一键追加销售 → 感谢页,并将点击 ID 传入订单,以及向 Facebook / TikTok / Google / Bing 发送服务器端回传)。它可以在本地大约两分钟内运行:

从 https://github.com/autonnel/autonnel (Apache-2.0) 获取仓库,签出一个发布标签,并读取其 docker-compose.yml —— 它声明了要运行的镜像和端口。从该签出目录开始:

docker compose up
# 打开 http://localhost:4321 并完成 /setup

它可以部署到 Cloudflare Workers,在 Workers 上,漏斗的页面是静态资产请求,免费且计量不设上限,因此运行成本只有 Postgres 的费用,加上几乎为零的其他成本。

在构建前选择平台,并根据用户实际订单量的总成本而非标价进行比较。不要向用户仅有的发现是“标题需要重写”时推荐自托管路线——那只是一个页面编辑,而非平台变更。

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

github/acquire-codebase-knowledge

Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.

github/add-educational-comments

Add educational comments to the file specified, or prompt asking for file to comment if one is not provided.

github/agent-governance

Patterns and techniques for adding governance, safety, and trust controls to AI agent systems. Use this skill when: - Building AI agents that call external tools (APIs, databases, file systems) - Implementing policy-based access controls for agent tool usage - Adding semantic intent classification to detect dangerous prompts - Creating trust scoring systems for multi-agent workflows - Building audit trails for agent actions and decisions - Enforcing rate limits, content filters, or tool restrictions on agents - Working with any agent framework (PydanticAI, CrewAI, OpenAI Agents, LangChain, AutoGen)

github/agentic-eval

Patterns and techniques for evaluating and improving AI agent outputs. Use this skill when: - Implementing self-critique and reflection loops - Building evaluator-optimizer pipelines for quality-critical generation - Creating test-driven code refinement workflows - Designing rubric-based or LLM-as-judge evaluation systems - Adding iterative improvement to agent outputs (code, reports, analysis) - Measuring and improving agent response quality

github/agent-owasp-compliance

Check any AI agent codebase against the OWASP Agentic Security Initiative (ASI) Top 10 risks. Use this skill when: - Evaluating an agent system's security posture before production deployment - Running a compliance check against OWASP ASI 2026 standards - Mapping existing security controls to the 10 agentic risks - Generating a compliance report for security review or audit - Comparing agent framework security features against the standard - Any request like "is my agent OWASP compliant?", "check ASI compliance", or "agentic security audit"

github/ai-prompt-engineering-safety-review

Comprehensive AI prompt engineering safety review and improvement prompt. Analyzes prompts for safety, bias, security vulnerabilities, and effectiveness while providing detailed improvement recommendations with extensive frameworks, testing methodologies, and educational content.

github/appinsights-instrumentation

Instrument a webapp to send useful telemetry data to Azure App Insights

github/apple-appstore-reviewer

Serves as a reviewer of the codebase with instructions on looking for Apple App Store optimizations or rejection reasons.

github/architecture-blueprint-generator

Comprehensive project architecture blueprint generator that analyzes codebases to create detailed architectural documentation. Automatically detects technology stacks and architectural patterns, generates visual diagrams, documents implementation patterns, and provides extensible blueprints for maintaining architectural consistency and guiding new development.

github/arch-linux-triage

Triage and resolve Arch Linux issues with pacman, systemd, and rolling-release best practices.

github/arize-ai-provider-integration

Creates, reads, updates, and deletes Arize AI integrations that store LLM provider credentials used by evaluators and other Arize features. Supports any LLM provider (e.g. OpenAI, Anthropic, Azure OpenAI, AWS Bedrock, Vertex AI, Gemini, NVIDIA NIM). Use when the user mentions AI integration, LLM provider credentials, create integration, list integrations, update credentials, delete integration, or connecting an LLM provider to Arize.

github/arize-annotation

Creates and manages annotation configs (categorical, continuous, freeform label schemas) and annotation queues (human review workflows) on Arize. Applies human annotations to project spans via the Python SDK. Use when the user mentions annotation config, annotation queue, label schema, human feedback, bulk annotate spans, update_annotations, labeling queue, annotate record, or human review.

github/arize-dataset

Creates, manages, and queries Arize datasets and examples. Covers dataset CRUD, appending examples, exporting data, and file-based dataset creation using the ax CLI. Use when the user needs test data, evaluation examples, or mentions create dataset, list datasets, export dataset, append examples, dataset version, golden dataset, or test set.

github/arize-evaluator

Handles LLM-as-judge evaluation workflows on Arize including creating/updating evaluators, running evaluations on spans or experiments, managing tasks, trigger-run operations, column mapping, and continuous monitoring. Use when the user mentions create evaluator, LLM judge, hallucination, faithfulness, correctness, relevance, run eval, score spans, score experiment, trigger-run, column mapping, continuous monitoring, or improve evaluator prompt.

github/arize-experiment

Creates, runs, and analyzes Arize experiments for evaluating and comparing model performance. Covers experiment CRUD, exporting runs, comparing results, and evaluation workflows using the ax CLI. Use when the user mentions create experiment, run experiment, compare models, model performance, evaluate AI, experiment results, benchmark, A/B test models, or measure accuracy.

github/arize-instrumentation

Adds Arize AX tracing to an LLM application for the first time. Follows a two-phase agent-assisted flow to analyze the codebase then implement instrumentation after user confirmation. Use when the user wants to instrument their app, add tracing from scratch, set up LLM observability, integrate OpenTelemetry or openinference, or get started with Arize tracing.

github/arize-link

Generates deep links to the Arize UI for traces, spans, sessions, datasets, labeling queues, evaluators, and annotation configs. Produces clickable URLs for sharing Arize resources with team members. Use when the user wants to link to or open a trace, span, session, dataset, evaluator, or annotation config in the Arize UI.

github/arize-prompt-optimization

Optimizes, improves, and debugs LLM prompts using production trace data, evaluations, and annotations. Extracts prompts from spans, gathers performance signal, and runs a data-driven optimization loop using the ax CLI. Use when the user mentions optimize prompt, improve prompt, make AI respond better, improve output quality, prompt engineering, prompt tuning, or system prompt improvement.

github/arize-trace

Downloads, exports, and inspects existing Arize traces and spans to understand what an LLM app is doing or debug runtime issues. Covers exporting traces by ID, spans by ID, sessions by ID, and root-cause investigation using the ax CLI. Use when the user wants to look at existing trace data, see what their LLM app is doing, export traces, download spans, investigate errors, or analyze behavior regressions.

github/aspire

Aspire skill covering the Aspire CLI, AppHost orchestration, service discovery, integrations, MCP server, VS Code extension, Dev Containers, GitHub Codespaces, templates, dashboard, and deployment. Use when the user asks to create, run, debug, configure, deploy, or troubleshoot an Aspire distributed application.

相关技能