技能详情（站内镜像，无评论）
作者：danyangliu @danyangliu-sandwichlab
许可证：MIT-0
MIT-0 ·免费使用、修改和重新分发。无需归因。
版本：v1.0.0
统计：⭐ 1 · 175 · 0 current installs · 0 all-time installs
⭐ 1
安装量（当前） 0
🛡 VirusTotal ：良性 · OpenClaw ：良性
Package：danyangliu-sandwichlab/pixel-attribution-readiness-checker
安全扫描（ClawHub）
- VirusTotal ：良性
- OpenClaw ：良性
OpenClaw 评估
The skill is an instruction-only checklist for auditing ad pixels and attribution readiness and its requirements and instructions are coherent with that purpose.
目的
Name and description (pixel/install/event integrity/attribution) match the SKILL.md content. Declared inputs (entity_ids, incident_or_audit_scope, time_window, optional logs) are appropriate for an audit-oriented skill. No unrelated credentials, binaries, or config paths are requested.
说明范围
SKILL.md contains operational audit steps, decision rules, examples, and output contracts. It does not instruct reading arbitrary system files, accessing environment variables, or calling unexpected external endpoints. It stays within advisory/audit scope rather than automating platform logins or API calls.
安装机制
No install spec or code files are present; this is instruction-only so nothing is written to disk or downloaded.
证书
The skill requests structured inputs (entity IDs, logs, owner contacts) but does not request platform credentials. This is coherent if the skill is intended to produce human-actionable plans from provided data; if the user expects the skill to make API calls or take actions, credentials would be required and should be scoped (read-only) and provided deliberately.
持久
always is false and the skill is user-invocable. It does not request persistent system presence or modify other skills or agent-wide settings.
综合结论
This skill is an advisory checklist — it doesn’t request credentials or install code, so it’s coherent for producing audit findings and action plans. Before using it: (1) don’t paste full account API keys or passwords into chat; if you want automated checks, provide read-only credentials or exports of logs only, and limit scope. (2) Treat any recommended 'containment' or platform actions as human-reviewed steps before executing them. (3) If yo…
安装（复制给龙虾 AI）
将下方整段复制到龙虾中文库对话中，由龙虾按 SKILL.md 完成安装。
请把本段交给龙虾中文库（龙虾 AI）执行：为本机安装 OpenClaw 技能「Ads Pixel Readiness」。简介：Validate event tracking and attribution readiness for Meta Pixel, Google Ads ta…。
请 fetch 以下地址读取 SKILL.md 并按文档完成安装：https://raw.githubusercontent.com/openclaw/skills/refs/heads/main/skills/danyangliu-sandwichlab/pixel-attribution-readiness-checker/SKILL.md
（来源：yingzhi8.cn 技能库）SKILL.md
---
name: pixel-attribution-readiness-checker
description: Validate event tracking and attribution readiness for Meta Pixel, Google Ads tags, TikTok Pixel, and cross-channel optimization.
---
# Ads Pixel Readiness
## Purpose
Core mission:
- pixel install checks, event integrity, attribution readiness
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
- this specific capability: pixel install checks, event integrity, attribution readiness
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
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