CtrlK
BlogDocsLog inGet started
Tessl Logo

robius-matrix-integration

CRITICAL: Use for Matrix SDK integration with Makepad. Triggers on: Matrix SDK, sliding sync, MatrixRequest, timeline, matrix-sdk, matrix client, robrix, matrix room, Matrix 集成, 聊天客户端

59

Quality

70%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/robius-matrix-integration/SKILL.md

The canonical home for this skill is robius-matrix-integration in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

71%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 a concrete, well-structured pattern reference with executable Rust code and a clear architectural flow. Its main gaps are in progressive disclosure: heavy inlined reference material and reference files that are listed but not actually present in the bundle.

Suggestions

Create the three referenced files under references/ (or remove the Reference Files section) so the promised navigation resolves to real content.

Move the large enum definitions (MatrixRequest, TimelineUpdate, RoomsListUpdate) into those reference files and keep SKILL.md as an overview pointing to them, improving both conciseness and progressive disclosure.

Add an explicit validation/checklist step in the worker-task flow (e.g., verify room exists and client is ready before dispatching) to turn implicit guards into named checkpoints.

DimensionReasoningScore

Conciseness

Prose is lean and domain-specific (Robrix/matrix-sdk APIs Claude genuinely lacks), with code doing the heavy lifting; minor trims possible in the large inlined enum dumps (MatrixRequest, TimelineUpdate, RoomsListUpdate), keeping it just below the score-5 'every token earns its place' anchor.

4 / 5

Actionability

Multiple concrete, mostly copy-paste-ready Rust examples (submit_async_request, matrix_worker_task, spawn_timeline_subscriber, build_client) cover common cases, but elisions like "// ... handle other requests" and "// ... handle other updates" leave minor gaps versus the fully-complete score-5 anchor.

4 / 5

Workflow Clarity

The request→worker→spawn→channel-update→SignalToUI→UI-poll flow is clearly sequenced and includes guards ("Room not ready yet" continue, PaginationError handling) and a Best Practices checklist; not score 5 because validation feedback loops are implicit rather than called out as explicit checkpoints.

4 / 5

Progressive Disclosure

Section headers are well-organized, but large reference-style enum dumps are inlined in SKILL.md and the three files listed under 'Reference Files' (references/matrix-client.md, timeline-handling.md, moly-api-integration.md) do not exist in the bundle — navigation is promised but broken, matching 'content that should be separate is inline' with non-real references.

3 / 5

Total

15

/

20

Passed

Description

68%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 has strong trigger coverage and a distinct, low-conflict niche, with an explicit use-when clause. Its main weakness is specificity: it states the integration domain but no concrete actions the skill performs.

Suggestions

Add 1-2 concrete actions to the description, e.g. 'Implements MatrixRequest request/response patterns, sliding sync room lists, and per-room timeline subscriptions in Makepad apps'.

Drop or de-emphasize internal jargon triggers like 'MatrixRequest' in favor of natural user phrasing such as 'Matrix messaging' or 'homeserver connection'.

DimensionReasoningScore

Specificity

The description names the domain ("Matrix SDK integration with Makepad") but lists no concrete actions — it only states a use-case and trigger keywords, matching the 'Names the domain but actions are minimal or generic' anchor rather than score 3 which requires 1-2 concrete actions.

2 / 5

Completeness

It provides both a 'what' ("Matrix SDK integration with Makepad") and an explicit 'when' ("Use for..." plus a "Triggers on:" keyword list); the 'when' is concrete but the 'what' lacks concrete actions, so it falls just short of the score-5 anchor.

4 / 5

Trigger Term Quality

Good keyword coverage spanning natural terms ("matrix client", "matrix room", "robrix", "sliding sync") plus Chinese variants ("Matrix 集成", "聊天客户端"), though it mixes in technical jargon ("MatrixRequest", "matrix-sdk") and omits some natural synonyms like "homeserver" or "Matrix messaging".

4 / 5

Distinctiveness Conflict Risk

The niche is clear (Matrix SDK + Makepad, with robrix/matrix-sdk/matrix room triggers) and unlikely to fire for unrelated skills, matching the 'Clear niche with distinct triggers; minimal conflict risk' anchor.

5 / 5

Total

15

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

14

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.