How to Validate md2wechat-skill in Claude Code

The md2wechat-skill repository documents a Claude Code plugin-marketplace installation path. The installation path is distribution evidence, not proof of end-to-end Claude Code compatibility.

The practical question is whether the current host can discover the main CLI and complete a no-side-effect smoke test before any publishing action is enabled.

Why repeated prompting is not enough

Many people start like this:

• ask Claude Code to write an article
• ask it to rewrite the structure
• ask it to output something "suitable for WeChat"

That can work for one-off cases, but it does not define:

• which tool should be called
• which parameters should be used
• how themes should be passed
• how draft creation should be triggered

The validation path

For Claude Code, validate the integration in this order:

1. Install the main md2wechat CLI and run its JSON discovery commands
2. Install md2wechat-skill through the documented marketplace path
3. Confirm that Claude Code discovers the Skill and CLI without guessing commands
4. Run conversion, inspection, and preview with no publishing side effect
5. Record an end-to-end smoke result before claiming draft support for this host

Project link:

• GitHub: geekjourneyx/md2wechat-skill

Installation

The public installation path for Claude Code is:

/plugin marketplace add geekjourneyx/md2wechat-skill
/plugin install md2wechat@geekjourneyx-md2wechat-skill

What installation proves

Installation can prove that the package is discoverable through the documented distribution path. It does not by itself prove that the host can execute every capability. Validate:

• CLI binary visibility and permissions
• version, capabilities, and layout discovery JSON
• conversion, inspection, preview, and failure handling
• credential and publishing boundaries

After that smoke test passes and is recorded, intended requests include:

• Convert this Markdown into WeChat formatting
• Preview the result with a specific theme
• Send the result into the draft box

When this validation is worth running

The validation is relevant when:

• you already use Claude Code for content and tooling work
• you want WeChat formatting to become part of the workflow
• you want to determine whether conversion and draft creation can become callable actions on the current host

How it differs from CLI and plugins

You can think about the stack this way:

• the main md2wechat CLI is the core CLI and shell path
• md2wechat-skill is the core path for skill-aware Agents
• md2wechat-lite is an optional lightweight client
• obsidian-md2wechat is better for Obsidian-first workflows
• feishu-md2wechat is better for Feishu-first workflows

Closing thought

The public installer makes Claude Code a concrete integration candidate. Treat the Skill as distributed but compatibility as pending until the current host passes and records the full smoke test.