AgentKit
DocsKitsCLI ReferenceDesktop App

Skills

Create and schedule social drafts with ak:social

Produce platform-aware social content and schedule artifacts with ak:social while keeping credentials, account changes, and publishing separately approved.

Use ak:social to create platform-aware posts, threads, carousels, stories, or reels, or to build a weekly, monthly, or campaign schedule. The Skill includes reference workflows for provider APIs, but its bundled scheduling script only previews a queued post; actual publishing requires a separate integration.

Choose ak:social for channel-ready drafts and plans

Use ak:social when

  • You have approved audience, message, proof, brand voice, channel, and CTA.
  • You need content for twitter/x, linkedin, instagram, tiktok, youtube, facebook, or threads.
  • You need a post, thread, carousel, story, or reel draft.
  • You need a schedule for a week, month, or named campaign.

Choose another workflow when

  • You still need positioning, content pillars, or campaign strategy.
  • You need a live community-management response involving safety, moderation, legal, or crisis escalation.
  • You want the assistant to authorize OAuth, spend money, publish, delete, comment, repost, or change a live account. Those are separate external actions.

Prepare content and authority inputs

Confirm Marketing Kit is installed for the current runtime and scope. Provide the target platform, content type, audience, objective, verified claims, brand rules, CTA, media paths, account owner, timezone, campaign dates, and whether the output is draft-only. For a schedule, provide the actual content inventory or topics and team capacity.

Current platform policies, formats, disclosure rules, quotas, and API versions can differ from bundled references. Verify them against official provider documentation before approval or implementation.

RuntimeInvocationAvailability boundary
Claude Code/ak:social ...Native delivery is the default; provider actions still require configured credentials and explicit approval.
Cursor/ak:social ...The Skill is projected to Cursor and slash invocation is user-verified; no account connection is implied.
Codex$ak:social ...The Skill uses native Codex discovery; supported local drafting does not establish provider API parity.

Create a draft or schedule

/ak:social linkedin post "Draft a launch post from the approved release brief. Cite the source internally, avoid unverified results, and do not publish"

The canonical input shape is [platform] [type] OR [schedule]. The schedule route accepts week, month, or campaign [name].

Understand the stages

  1. Confirm channel and objective. Capture platform, content type, audience, desired action, source evidence, and account boundary.
  2. Load brand context. Apply approved voice, terminology, visual direction, prohibited claims, and disclosure requirements.
  3. Draft for the platform. Structure the requested post type and propose hashtags, hook, CTA, and media treatment without assuming they will perform.
  4. Validate the artifact. The bundled validator can check its embedded text and media rules for supported platforms; these checks may be stale and are not provider acceptance.
  5. Plan timing when requested. schedule creates markdown schedule and calendar artifacts. The bundled schedule-post.js prints a preview and explicitly states that actual posting requires API integration.
  6. Return evidence and approvals. Report files, sources, validation warnings, proposed times, timezone, and every external action still pending.

Keep provider effects behind a separate gate

API examples can change live accounts

Provider reference workflows include OAuth scopes and write calls that can upload media, publish posts, reply, comment, or repost. Do not execute them from a drafting request. Confirm the exact account, content, visibility, credentials, current provider contract, and human approval immediately before any external call.

Never expose tokens in prompts, logs, or content artifacts. Review privacy, copyright, endorsements, sponsorship and AI-content disclosures, community rules, and moderation risk. A unified API service can add cost and another data processor; approve that provider relationship separately.

Verify outputs and evidence

Normal drafts go to assets/posts/{platform}/{date}-{slug}.md. The schedule route writes assets/posts/schedule-{period}.md and can add assets/posts/calendar-{period}.md.

A complete result identifies the platform, content type, sources, brand rules, media, timezone, proposed time, validator version or assumptions, and publish status. For an actual provider action, require a returned platform post ID or URL and inspect the live result; a local “scheduled” preview is not evidence of remote scheduling or publication.

Troubleshoot and know the limits

SymptomSafe next step
A platform limit or format conflicts with the providerTreat the provider's current official documentation and API response as authoritative.
The scheduler says pendingThis is the local preview object, not remote state; configure and approve a separate integration if needed.
Media validation passes but upload failsRecheck the current account, MIME type, size, duration, provider permissions, and API response.
A token or rate-limit error occursStop repeated calls, protect the token, follow provider recovery guidance, and avoid guessing retry limits.
The draft includes an unsupported claim or fake trendRemove it or attach current evidence before approval.
Runtime discovery failsFollow Runtime cannot find a Skill or Agent.

The Skill cannot guarantee reach, engagement, virality, conversion, provider acceptance, or that bundled platform data remains current. Continue with the Marketing Kit overview, keeping every live account effect in a separately authorized workflow.