by taisly
Taisly Agent Kit: MCP server, CLI, SDK, and agent docs for publishing videos to TikTok, Reels, Shorts, X, and Facebook.
# Add to your Claude Code skills
git clone https://github.com/taisly/agentGuides for using ai agents skills like agent.
Last scanned: 7/6/2026
{
"issues": [],
"status": "PASSED",
"scannedAt": "2026-07-06T08:19:26.940Z",
"npmAuditRan": true,
"pipAuditRan": true,
"promptInjectionRan": true
}See how agent compares with popular alternatives.
agent is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by taisly. Taisly Agent Kit: MCP server, CLI, SDK, and agent docs for publishing videos to TikTok, Reels, Shorts, X, and Facebook. It has 222 GitHub stars.
Yes. agent passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.
Clone the repository with "git clone https://github.com/taisly/agent" and add it to your Claude Code skills directory (see the Installation section above). agent ships a SKILL.md manifest, so compatible agents can discover and load it automatically.
agent is primarily written in JavaScript. It is open-source under taisly on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh agent against similar tools.
No comments yet. Be the first to share your thoughts!
From $49 · 30 days · terms & refunds
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM lists this project for discovery and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
Automated security scan — not a certification.
Full documentation: https://docs.taisly.com/docs/mcp
Prefer the existing Taisly MCP connection. OAuth already provides access; do not install the package, request an API key, or run local setup/checkin tools when remote MCP is available.
If it is not connected, help the user add https://app.taisly.com/mcp as a remote Streamable HTTP MCP server with OAuth in a compatible client. Client settings or workspace policies may require human action. After authorization, refresh tools according to the client's instructions.
taisly_auth_status and taisly_platforms_list. An empty account list is not a login failure.connectUrl from taisly_platform_connect_start, wait for browser approval, then check connection.taisly_platform_schema and validate the public video URL, caption, destinations and schedule with taisly_posts_validate.taisly_posts_create with confirmed: true.historyId and check taisly_posts_status. Accepted is not published; report each destination's PENDING, SUCCESS or FAILED result accurately. A scheduled post has not yet been published.Only call tools advertised by the server. Remote MCP does not expose taisly_agent_setup_start or taisly_agent_checkin. Never print credentials. If access expires, use the client's OAuth reconnect action, not CLI installation or an API-key fallback. Do not blindly retry creation after a timeout; check history first.
Remote MCP cannot read local files or private chat attachments. Ask for a public downloadable video URL. If the user explicitly needs a local-file workflow, explain the optional local MCP or CLI package before installing anything.
Package guide: https://docs.taisly.com/en/docs/agents/agent-kit REST API: https://docs.taisly.com/en/docs/api
API keys and the npm package are developer alternatives, not prerequisites for remote MCP.

