CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

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
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 has the right shape for a progressive-disclosure skill — lean overview, quick-start code, and a reference catalog — but is undermined by marketing fluff, a stale date, missing setup steps, and a resources section that references files that don't exist while ignoring real ones (scripts, error-catalog.md). Fixing the reference list to match the actual bundle is the highest-leverage improvement.

Suggestions

Reconcile the Resources section with the actual bundle: remove or create references/tool-calling-guide.md and references/theme-customization.md, drop the '15+ template files' claim (no templates exist), and add entries for the unreferenced error-catalog.md and scripts/ (check-versions.sh, install-dependencies.sh).

Cut the 'Core Features' bullet list and the 'Last Updated: 2025-11-10' line — both are padding Claude doesn't need, and the date is time-sensitive information outside a deprecated/old-patterns section.

Make the Quick Start fully executable by adding the install/setup step (e.g., npm install thesys plus minimal provider configuration) and replace the redundant second example with a pointer to the integration guide for each deployment target.

DimensionReasoningScore

Conciseness

The body is short, but it contains a time-sensitive "Last Updated: 2025-11-10" line outside any deprecated section, a marketing-flavored "Core Features" list ("AI-Powered: Uses LLMs for intelligent design") that assumes Claude's intelligence poorly, and a second "Example" that merely repeats the Quick Start with a different prop. This fits anchor 3 ("mostly efficient but includes some unnecessary explanation or could be tightened"); it is not 4 because the date and fluff bullets are explicitly penalized, and not 2 because the padding is a small fraction of an otherwise lean document.

3 / 5

Actionability

The Quick Start is near-executable TypeScript ("const ui = await generateUI({...})"), but there is no install/setup step for the SDK, and the second example is a fragment ("theme: 'modern'") with no surrounding code or explanation — key details are missing for a copy-paste start. That places it at anchor 3 rather than 4 (which requires only minor gaps); it is above 2 because real, runnable-looking code is present.

3 / 5

Workflow Clarity

Beyond a single Quick Start snippet there is no sequenced process: integration, tool calling, theming, and deployment are mentioned only as one-line file pointers with no ordering, checkpoints, or "start here, then..." guidance. Anchor 3 ("sequence present but checkpoints missing or implicit") is the best fit — the skill is not destructive so no validation cap applies, but the document exceeds the simple-skill exception (73 lines, multiple workflows) so it cannot score 5 without an explicit flow.

3 / 5

Progressive Disclosure

The structure is genuinely hub-like (short body, one-level-deep references with descriptions), but scored against the actual bundle it degrades: "references/tool-calling-guide.md" and "references/theme-customization.md" do not exist in ./references/, the claimed "15+ template files" are absent from the bundle, error-catalog.md is orphaned (never referenced), and scripts/check-versions.sh and scripts/install-dependencies.sh are unmentioned. That mixture of good structure with broken/phantom navigation fits anchor 3 rather than 4 ("minor organization gaps" would not include non-existent paths).

3 / 5

Total

12

/

20

Passed

Description

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

The description is an exemplar: concrete capabilities, explicit technology names, and a literal 'Use when...' clause with natural user phrasings including the product name. It closely matches the rubric's good_overall_examples with no fluff, over-claims, or voice violations.

DimensionReasoningScore

Specificity

"Generate, modify, and style React components from natural language using the Thesys SDK" plus "schema-driven UI generation, theme customisation, tool calling integration, and deployment to Vite, Next.js, or Cloudflare Workers" lists multiple concrete actions with the exact technologies involved, matching the comprehensive anchor. It is not the level below (4) because no meaningful capability is left unnamed; generation, styling, theming, tool calling, and deployment are all enumerated.

5 / 5

Completeness

The description explicitly answers "what" (generate/modify/style React components, schema-driven generation, theming, tool calling, deployment targets) and "when" via a literal "Use when the user says..." clause with concrete trigger phrases. This matches the top anchor exactly; level 4 would require the 'when' to be less explicit or specific.

5 / 5

Trigger Term Quality

"generate UI", "create a component", "build an interface", "Thesys", "generative UI", and "turn a description into a React component" are exactly the natural phrasings a user would say, including the product name and synonyms. It exceeds anchor 4 ("a few natural terms missing") because both casual ("build an interface") and technical ("generative UI", "Thesys") variants are covered.

5 / 5

Distinctiveness Conflict Risk

The niche is clear and named (Thesys SDK, generative UI, C1-style component generation) with product-specific triggers ("Thesys", "generative UI"), minimizing overlap with generic React or UI skills. It is above anchor 4 because the branded product name makes it nearly impossible to fire for the wrong skill.

5 / 5

Total

20

/

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

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

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.