Social Media Publisher

# Social Media Publisher

Use this skill to create, update, list, delete, schedule, or publish social
posts through the PostPlus-managed social publishing workspace.

Apply shared rulebook, approval, and user-guidance rules from `postplus-shared`.

## Ownership And Auth Boundary

PostPlus holds the platform-owned social publishing workspace. End users do not
need separate publishing-service accounts and should not provide third-party
publishing-service credentials to the agent.

Channel onboarding uses the PostPlus invite-link path:

1. PostPlus Cloud creates an invite link for the target social platform.
2. The user authorizes their social account on the platform OAuth screen.
3. The resulting channel token lands in the PostPlus social publishing
   workspace.
4. PostPlus labels the channel with the user's PostPlus account id.

Scripts receive PostPlus-hosted request envelopes and customer config files,
not hidden server credentials.

## Safe Default

the local request, enforces the integration allowlist, writes a preview
envelope, emits an approval request, and does not call the remote publishing
service.

Actual remote mutation requires:

- `--execute`,
- `--approval-file <approved.json>`,
- an onboarded and allowed integration id,
- current entitlement or channel evidence for publish-like operations.

or publishing an existing draft.

## Required Input

- A hosted capability request JSON with `capability: "social-publishing"`,
  a supported `operation`, `operationId`, and publishing `input`.
- A bare customer config JSON with `allowedIntegrationIds` at the top level.
- Workspace/account identity, integration id, content/media, and post or group
  ids required by the selected operation.

Do not wrap the customer config in the hosted capability request.

## Default Workflow

1. Confirm the channel was onboarded through the invite-link flow.
2. List integrations to confirm the exact integration id.
3. Build the hosted capability request and bare customer config.
4. Keep reviewable work in `draft` unless the user explicitly approves
   scheduling or publishing.
   approval and current channel evidence.

## User-Facing Blockers

Stop and explain when:

- no PostPlus auth/session is available,
- the channel was not onboarded through the invite-link flow,
- the integration id is missing or not in `allowedIntegrationIds`,
- required content, media, post id, or group id is missing,
- approval or quote confirmation is required,
- entitlement or current channel evidence is missing for a publish-like action,
- the hosted service returns a stable product error.

Do not expose server-side implementation names or ask for third-party publishing-service
credentials. Do not bypass quote confirmation or approval boundaries.

## Handoff

Return structured preview/result JSON, the approval or quote-confirmation
command when required, or the exact product error and next boundary.

## Public Command Boundary

- Choose the smallest matching command or workflow from the user input and run
  it directly.
- Readiness diagnostics: `postplus doctor --skill social-media-publisher`.
- If an owned CLI or script command fails, report the exact error and stop. Do
  not bypass the failure with metadata-only answers, readiness probing, local
  payload rewrites, fallback providers, or unpublished tools.
- Use `postplus publish schema --json` only when constructing or repairing an unknown request shape.
- Hosted publishing capability: `postplus publish capability --request <hosted-capability-request.json> --output <result.json>`.
- Preview and approval boundaries stay explicit; do not execute irreversible publishing without the required approval artifact.
- If the CLI returns a quote-co