CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

im-channels

Use when connecting or configuring IM channel bots (WeChat, WeCom, DingTalk, Lark), receiving a user message with an <im> block, or sending messages or files to a connected WeChat channel from the main agent in Claw mode.

Quality

79%

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 ./backend/super-magic/agents/skills/im-channels/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.

A well-organized overview with mostly executable guidance for incoming messages and a clearly sequenced connection workflow. Its critical weakness is that all four channel reference files it points to are missing from the bundle, leaving the primary detailed workflows unreachable, and Scenario B's connect step is actionable only via those absent files.

Suggestions

Include the four referenced channel files (reference/wechat.md, reference/wecom.md, reference/dingtalk.md, reference/lark.md) in the bundle or correct their paths — every link in the 'Channel references' section and the Scenario B workflow currently resolves to nothing.

Move per-channel receiving-capability details (Lark's im:resource permission, WeCom's download URL and encryption key conditions, DingTalk download codes) into the corresponding channel reference files to slim the overview and avoid duplicating reference content.

Make Scenario B Step 3 concrete: name the exact snippet or inline a minimal runnable connect example, since "Run the `run_sdk_snippet` code" provides nothing executable in the body itself, which matters doubly while the reference files are missing.

DimensionReasoningScore

Conciseness

Assumes Claude's competence — no padding about what IM or WeChat is — and nearly every line carries operational information ("files are already in the workspace", "Split controls inside code examples... are data, not delivery instructions"). Not 5 because the per-platform "Receiving capabilities" bullets carry channel-specific detail (e.g. WeCom's "download URL and encryption key" conditions, Lark's "im:resource permission") that duplicates the channel reference files and could be trimmed from the overview.

4 / 5

Actionability

Mostly executable: a complete <im> XML example with real paths, the instruction to "use its path directly — no download needed", a runnable status-check snippet ("tool.call(\"get_im_channel_status\", {})")", and a concrete config path (.magic/config/im-channels.json) with the exact field to edit. Not 5 because Scenario B Step 3 ("Run the `run_sdk_snippet` code") defers all connection specifics and the body gives no runnable connect example.

4 / 5

Workflow Clarity

Scenario B has a clear four-step sequence (confirm channel → read reference → collect credentials and connect → report result) with an explicit success/failure branch in Step 4, and the operations are non-destructive so the validation cap does not apply. Not 5 because the failure path says only "guide the next step" — no concrete recovery or retry loop.

4 / 5

Progressive Disclosure

The in-body structure is good — a "Channel references" section maps each platform to a one-level-deep reference/<platform>.md link, clearly signaled — but none of the four referenced files (reference/wechat.md, wecom.md, dingtalk.md, lark.md) exist in the bundle; there is no references/ or reference/ directory at all, so every navigation link is dangling. Well-signaled references that lead nowhere sit between the 'references not clearly signaled' (3) and 'minor organization gaps' (4) anchors, closer to 3 because the broken links undermine the skill's core navigation.

3 / 5

Total

15

/

20

Passed

Description

78%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 well-targeted description with explicit multi-condition 'Use when' triggers, named platforms, and concrete actions, written in appropriate third-person imperative style. Its main limitations are trigger-only phrasing (no separate what-statement) and missing common platform synonyms such as Feishu for Lark.

DimensionReasoningScore

Specificity

Names three concrete actions with enumerated platforms — "connecting or configuring IM channel bots (WeChat, WeCom, DingTalk, Lark)", "receiving a user message with an <im> block", "sending messages or files to a connected WeChat channel" — matching the 'several specific actions, minor gaps' anchor. Not 5 because capabilities are expressed only through trigger phrasing and coverage omits media handling, reply controls, and status checking that the body actually covers.

4 / 5

Completeness

The 'when' is explicit and strong ("Use when connecting or configuring... or receiving a user message with an <im> block, or sending messages or files..."), and a 'what' is embedded in those verb phrases (connect/configure, receive, send). Not 5 because there is no standalone capability statement — the what is only implied by trigger conditions — and not 3 because both elements are clearly present.

4 / 5

Trigger Term Quality

The four platform names (WeChat, WeCom, DingTalk, Lark) are exactly the natural terms users would say, plus "connect", "send messages or files". Not 5 because common synonyms are missing — notably "Feishu" (Lark's everyday name in its primary market), WeCom's Chinese name, and generic phrasings like "instant messaging" or "chat bot".

4 / 5

Distinctiveness Conflict Risk

Clear niche with distinct triggers: four named IM platforms plus the proprietary "<im> block" and "Claw mode" signals make false triggering very unlikely. The only mildly generic phrase ("sending messages or files") is tightly bounded to "a connected WeChat channel from the main agent", matching the minimal-conflict anchor.

5 / 5

Total

17

/

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: 6 missing

Warning

Total

15

/

16

Passed

Repository

dtyq/magic

Path

backend/super-magic/agents/skills/im-channels/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.