---
name: meta-audiences-stinger
description: "Prepare Meta customer, website, lookalike, engagement and saved-targeting audiences; validate IDs and private member changes before approved Zernio actions."
license: AGPL-3.0-or-later
compatibility: "Claude Code, Cursor, ChatGPT Codex, Claude Cowork"
metadata:
  hive-tier: specialist
  hive-drone: meta-audiences-wasp-drone
  component-version: "0.1.0"
---

# Meta Audiences

Own audience source/type/identity validation, private member preparation and specifically approved Zernio audience changes. Produce minimal aggregate receipts, without shipping personal identifiers or treating acceptance as matched readiness.

## Procedure

1. Read [README](README.md), the selected guide and [operation boundaries](references/operation-boundaries.md). Resolve Foundation and the exact selected Core prerequisites before acting.
2. Select the exact brand/profile/account/native object and user-requested scope. Keep preparation, provider reads, jobs/imports and writes distinct. Preserve valid session approval; do not re-ask solely because another coordinated owner relayed it.
3. Use the frozen Foundation artifacts schemaVersion 1.0.0 and contractRevision 1 where applicable. Validate shape offline, then independently verify scope, evidence, exact revision/hash, approval source and current before-state.
4. Use Foundation's canonical current operation registry and offline qualifier/parser/guard. Domain fragments are evidence, not an alternate dispatcher. An absent, malformed or unconfirmed contract remains blocked.
5. Run the relevant offline helper from this skill directory with `python -m scripts.audience_preflight` and a private local input file. It makes no provider call and does not grant execution authority.
6. Carry out only an explicitly scoped and qualified provider operation when the user's exact approval covers its effect. Otherwise finish the local report/proposal with the blocker. Never loop automatic writes.
7. Retain requested/covered scope, missing/partial/unknown results and meaningful readback. Save private artifacts in the Foundation brand workspace and report what was performed, verified and blocked.

## Guide map

- [Select and prepare the exact Meta audience branch](guides/build-an-audience.md)
- [Review private customer-list add/remove batches](guides/member-changes.md)
- [Inspect status or prepare a qualified update/delete](guides/inspect-and-maintain.md)

## References

- [Offline helper](references/local-helper.md): contract, input/output and evidence limits.
- Source fragments (`../../../meta-foundation/references/zernio-operations.json`; source reference, not bundled; resolve the selected prerequisite owner): exact source evidence for Foundation integration; not invocation authority.
- [Research distillation](references/research/distilled-meta-audiences.md): domain claims, conflicts and version limits. Raw research is source-only provenance.
- [Paired Drone](../../agents/meta-audiences-wasp-drone.md): focused execution owner.

## 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-advertising-stinger](../meta-advertising-stinger/SKILL.md) - Related specialist; route its owned work separately.
  - [meta-ad-research-stinger](../meta-ad-research-stinger/SKILL.md) - Related specialist; route its owned work separately.

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