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

61%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/thesys-generative-ui/skills/thesys-generative-ui/SKILL.md

Quality

Discovery

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.

This is a strong skill description that clearly articulates specific capabilities (generating, modifying, and styling React components via the Thesys SDK), covers multiple deployment targets, and provides explicit trigger terms in a 'Use when...' clause. It uses proper third-person voice throughout and is concise yet comprehensive, making it easy for Claude to distinguish from other UI or React-related skills.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: generate, modify, and style React components; schema-driven UI generation; theme customisation; tool calling integration; deployment to Vite, Next.js, or Cloudflare Workers.	3 / 3
Completeness	Clearly answers both 'what' (generate/modify/style React components, schema-driven UI, theme customisation, tool calling, deployment) and 'when' with an explicit 'Use when...' clause listing specific trigger phrases.	3 / 3
Trigger Term Quality	Includes strong natural trigger terms users would say: 'generate UI', 'create a component', 'build an interface', 'Thesys', 'generative UI', 'turn a description into a React component'. These cover common phrasings well.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive due to the specific mention of Thesys SDK, schema-driven UI generation, and the particular deployment targets (Vite, Next.js, Cloudflare Workers). Unlikely to conflict with generic React or UI skills.	3 / 3
	Total	12 / 12 Passed

Implementation

22%

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

This skill provides a clean structure and good reference organization but falls short on actionability and workflow clarity. The code examples appear fabricated rather than reflecting the actual Thesys SDK API, and there are no concrete setup/installation/deployment workflows despite the skill claiming to cover three deployment targets. The core features section wastes tokens explaining concepts Claude already understands.

Suggestions

Replace the Quick Start with verified, executable code showing actual Thesys SDK installation (`npm install`) and real API usage including provider configuration and streaming setup.

Add a concrete multi-step workflow for at least one deployment target (e.g., Vite) with explicit validation steps: install → configure provider → generate component → verify render → build.

Remove the 'Core Features' bullet list — it explains what generative UI is, which Claude already knows. Replace with a concise constraints/gotchas section (e.g., required env vars, supported React versions, streaming requirements).

Provide the referenced bundle files or remove references to non-existent files to avoid misleading Claude into hallucinating file contents.

Dimension	Reasoning	Score
Conciseness	Mostly efficient but includes some unnecessary filler like the 'Core Features' bullet list which explains what generative UI is (natural language, AI-powered, React components) — things Claude already knows. The 'AI-Powered: Uses LLMs for intelligent design' line adds zero value.	2 / 3
Actionability	The code examples look plausible but are likely not executable — `generateUI` returning JSX directly that you embed in a component via `{ui}` doesn't match real Thesys SDK usage patterns (which involve streaming, chat contexts, and provider setup). There are no concrete commands for installation, no import paths verified, and no real configuration shown for any of the three deployment targets mentioned in the description.	1 / 3
Workflow Clarity	There is no workflow at all — no sequenced steps for setting up a project, no integration steps for Vite/Next.js/Cloudflare, no validation checkpoints. The skill describes a multi-framework SDK but provides no process for going from zero to a working component in any framework.	1 / 3
Progressive Disclosure	The references section is well-organized with clear one-level-deep pointers to specific files covering tool calling, themes, integration, and errors. However, no bundle files were provided, so none of these references actually exist, making the navigation structure aspirational rather than functional. The SKILL.md body itself is thin enough that the references are doing heavy lifting that can't be verified.	2 / 3
	Total	6 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: secondsky/claude-skills
Commit: 5e92b71

Reviewed: 3 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.