taisly-social-media-posting — Claude Code skill: install & use
Connects your AI agent to Taisly over MCP to schedule and publish video posts, inspect upload statuses, and manage automated repost rules.
npx skills add taisly/agent --skill taisly-social-media-posting -a claude-codeWhat taisly-social-media-posting does
This skill guides agents through publishing to social platforms via the remote Streamable HTTP MCP server at https://app.taisly.com/mcp. Authentication runs over OAuth without requiring local API keys or npm package installations. The agent verifies login state using taisly_auth_status and matches destination IDs returned by taisly_platforms_list.
Before submitting any post, the agent checks destination schemas and validates caption, schedule, and targets using taisly_posts_validate. Creating a publication via taisly_posts_create requires explicit user confirmation. Afterwards, it tracks progress through taisly_posts_status with the returned historyId to report pending, successful, or failed states.
Remote MCP cannot read local files or private chat attachments directly. Any video you want to publish must be hosted at an accessible downloadable link.
What it helps with
- schedule video posts across multiple social platforms
- check post delivery status with
taisly_posts_status - configure automated repost rules between accounts
- connect external social profiles using the
connectUrllink
Example prompts for the agent
- Check my Taisly authorization status and list connected platforms
- Schedule a video post using a public URL for tomorrow at noon
- Inspect the delivery status of the recent post by its history ID
How to install taisly-social-media-posting
1Skills CLI (Vercel)
npx skills add taisly/agent --skill taisly-social-media-posting -a claude-code2Manually: put the files in place
~/.claude/skills/taisly-social-media-posting/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/taisly-social-media-posting/
1Skills CLI (Vercel)
npx skills add taisly/agent --skill taisly-social-media-posting -a codex2Manually: put the files in place
.agents/skills/taisly-social-media-posting/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add taisly/agent --skill taisly-social-media-posting -a cursor2Manually: put the files in place
.cursor/skills/taisly-social-media-posting/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install taisly/agent taisly-social-media-posting2Manually: put the files in place
.github/skills/taisly-social-media-posting/SKILL.md1Skills CLI (Vercel)
npx skills add taisly/agent --skill taisly-social-media-posting -a gemini-cli2Platform CLI
gemini skills install https://github.com/taisly/agentManually: put the files in place
.devin/skills/taisly-social-media-posting/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add taisly/agent --skill taisly-social-media-posting -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about taisly-social-media-posting
How to install taisly-social-media-posting in Claude Code?
Run npx skills add taisly/agent --skill taisly-social-media-posting -a claude-code. This writes the skill definition to ~/.claude/skills/taisly-social-media-posting/SKILL.md.
What does taisly-social-media-posting do?
It lets the AI agent connect to Taisly via remote MCP to schedule video posts, monitor delivery statuses, and configure repost rules across social networks.
Can remote MCP upload video files stored on local disk?
No, remote MCP does not access your local filesystem or private chat attachments. You need to provide a public downloadable URL for the video file.
Source text
SKILL.md · MIT
--- name: taisly-social-media-posting description: Connect AI agents to Taisly through MCP to publish and schedule videos, inspect history, and manage reposts. version: 0.2.10 metadata: publicName: Taisly Social Media Posting Skill --- # Taisly social posting Full documentation: https://docs.taisly.com/docs/mcp ## Remote 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. 1. Call `taisly_auth_status` and `taisly_platforms_list`. An empty account list is not a login failure. 2. Match the user's requested destinations to exact returned platform IDs. 3. For a missing social account, get permission to start connection, show the `connectUrl` from `taisly_platform_connect_start`, wait for browser approval, then check connection. 4. Read `taisly_platform_schema` and validate the public video URL, caption, destinations and schedule with `taisly_posts_validate`. 5. Show the final video, caption, exact accounts and schedule. Obtain user approval before calling `taisly_posts_create` with `confirmed: true`. 6. Save `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. 7. List existing repost rules and confirm source and destination accounts before creating a requested rule. 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. ## Developer and local-file alternatives 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.
© taisly · MIT · taisly/agent
