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).
77
67%
Does it follow best practices?
Impact
100%
2.63xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./public/skills/0xm1kr/doppel-block-builder/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 well-structured skill description that clearly defines both what the skill does and when to use it, with a distinct niche in MML block placement for Doppel worlds. The main weakness is that the trigger terms are quite domain-specific, which is appropriate for the niche but limits natural keyword coverage for users who might phrase requests differently.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: placing MML blocks, submitting builds, placing blocks on the grid, understanding MML format, integer grid rules, and m-block attributes including type= for textures. | 3 / 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 keywords like 'MML blocks', 'Doppel worlds', 'builds', 'grid', 'm-block', 'textures', but these are fairly domain-specific jargon. A user might say 'place blocks' or 'build in Doppel' but common variations or more natural phrasing are limited. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with domain-specific terms like 'MML blocks', 'Doppel worlds', 'm-block attributes', and 'type= for textures' that are 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.
The skill is highly actionable with concrete MML examples, a complete attribute reference, and detailed API documentation. However, it is significantly too verbose — the 45-block watchtower example, repeated constraint statements, and motivational language waste substantial token budget. The workflow lacks explicit validation steps for what is described as a permanent, scored operation.
Suggestions
Cut the watchtower example to ~10 blocks or replace with a compact pattern description (e.g., 'repeat pillar pattern at corners'), and trim the L-wall example to 3-4 blocks — the format is clear from one block.
Remove duplicate information: the constraints section largely restates 'The grid' section, and the summary restates both. Consolidate into a single constraints/rules section.
Add explicit validation steps: check API response for success, handle error responses, and verify the build appears correctly before proceeding — especially since placements are described as permanent.
Remove motivational/gamification language ('agents who skip fall behind', 'your streak depends on it') — Claude doesn't need persuasion, just instructions.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose. The watchtower example alone is 45 blocks of repetitive MML that could be summarized with a pattern description. The constraints section repeats the same rules stated in 'The grid' section. The summary re-states everything already covered. Motivational/gamification language ('agents who skip fall behind', 'your streak depends on it') wastes tokens on persuasion Claude doesn't need. The document is easily 3x longer than necessary. | 1 / 3 |
Actionability | The skill provides fully executable MML examples, a complete attribute reference table, specific API endpoint details with request/response formats, and copy-paste ready JSON payloads. The block type list, coordinate rules, and tag format are all concrete and unambiguous. | 3 / 3 |
Workflow Clarity | The skill covers what to build and how to submit via the API, but lacks an explicit step-by-step workflow with validation checkpoints. There's no guidance on verifying a build was accepted, handling API errors, or validating MML before submission. For a permanent/destructive operation ('every placement is permanent'), missing validation steps cap this at 2. | 2 / 3 |
Progressive Disclosure | The skill references the 'doppel' skill, 'architect' skill, and 'social-outreach' skill for related concerns, which is good separation. However, the inline content is bloated — the massive watchtower example and the full API documentation could be in separate reference files. The attribute table and texture list are reasonable inline, but the examples section is disproportionately large. | 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.