---
name: meta-leads-stinger
description: "Export scoped Meta leads privately and prepare form or status handoffs through Zernio. Use for cursor-complete lead exports, identity checks and private handoff ledgers."
license: AGPL-3.0-or-later
compatibility: "Claude Code, Cursor, ChatGPT Codex, Claude Cowork; qualified Zernio MCP and Python artifact runtime"
metadata:
  hive-tier: specialist
  hive-drone: meta-leads-wasp-drone
  domain: meta-community
  version: "0.1.0"
  author: "Legion Code Inc."
---

# Meta Leads

## Purpose

Normalize verified lead captures and produce a private, CSV-safe export, coverage manifest and handoff summary. Export never changes status, creates a form or contacts a person.

## When to use

Use when the user's task matches this skill's guide map and the selected account/profile has the required capability. Validate current provider contracts and report unavailable capabilities rather than inferring access from a tool name.

## When not to use

Inbox review and replies belong to meta-community-stinger. Ads optimization consumes aggregate business outcomes through its own pipeline. Do not upload customer lists, send messages, activate lead workflows or infer legal consent from a stored field.

## Procedure

1. Resolve the selected Core router and Foundation prerequisites and bind exact profile/account, form/Page, time and field scope.
2. Read the task guide and current distilled provider contract. Reject unfiltered all-team defaults and unresolved cross-Page access.
3. Collect documented lead pages with stable filters and opaque cursors into a private capture; record actual source and freshness.
4. Use the offline helper to verify evidence hashes, account/form scope, cursor completion, duplicate identity and missing/null/empty fields.
5. Export only to the selected private workspace. Require an explicit partial-export choice when coverage is incomplete; never mark an incomplete collection complete.
6. Present only counts and coverage in shareable output. Keep row-level answers/consents/identifiers private and handle form/status/test-lead changes as separately approved proposals.

## References map

- [Guide map](README.md)
- [Task guide: export-leads](guides/export-leads.md)
- [Task guide: forms-and-status](guides/forms-and-status.md)
- [Provider research](references/research/distilled-leads.md)
- Shared Foundation contracts (`../../../meta-foundation/contracts/README.md`; source reference, not bundled; resolve the selected prerequisite owner)
- [scripts/lead_tools.py](scripts/lead_tools.py) for offline artifact preparation; the helper makes no provider call.

## 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:
  - [meta-community-stinger](../meta-community-stinger/SKILL.md) - The paired community/lead domain handoff.

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