---
name: meta-commerce-stinger
description: "Audit Meta catalogs, products and feeds, and prepare reviewed product or store-sync changes through Zernio. Use for catalog validation, feed outcomes and commerce issues."
license: AGPL-3.0-or-later
compatibility: "Claude Code, Cursor, Codex, Claude Cowork; selected Foundation and approved Python runtime"
metadata:
  hive-tier: specialist
  hive-drone: meta-commerce-wasp-drone
  domain: meta-commerce
---

# Meta Commerce Stinger

Audit selected catalogs, prepare precise product changes and explain feed/sync outcomes with actual evidence. Own the four Commerce task procedures and local validation/export. Keep advertising and website tracking with their existing owners.

## Procedure

1. Resolve the selected Core router, Foundation and exact workspace/profile/account/catalog/store context. Load [the guide map](README.md) and choose the requested verb.
2. Apply [identity and field rules](references/catalog-fields.md) and [operation effects](references/operations-and-effects.md). Missing `catalog_management`, incomplete data and unqualified verticals stay explicit.
3. Collect only requested read evidence or use a saved private snapshot. Run [the offline helper](references/offline-helper.md) for audit, processing interpretation, safe CSV or unapproved draft preparation.
4. For a provider change, prepare the exact payload and meaningful verification plan through Foundation. Reuse a matching valid user decision; otherwise request review of the concrete result. The helper never performs a provider request or grants authority.
5. Preserve IDs/handles and source coverage; distinguish accepted, pending, clean success and partial/unknown outcome. Do not blind-retry a create/import or claim stopping a sync removed products.
6. Return the private artifacts, actual checks, limitations and next owner. Keep source/fixture evidence distinct from host/account acceptance.

## References map

- [README.md](README.md): command-to-guide routing and current permission boundary.
- [Catalog audit](guides/audit-catalog.md), [product updates](guides/review-product-updates.md), [feed check](guides/check-product-feed.md), [issue report](guides/report-catalog-issues.md), [advanced sync review](guides/review-store-sync.md).
- [Fields](references/catalog-fields.md), [effects](references/operations-and-effects.md), [offline helper](references/offline-helper.md): load before their corresponding work.
- [Commerce research distillation](references/research/distilled-commerce.md): current source-grounded contract and open gaps; raw archives are source-only, not runtime prerequisites.
- `scripts/catalog_tools.py`: offline audit, status, unapproved draft and safe CSV module. No network transport.
- [Paired specialist](../../agents/meta-commerce-wasp-drone.md): persona, ownership and reporting boundary.

## 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:
  - [Foundation routing and operation handoff](references/operations-and-effects.md) explains how to resolve the selected router, shared artifacts and provider policy. Do not substitute a cached source for an unavailable prerequisite.

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