CtrlK
BlogDocsLog inGet started
Tessl Logo

wechat-official-formatter

Must be used for WeChat Official Account writing, Xiaohongshu-to-WeChat expansion, WeChat rich-text formatting, public-account draft preparation, binding checks, and draft publishing decisions.

65

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./desktop/electron/system-skills/wechat-official-formatter/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

A concise, well-organized instruction-only skill, but its formatting and draft-publishing guidance stays abstract and lacks an explicit validation feedback loop for the publishing step, capping actionability and workflow clarity at 2.

Suggestions

Add a concrete WeChat HTML/structure template or a short example so formatting guidance is copy-paste ready rather than abstract.

Add an explicit validate→fix→retry checkpoint for the draft-publishing step (e.g., check cover/credentials/assets, surface what is missing, retry once resolved) to lift workflow clarity to 3.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — every line is actionable guidance with no padding or explanation of concepts Claude already knows, matching the score-3 anchor.

3 / 3

Actionability

Guidance is concrete and specific ('clean WeChat HTML with stable heading hierarchy, readable paragraphs, quotes, lists, and inline emphasis', 'prefer the first relevant article image as cover'), but the formatting mechanics stay abstract without templates or concrete binding commands, so it is not fully copy-paste ready.

2 / 3

Workflow Clarity

The five-step workflow is clearly sequenced and the binding/draft section surfaces missing-asset errors, but draft publishing is an external/batch operation lacking an explicit validate→fix→retry feedback loop, which caps workflow clarity at 2 per the feedback-loops note.

2 / 3

Progressive Disclosure

This is a short, single-purpose skill under 50 lines with no bundle files, organized into clear sections (Workflow, Output Rules, Binding And Draft Rules), qualifying for a 3 under the simple-skills note.

3 / 3

Total

10

/

12

Passed

Description

82%

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

A specific, well-triggered description with a clear niche, but it states a 'Must be used for' mandate rather than an explicit 'Use when...' trigger clause, which caps completeness at 2.

Suggestions

Add an explicit 'Use when...' trigger clause naming user signals (e.g., 'Use when the user asks to format a WeChat Official Account article, expand a Xiaohongshu post to WeChat, or prepare a public-account draft') to lift completeness to 3.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete actions — 'WeChat Official Account writing, Xiaohongshu-to-WeChat expansion, WeChat rich-text formatting, public-account draft preparation, binding checks, and draft publishing decisions' — matching the score-3 anchor for listing several specific concrete actions.

3 / 3

Completeness

It clearly answers 'what' but the description uses a 'Must be used for' mandate rather than an explicit 'Use when...' trigger clause tied to user signals, so per the guideline a missing explicit trigger caps completeness at 2.

2 / 3

Trigger Term Quality

Natural user-facing terms are well covered ('WeChat Official Account writing', 'WeChat rich-text formatting', 'public-account draft', 'binding checks', 'draft publishing'), which a user would naturally say when needing this skill.

3 / 3

Distinctiveness Conflict Risk

The WeChat Official Account / public-account draft niche is clearly distinct with specific triggers, making it unlikely to fire for an unrelated skill.

3 / 3

Total

11

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Jamailar/Beav
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.