CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

wechat-article-reader

Read 微信公众号 articles from mp.weixin.qq.com links using available web or browser tools. Report verification walls honestly; reading alone does not modify notes or queues.

69

Quality

87%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A tight, single-purpose instruction skill: every sentence directs behavior, validation checkpoints are explicit, and common failure modes (paywalls, captchas, missing tools, storage handoff) each have a concrete response. It earns top marks under the rubric's simple-skill guidance for a short, well-organized, reference-free skill.

DimensionReasoningScore

Conciseness

"先使用当前环境可用的网页读取工具读取用户提供的文章。普通读取失败时…" — every line is dense, imperative instruction with no explanation of concepts Claude already knows (no primer on WeChat, web tools, or scraping) and no padding; even the final "此公开版不附旧机专用 Playwright 脚本" line earns its place by warning against hunting for or downloading readers. Matches anchor 5 (lean and efficient); not 4 because there is no over-explanation to trim.

5 / 5

Actionability

Concrete, executable guidance throughout: exact fields to verify ("核对标题、作者、正文、发布日期和原始链接"), a defined output format ("精要摘要、证据范围、引用与未验证项"), and specific fallbacks for every common case (browser capability on normal-read failure, captcha/login → ask user, "工具不可用时明确报告,不临时下载未知读取器"). Matches anchor 5; not 4 because no common case is left unspecified — the absence of code is not penalized for an instruction-only skill per the rubric's scoring notes.

5 / 5

Workflow Clarity

Clear sequence with explicit validation and error-recovery paths: "先…读取文章" → "普通读取失败时…再尝试实际页面" → verify → output, with checkpoints like "只有真正看到的内容才能标为已读" and "验证实际落库", plus recovery loops for captcha, inaccessible pages, and tool unavailability. Reading is non-destructive, so the destructive/batch cap does not apply; matches anchor 5 for this single-task, checklist-driven workflow.

5 / 5

Progressive Disclosure

At 19 lines with no bundle files (references/, scripts/, assets/ are absent) and no external references needed — the body explicitly delegates to host-provided tools — it meets the rubric's under-50-line exception: a single H1, a lead operational paragraph, a bullet checklist, and scoped closing paragraphs are well-organized sections. Not 4 because nothing that belongs in a separate file is inlined and no reference is buried.

5 / 5

Total

20

/

20

Passed

Description

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

A distinctive, third-person description with a clear "what" and strong platform-specific triggers, weakened only by the missing explicit "Use when…" trigger clause and absent English synonyms for the platform. The frontmatter name (wechat-article-reader) is consistent with the description's scope.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user shares an mp.weixin.qq.com link or asks to read a 微信公众号/WeChat official account article" — this would lift completeness from 3 to 4-5.

Include English synonyms ("WeChat article", "WeChat official account") alongside 微信公众号 to broaden natural trigger-term coverage for non-Chinese phrasings.

Mention the output deliverables (summary with evidence scope and unverified items) among the listed actions to close the coverage gap in specificity.

DimensionReasoningScore

Specificity

"Read 微信公众号 articles from mp.weixin.qq.com links using available web or browser tools. Report verification walls honestly" names the exact platform and URL plus specific actions (read, report walls, no side effects: "reading alone does not modify notes or queues"). Matches anchor 4 (several specific actions, minor gaps); not 5 because coverage is incomplete — the body's summarization/verification outputs are absent — and not 3 because the actions go well beyond "names domain and 1-2 actions" in specificity.

4 / 5

Completeness

The "what" is clear ("Read 微信公众号 articles from mp.weixin.qq.com links using available web or browser tools"), but there is no "Use when…" clause or equivalent explicit trigger guidance — the "when" is only weakly implied by the URL mention. Per the rubric guideline, a missing 'Use when…' clause caps completeness at 3 even with a clear what; not 4 because the trigger condition is never stated explicitly.

3 / 5

Trigger Term Quality

"微信公众号" and "mp.weixin.qq.com" are the natural phrases users say or paste when asking for this, giving strong triggers. Matches anchor 4 (good coverage, a few natural terms missing); not 5 because English synonyms like "WeChat (official account) article" are absent, and not 3 because the domain name plus exact URL far exceed "some relevant keywords".

4 / 5

Distinctiveness Conflict Risk

"微信公众号 articles from mp.weixin.qq.com links" carves out a clear niche with distinct, near-unique triggers (the specific host and platform name); risk of firing for a generic web-reading or note-management skill is minimal. Matches anchor 5; not 4 because the platform-specific URL trigger leaves essentially no overlap with closely related skills.

5 / 5

Total

16

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

huangruiteng/CS-Notes

Path

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