thesys-generative-ui

> Generate, modify, and style React components from natural language using the Thesys SDK. Guides schema-driven UI generation, theme customisation, tool calling integration, and deployment to Vite, Next.js, or Cloudflare Workers. Use when the user says "generate UI", "create a component", "build an interface", "Thesys", "generative UI", or asks to turn a description into a React component.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Advisory

Suggest reviewing before use

Quality

Content

65%

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

The body is concise and well-structured with executable Quick Start code and a clear reference index, but it stops short of fully actionable detail and lists references and templates that are not present in the bundle. No verification step is given for generated output.

Suggestions

Resolve dangling references: either add the missing `references/tool-calling-guide.md` and `references/theme-customization.md` (or `theme-customization` coverage) and the advertised template files, or remove them from the Resources section so every listed path exists.

Document the `theme` and `schema` parameters used in the examples (valid theme values, the full component schema shape) so the Quick Start code is copy-paste ready rather than illustrative.

Add a short verification step after generation (e.g., render the component / check it matches the requested props) to give the workflow an explicit validation checkpoint.

Dimension	Reasoning	Score
Conciseness	The body is lean — a tight Quick Start, a short feature list, and a reference index — with no padded explanations of concepts Claude already knows. Every section earns its place; the only time-sensitive line ('Last Updated: 2025-11-10') is a minor, non-padded detail.	3 / 3
Actionability	Quick Start and Example provide executable code, but details are incomplete: the example passes `theme: 'modern'` without explaining valid values, and the `schema` shape (`type: 'component'`, `props: [...]`) is presented without validation against the real API, leaving key details implicit.	2 / 3
Workflow Clarity	The skill is largely a single generate-call, but the body offers no sequenced process and no validation/verification checkpoint (e.g., confirming a generated component renders or matches the schema), so the sequence is implicit rather than explicit.	2 / 3
Progressive Disclosure	Sections are well organized and references are one level deep, but two listed files do not exist in the bundle (`references/tool-calling-guide.md`, `references/theme-customization.md`) and the advertised 'Templates (15+ files)' are absent, so the navigation points to missing material.	2 / 3
	Total	9 / 12 Passed

Description

100%

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 specific, third-person, and provides explicit trigger terms covering both what the skill does and when to invoke it. It is a strong, concise skill description with no over-claims or fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Generate, modify, and style React components', 'schema-driven UI generation, theme customisation, tool calling integration, and deployment to Vite, Next.js, or Cloudflare Workers' — matching the level-3 anchor.	3 / 3
Completeness	Both 'what' (concrete actions) and 'when' (explicit 'Use when the user says...' clause) are clearly present, satisfying the level-3 anchor.	3 / 3
Trigger Term Quality	Natural trigger terms a user would say are well covered — 'generate UI', 'create a component', 'build an interface', 'Thesys', 'generative UI'. Third-person voice ('Generate, modify') is correct, so no specificity penalty applies.	3 / 3
Distinctiveness Conflict Risk	A clear niche (Thesys-driven generative UI) with distinct triggers makes it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	15 / 16 Passed

Repository: secondsky/claude-skills
Commit: c4889f6

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.