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

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/thesys-generative-ui/skills/thesys-generative-ui/SKILL.md

Quality

Content

65%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 reasonably lean overview with executable examples and a sensible reference layout, weakened by a missing multi-step workflow with validation and by broken/missing bundle paths that harm navigation.

Suggestions

Add a short, numbered deployment workflow with an explicit validation step (e.g. build → type-check → preview) for the Vite/Next.js/Cloudflare targets, since integration is a fragile multi-step process.

Fix or remove dangling references: create references/tool-calling-guide.md and references/theme-customization.md (or point to the existing tool-calling.md / theme docs), and either provide a templates/ directory or drop the "15+ templates" claim.

Tighten actionability by including the inline setup line (e.g. `npm install thesys`) alongside the Quick Start import, so the first example is fully runnable as written.

Dimension	Reasoning	Score
Conciseness	The body is lean with code that earns its place and no concept over-explanation; only minor trimmable fluff (e.g. "AI-Powered: Uses LLMs for intelligent design") keeps it just below the top anchor.	4 / 5
Actionability	Two executable TypeScript generateUI examples are concrete and copy-paste ready, but inline setup context (install/import) is absent and the second example reuses the same call shape, leaving minor gaps.	4 / 5
Workflow Clarity	No explicit multi-step sequence or validation checkpoints are given; deployment to Vite/Next.js/Cloudflare is a fragile integration that the body only implies via references, so checkpoints are missing despite a sequence being present.	3 / 5
Progressive Disclosure	Structure is well grouped and references are one level deep and clearly signaled, but navigation is undermined by broken links: tool-calling-guide.md and theme-customization.md do not exist and the advertised "15+ templates" have no corresponding directory.	3 / 5
	Total	14 / 20 Passed

Description

92%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, third-person description that pairs comprehensive concrete capabilities with an explicit trigger clause. Minor synonym coverage gaps keep trigger_term_quality just below the top anchor.

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" — giving comprehensive coverage with no significant gaps.	5 / 5
Completeness	Explicitly answers both what it does (the action list) and when to use it via a clear "Use when..." clause with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ("generate UI", "create a component", "build an interface", "Thesys", "generative UI", "turn a description into a React component") with good synonym coverage, but a few natural variants (e.g. "Thesys SDK", product-specific synonyms) are missing.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche — Thesys-driven generative React UI with named deployment targets — with distinct triggers and minimal overlap risk against other skills.	5 / 5
	Total	19 / 20 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
Path: plugins/thesys-generative-ui/skills/thesys-generative-ui/SKILL.md
Commit: ad16332

Reviewed: 12 days 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.