Free AI-first social media posting for short-form video. Taisly Agent Kit is a JSON-first SDK, CLI, Agent Skill, and MCP server that lets AI agents, developer tools, and automation workflows publish videos to TikTok, Instagram Reels, YouTube Shorts, X, Facebook, and other connected social platforms through Taisly.
Use it when your agent can create content, write captions, or prepare a campaign, but still needs a reliable video publishing API to put that content online. The package is free to install and designed to get an agent from idea to published video without building every platform integration yourself.
Website | Agent Kit | API Docs | npm | GitHub | MCP Registry | Glama | Guide
Read this guide in: English, Español, Deutsch, Français, Português, ไทย, 中文, Bahasa Indonesia, Русский, Nederlands, 한국어, 日本語, العربية, Türkçe, Polski.
Taisly handles the connected accounts and posting execution. Your agent handles planning, caption writing, campaign logic, or workflow orchestration.
No credit card is required to get started. Paid plans are for teams and workflows that need more scale.
This package includes the Taisly Social Media Posting Skill in SKILL.md. Use it with Claude Code, Codex, Cursor, OpenClaw, and other agents when you want the agent to understand the safe posting workflow before it touches live social accounts.
Recommended skill workflow:
auth -> platforms -> validate -> confirm -> create -> status
The skill tells agents to discover connected accounts, validate the post, ask for explicit user confirmation, create the post, and save the returned historyId for status checks.
This package includes a Codex plugin manifest in .codex-plugin/plugin.json. The plugin points Codex to the canonical SKILL.md file and the official remote MCP server:
https://app.taisly.com/mcp
Use the plugin when you want Codex to discover both the posting workflow instructions and the Taisly MCP tools from one package. The root SKILL.md is the single source of truth for the agent workflow.
Remote MCP is the default AI-agent connection. If Taisly tools are already available, call taisly_auth_status and taisly_platforms_list directly. OAuth provides access; do not install this package or ask for an API key for that connection.
Help me connect Taisly to this agent using the setup guide. Check access and list my connected social accounts. Do not publish anything during setup.
Full documentation: https://docs.taisly.com/docs/mcp
The remote server URL is https://app.taisly.com/mcp. Add it through your client's remote MCP and OAuth settings if needed. Human authorization or administrator approval may be required. On expiry, reconnect through OAuth rather than switching to the CLI.
Use the following package instructions for explicit SDK, CLI or local-file workflows. They are not remote MCP setup requirements.
npm install -g @taisly/agent
Or run it without a global install:
npx @taisly/agent help
Start the stdio MCP server:
npx @taisly/agent mcp
For local development inside this repository:
node packages/agent/src/cli.js help
For the local package, browser setup can store a local credential without manually copying an API key. Use any short agent slug, for example claude-code, codex, cursor, windsurf, openclaw, hermes-agent, cline, or aider.
Help me set up Taisly Agent Kit.
1. Install the CLI: npm i -g @taisly/agent
2. Run taisly setup --agent <agent-slug> and send me the login URL so I can finish authentication.
3. Wait for me to finish login in the browser.
4. Run taisly checkin --agent <agent-slug>.
5. Tell me if Taisly is connected and ready. If not, tell me what failed.
If you cannot install or run the Taisly CLI in this environment, stop and tell me to open Taisly Settings instead.
The setup command stores a local Taisly agent credential, so later CLI and MCP commands can run without manually copying an API key.
Manual fallback: create an API key in Taisly Settings, then set:
export TAISLY_API_KEY="taisly_..."
Advanced: by default, the browser setup stores the local credential in ~/.taisly/config.json. Most users should not change this. Set TAISLY_CONFIG_HOME=/path/to/dir only for CI, tests, or isolated agent profiles that need a separate credential store.
List the connected social accounts available to the API key:
taisly auth:status
taisly platforms:list
Connect a social account from an AI-agent flow:
taisly platforms:connect:start --platform instagram
# Open the returned connectUrl and finish authorization in the browser.
taisly platforms:connect:check --platform instagram
taisly platforms:list
Supported connect slugs: instagram, tiktok, youtube, x, facebook.
Validate a local video before publishing:
taisly posts:validate \
--video ./launch.mp4 \
--platforms platform_id_1,platform_id_2 \
--description "Launch day"
Publish now:
taisly posts:create \
--video ./launch.mp4 \
--platforms platform_id_1,platform_id_2 \
--description "Launch day"
Schedule for later:
taisly posts:create \
--video ./launch.mp4 \
--platforms platform_id_1,platform_id_2 \
--description "Launch day" \
--scheduled "2026-06-14T09:00:00+07:00"
Check the returned post:
taisly posts:status --id <historyId>
Discover supported options and accepted values for each destination platform:
taisly platforms:schema --platform TikTok
taisly platforms:schema --platform YouTube
Group options by platform name in settings. For example:
taisly posts:create \
--video ./launch.mp4 \
--platforms your_tiktok_platform_id,your_youtube_platform_id \
--description "Product walkthrough" \
--settings '{"TikTok":{"status":"PUBLIC_TO_EVERYONE"},"YouTube":{"title":"Product walkthrough","status":"unlisted"}}'
With --json, put the same object in the input file's settings property. SDK
calls accept settings as an object. For remote or local MCP, discover options
with taisly_platform_schema and pass settings to both taisly_posts_validate
and taisly_posts_create. The HTTP API accepts a JSON-encoded settings form field.
| Platform | Settings | Meaning |
|---|---|---|
| TikTok | status |
PUBLIC_TO_EVERYONE, MUTUAL_FOLLOW_FRIENDS, FOLLOWER_OF_CREATOR, or SELF_ONLY, subject to the account's available visibility options. |
| TikTok | comment_disabled, duet_disabled, stitch_disabled |
Boolean switches; true disables the interaction. |
| TikTok | brand_content_toggle |
Boolean; discloses a paid partnership promoting a third-party business. Cannot be combined with SELF_ONLY. |
| TikTok | brand_organic_toggle |
Boolean; discloses promotion of the creator's own business. Both brand switches may be enabled together. |
| TikTok | is_aigc |
Boolean; true enables the native AI-generated content label. Omit to keep existing behavior, or explicitly pass false. |
| YouTube | title |
Optional video title, up to 100 characters. Omit to use the post caption. |
| YouTube | status |
public, private, or unlisted. |
For example, a public TikTok post promoting your own business and an unlisted YouTube post with its own title can share one request:
{
"settings": {
"TikTok": {
"status": "PUBLIC_TO_EVERYONE",
"brand_organic_toggle": true,
"comment_disabled": false
},
"YouTube": {
"title": "Product walkthrough",
"status": "unlisted"
}
}
}
These settings work with