BulkPublish Handoff

SkillProductivity

Prepare an approved social content queue for BulkPublish scheduling or publication. Use when "schedule social posts", "publish the calendar", "send posts to BulkPublish", or "hand off approved social content".

Use BulkPublish Handoff in Claude, ChatGPT or Ahel Desktop

Free. Sign in, add BulkPublish Handoff and connect your AI. About a minute.

Also: Claude Code · Cursor · Codex

Then ask your AI: use the BulkPublish Handoff skill

Details

Instructions available. Your AI can read the instructions. Execution depends on the setup they require.

Add Ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.

BulkPublish HandoffStart free

What this skill tells your AI

The instructions your AI receives, as published by cgallic/kai-cmo-harness in harness/skills/kai-bulkpublish/SKILL.md and read by Ahel’s review.

Use this skill after /kai-social, /kai-repurpose, or another content workflow has produced a reviewed calendar. This skill prepares the handoff; it does not bypass approval or silently publish.

Inputs

  • Approved social post calendar with platform, content, media, and links
  • BulkPublish channel IDs or names
  • Desired schedule and IANA timezone
  • Approval status and the person authorized to publish

Workflow

  1. Confirm every post has an explicit approval state and remove anything still in draft or rejected status.
  2. Validate each platform’s character, link, media, and format requirements.
  3. Resolve channel IDs with BulkPublish list_channels; never infer IDs from names alone.
  4. Create drafts or approval-gated scheduled posts through the BulkPublish API or MCP server.
  5. Before any external publish action, show the final post count, channels, media, and schedule and obtain immediate authorization.
  6. Record returned post IDs, status, schedule time, and any per-platform failures in the campaign record.
  7. After publication, use BulkPublish analytics to compare outcomes with the campaign objective without promising reach, engagement, or revenue.

Safety gates

  • Treat scheduling and publishing as external side effects.
  • Never expose API keys, cookies, or private analytics in content or logs.
  • Stop if the audience, account, channel, media, or schedule is ambiguous.
  • Do not claim guaranteed engagement, virality, conversions, or revenue.

References

Signals

GitHub stars
54
Forks
8
Last commit
Oct 2026
Advanced
Item type
skill
Key
kai-bulkpublish
Source
github.com/cgallic/kai-cmo-harness