Taisly Agent Kit provides an AI-first solution for publishing short-form videos across major social media platforms like TikTok, Instagram Reels, YouTube Shorts, X, and Facebook. It targets developers and AI agents (e.g., Codex, Claude Code) seeking to automate content deployment without building individual platform integrations. The primary benefit is enabling AI-driven content creation workflows to seamlessly publish videos via a reliable, free-to-install SDK, CLI, and API.

How It Works

The kit leverages a JSON-first SDK, CLI, Agent Skill, and MCP server to offer a standardized workflow for AI agents. This approach abstracts complex platform integrations, enabling agents to manage account discovery, content validation, posting, and status checks through a predictable, safe JSON interface. This simplifies cross-platform video publishing and allows AI agents to focus on content creation and campaign logic rather than API intricacies.

Quick Start & Requirements

Install via npm: npm install -g @taisly/agent. Run commands using npx @taisly/agent. Requires Node.js/npm. Key resources include the Agent Kit page, API Docs, and GitHub repo.

Highlighted Details

• AI-first, free-to-install SDK for short-form video publishing.
• JSON-first workflow for AI agents: auth, platform discovery, validation, creation, status.
• Supports major platforms: TikTok, Instagram Reels, YouTube Shorts, X, Facebook.
• Includes Agent Skill and Codex plugin for seamless AI integration.
• Offers both local (stdio) and remote (HTTP) MCP server options.

Maintenance & Community

No specific details on maintainers, community channels (e.g., Discord, Slack), or roadmap are provided in the README. The project is hosted on GitHub.

Licensing & Compatibility

License type is not explicitly stated in the README. The package is described as 'free to install' and 'free AI-first posting,' suggesting a permissive model, but explicit terms for commercial use or redistribution are absent.

Limitations & Caveats

Not a video editor or social media dashboard. Requires Taisly account and connected social profiles. posts:status relies on recent history due to lack of a dedicated endpoint. Remote MCP requires public video URLs; local files necessitate CLI or local MCP. Media upload reuse is a future feature.