taisly-social-media-posting
VerifiedConnect AI agents to Taisly through MCP to publish and schedule videos, inspect history, and manage reposts.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.5 KB |
| assets/taisly-agent-banner.jpg | binary | 131.1 KB |
| examples/campaign.json | config | 181 B |
| examples/claude-code/schedule-video.md | markdown | 1.2 KB |
| examples/codex/post-video.md | markdown | 1.3 KB |
| examples/cursor/post-build-demo-video.md | markdown | 1.2 KB |
| examples/post-video.shexecutable | script | 390 B |
| examples/schedule-video.shexecutable | script | 489 B |
examples/codex/post-video.md
View on GitHub# Codex Recipe: Post A Short Video Through Taisly
Use this recipe when the user asks Codex to publish a short-form video through Taisly.
## Preconditions
- `TAISLY_API_KEY` is set in the local environment.
- The video file exists locally.
- The user has connected social accounts in Taisly.
## Prompt Shape
```txt
Post ./launch.mp4 to my TikTok and YouTube Shorts accounts with this caption:
"New product update is live."
Ask me to confirm the destination accounts before publishing.
```
## Steps For Codex
1. Check authentication.
```bash
taisly auth:status
```
2. List connected accounts.
```bash
taisly platforms:list
```
3. Ask the user to confirm exact destination account IDs.
4. Create a payload file.
```json
{
"video": "./launch.mp4",
"platforms": ["platform_id_1", "platform_id_2"],
"description": "New product update is live."
}
```
5. Validate before posting.
```bash
taisly posts:validate --json ./campaign.json
```
6. Publish only after confirmation.
```bash
taisly posts:create --json ./campaign.json
```
7. Store and report the returned `historyId`.
```bash
taisly posts:status --id <historyId>
```
## Safety
- Do not invent platform IDs.
- Do not post to every connected account unless the user explicitly asks.
- Do not print `TAISLY_API_KEY`.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Unverified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |