channel-line

LINE messaging channel for Clawdbot agent

Quality

52%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/channels/line/SKILL.md

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 body is admirably concise and the setup commands are executable, but it stops at installation and never explains how to run or use the channel. It also fails to point readers to the scripts/channel.py implementation that carries the real logic.

Suggestions

Add a short usage/run section showing how to invoke scripts/channel.py and the stdin JSON command protocol for send/send_file/reply.

Reference the implementation explicitly, e.g. "See scripts/channel.py for the channel runtime" so the bundle file is clearly signaled.

Include a minimal send example with expected input/output events so the workflow is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is a lean overview with executable setup commands and no padding or explanation of concepts Claude already knows, matching the score-3 anchor of lean, efficient content where every token earns its place.	3 / 3
Actionability	The Setup block gives concrete executable commands, but there is no usage guidance for the supported actions (send, send_file, reply) and no example of invoking the channel, matching the score-2 anchor of some concrete guidance that is incomplete and missing key details.	2 / 3
Workflow Clarity	Setup is sequenced (venv then pip install), but the operational workflow for actually running the channel and handling messages is absent with no validation or checkpoints, matching the score-2 anchor of steps listed with implicit or missing checkpoints.	2 / 3
Progressive Disclosure	The body is well-organized into concise sections, but the core bundle file scripts/channel.py (the actual implementation) is not referenced or signaled anywhere in the body, matching the score-2 anchor of structure present but references not clearly signaled.	2 / 3
	Total	9 / 12 Passed

Description

40%

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 correctly identifies the domain and platform but is too thin: it states no concrete actions and lacks an explicit use-when trigger clause. It is distinguishable by the LINE name yet would benefit from naming capabilities and trigger terms.

Suggestions

Name concrete actions, e.g. "Send messages, files, and replies to LINE Messenger users via the Clawdbot agent."

Add an explicit trigger clause such as "Use when connecting the Clawdbot agent to LINE Messenger or when the user mentions LINE bots/messaging."

Drop or contextualize the product jargon "Clawdbot agent" with a natural phrasing a user would actually say.

Dimension	Reasoning	Score
Specificity	The description "LINE messaging channel for Clawdbot agent" names only the domain via an abstract noun phrase; it lists no concrete actions (e.g. send, reply, send_file), matching the vague/no-actions anchor rather than the score-2 anchor that names some actions.	1 / 3
Completeness	It answers what the skill is (a LINE messaging channel) but provides no "Use when..." clause or equivalent explicit trigger guidance, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	"LINE" and "messaging" are natural terms a user would say, but coverage is thin and "Clawdbot agent" is product jargon, so it matches the score-2 anchor of some relevant keywords missing common variations rather than the comprehensive score-3 example.	2 / 3
Distinctiveness Conflict Risk	"LINE" is a specific platform giving it a niche, but "messaging channel" is a broad category with many similar channel skills and there are no distinct triggers, matching the score-2 anchor of being somewhat specific yet able to overlap with similar skills.	2 / 3
	Total	7 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: SharpAI/DeepCamera
Path: skills/channels/line/SKILL.md
Commit: 2264fcb

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.