CtrlK
BlogDocsLog inGet started
Tessl Logo

rei

Set up Rei Qwen3 Coder as a model provider. Use when configuring coder.reilabs.org, adding Rei to Clawdbot, or troubleshooting 403 errors from Rei endpoints.

92

1.66x
Quality

88%

Does it follow best practices?

Impact

100%

1.66x

Average score across 3 eval scenarios

SecuritybySnyk

Risky

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-crafted skill that provides multiple paths to accomplish the same task (script, agent, manual) with appropriate detail for each. It's concise, actionable, and well-organized. The main gap is the lack of a verification step after setup to confirm the provider is working correctly before the user encounters errors in production.

Suggestions

Add a verification step after setup, e.g., 'Verify: `clawdbot model list | grep rei`' or a test command to confirm the endpoint responds before switching to it.

DimensionReasoningScore

Conciseness

The content is lean and efficient. It doesn't explain what Qwen3 is, what OpenAI-compatible endpoints are, or how API keys work. Every section serves a distinct purpose and there's no padding or unnecessary context.

3 / 3

Actionability

Provides fully executable commands (setup script, switch script, revert script), copy-paste ready JSON configuration for manual setup, and specific chat commands for model switching. All guidance is concrete and immediately usable.

3 / 3

Workflow Clarity

The setup workflow is clear with a single script, and there's a revert path for error recovery. However, there are no validation checkpoints — after setup, there's no step to verify the provider was added correctly or test the connection before use. For a configuration task that can produce 403 errors, a verification step would be valuable.

2 / 3

Progressive Disclosure

Content is well-structured with clear sections progressing from simplest (script setup) to most detailed (manual setup). The skill is under 50 lines of core content and references scripts appropriately. Troubleshooting is concise and placed at the end where it belongs.

3 / 3

Total

11

/

12

Passed

Description

89%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a well-crafted skill description for a narrow, specific task. It excels at completeness with a clear 'Use when' clause and has excellent distinctiveness due to unique proper nouns. The only minor weakness is that the 'what' portion could enumerate more specific actions beyond just 'set up'.

DimensionReasoningScore

Specificity

Names the domain (model provider setup) and some actions (configuring, adding, troubleshooting 403 errors), but doesn't list comprehensive concrete actions like specific configuration steps or multiple troubleshooting scenarios.

2 / 3

Completeness

Clearly answers both 'what' (set up Rei Qwen3 Coder as a model provider) and 'when' (configuring coder.reilabs.org, adding Rei to Clawdbot, troubleshooting 403 errors) with an explicit 'Use when' clause.

3 / 3

Trigger Term Quality

Includes highly specific natural trigger terms users would actually say: 'Rei Qwen3 Coder', 'coder.reilabs.org', 'Clawdbot', '403 errors', 'Rei endpoints'. These are precise terms that match real user queries.

3 / 3

Distinctiveness Conflict Risk

Extremely distinct with unique proper nouns (Rei Qwen3 Coder, Clawdbot, coder.reilabs.org) that are unlikely to conflict with any other skill. The niche is very clearly defined.

3 / 3

Total

11

/

12

Passed

Validation

100%

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

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
Demerzels-lab/elsamultiskillagent
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.