CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

baoyu-post-to-wechat

Posts content to WeChat Official Account (微信公众号) via API or Chrome CDP. Supports article posting (文章) with HTML, markdown, or plain text input, and image-text posting (贴图, formerly 图文) with multiple images. Markdown article workflows default to converting ordinary external links into bottom citations for WeChat-friendly output. Use when user mentions "发布公众号", "post to wechat", "微信公众号", or "贴图/图文/文章".

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a strongly engineered skill body: checklist-driven workflow with decision tables and validation gates, fully executable commands with flag-level precision, verified one-level-deep reference files, and disciplined table-based conciseness that assumes Claude's competence. The only weakness is mild: the remote-api architecture prose and the feature-comparison table could be tightened or delegated to references.

DimensionReasoningScore

Conciseness

The body is dense and table-driven with essentially no explanation of concepts Claude already knows — e.g., the troubleshooting table, the EXTEND.md key table, and the one-line 'Never pre-convert markdown to HTML' rule all carry pure operational signal. It falls short of 5 only in a few spots that could be trimmed or moved to references: the multi-sentence prose in Step 2 explaining the remote-api SSH SOCKS5 architecture ('Rendering, image processing, draft assembly and HTML rewriting stay local; only the HTTPS calls ... go through an SSH SOCKS5 forward') and the 13-row Feature Comparison table partially duplicate information already conveyed by the Step 2 method table. Not 3: these are minor instances of over-explanation in an otherwise efficient document, not a pattern of unnecessary explanation.

4 / 5

Actionability

Guidance is copy-paste ready throughout: full bash invocations with every flag ('${BUN_X} {baseDir}/scripts/wechat-api.ts <file> --theme <theme> --remote [--remote-host <host>] ...'), the exact API endpoint and payload rules ('POST https://api.weixin.qq.com/cgi-bin/draft/add?access_token=ACCESS_TOKEN', 'article_type: news (default) or newspic'), concrete fallback chains ('CLI --cover → frontmatter (coverImage / featureImage / cover_image / cover / image) → imgs/cover.png → first inline image → stop and request one'), and specific plain-text file-naming rules ('post-to-wechat/YYYY-MM-DD/<slug>.md'). Not 4: commands are executable as written and the common cases (api, remote-api, browser, image-text) each have a complete example with no gaps.

5 / 5

Workflow Clarity

The Article Posting Workflow is an explicit checklist ('- [ ] Step 0: Load preferences ... - [ ] Step 5: Report completion') with per-step decision tables (input-type detection, method selection, metadata field resolution), an explicit validation gate in Step 0 ('if missing, finish first-time setup before any other question'), a pre-flight permission check with a failure→fix table, and a Troubleshooting section with feedback loops for error recovery (e.g., 'errcode 40164' → add egress IP to the allowlist, SOCKS proxy not ready → check key/host/timeout). Not 4: checkpoints are explicit at nearly every step, including the mandatory cover-image stop condition and the completion report enumerating what must be verified.

5 / 5

Progressive Disclosure

SKILL.md is a clear overview that delegates details to well-signaled, one-level-deep references that all exist in the bundle: 'references/config/first-time-setup.md', 'references/multi-account.md', 'references/api-setup.md', 'references/image-text-posting.md', 'references/article-posting.md' — verified present in ./references/ (plus ./references/config/), and none of these files point to further nested references. The Script Directory table gives a purpose for each script, matching the actual scripts/ contents. Not 4: every reference is clearly signaled at its point of use, the split is appropriate (details out, decisions in), and navigation requires no second hop.

5 / 5

Total

19

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is a model example: it states the skill's concrete capabilities (two posting modes, three input formats, citation conversion, API and browser transports) in third person, and closes with an explicit 'Use when...' trigger list covering both Chinese and English phrasings plus feature-name synonyms. It is concise, specific, and highly distinguishable from other skills.

DimensionReasoningScore

Specificity

Quotes multiple concrete actions: 'Posts content to WeChat Official Account (微信公众号) via API or Chrome CDP', 'article posting (文章) with HTML, markdown, or plain text input', 'image-text posting (贴图, formerly 图文) with multiple images', 'converting ordinary external links into bottom citations' — comprehensive coverage of both posting modes, all input formats, and a transformation behavior. Not 4: coverage of the skill's capabilities is complete rather than having minor gaps; not below: every clause names a specific action, no vague filler.

5 / 5

Completeness

Explicitly answers what ('Posts content to WeChat Official Account ... via API or Chrome CDP. Supports article posting ... and image-text posting ... with multiple images') and when ('Use when user mentions "发布公众号", "post to wechat", "微信公众号", or "贴图/图文/文章"') with concrete trigger phrases. Not 4: the 'when' clause is explicit and enumerated rather than merely present; not 3: both halves are clearly stated, matching the top anchor's exemplar pattern.

5 / 5

Trigger Term Quality

Triggers span both user languages and feature synonyms: '发布公众号', 'post to wechat', '微信公众号', '贴图/图文/文章'. Not 4: it covers the natural phrasings a Chinese-speaking user would say (发布/公众号) alongside the English phrasing and both the current and former name for image-text posting, rather than leaving a few natural terms missing. Not below: all listed terms are phrases users would actually say, not jargon.

5 / 5

Distinctiveness Conflict Risk

Clear niche — posting to a WeChat Official Account — with distinct, unambiguous triggers ('微信公众号', 'post to wechat', '发布公众号'); no other plausible skill would claim these phrases. Not 4: there is no meaningful overlap risk with closely related skills since the domain and triggers are uniquely identifying, satisfying the 'clear niche with distinct triggers; minimal conflict risk' anchor.

5 / 5

Total

20

/

20

Passed

Validation

75%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 1 deeper-than-1-level

Warning

Total

12

/

16

Passed

Repository

JimLiu/baoyu-skills

Path

skills/baoyu-post-to-wechat/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.