菜单
Orchestrates posting a video to multiple social platforms (LinkedIn, X/Twitter). Use when user wants to post a video to social media, share a video on LinkedIn/X, or says "post this video".
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/mediar-ai/skillhubz --skill video-social-poster命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| name | video-social-poster |
| description | Orchestrates posting a video to multiple social platforms (LinkedIn, X/Twitter). Use when user wants to post a video to social media, share a video on LinkedIn/X, or says "post this video". |
| allowed-tools | Bash, Read, Grep, mcp__playwright-extension__*, mcp__macos-use__* |
High-level orchestrator for posting a video with text to one or more social media platforms. Delegates to platform-specific skills.
Confirm you have:
If any are missing, ask the user.
Delegate to the appropriate platform-specific skill:
| Platform | Skill | Key Notes |
|---|---|---|
linkedin-video-post | Don't need to close Playwright for upload | |
| X/Twitter | x-video-post | Must close Playwright before file upload |
Important ordering: If posting to both platforms, post to LinkedIn first, then X. This is because X requires closing the Playwright browser connection, which would disrupt LinkedIn posting if done first.
After each platform post:
Standard Playwright browser_file_upload fails on these platforms with Protocol error (DOM.setFileInputFiles): Not allowed. The solution is a hybrid approach using Playwright for web interactions and macOS-use MCP for native file dialog handling. See social-media-video-upload skill for the full technical pattern.
social-media-video-upload — Core hybrid upload pattern (reference doc)linkedin-video-post — LinkedIn step-by-step workflowx-video-post — X/Twitter step-by-step workflowValidate rights-aware AI-hybrid video-production metadata with SHAR Production's local read-only MCP tool.
Publish files, folders, and artifacts to the web. Static hosting for HTML sites, images, PDFs, reports, dashboards, and any file type. Use when asked to publish, host, upload, serve, or share work at a live URL. Also use to propose a rendered page when a report, comparison, chart, design document, or status page would work better than terminal text, but do not create or update a remote site until the user asks or agrees. Account publishing gives a permanent, private-by-default URL visible to org members; --anonymous gives a temporary public URL with no account. Use the valet CLI when available and its MCP server when the CLI cannot run. For deploying an AI agent rather than static files, use the `valet` skill instead.
Use when the user wants to manage Valet agents, channels, connectors, organizations, or environment variables (secrets and plain config) via the valet CLI. Handles creation, deployment, linking, teardown, and all multi-step workflows. Also use when asked to "create an agent", "deploy an agent", "design an agent", "build me an agent that...", "create a connector", "set up a webhook", or anything involving the Valet platform or any request to create and deploy AI agents. Also use when asked to "learn from this session", "capture this workflow", "save this as an agent", "make this repeatable", or when writing SOUL.md files.