CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

wechat-article

AI Berkshire skill: 微信公众号文章:作者-编辑-读者三Agent协作. Source: skills/wechat-article.md.

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./codex-skills/wechat-article/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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.

The body is a strong operational playbook: concrete commands, complete prompt templates, and a well-sequenced multi-agent workflow with explicit feedback-handling rules. Its main weaknesses are a fully-inlined structure with no progressive disclosure into reference files, and a couple of non-workflow sections (the Codex adapter note) that pad the token budget.

Suggestions

Move the three prompt templates (author, editor, reader) into references/ files (e.g. references/author-prompt.md) and link them from the phase sections, keeping SKILL.md as a lean overview.

Add an explicit final-validation step in 阶段四 ('verify the finished draft against every 写作红线 item before saving') to close the workflow's feedback loop.

Trim or relocate the Codex adapter note — it is adapter plumbing, not part of the writing workflow, and costs ~10 lines of always-loaded context.

DimensionReasoningScore

Conciseness

The body is dense and task-specific: complete prompt templates, decision tables (reader positioning, feedback synthesis, file naming), and a red-lines checklist, with no explanation of concepts Claude already knows. Minor trim candidates: the 'Codex adapter note' section is harness plumbing rather than workflow content, and the 设计理念 section spends lines justifying the approach rather than instructing. Fits anchor 4 (efficient, minor over-explanation) rather than 5, since those sections could be tightened.

4 / 5

Actionability

Highly actionable: copy-paste-ready prompt templates with clearly marked placeholders, an exact extraction command (`pdftoppm -png -r 900 -f {页码} -l {页码} 论文.pdf /tmp/page`), specific quality gates (≥900 DPI, ≥500KB, `compress_level=1`), and concrete naming schemes. Falls short of anchor 5 only because the PIL cropping step is described ("用 PIL 按坐标裁切") without executable code, unlike the fully-specified pdftoppm step. Well above anchor 3, which expects pseudocode-level guidance.

4 / 5

Workflow Clarity

Four clearly sequenced phases with explicit steps, parallel-agent orchestration instructions, a checkpoint after drafting ("检查初稿文件是否生成,阅读全文确认内容完整性"), a feedback-prioritization table for conflicting review feedback, and an escalation loop for image quality (500KB→1200/1500 DPI). Not a destructive/batch operation, so the validation cap does not apply. Short of anchor 5 because there is no explicit final verification pass against the 写作红线 checklist before publishing the file — the rules are stated but no step says to check them.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), so all content is inlined in a ~230-line body. Sections are well-organized with clear headers, but the three large prompt templates (~25-40 lines each) are exactly the kind of stable, detailed material that belongs in separate reference files read only when that phase runs. This fits anchor 3 (some structure, content that should be separate is inline) rather than 2, since the structure and navigation are good; it cannot score higher because nothing is split out and no references are signaled.

3 / 5

Total

15

/

20

Passed

Description

48%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 identifies a distinct niche but severely under-sells it: it reads as a repository label rather than a capability statement. It lacks any 'when to use' trigger guidance and any enumeration of the concrete actions the skill actually performs.

Suggestions

Add a 'Use when...' clause with concrete triggers, e.g. "Use when the user asks to write a 微信公众号 article, interpret a paper/tech topic for a WeChat audience, or says 公众号/推文/写文章".

Enumerate the concrete capabilities: deep-research the topic in parallel, draft a 3000-4000字 article, extract high-resolution figures from paper PDFs, and revise via author-editor-reader review.

Drop the metadata fragments "AI Berkshire skill:" and "Source: skills/wechat-article.md" — they consume the description budget without informing capability or triggering.

DimensionReasoningScore

Specificity

The description names the domain ("微信公众号文章") and one mechanism ("作者-编辑-读者三Agent协作") but states no concrete actions — nothing about deep research, drafting, editing, figure extraction, or publishing. The prefixes "AI Berkshire skill:" and "Source: skills/wechat-article.md" are repository metadata, not capabilities. This matches anchor 2 (domain named, actions minimal/generic) better than anchor 3, which expects 1-2 stated concrete actions.

2 / 5

Completeness

The 'what' is present but terse — produce a WeChat official-account article via three-agent collaboration — and there is no 'Use when...' clause or equivalent trigger guidance anywhere in the description, which caps completeness at 3 per the judging guidelines. The "Source:" sentence adds noise without answering 'when'. Not score 2 because the 'what' is not vague; not 4 because 'when' is entirely absent rather than merely improvable.

3 / 5

Trigger Term Quality

"微信公众号" and "文章" are natural terms a user would say (e.g. "写一篇公众号文章"), and "三Agent协作" signals the approach. However, common variations and synonyms are missing: 微信, 推文, 公众号写作, 写文章, tech-report interpretations (论文解读), and English equivalents. Fits anchor 3: some relevant keywords but missing common variations.

3 / 5

Distinctiveness Conflict Risk

WeChat official-account article production is a clear niche unlikely to collide with unrelated skills, and "三Agent协作" further distinguishes it. Minor overlap risk remains with generic writing/research-report skills, since no trigger phrases delineate the boundary — fits anchor 4 rather than 5, which expects distinct explicit triggers.

4 / 5

Total

12

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing, 1 suspicious

Warning

Total

15

/

16

Passed

Repository

xbtlin/ai-berkshire

Path

codex-skills/wechat-article/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.