CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

channel-signal

Signal messaging channel for Clawdbot agent

Quality

55%

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

Quality

Content

57%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 refreshingly concise and the setup block is executable, but it covers only environment setup and never explains how to operate the channel or where the real logic lives (scripts/channel.py). Claude would know how to install dependencies but not how to send a message.

Suggestions

Add a short Usage section showing how to run scripts/channel.py for send/send_file/react/reply with a concrete command example.

Link to scripts/channel.py explicitly so Claude knows where the implementation and action handlers live.

Include a verification step after setup (e.g. run signal-cli --version or send a test message) to confirm the channel works before relying on it.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence — just an intro line and an executable setup block — with only minor padding ("the most private messaging channel"); this fits 'Efficient; minor instances of over-explanation that could be trimmed' rather than the fully token-perfect level 5.

4 / 5

Actionability

The setup commands (venv, pip install) are concrete and executable, but there is no guidance on actually using the channel (send/send_file/react/reply) or invoking scripts/channel.py, fitting 'Some concrete guidance but incomplete; missing key details' rather than the mostly-complete level 4.

3 / 5

Workflow Clarity

A rough setup sequence is present but the operational workflow (how to run the channel, handle events, verify it works) is absent, matching 'Steps listed but validation gaps; sequence present but checkpoints missing'; it does not reach 4 because key operational steps and any verification checkpoint are missing.

3 / 5

Progressive Disclosure

The body has a single Setup section but never surfaces the actual implementation (scripts/channel.py) or the supported actions declared in frontmatter, fitting 'Some structure but could be better organized; references present but not clearly signaled'; the simple-skill exception does not lift it to 4 because the core functionality is not navigated to.

3 / 5

Total

13

/

20

Passed

Description

32%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 identifies a distinct niche (Signal + Clawdbot), but it is too sparse: it states no concrete actions, lacks natural trigger phrases, and omits any 'when to use' guidance. It reads as a label rather than a usable skill description.

Suggestions

Add concrete actions, e.g. 'Send messages, files, reactions, and replies via Signal using signal-cli.'

Append a trigger clause such as 'Use when the user wants to send or receive Signal messages, or connect the Clawdbot agent to Signal.'

Include natural synonyms/extensions users might say (e.g. 'Signal', 'signal-cli', 'Signal messenger') to improve trigger matching.

DimensionReasoningScore

Specificity

The description names the domain ("Signal messaging channel") but lists no concrete actions, matching the anchor 'Names the domain but actions are minimal or generic'; it does not reach level 3, which requires 1-2 named actions.

2 / 5

Completeness

It offers a vague 'what' (a messaging channel) and no 'when'/use-guidance, matching the level-2 anchor 'Has a vague what and no when'; the missing 'Use when...' clause caps completeness at 3 per the guidelines, and there is no when at all so it stays at 2.

2 / 5

Trigger Term Quality

"Signal" and "messaging channel" are the only keywords, with no natural trigger phrases a user would say (e.g. 'send a Signal message', 'notify via Signal'); this fits 'one or two generic keywords; missing the natural phrases users say' rather than the broader coverage at level 3.

2 / 5

Distinctiveness Conflict Risk

Naming both "Signal" and "Clawdbot agent" carves a clear niche with low overlap risk, fitting 'Mostly distinct; minor overlap risk'; it does not reach 5 because there is no explicit trigger phrase to fully disambiguate usage.

4 / 5

Total

10

/

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/signal/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.