md2wechat-skill: WeChat Formatting for Claude Code and OpenClaw

If md2wechat-lite fits scripts and shell workflows, md2wechat-skill fits environments that already support skills.

That is the point of the project: make WeChat formatting easier to call from agent runtimes such as Claude Code and OpenClaw.

Project link:

GitHub: geekjourneyx/md2wechat-skill

What it is

md2wechat-skill packages WeChat-formatting capability in a form that skill-enabled agents can install and invoke more consistently.

That matters because API docs alone are not always enough. A runtime still has to decide:

which capability is available
how it should be called
which inputs belong together
whether the task should use a CLI path or an HTTP path

A skill reduces that ambiguity.

Why the skill form matters

The integration problem is often not the API itself. The problem is that the calling pattern is still loose.

If the only artifact is a raw API document, the runtime has to infer too much:

the correct order of operations
the expected arguments
the right install entrypoint
the difference between command-line and service workflows

A skill does not replace the API. It makes the calling surface more structured.

Which environments it fits

Based on the public project positioning, md2wechat-skill is a good fit for:

Claude Code
OpenClaw
other agent environments that support a similar skill distribution model

These environments already expect reusable capabilities to arrive as installable units. A skill matches that expectation better than a standalone document.

Installation

Claude Code

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

OpenClaw

curl -fsSL https://raw.githubusercontent.com/geekjourneyx/md2wechat-skill/main/scripts/install-openclaw.sh | bash

Those commands already define the practical entrypoints:

where the project lives
how the environment installs it
which skill name gets registered

When it is the right entrypoint

1. You already work inside Claude Code

If most of your writing or automation work already happens there, a skill is usually more direct than manually reassembling the workflow.

2. You are distributing capabilities in OpenClaw

If your team already installs tools as OpenClaw skills, keeping WeChat formatting in the same form keeps the integration consistent.

3. You want a reusable agent capability, not just a one-off command

A skill is easier to keep as part of a longer-lived agent toolbox.

Skill vs CLI

This is the most common comparison:

md2wechat-lite is better for shell scripts, local commands, and pipeline-style execution
md2wechat-skill is better for Claude Code, OpenClaw, and other skill-aware runtimes

They are not competing products. They cover different entrypoints.

Closing thought

md2wechat-skill exists for one clear reason: some environments work better with installable capabilities than with raw API docs or a standalone CLI.

If your main runtime is Claude Code or OpenClaw, this is usually the cleaner place to start.