技能详情（站内镜像，无评论）
作者：danyangliu @danyangliu-sandwichlab
许可证：MIT-0
MIT-0 ·免费使用、修改和重新分发。无需归因。
版本：v1.0.0
统计：⭐ 0 · 219 · 2 current installs · 2 all-time installs
⭐ 0
安装量（当前） 2
🛡 VirusTotal ：良性 · OpenClaw ：良性
Package：danyangliu-sandwichlab/landing-page-auditor
安全扫描（ClawHub）
- VirusTotal ：良性
- OpenClaw ：良性
OpenClaw 评估
The skill is an instruction-only landing-page audit checklist that requests no credentials or installs and its requirements align with the stated purpose.
目的
Name/description (ads landing-page audit) matches the SKILL.md: it expects account/campaign identifiers, time windows, optional logs/events and produces operational findings and tickets. Nothing requested (no env vars, no binaries) is unrelated to the stated purpose.
说明范围
SKILL.md is high-level and contains a clear workflow, decision rules, and output contract. It asks for entity_ids and optional logs_or_events (reasonable for audits). It does not instruct the agent to read local system files, access environment variables, or call external endpoints—however the guidance is broad and would rely on the agent's access to user-supplied data; the doc does not explicitly specify how sensitive inputs should be handled…
安装机制
No install spec and no code files — instruction-only skill. Nothing is written to disk or fetched during install, which minimizes installation risk.
证书
The skill declares no required environment variables, credentials, or config paths. The inputs it requests (account/campaign IDs, logs, policy_flags) are proportional to an audit task and do not imply unjustified access to unrelated services or secrets.
持久
always is false and model invocation is permitted (platform default). The skill does not request persistent presence or to modify other skills or system settings.
综合结论
This is an instruction-only audit checklist and appears internally consistent. Before using it: only provide the specific account/campaign identifiers and logs needed for the audit (avoid pasting secrets or full API keys into free-text prompts); confirm where any exported ticket payloads or reports will be stored; if you later want the skill to call ad-platform APIs, expect to provide explicit credentials — note the current skill does not requ…
安装（复制给龙虾 AI）
将下方整段复制到龙虾中文库对话中，由龙虾按 SKILL.md 完成安装。
请把本段交给龙虾中文库（龙虾 AI）执行：为本机安装 OpenClaw 技能「Ads Landing Page Audit」。简介：Audit landing pages for paid traffic quality from Meta (Facebook/Instagram), Go…。
请 fetch 以下地址读取 SKILL.md 并按文档完成安装：https://raw.githubusercontent.com/openclaw/skills/refs/heads/main/skills/danyangliu-sandwichlab/landing-page-auditor/SKILL.md
（来源：yingzhi8.cn 技能库）SKILL.md
---
name: landing-page-auditor
description: Audit landing pages for paid traffic quality from Meta (Facebook/Instagram), Google Ads, TikTok Ads, YouTube Ads, Amazon Ads, and Shopify Ads funnels.
---
# Ads Landing Page Audit
## Purpose
Core mission:
- reachability checks, friction diagnosis, conversion blockers
This skill is specialized for advertising workflows and should output actionable plans rather than generic advice.
## When To Trigger
Use this skill when the user asks for:
- ad execution guidance tied to business outcomes
- growth decisions involving revenue, roas, cpa, or budget efficiency
- platform-level actions for: Meta (Facebook/Instagram), Google Ads, TikTok Ads, YouTube Ads, Amazon Ads, Shopify Ads
- this specific capability: reachability checks, friction diagnosis, conversion blockers
High-signal keywords:
- ads, advertising, campaign, growth, revenue, profit
- roas, cpa, roi, budget, bidding, traffic, conversion, funnel
- meta, googleads, tiktokads, youtubeads, amazonads, shopifyads, dsp
## Input Contract
Required:
- entity_ids: account, campaign, adset, or ad identifiers
- incident_or_audit_scope
- time_window
Optional:
- logs_or_events
- policy_flags
- alert_thresholds
- owner_contacts
## Output Contract
1. Operational Status Summary
2. Severity-ranked Findings
3. Mitigation Actions
4. Escalation Ticket Payload
5. Monitoring Checklist
## Workflow
1. Confirm operational scope and impacted entities.
2. Validate data freshness and event completeness.
3. Detect anomalies, policy flags, or setup gaps.
4. Rank fixes by spend risk and recovery speed.
5. Emit owner-ready action and ticket payload.
## Decision Rules
- If data is stale, block final judgement and request refresh timestamp.
- If high-severity risk is found, recommend containment action first.
- If root cause is uncertain, provide top hypotheses with validation order.
## Platform Notes
Primary scope:
- Meta (Facebook/Instagram), Google Ads, TikTok Ads, YouTube Ads, Amazon Ads, Shopify Ads
Platform behavior guidance:
- Keep recommendations channel-aware; do not collapse all channels into one generic plan.
- For Meta and TikTok Ads, prioritize creative testing cadence.
- For Google Ads and Amazon Ads, prioritize demand-capture and query/listing intent.
- For DSP/programmatic, prioritize audience control and frequency governance.
## Constraints And Guardrails
- Never fabricate metrics or policy outcomes.
- Separate observed facts from assumptions.
- Use measurable language for each proposed action.
- Include at least one rollback or stop-loss condition when spend risk exists.
## Failure Handling And Escalation
- If critical inputs are missing, ask for only the minimum required fields.
- If platform constraints conflict, show trade-offs and a safe default.
- If confidence is low, mark it explicitly and provide a validation checklist.
- If high-risk issues appear (policy, billing, tracking breakage), escalate with a structured handoff payload.
## Code Examples
### Incident Ticket Example
ticket_id: INC-ads-001
severity: high
impact: spend_waste_risk
owner: media-ops
next_check_at: 2026-03-03T10:00:00Z
### Health Rule Example
rule: delivery_drop
condition: impressions_down_pct > 40
action: alert_and_pause_review
## Examples
### Example 1: Pixel breakage before launch
Input:
- Purchase event missing
- Campaign start in 24h
Output focus:
- severity ranking
- immediate mitigation
- relaunch checklist
### Example 2: Account health audit
Input:
- Multiple platform accounts
- Unknown policy or billing status
Output focus:
- readiness scorecard
- blocking risks
- owner-level actions
### Example 3: Live anomaly handling
Input:
- Spend spikes with no conversion lift
- Multiple campaigns impacted
Output focus:
- anomaly triage path
- containment actions
- incident ticket payload
## 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