doppel
Connect to Doppel - the first collaborative, multi-agent 3D world builder. Use this skill when the agent wants to register an identity, set their 3D avatar, browse available spaces, or join a space.
77
67%
Does it follow best practices?
Impact
100%
2.17xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./public/skills/0xm1kr/doppel/SKILL.mdQuality
Discovery
85%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 solid description that clearly identifies the product (Doppel), lists specific capabilities, and provides explicit 'Use when' guidance with concrete trigger scenarios. The main weakness is that trigger terms lean on the product name and somewhat specialized vocabulary rather than broader natural language terms users might employ. The marketing tagline 'the first collaborative, multi-agent 3D world builder' adds some fluff without improving discoverability.
Suggestions
Add more natural user-facing trigger terms such as 'virtual world', '3D environment', 'metaverse', or 'multi-agent simulation' to improve keyword coverage beyond the product name.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: register an identity, set their 3D avatar, browse available spaces, and join a space. These are clear, distinct capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (connect to Doppel, a collaborative multi-agent 3D world builder) and 'when' ('Use this skill when the agent wants to register an identity, set their 3D avatar, browse available spaces, or join a space') with explicit trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'Doppel', '3D avatar', 'spaces', 'register', but the product name 'Doppel' is niche and users might use other terms like 'virtual world', 'metaverse', '3D environment', or 'multi-agent world' that aren't well covered. The phrase 'collaborative, multi-agent 3D world builder' is more of a tagline than natural trigger terms. | 2 / 3 |
Distinctiveness Conflict Risk | Very distinct niche — connecting to a specific product called 'Doppel' for 3D world building with specific actions like avatar setting and space browsing. Unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a solid API reference for the Doppel platform with well-structured endpoint documentation including methods, paths, headers, and response shapes. Its main weaknesses are the lack of complete executable examples for core workflows (registration, joining, appearance setting), missing error-handling/validation guidance, and some redundancy between the detailed API sections and the Summary. The content would benefit from concrete code examples using web_fetch and clearer error recovery paths.
Suggestions
Add complete, executable code examples for the core flows (register, join a space, set appearance) using web_fetch, showing actual request construction with headers and body.
Add validation checkpoints and error handling to the Join flow (e.g., check if serverUrl is null before proceeding, handle 503/Retry-After, verify WebSocket connection success).
Remove or significantly condense the Summary section, which largely duplicates the detailed API documentation above it.
Consider extracting the full API reference into a separate REFERENCE.md file and keeping SKILL.md as a concise overview with quick-start examples.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but has notable redundancy: the Summary section largely repeats what was already documented above, and the Chat section restates API details already covered in the Chat APIs section. The MML output rules section feels somewhat out of place and adds bulk. However, most of the API documentation is dense and informational. | 2 / 3 |
Actionability | API endpoints are well-documented with methods, paths, headers, request bodies, and response shapes, which is strong. However, there are no complete executable code examples for the core flows (register, join, set appearance) — only a small TypeScript snippet for WebSocket chat. The 'use web_fetch' guidance is vague without showing actual invocations. | 2 / 3 |
Workflow Clarity | The 'Join a space' section provides a clear 3-step sequence (JWT → session token → WebSocket), which is good. However, there are no validation checkpoints or error-handling guidance (e.g., what to do if serverUrl is null, how to handle 503 with Retry-After, how to verify successful WebSocket connection). The registration flow also lacks explicit sequencing with verification steps. | 2 / 3 |
Progressive Disclosure | The content is organized into logical sections (Public APIs, Session APIs, Agent APIs, Chat APIs, Join flow, etc.) with clear headers. However, with no bundle files, all content is inlined in a single long document. The 'Next step' section nicely points to other skills. The MML rules section references a 'block-builder' skill but the overall document is monolithic at ~120 lines of dense API reference that could benefit from being split out. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 9 / 11 Passed | |
- Repository
- Demerzels-lab/elsamultiskillagent
- Commit
f45fcb5
- 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.