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/claude-code/schedule-video.md
View on GitHub# Claude Code Recipe: Schedule A Video Post
Use this recipe when the user asks Claude Code to schedule a short-form video through Taisly.
## Prompt Shape
```txt
Schedule ./demo.mp4 for tomorrow at 9 AM Bangkok time on my Instagram Reels and TikTok accounts.
Caption: "A quick demo of what shipped today."
```
## Steps
1. Discover connected accounts.
```bash
taisly platforms:list
```
2. Inspect constraints for the target platforms.
```bash
taisly platforms:schema --platform TikTok
taisly platforms:schema --platform Instagram
```
3. Convert the requested time to an explicit ISO timestamp.
```json
{
"video": "./demo.mp4",
"platforms": ["instagram_platform_id", "tiktok_platform_id"],
"description": "A quick demo of what shipped today.",
"scheduled": "2026-06-14T09:00:00+07:00"
}
```
4. Validate and ask for confirmation.
```bash
taisly posts:validate --json ./campaign.json
```
5. Create the scheduled post after confirmation.
```bash
taisly posts:create --json ./campaign.json
```
6. Report the returned `historyId` and scheduled time.
## Safety
- Always show the exact destination account names/IDs before scheduling.
- Do not silently change timezone.
- If the date is ambiguous, ask the user before creating the post.
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 |