---
name: meta-publishing-stinger
description: "Prepare and preflight exact Meta publishing, scheduling, queue and review actions through canonical Foundation guards, then reconcile per-target provider readback."
license: AGPL-3.0-or-later
compatibility: "Claude Code, Cursor, ChatGPT Codex, Claude Cowork; Python 3.11+ for offline manifests"
metadata:
  hive-tier: specialist
  hive-drone: meta-publishing-wasp-drone
  version: "0.1.0"
  author: "Legion Code Inc."
---

# Meta Publishing

Start with [README.md](README.md). Own the exact provider-action boundary and per-target readback. The included helpers prepare and validate local data only; they are not a network executor. No installation or actual publishing readiness is inferred from these source files.

## Procedure

1. Resolve actual selected Foundation, CTR-001 revision1 / schemaVersion1.0.0 and its B03 operation/guard helper. Obtain the approved draft revision, exact profile/account/platform and current identity/readiness evidence. Organic scope has a null native Ads ID.
2. Follow [prepare-manifest](guides/prepare-manifest.md). Choose explicit draft, immediate, future schedule, native pending approval, queue or review. Prepare one guarded target per frozen scope, exact asset hashes and a saved per-logical-post idempotency key.
3. Show exact content, media, destination, state, time/timezone and effects. Draft mode cannot carry scheduling flags; queues use provider slot locking. An elapsed native approval can publish shortly and must appear in the reviewed effects.
4. Follow [preflight-action](guides/preflight-action.md). Validate both shared artifacts, independently authenticate the decision, recheck current state and bytes, and delegate to canonical B03 qualification/guards. Missing headers/transport/operation blocks that action; never extract connector credentials or invent a tool.
5. A passing offline precondition still says executionAuthorized:false. Only the selected host execution owner may perform the exact already authorized provider operation through a qualified transport. If that exact authorization already exists, continue without redundant approval.
6. Follow [readback-and-recovery](guides/readback-and-recovery.md). Preserve IDs and pending state; reconcile the same post instead of recreating it. Distinguish each target's success/failure and provider reports from separate public observation.
7. Record the exact outcome, hashes, evidence and any cleanup/recovery handoff. Do not call partial, scheduled or pending a public post. Cleanup, editing and unpublish have their own supported operation and action scope.

## References

- [Publishing contract](references/publishing-contract.md) and [synthetic manifest template](templates/manifest-request.json).
- [Fresh domain research](references/research/distilled-research.md) and [source qualifications](references/research/source-conflicts.md).
- Offline entry point: `python -B -m scripts.publishing` from this skill directory. Host callbacks are trusted integration code, never user-supplied JSON assertions.

## 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-content-stinger](../meta-content-stinger/SKILL.md) - Briefs, calendars and draft versions before delivery.