Content
68%Weight 40%Scale 1-5Reviews 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.
| Dimension | Reasoning | Score |
|---|---|---|
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 |