CtrlK
BlogDocsLog inGet started
Tessl Logo

im-channels

Use when connecting or configuring IM channel bots (WeChat, WeCom, DingTalk, Lark), or when you receive a user message that contains an <im> block indicating it was sent from an IM channel — read this skill to understand what the context means and how to handle it correctly.

63

Quality

75%

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 ./backend/super-magic/agents/skills/im-channels/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

The content is concise and well-organized with a clear two-scenario structure, but its actionability and workflow clarity are undermined because the primary bot-connection path depends on reference files that are not present in the bundle.

Suggestions

Bundle the four referenced files (reference/wechat.md, wecom.md, dingtalk.md, lark.md) or inline the essential connect steps so the central workflow is executable without missing references.

Add an explicit validation/verification checkpoint in Scenario B (e.g., confirm the connection via get_im_channel_status before reporting success) to close the workflow's feedback loop.

Provide a concrete, self-contained run_sdk_snippet example for at least one platform in the body so the connect action is actionable when the reference file is unavailable.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no padded explanations of what IM platforms or libraries are, terse field semantics, and direct guidance where every section earns its place.

3 / 3

Actionability

Concrete guidance is present (exact <im> block format, 'use its path directly', and a copy-paste status snippet), but the central connect-a-bot action is gated behind reference files that are not bundled, so the key workflow is not self-contained.

2 / 3

Workflow Clarity

Scenario B has a clearly sequenced 4-step process with a success/failure branch, but the risky connection step delegates all execution and validation to the missing reference file, leaving validation checkpoints only implicit.

2 / 3

Progressive Disclosure

The overview is well structured and correctly splits per-platform detail into one-level-deep, clearly signaled reference links — but the referenced files (reference/wechat.md, wecom.md, dingtalk.md, lark.md) do not exist in the bundle, so the signaled references do not resolve.

2 / 3

Total

9

/

12

Passed

Description

85%

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 strong description that explicitly covers both what the skill does and when to use it, with concrete actions and a distinct IM-channel niche. Its only weakness is that half of the trigger language relies on an internal <im> signal rather than naturally voiced user phrasing.

DimensionReasoningScore

Specificity

Names multiple concrete actions ('connecting or configuring IM channel bots', 'understand what the context means', 'handle it correctly') across four named platforms, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what (connecting/configuring bots and understanding incoming <im> messages) and when via 'Use when connecting or configuring...' and the '<im>' block trigger, matching the 'clearly answers both what AND when with explicit triggers' anchor.

3 / 3

Trigger Term Quality

Natural terms like 'connecting' and 'configuring' bots and platform names appear, but the second trigger ('when you receive a user message that contains an <im> block') is an internal/technical signal rather than language a user would naturally say, leaving common variations uncovered.

2 / 3

Distinctiveness Conflict Risk

A clear niche (IM channel bots for WeChat/WeCom/DingTalk/Lark plus inbound <im> blocks) with distinct triggers that are unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 4 missing

Warning

Total

15

/

16

Passed

Repository
dtyq/magic
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.