Yixiaoer Multi-Platform Multi-Account Publishing Manager

Problem

Operators managing multiple accounts across several social platforms often face fragmented publishing rules, unclear asset status, and hard-to-debug failures. When an AI agent is involved, the bigger issue is avoiding ad hoc publishing logic and making the workflow explicit, repeatable, and inspectable. This skill targets that onboard-first, manage-later stage: it brings the Yixiaoer workflow into the agent environment as a standardized setup layer instead of leaving the model to improvise platform-specific publishing behavior.

How It Works

The bootstrap skill has a narrow responsibility: prepare the yxer CLI, verify the environment, sync the formal skill, and stop after the environment check passes. It does not directly perform publishing, account lookup, asset upload, or payload validation. Those capabilities continue in the formal yixiaoer skill. The design goals are:
- Standardized workflow: separate account confirmation, asset upload, field validation, and publishing into repeatable steps.
- Platform-aware distribution: handle content according to the actual field rules of platforms such as Douyin, Channels, and Xiaohongshu.
- Unified asset management: upload images, videos, and covers before reusing them for multi-platform publishing.
- Validate before distribution: preview and validate content before release to reduce failure rate.
- Traceable process: keep publishing status, error causes, and task results queryable for review.

Boundaries

It fits first-time onboarding, CLI upgrades, re-syncing the formal skill, or cases where an agent needs a standardized Yixiaoer flow. It is not a publishing executor. After setup, upgrade, sync, and environment checks, the workflow should move to the formal skill for business operations. The runtime still needs Node.js, npm, and npx available; configuration must be initialized with a valid API key before dependent steps can continue.