CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

channel-line

LINE messaging channel for Clawdbot agent

Quality

56%

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 ./skills/channels/line/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

43%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 admirably brief and well-sectioned for a simple skill, but it stops at environment setup and omits the actual channel-usage workflow, runtime invocation, and credential configuration. The dangling reference to a non-existent requirements.txt and the absence of any pointer to scripts/channel.py weaken actionability and navigation.

Suggestions

Add a concrete run/configure example, e.g. how to invoke scripts/channel.py with --channel-secret and --channel-access-token or a config file, plus the stdin JSON command format.

Either create requirements.txt (with line-bot-sdk) or remove the `pip install -r requirements.txt` line so the setup block is executable as written.

Add a brief '## Usage' or '## Commands' section covering the supported actions (send, send_file, reply) and link to scripts/channel.py so progressive disclosure is clear.

DimensionReasoningScore

Conciseness

The body is lean ('Connect SharpAI Aegis's Clawdbot agent to LINE Messenger' plus a compact setup block), with only minor non-earning padding in 'Popular in Japan, Taiwan, Thailand, and Indonesia.', fitting the score-4 anchor of efficient with minor trims possible; it is not a 5 because that popularity line adds no actionable value and not a 3 because no concepts are over-explained.

4 / 5

Actionability

Only a venv/pip setup block is provided; there are no concrete steps to run scripts/channel.py, configure credentials, set up a webhook, or send a message, and the referenced requirements.txt does not exist, matching the score-2 anchor of minimal concrete guidance missing the specific steps to execute.

2 / 5

Workflow Clarity

A rough setup sequence exists but the actual usage workflow (configure channel_secret/access_token, launch the channel, handle incoming/outgoing messages) is absent with no validation checkpoints, matching the score-2 anchor of rough sequence with many gaps and no validation.

2 / 5

Progressive Disclosure

There is a titled '## Setup' section and the skill is short, but the body never navigates to the bundled scripts/channel.py and references a missing requirements.txt, fitting the score-3 anchor of some structure with references not clearly signaled; it is not a 4 because navigation to the script is missing and not a 2 because the content is sectioned rather than a monolithic wall.

3 / 5

Total

11

/

20

Passed

Description

48%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 concise and clearly niched to LINE + Clawdbot, but it is purely a 'what' statement with no concrete actions and no 'when to use it' trigger guidance. Adding a Use-when clause and naming supported actions would lift the capped dimensions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when connecting the Clawdbot agent to LINE Messenger for sending messages or replying to users.'

Name the concrete supported actions (send, send_file, reply) in the description so specificity moves from domain-naming to action-listing.

Include natural user synonyms such as 'LINE Messenger' or 'LINE Bot' to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

The phrase 'LINE messaging channel for Clawdbot agent' names the domain but lists no concrete actions (e.g. send, reply), matching the score-2 anchor 'Names the domain but actions are minimal or generic'. It is not a 1 because it does identify a specific channel/agent, and not a 3 because no concrete actions are enumerated.

2 / 5

Completeness

A clear 'what' is present ('LINE messaging channel for Clawdbot agent') but there is no 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 3 and matches the score-3 anchor.

3 / 5

Trigger Term Quality

'LINE' and 'messaging' are relevant natural keywords, but common variations/synonyms a user might say (e.g. 'LINE Messenger', 'LINE Bot', 'LINE login') are absent, fitting the score-3 anchor of some relevant keywords missing common variations.

3 / 5

Distinctiveness Conflict Risk

The combination of 'LINE' and 'Clawdbot agent' carves a clear niche with only minor overlap risk against other messaging-channel skills, matching the score-4 anchor; it is not a 5 because no explicit distinct trigger phrases are given.

4 / 5

Total

12

/

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

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

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.