CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

open-design

Generate web, mobile, and desktop prototypes, slides, dashboards, and editorial layouts from a single prompt using brand-grade design systems. Use when the user wants /web-prototype, /mobile-app, or /dashboard interactive HTML previews exportable to HTML, PDF, PPTX, or MP4 without Figma.

Quality

77%

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 ./skills/web-and-frontend-development/open-design/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 concise, well-sectioned overview that avoids padding and states clear guardrails, but it reads more like a catalog of example prompts than an operational skill. Actionability and workflow clarity are the weak points: two of three commands lack any workflow, and none of the workflows include validation steps or concrete implementation details.

Suggestions

Add concrete implementation guidance for each command: a starter sandboxed-HTML scaffold, named design token values (spacing scale, color roles, typography stack), and the sandboxing technique to use, instead of directives like "Apply design tokens for spacing, color, and typography".

Add validation checkpoints to the /web-prototype workflow (e.g., verify all navigation links resolve and the preview renders before offering export) and mirror the workflow structure in /mobile-app and /dashboard, which currently have only example prompts.

Specify the export mechanism — the actual tooling or commands used to produce PDF, PPTX, and MP4 — so the guardrail "Note export dependencies (PDF/PPTX/MP4) if tooling is unavailable" is actionable rather than abstract.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no space is spent explaining known concepts, and example prompts are compact. Minor instances could be trimmed: the intro line "Local-first, open-source design system for rapid prototyping..." largely repeats the frontmatter description, and "Runs on Claude Code, Cursor, Codex, Gemini CLI, and Copilot" is only marginally actionable.

4 / 5

Actionability

Guidance such as "Build sandboxed HTML with navigation between key views" and "Apply design tokens for spacing, color, and typography" is high-level direction without specifics — no HTML scaffold, no token names or values, no export commands or tooling names. The example prompts are concrete illustrations of desired output, which keeps this above the minimal-guidance anchor, but key execution details are missing.

3 / 5

Workflow Clarity

Only /web-prototype has a sequenced workflow (clarify → build → apply tokens → offer export); /mobile-app and /dashboard consist solely of example prompts with no steps. No validation checkpoints exist anywhere (e.g., verifying the preview renders or links resolve), matching the "sequence present but checkpoints missing" anchor; this is not a destructive/batch skill, so no hard cap applies.

3 / 5

Progressive Disclosure

There are no bundle files, and the ~59-line body is well-organized into clear per-command sections, a Guardrails section, and a source-repo pointer, with no nested references. It scores 4 rather than 5 due to minor organization gaps — the workflow structure is inconsistent across the three command sections — and because the body slightly exceeds the under-50-line simple-skill threshold.

4 / 5

Total

14

/

20

Passed

Description

83%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.

A strong description: it states concrete capabilities with explicit export formats, includes an explicit "Use when..." clause with natural trigger terms, and is clearly distinguishable from unrelated skills. The main gaps are missing common synonyms (mockup, wireframe, landing page) and reliance on a single generate-verb framing.

DimensionReasoningScore

Specificity

"Generate web, mobile, and desktop prototypes, slides, dashboards, and editorial layouts" and "exportable to HTML, PDF, PPTX, or MP4" name several concrete outputs and formats, matching the 'several specific actions; minor gaps' anchor. It falls short of 5 because the description is essentially one action verb ('generate') with many objects rather than multiple distinct concrete actions.

4 / 5

Completeness

It explicitly answers both: the "what" ("Generate web, mobile, and desktop prototypes, slides, dashboards, and editorial layouts... using brand-grade design systems") and the "when" ("Use when the user wants /web-prototype, /mobile-app, or /dashboard interactive HTML previews"). Both are concrete and explicit, matching the top anchor; the "when" clause names specific trigger commands.

5 / 5

Trigger Term Quality

Triggers like "/web-prototype", "/mobile-app", "/dashboard", "prototypes", and "dashboards" are phrases users would naturally say, giving good coverage. A few natural synonyms are missing (e.g., "mockup", "wireframe", "landing page", "UI"), keeping it below the comprehensive-coverage anchor at 5.

4 / 5

Distinctiveness Conflict Risk

Slash-command triggers and the "without Figma" positioning carve out a clear niche with mostly distinct triggers. Minor overlap risk remains with presentation and data-visualization skills ("slides", "dashboards"), so it does not reach the minimal-conflict anchor at 5.

4 / 5

Total

17

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

eigent-ai/agent-skills

Path

skills/web-and-frontend-development/open-design/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.