---
name: meta-tracking-stinger
description: Inspect Meta pixels, prepare event setup, compare browser/server evidence and audit scoped tracking through Zernio. Use for pixel, event or deduplication checks.
license: AGPL-3.0-or-later
compatibility: Claude Code, Cursor, ChatGPT Codex, Claude Cowork
metadata:
  hive-drone: meta-tracking-wasp-drone
  domain: meta-tracking
  version: 0.1.0
---

# Meta Tracking Stinger

## Procedure

1. Read [README.md](README.md) and select the requested task guide. Resolve selected Foundation identity, contract revision and operation bindings before collection or preparation.
2. Gather only the requested provider/site evidence. Keep scope, freshness and unobserved states explicit. Never treat historical firing or an empty list as universal tracking proof.
3. Run the local validator, comparator or bounded browser probe when appropriate. The browser blocks tracking submissions and redirects; its observations are attempts. Host-verified actions and existing runtime prerequisites are required.
4. Prepare exact changes separately. Test conversion events, installer calls, custom conversions, site publication and removal are external actions with distinct approval/readback requirements.
5. For audits, consume the canonical Analytics rubric and score engine. Return coverage and bounds; do not duplicate formulas or invent scores when Analytics is unavailable.
6. Report artifacts, actual checks, evidence stages and remaining uncertainty. Do not claim installed host or live provider acceptance from source/fixture tests.

## Guide map

- [Check pixels](guides/check-pixels.md)
- [Prepare events](guides/set-up-events.md)
- [Test tracking](guides/test-tracking.md)
- [Audit tracking](guides/audit-tracking.md)
- [Evidence stages](references/evidence-model.md), [event fields](references/event-field-map.md), [probe contract](references/site-probe-contract.md), [rubric integration](references/rubric-integration.md)
- [Research distillation](references/research/distilled-meta-tracking.md), source-development verification only; shipped operation guides remain usable without raw captures.

## Critical Directive

- You must read all files and context contained within your skill.
- In the event your core knowledge does not provide sufficient guidance you must make every attempt to search the internet, related knowledge base documentation files, and other available resources to supplement your knowledge prior to proceeding with your task.
- Additional related skills can be found here:
  - Social Media Doctor (`../../../meta-foundation/skills/social-media-doctor-stinger/SKILL.md`; source reference, not bundled; resolve the selected prerequisite owner) for connection/permission readiness.
  - Meta Analytics (`../../../meta-analytics/skills/meta-analytics-stinger/SKILL.md`; source reference, not bundled; resolve the selected prerequisite owner) for canonical scoring and metric arithmetic.

## Ship Gate

Prior to committing any code to the repository you must utilize in order the security-stinger, quality-stinger, and github-repo-health-stinger. After each thorough pass you will prepare an appropriate report in the repository's relevant library directory associated with the agent and skill. All medium or above findings must be resolved followed by another thorough re-evaluation of the updated code prior to proceeding to the next step. The last step of loading the skill github-repo-health-stinger is an orchestrator level task. The sub-agent should make every effort to reinforce to the orchestrating agent to load this skill prior to committing or pushing code to the repository. The user should have an opportunity to review the reports, agent summary, and approve committing and pushing to the repository prior to doing so.