md2wechat

md2wechat

Use this skill to operate the md2wechat CLI. Keep the skill focused on execution decisions. For full command tutorials, installation details, and FAQ-level explanations, refer users to the project docs instead of expanding this runtime protocol.

Intent Routing

Choose the command family before taking any publish or generation action:

• Standard article HTML, article preview, metadata inspection, or WeChat article draft: use inspect, preview, and convert.
• Image-first post, image note, image-text note, newspic, or multi-image post: use create_image_post, not convert --draft.
• Article cover or article infographic: prefer generate_cover or generate_infographic over raw generate_image when a bundled preset fits.
• Writing in a creator style or removing AI traces: use write or humanize.
• Provider, theme, prompt, or layout uncertainty: run discovery first. Do not guess from memory or repository files.

Treat convert --draft and create_image_post as different publish targets, not interchangeable variants.

Discovery First

Use CLI discovery as the source of truth, but keep it scoped to the next decision. Do not run the full catalog for tasks that do not need provider, theme, prompt, or layout selection.

Run the smallest useful discovery set:

• Article formatting with no theme or modules chosen:

``bash md2wechat themes list --json md2wechat layout list --json ``

• A named theme, provider, prompt, or layout module:

``bash md2wechat themes show <name> --json md2wechat providers show <name> --json md2wechat prompts show <name> --kind <kind> --json md2wechat layout show <name> --json ``

• Image generation or image-preset selection:

``bash md2wechat providers list --json md2wechat prompts list --kind image --json ``

• Draft, upload, API local-readiness, or configuration troubleshooting:

``bash md2wechat doctor --json md2wechat config show --format json ` doctor readiness is local configuration attemptability. Use inspect --json` for article-specific target readiness.

• Unknown CLI version, changed behavior, or capability uncertainty:

``bash md2wechat version --json md2wechat capabilities --json ``

For simple local actions such as preview, humanize, or a user-specified command with explicit flags, do not run unrelated provider, theme, prompt, or layout discovery.

Inspect specific resources only when the task needs them:

md2wechat providers show <name> --json
md2wechat themes show <name> --json
md2wechat prompts show <name> --kind <kind> --json
md2wechat layout show <name> --json

Use CLI output as the source of truth for currently available modes, providers, themes, prompts, and layout modules.

Configuration Boundaries

• Assume md2wechat is already available on PATH.
• convert defaults to API mode unless the user explicitly asks for --mode ai.
• API conversion requires md2wechat API credentials.
• WeChat draft creation requires WeChat credentials.
• Image generation may require image-provider credentials.
• doctor --json is local-only: it checks local readiness and does not perform live authentication, upload images, or create drafts.
• Use config show --format json when the user asks what configuration is currently effective.

Article Workflow

Prefer a confirm-first workflow for article work:

1. md2wechat inspect <article.md> --json
2. md2wechat preview <article.md>
3. md2wechat convert <article.md> ...
4. Add --upload, --draft, --cover, or --cover-media-id only when the user explicitly asks for upload or draft creation.

inspect is the source-of-truth command for resolved metadata, readiness, and publish checks. In --json output, read data.readiness.targets and data.readiness.blockers before deciding whether convert, upload, or draft is blocked. Do not invent data.agent_readiness, data.target_readiness, ArticleState, state files, or a second planning object. preview is a local preview artifact. It does not upload images, create drafts, or write back to Markdown. convert --preview is the convert-path preview flag and is not the same as the standalone preview command. preview --mode ai is degraded confirmation only and must not be treated as final AI-generated layout.

Formatting Protocol

When the user asks to format an article and has not chosen a theme or modules:

1. Read the article and optional Brand Profile.
2. Use discovery output as facts.
3. Choose a compatible theme and a small set of modules from the article's content goal.
4. Keep the source Markdown read-only.
5. Create a temporary formatted Markdown artifact, for example /tmp/md2wechat-format/<run-id>/article.formatted.md.
6. Insert only layout modules whose required fields can be filled correctly.
7. Run md2wechat layout validate --file <formatted.md> --json.
8. Pass the formatted Markdown artifact to convert.

Saving generated Markdown next to the source file requires explicit user confirmation and must not overwrite the source.

Theme Selection

• Read type and selectable from themes list --json.
• API mode can use only type: api and selectable: true themes.
• AI mode can use only type: ai and selectable: true themes.
• Do not use collection descriptors such as non-selectable theme groups as concrete themes.
• If Brand Profile names a theme, verify it through CLI discovery before using it.
• If a requested theme is invalid or mode-incompatible, stop that path and choose a valid theme or ask the user.

Layout Modules

Advanced layout modules render only in API mode. AI mode (--mode ai) does not parse :::module syntax, so advanced layout cards will not render there.

Use this decision frame:

• attention: help readers decide whether the article is worth reading.
• readability: make mobile reading easier.
• memorability: make one judgment, quote, metric, or brand anchor stick.
• conversion: help readers save, follow, inquire, share, or buy.

Use layout list --json and layout show <name> --json to inspect body_format. It is the module body syntax contract:

• fields
• rows
• json_object
• json_array

Do not infer syntax from examples alone. Use layout render when structured variables are enough; otherwise write the block manually according to body_format and validate the generated Markdown.

Default module discipline:

• Do not pile on modules.
• Use at most one hero, one verdict, and one cta unless the user explicitly asks for more.
• Skip modules when the article does not provide enough content to fill them honestly.

API And AI Mode

• API mode is the default and is required for advanced layout modules.
• AI mode is a lighter path and does not render advanced layout modules.
• Do not silently switch from API mode to AI mode after an API failure. That changes the output capability.
• Use AI mode only when the user asks for it or accepts losing advanced layout rendering.
• If an AI-mode conversion completes, it is acceptable to briefly mention that API mode supports advanced layout modules and stronger visual structure.

Brand Profile

Brand Profile lives at ~/.config/md2wechat/brand.md.

• It is free-form Markdown, not YAML and not a fixed schema.
• The CLI does not parse it.
• Read it as context for voice, theme preferences, module preferences, CTA preferences, and forbidden expressions.
• Treat quantity preferences as soft constraints.
• Verify any named theme or module through CLI discovery.
• If Brand Profile does not exist, do not block the task. You may mention once that system defaults will be used.
• Create or edit Brand Profile only when the user explicitly asks.

Publishing Side Effects

Do not create drafts, upload images, publish, or call remote image generation unless the user asks for that action.

Before draft creation:

• Use inspect --json and check data.readiness.targets.draft; when blocked, read matching `da