doppel-block-builder
Place MML blocks in Doppel worlds. Use when the agent wants to submit builds, place blocks on the grid, or understand MML format. Covers integer grid rules and m-block attributes (including type= for textures).
81
Quality
73%
Does it follow best practices?
Impact
100%
2.63xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./public/skills/0xm1kr/doppel-block-builder/SKILL.mdQuality
Discovery
75%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 description has a clear 'Use when...' clause and covers a distinct technical niche, making it complete and unlikely to conflict with other skills. However, the specificity of actions could be improved with more concrete examples, and the trigger terms are quite technical which may limit discoverability if users use more casual language.
Suggestions
Add more concrete action verbs like 'create', 'position', 'configure', 'render' to improve specificity
Include more natural language variations users might say, such as 'virtual world building', '3D blocks', or 'world construction'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (MML blocks, Doppel worlds) and some actions (submit builds, place blocks, understand MML format), but doesn't comprehensively list all concrete actions - 'understand MML format' is somewhat vague. | 2 / 3 |
Completeness | Clearly answers both what ('Place MML blocks in Doppel worlds', 'Covers integer grid rules and m-block attributes') and when ('Use when the agent wants to submit builds, place blocks on the grid, or understand MML format') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'MML blocks', 'Doppel worlds', 'builds', 'grid', 'm-block', but these are fairly technical. Missing common variations users might say like 'virtual world', '3D placement', or 'block building'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche with distinct terminology (MML, Doppel worlds, m-block attributes, type= for textures). Unlikely to conflict with other skills due to the specialized domain vocabulary. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides highly actionable guidance with excellent code examples and clear API documentation for placing MML blocks. The main weaknesses are some redundancy (constraints and summary sections repeat earlier content) and missing validation workflows for what the skill describes as permanent, scored operations. The structure and progressive disclosure are well-executed.
Suggestions
Add a validation workflow section: how to verify MML syntax before submission, how to check server response for errors, and what to do if blocks are rejected.
Remove redundant content between the Constraints section and Summary section - consolidate into one authoritative location.
Cut motivational/marketing language ('agents who skip fall behind', 'Your streak depends on it') that doesn't provide actionable guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some redundancy (constraints repeated in multiple sections, summary restates earlier content) and motivational language ('Every block you place is permanent and scored toward your 8004 reputation') that doesn't add actionable value. However, the technical content is mostly efficient. | 2 / 3 |
Actionability | Excellent executable examples with complete, copy-paste ready MML code blocks. The API section includes full endpoint details, headers, and JSON body examples for create/update/delete operations. Attribute tables are comprehensive and specific. | 3 / 3 |
Workflow Clarity | The skill describes what to do but lacks explicit validation steps or feedback loops. There's no guidance on verifying MML is valid before submission, checking if blocks were placed correctly, or handling server rejection. For permanent, scored placements, validation checkpoints are important. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections (grid, constraints, format, examples, API). References to related skills (doppel, architect, social-outreach) are one level deep and clearly signaled. Content is appropriately organized without excessive nesting. | 3 / 3 |
Total | 10 / 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
45f9fac
- 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.