video-publisher
Video Publisher
Prepare one confirmed video package and drive selected creator platforms to a verified draft state. Use Ego Lite for all live creator-page work.
Configuration And Onboarding
At the start of every invocation, before inspecting a video or opening a browser, run:
node scripts/config.mjs status
If onboardingRequired is true, stop the publishing flow and onboard the user. Ask first which supported creator platforms the user actually has; require at least one and never assume all four. Then ask which of those available platforms should run by default, proposing all available platforms as the default subset. Ask for Douyin topics only when Douyin is available and Bilibili automatic tags only when Bilibili is available. Collect the source directory, shared copy/tag preferences, and whether every video may truthfully be declared original; keep concurrency 4/4 and platform cover as proposed defaults unless the user changes them. Summarize the choices before writing. Save available accounts with repeatable --available-platform flags and defaults with repeatable --platform flags, run validate, and continue only when onboardingRequired is false.
Configuration is per user at $XDG_CONFIG_HOME/video-publisher/config.json, or $HOME/.config/video-publisher/config.json. VIDEO_PUBLISHER_CONFIG overrides the path. Never put a user's configuration inside the shareable Skill folder.
An explicit current request overrides the package; explicit package fields override configuration defaults. A current request may select any configured available platform, but it cannot silently add an unavailable platform: update onboarding and confirm that account first. The onboarding configuration may persist the user's truthful standing originality policy and declared platform availability, but never cookies, credentials, video-specific paths, or final-publish authorization. Read references/configuration.md for the schema and onboarding command.