Yizhuan Content and Competitor Data Tool

Problem

When an Agent connects to Yizhuan data capabilities, the blocker is often not business logic but environment drift: the CLI is missing, the formal Skill is not synced, API keys leak into chat or logs, or failed installation steps are skipped.

How It Works

This bootstrap skill treats onboarding as a single-responsibility installation pipeline:

• CLI installation: after confirmation, it pulls the latest stable npm package @yizhuan-cli/cli@latest.
• Version check: it verifies the CLI prints a valid version before proceeding.
• Formal Skill sync: when multiple hosts are detected, it selects the target explicitly instead of overwriting unknown directories.
• Configuration init: API keys are entered through a non-echo local prompt or --api-key-stdin, keeping them out of arguments and logs.
• Diagnostics: it reports success only after CLI, config, authentication, and Skill status all pass.

Boundaries

It handles install, upgrade, sync, and diagnosis only. After diagnostics pass, switch to the formal yizhuan-cli skill for work, author, trend, competitor, collection, or membership queries; do not continue business writes here.