内容分四块: 1、产品规划产出 —— MCN 短视频整合营销工作台的①段五份(1a 需求/1b 竞品/1c 画像/1d 策略/1e 场景)、②段两份(2a 功能/2b 布局)、③段界面(DESIGN.md 契约与令牌表 + mcn-workbench.html 原型 + 实测/会诊/审查三份 + 23 张闸门截图)。 2、开源竞品调研 —— 5 个内容工作台项目的取证原始件与 1b 系列分析文档。 3、参考资料 —— 竞品视频抽帧 1145 张 + 2 个源视频 + 功能点截图。 4、机制侧 —— 协作脚本与状态台账、工作区记忆日志、抽帧/OCR 脚本。 .gitignore 只排运行时日志、脚本备份副本与一次性探针输出,其余按原样入库。
2.7 KiB
2.7 KiB
name, description
| name | description |
|---|---|
| postsider-content-publishing | Create a PostSider draft, schedule a post, or publish a post now after resolving the target channel and validating the requested content. Use when the user asks to draft, schedule, queue, or publish social content. |
Create, schedule, or publish PostSider content
Use this skill for one intentional publishing action. The user's explicit instructions take precedence over workflow defaults. Do not add a separate approval round when the user already supplied or approved the exact content, target channel, and timing.
Required inputs
Before a write, establish:
- exact post content;
- target channel or channels;
- action: draft, schedule, or publish now;
- publish time and timezone for a scheduled post;
- media, if required by the selected platform.
Ask only for a missing detail that changes the action. Never invent ids, dates, content, media paths, or platform settings.
Workflow
- Call
postsider_list_channelsand resolve each requested channel to a fresh id. - For scheduling, call
postsider_get_publishing_state. If publishing is paused, stop and explain that new scheduled posts are rejected while paused. - Review the relevant date range with
postsider_list_postswhen the user asks to avoid calendar conflicts. Usepostsider_find_slotonly when the user asks for the queue's next free time or accepts queue-based timing. - If media is supplied as a public HTTPS URL and must be stored first, call
postsider_upload_media_from_urlonce and use the returned media object. Do not request credentials or authentication secrets as tool inputs. - Call
postsider_create_postwith the action the user requested:draftfor a draft;schedulefor a future time;nowonly when the user explicitly asks to publish immediately.
- Call
postsider_get_postwith the returned id. Verify the stored content, target channel, state, publish time, and media before reporting success. - If the write fails, report a concise actionable error without exposing credentials, tokens, debug payloads, or internal telemetry. Do not retry a write blindly.
Consequential actions
- A clear instruction to schedule a specific post at a specific time is authorization to schedule it.
- A clear instruction to publish a specific post now is authorization to publish it now. If "publish" could mean draft or schedule, ask which outcome the user wants.
- Do not turn a request to prepare or suggest copy into a write.
- Do not use
postsider_delete_postorpostsider_pause_publishingin this workflow.
Output
Return the final content, channel, action, state, and local publish time. Include the verified post id. Say plainly what could not be verified.