CtrlK
BlogDocsLog inGet started
Tessl Logo

add-wechat

Add WeChat (personal) channel integration via Tencent's official iLink Bot API. Uses long-polling and QR scan — no webhook, no ToS risk, no paid token.

64

Quality

76%

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 ./.claude/skills/add-wechat/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 high-quality, action-oriented install/credential/wiring guide with concrete commands, explicit validation, and a verified referenced script. Minor gaps are a slightly mislabeled cross-reference and a little inline reference material that could be split out.

DimensionReasoningScore

Conciseness

The body is efficient and command-driven with little concept padding Claude already knows, though a few prose blocks (the differentiator bullets, the dense validation-explainer at the end of step 4) could be trimmed slightly.

4 / 5

Actionability

Guidance is fully executable and copy-paste ready: nc:copy/append/dep/run blocks, exact bash and systemctl/launchctl commands, env vars, concrete file paths, plus non-interactive flags and a raw ncl equivalent covering the common cases.

5 / 5

Workflow Clarity

Clear numbered sequences across Install, Credentials, and Wire with explicit validation checkpoints ("Both must be clean before proceeding", build+test, final test-the-wiring step) and a session-expiry feedback loop; a small cross-reference in Install step 4 says "above" but points to sections that appear below, a minor navigation gap.

4 / 5

Progressive Disclosure

Well-organized single-file overview with the wire-dm.ts helper correctly referenced as a real one-level-deep bundle file (verified in ./scripts/), plus a Channel Info reference section; structure is good but the body still inlines some reference-style material that could be split out.

4 / 5

Total

17

/

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.

The description is specific, distinct, and in correct third-person voice, clearly scoping a personal-WeChat integration via Tencent's iLink API. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user wants to add a personal WeChat (not WeCom) channel or mentions WeChat bot integration.'

Add a couple of natural synonym/variation terms (e.g. '微信', 'WeChat bot') to broaden trigger coverage.

Keep the differentiator clause (no webhook / no ToS risk / no paid token) — it is doing useful work for distinctiveness.

DimensionReasoningScore

Specificity

Names the domain ("Add WeChat (personal) channel integration") and concrete mechanisms ("Tencent's official iLink Bot API", "long-polling and QR scan") with several specific actions, though coverage is focused on a single integration rather than broad.

4 / 5

Completeness

The "what" is clearly stated (add WeChat via iLink Bot API using long-polling/QR scan), but there is no explicit "Use when..." trigger clause, so per the missing-trigger-guidance cap completeness cannot exceed 3.

3 / 5

Trigger Term Quality

"Add WeChat", "WeChat (personal)", and "channel integration" are natural terms a user would say, and "iLink Bot API" is on point, but it lacks common synonym/variation coverage beyond the single "WeChat" keyword.

4 / 5

Distinctiveness Conflict Risk

"Tencent's official iLink Bot API" for personal WeChat is a clear niche explicitly distinguished from WeCom/PadLocal, with distinct triggers and minimal overlap with other 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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
nanocoai/nanoclaw
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.