CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ui-creator

Converts UI images and/or OpenAPI specs into web application components with routing and service integration. Supports Angular and React (Vite). When UI images are provided, generates visual components using an integrated image-to-component procedure with screenshot validation. When only an OpenAPI spec is provided (no images), generates all pages directly using neutral default tokens. Supports any combination of images and OpenAPI spec.

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-engineered orchestrator skill: concrete executable commands, a clearly gated multi-step workflow with mandatory validation and feedback loops, and clean progressive disclosure into a real, well-organized bundle. The only real weakness is redundancy — the mock URL verification and placehold.co fallback instructions are duplicated between Step 5.1 and Step 7, and the uninterrupted-execution directive is stated three times.

DimensionReasoningScore

Conciseness

The body is dense, imperative, and assumes Claude's competence — no explanation of known concepts — but has real redundancy: the mock image URL HEAD-check and placehold.co fallback appears in both Step 5.1 and Step 7 item 3, and 'Do NOT stop / return control to the user' is repeated in Phase A, Phase B, and the Critical rules. Efficient overall, just not 'every token earns its place'.

4 / 5

Actionability

Guidance is copy-paste ready throughout: 'test -d node_modules/playwright && test -d node_modules/tsx || npm install playwright tsx', 'npx playwright install chromium', 'curl -s -o /dev/null -w "%{http_code}" "<url>"', the placehold.co URL template with parameter meanings, port-fallback commands ('ng serve --port 4201', 'npm run dev -- --port 5174'), and a concrete example of the Step 4 page-map output. Specific examples cover the common cases and delegate platform detail to real reference files.

5 / 5

Workflow Clarity

A clearly sequenced 8-step workflow with explicit validation gates and feedback loops for a batch operation: mandatory Step 5.1 ('Do NOT proceed to Step 6 until all image URLs return 200'), per-page screenshot verification with 'Fix any obvious inconsistencies', a growing style-reference learn loop between pages, build verification in Step 8, and a Critical rules checklist. This matches the validate → fix → re-validate anchor.

5 / 5

Progressive Disclosure

The body is an orchestrator overview with well-signaled, one-level-deep links to real bundle files — platform-angular.md, platform-react.md, design-tokens-guide.md, mock-server-template.md, image-to-component.md, genexus-backend.md all exist in references/, and scripts/capture-screenshot.ts exists for the screenshot procedure. Platform-specific and procedural detail is appropriately split out, and inline content stays at the orchestration level.

5 / 5

Total

19

/

20

Passed

Description

66%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 specific, third-person description that clearly conveys what the skill does across its input modes, with strong concrete capability statements. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness and slightly weakens trigger-term quality. Adding trigger phrasing with natural synonyms (mockup, screenshot, design-to-code) would raise it to the top band.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user provides UI mockups/screenshots or an OpenAPI spec and wants a working web app generated from them.'

Include natural synonyms users would say — 'mockup', 'screenshot', 'design', 'spec-to-app' — alongside 'UI images' and 'OpenAPI specs'.

Optionally mention secondary deliverables (mock server, running dev URL) to close the coverage gap in the capability list.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'Converts UI images and/or OpenAPI specs into web application components with routing and service integration', 'generates visual components using an integrated image-to-component procedure with screenshot validation', 'generates all pages directly using neutral default tokens' — in third person. Not a 5 because secondary capabilities (mock server, build verification, inferred pages from unmapped endpoints) are absent, leaving minor gaps in coverage.

4 / 5

Completeness

The 'what' is clearly and concretely answered (converts images/specs into components with routing and services, per-mode behavior), but there is no 'Use when...' clause or equivalent explicit trigger guidance — the internal 'When UI images are provided...' phrases describe operating modes, not when to invoke the skill, which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Good natural keyword coverage: 'UI images', 'OpenAPI specs', 'web application components', 'Angular', 'React (Vite)', 'routing', 'service integration' — terms a user asking for image-to-app or spec-to-app conversion would plausibly say. Not a 5 because common synonyms like 'mockup', 'screenshot', 'design', or 'frontend' are missing.

4 / 5

Distinctiveness Conflict Risk

The image-to-component plus OpenAPI-to-app niche with explicit platform names (Angular, React/Vite) is mostly distinct with clear triggers. Not a 5 because it could still overlap with generic web-development or UI-generation skills given no explicit trigger phrasing.

4 / 5

Total

15

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

cinthamo/genexus-skills

Path

frontend/ui-creator/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.