CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

channel-matrix

Matrix/Element messaging channel for Clawdbot agent

Quality

67%

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/matrix/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 content is admirably lean and well-structured for setup, but it stops at installation — it lacks actionable usage guidance and a clear end-to-end workflow for actually driving the Matrix channel.

Suggestions

Add a short usage section with an executable example of sending a message or invoking a supported action via scripts/channel.py.

Document the configuration workflow: set homeserver, access_token, and room_id, then run the channel, with a verification step that a test message arrived.

Explicitly link to scripts/channel.py from the body so readers can find the implementation details one level deep.

DimensionReasoningScore

Conciseness

The body is a lean one-line intro plus a single setup snippet with no padding or explanation of concepts Claude already knows; every token earns its place.

5 / 5

Actionability

The setup snippet (venv + pip install) is concrete and executable, but the body gives no actionable guidance for the skill's actual purpose — no examples of sending messages, files, reactions, or using the supported actions listed in frontmatter.

3 / 5

Workflow Clarity

A short setup sequence is present, but the end-to-end usage workflow (configure homeserver/access_token/room_id, run the channel, send a message) is missing, and there are no validation or verification checkpoints.

3 / 5

Progressive Disclosure

The body is well-organized into an intro and a Setup section and stays under 50 lines, with the channel implementation correctly split into scripts/channel.py (referenced one level deep in frontmatter); the minor gap is that the body never points the reader to channel.py for usage details.

4 / 5

Total

15

/

20

Passed

Description

52%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 distinct and names its niche clearly, but it is thin: it labels the channel without listing concrete actions and omits any 'when to use' trigger guidance.

Suggestions

Add concrete actions to the description, e.g. 'send messages, files, reactions, and replies via Matrix/Element'.

Append an explicit trigger clause such as 'Use when connecting Clawdbot to a Matrix/Element room'.

Include natural synonyms (chat, room, bot) to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

The phrase 'Matrix/Element messaging channel for Clawdbot agent' names the domain and target agent but offers no concrete actions — 'messaging channel' is a generic noun category rather than verbs like send, react, or edit (which appear in frontmatter but not the description).

2 / 5

Completeness

It states a clear 'what' (a Matrix/Element messaging channel for Clawdbot) but provides no 'when' guidance — no 'Use when...' clause or equivalent trigger, which caps completeness at 3 per the guidelines.

3 / 5

Trigger Term Quality

'Matrix/Element' and 'messaging channel' are relevant natural keywords a user would say, but coverage stops there — missing common synonyms such as chat, room, or bot that users also use for this domain.

3 / 5

Distinctiveness Conflict Risk

The combination of 'Matrix/Element' with 'Clawdbot agent' carves out a very specific integration niche with distinct triggers and minimal risk of firing for an unrelated skill.

5 / 5

Total

13

/

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