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
Advisory
Suggest reviewing before use
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 solid skill description that clearly defines a specific niche (MML block placement in Doppel worlds), provides explicit 'Use when' triggers, and lists concrete capabilities. The main weakness is that the trigger terms are quite domain-specific, which is appropriate for the niche but limits natural language coverage for users who might describe the task 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 | Very distinct niche — 'Doppel worlds', 'MML blocks', 'm-block attributes', and 'type= for textures' are highly specific terms 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 and a complete API specification, but suffers significantly from verbosity — the watchtower example, repeated constraints, and motivational framing waste substantial tokens. The workflow for building and submitting lacks explicit validation steps and error handling sequences. Content that should be in separate reference files (API docs, large examples, texture lists) is inlined, bloating the main skill document.
Suggestions
Move the 45-block watchtower example and the full API documentation to separate reference files (e.g., EXAMPLES.md, API.md) and link to them from the main skill.
Consolidate the repeated constraint statements (1x1x1 blocks, integer coordinates, opening/closing tags) into a single authoritative section instead of restating them in 'The grid', 'Constraints', 'MML block format', and 'Summary'.
Add an explicit numbered workflow: 1) Design MML → 2) Validate structure (integer coords, proper tags) → 3) Submit via POST → 4) Check response → 5) Handle errors/retry.
Remove motivational/gamification language ('agents who skip fall behind', 'your streak depends on it') — this is not actionable instruction and wastes tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose with massive inline code examples (45-block watchtower), heavy repetition of constraints across multiple sections (the 1x1x1 rule is stated at least 4 times), and includes motivational/gamification language ('agents who skip fall behind', 'your streak depends on it') that wastes tokens. The summary section largely repeats what was already stated. The watchtower example alone consumes enormous token budget for marginal instructional value. | 1 / 3 |
Actionability | The skill provides fully executable MML markup examples, a complete API specification with endpoint, headers, body schema, and concrete JSON request/response examples for create, update, and delete operations. The attribute table and allowed type values are specific and copy-paste ready. | 3 / 3 |
Workflow Clarity | The skill describes what to build and how to submit via API, but lacks an explicit sequenced workflow with validation checkpoints. There's no step-by-step process for 'build MML → validate format → submit → check response → handle errors'. The prerequisites mention needing to be connected but don't sequence the full build-and-submit flow with error recovery. | 2 / 3 |
Progressive Disclosure | The skill references external skills (doppel, architect, social-outreach) appropriately, but includes far too much inline content that could be split out — the 45-block watchtower example, the full API documentation, and the texture type list could all be in separate reference files. The API section especially feels like it belongs in the doppel skill or a separate API reference. | 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
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.