CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

muapi-floor-plan-rendering

Design a 2D floor plan and convert it into a realistic, high-quality 3D architectural rendering.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./library/visual/floor-plan-rendering/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

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

The body is a lean, well-structured, actionable two-phase workflow with concrete model IDs, prompt templates, and fallback instructions. Main gaps are minor: no failure/validation handling after image generation and slightly redundant framing content.

DimensionReasoningScore

Conciseness

The body is efficient: a compact inputs table, two templated phases with concrete prompts, and brief agent notes with no explanations of concepts Claude already knows. It falls short of 5 due to minor redundancy — the description is repeated verbatim as a bolded subtitle, and the 'Trigger Keywords' section duplicates information that belongs in the description.

4 / 5

Actionability

Concrete guidance is present: specific CLI commands ('muapi image generate' model=nano-banana-2, 'muapi image edit' model=nano-banana-2-edit), full prompt templates, aspect ratios, an auth fallback, and a curl fallback with polling. It is not a 5 because the muapi invocations are described as labeled steps rather than complete copy-paste command lines with argument syntax.

4 / 5

Workflow Clarity

The two-phase sequence (2D design → user approval → 3D conversion) is clearly ordered with an explicit checkpoint ('Present the 2D plan to the user for approval') and conditional branching on the optional input. It misses a 5 because there is no validation of generation results (e.g. checking the returned image or retry guidance on failure), only output presentation.

4 / 5

Progressive Disclosure

The skill has no bundle files and is under 50 lines, and per the rubric's simple-skill exception a well-organized single file scores 5. Sections (Inputs, Steps by phase, Trigger Keywords, Notes) are clearly headed and logically ordered with no inline content that belongs in a separate file.

5 / 5

Total

17

/

20

Passed

Description

53%Weight 40%Scale 1-5

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

The description is concise and clearly states what the skill does, but it lacks an explicit 'when to use' trigger clause and natural trigger-term coverage, capping both completeness and trigger quality at 3. It is a distinct niche skill with only minor conflict risk.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user wants to turn a floor plan, house layout, or apartment design into a 3D rendering.'

Include natural trigger synonyms in the description such as 'house plan', 'apartment layout', 'interior design rendering', and '2D to 3D conversion'.

Drop the 'realistic, high-quality' padding in favor of one more concrete capability detail to lift specificity.

DimensionReasoningScore

Specificity

The description names the domain and exactly two concrete actions — "Design a 2D floor plan" and "convert it into a realistic, high-quality 3D architectural rendering" — matching the '1-2 concrete actions, but not comprehensive' anchor. It is not a 4 because no further actions or coverage details are given, and 'realistic, high-quality' is mild fluff rather than additional capability.

3 / 5

Completeness

The 'what' is clear (design a 2D floor plan and convert it to a 3D rendering), but there is no 'Use when...' clause or equivalent trigger guidance in the description — the judging guidelines explicitly cap completeness at 3 in that case. It is not a 2 because the 'what' is concrete and unambiguous.

3 / 5

Trigger Term Quality

Relevant keywords like "2D floor plan" and "3D architectural rendering" appear, but common user variations (e.g. "render my house plan", "floor plan design", "3D house model") are missing from the description. This matches 'Some relevant keywords but missing common variations or synonyms' rather than the good coverage of a 4.

3 / 5

Distinctiveness Conflict Risk

Floor-plan-to-3D-rendering is a clear niche with distinct triggers and minimal overlap with other skills. It falls just short of a 5 because phrases like 'design' and 'rendering' could mildly overlap with general image-generation or design skills without more distinctive trigger phrasing.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

SamurAIGPT/Generative-Media-Skills

Path

library/visual/floor-plan-rendering/SKILL.md

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.