---
name: socialblaze-api
description: Read SocialBlaze channels, prepare authorized organic posts and library templates, or analyze post performance using the SocialBlaze developer CLI, GraphQL or MCP.
---

Use the user's existing SocialBlaze developer credential from `SOCIALBLAZE_API_KEY`. Keep it out of command arguments, URLs, source files and logs. The CLI uses environment credentials by default. Only explicit `init --save-token` persists them in a global local file; use that only when the user asks to save their credential. Repository configuration cannot supply credentials or change the origin. `SOCIALBLAZE_API_ORIGIN` optionally selects the server. This skill does not itself authorize a new grant, publication, deletion or message.

Read the current contract at https://wp.socialblaze.ai/developer/llms.txt and https://wp.socialblaze.ai/developer/schema.graphql when the requested fields are unfamiliar. `socialblaze tools list`, `tools describe NAME` and `schema describe TYPE` discover the actual scoped contract; discovery uses API work allowance. Do not assume another product's field names or infer support from a network's brand name.

Use `socialblaze account`, `channels`, and `tools describe create_draft` to establish the selected destinations and current capabilities. Named calls accept `--json`, `--file` or `--stdin`. `--dry-run` validates advertised input without calling the mutation; it still performs remote discovery and cannot establish provider validation or delivery. Use the existing content library rather than inventing another content store.

Preserve a stable `requestKey` and unchanged input when retrying an uncertain write. A changed action needs a new key. Read the latest version before editing. After a timeout, stop and inspect the existing result or retry the same input according to the user's intent. Never rotate keys or switch credentials to increase allowance. For HTTP 429, honor `Retry-After`; there are no automatic write retries. GraphQL errors can accompany HTTP 200, and typed `try` mutations may return `MutationError` in data.

Prepare a draft or request review when the user has asked for preparation. Publish or schedule only within their authorization, selected channels and current native rules. `accepted` means submitted locally, not delivered: read each destination's status, published URL and safe failure details. Thread replies wait for confirmed parents. A manual reminder or user-entered confirmation is not a provider delivery receipt. Do not repeat an ambiguous provider submission with a new request key.

For reporting, read [references/reporting.md](references/reporting.md). Inspect the deployed schema for `storedChannelAnalytics` before an existing-data-only request; older report reads can start collection. On the stored-only contract, refresh requires the separate explicit action and user intent. State the time range, timezone, counting basis, chosen metric and each network's coverage. Never turn unavailable data into zero or partial history into an exact total.

Templates retain native plan and role boundaries. `internal` is the existing workspace-shared default; explicit `private` templates are creator-only. Edits need the latest version and preserve omitted metadata. Public curated templates are not offered. No skill instruction grants access to another member's private content.

Content-group reads default to integration-owned discovery. Use explicit `discovery:workspace` on `list_content_items` / `get_content_item` (SDK `contentItems` / `contentItem`) only when the credential separately includes both `content:read` and `posts:read`; do not request or broaden a grant automatically. Native tenant, draft and selected-channel visibility still apply; native unassigned drafts are creator-only. Groups containing inaccessible destinations are excluded rather than revealing common captions or media. `managedByCurrentIntegration` records creator/connection ownership, not a permission grant. Cross-integration GROUP writes stay blocked, and individual post changes retain their independent authorization. Reset pagination when changing discovery.