posteyai/skills · Archived

postey-video

Turn one video into posts everywhere with Postey: transcribe it, write a caption per platform, upload with a cover frame, and leave drafts ready for approval. Handles local files and large uploads, which the MCP server cannot reach.

Installation

$ npx skills add posteyai/skills --skill postey-video

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Also in this package

Other skills from posteyai/skills.

npx skills add posteyai/skills

Browse all from posteyai/skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 6
License LICENSE
Default branch main
Open issues 0
Status Archived

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.0.2
Allowed toolsBash(${CLAUDE_SKILL_DIR}/scripts/postey.js:*)

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 4,067 B
  • docs SUMMARY.md 252 B

History

  1. First recorded snapshot · 5 installs

SKILL.md

Postey Video

One video becomes a caption per platform and a draft per account. Nothing publishes without the user's explicit approval, and scheduling counts as publishing.

Why this ships its own CLI

scripts/postey.js here is a byte-identical copy of the hub's, verified by scripts/check-script-parity.js. A skill cannot rely on the path to another skill's directory — no install layout guarantees one — so the copy travels with the pack. The consequence is that this skill and the hub version-bump together whenever the CLI changes.

capability-snapshot.json sits beside it because postey.js requires it at runtime for the platform list. A copy without it crashes on require.

Routing

Situation Path
A local video or image path CLI, unconditionally — MCP cannot see the user's disk
Transcription CLI (video transcribe); transcribe_video when your client has no shell
Large or chunked upload CLI — the MCP inline path is context-bound
Creating or updating the draft MCP (createpost / updatepost) — always, even after a CLI upload

The CLI stops at the upload and hands back the fields for the MCP write. It never creates the draft itself.

Workflow

  1. Read the accounts — postey://accounts, or get_accounts if your client cannot read

resources. Never assume which platforms are connected.

  1. Transcribe if there is no caption yet. Never paste a raw transcript as a caption.
  2. Write one caption per platform from the transcript. Craft rules come from the hub:

caption-playbook.md, hook-formulas.md, platform-archetypes.md and thread-and-video-formats.md. If a brand profile exists, its voice and banned lists apply.

  1. Upload via the CLI, taking the cover frame with it.
  2. Create the draft through MCP, then attach each additional platform with update_post on

the same post_id.

  1. Validate each platform with validatepostcontent, fix, then present the share link.

Reference

  • Full transcription and cross-post workflow: [video-workflow.md](video-workflow.md)
  • The video-everywhere content flow: [references/video-to-everywhere.md](references/video-to-everywhere.md)