CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

opentui-maker

Use proactively when the user wants to create, scaffold, or modify Terminal User Interface (TUI) applications using OpenTUI with SolidJS reactivity. Specialist for generating TUI components, routes, contexts, and ensuring correct build configuration with SolidJS preload and JSX pragma patterns.

Quality

82%

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

67%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 delivers concrete, executable guidance (preload pattern, JSX pragma, build config, validation checklist) in a mostly token-efficient, well-sectioned layout. Its critical flaw is that the progressive-disclosure architecture is fictional: WORKFLOW.md, TROUBLESHOOTING.md, and the templates/ directory it directs Claude to read are missing from the bundle, so the primary scaffold workflow cannot be executed as written. Secondary issues include a flexbox primer Claude doesn't need and a build snippet with an undefined variable.

Suggestions

Add the referenced bundle files (WORKFLOW.md, TROUBLESHOOTING.md, templates/_index.md, and at least one template under templates/{template-id}/source/) or remove/inline those references — the Template Selection Workflow currently fails at Step 1 because templates/_index.md does not exist.

Remove or drastically trim the Box Model Quick Reference table, which re-explains standard flexbox properties (flexDirection, flexGrow, alignItems, justifyContent) Claude already knows; keep only OpenTUI-specific properties like paddingX/paddingY if they differ from web CSS.

Complete the build.mjs example by defining repoRoot (e.g., const repoRoot = dirname(fileURLToPath(import.meta.url))) and including the outfile/outputDir config so it is copy-paste ready, and verify the validation script path works from the installed skill location.

DimensionReasoningScore

Conciseness

Largely efficient — critical patterns, color schemes, and project structure are dense and non-padded — but the Box Model Quick Reference re-explains standard flexbox ('flexDirection row/column', 'alignItems', 'justifyContent') Claude already knows, and the 26-line ASCII mockup could be tightened. Not a 3 because only a minority of sections need trimming; not a 5 because these unnecessary chunks are present.

4 / 5

Actionability

Mostly executable guidance: the launcher preload snippet, JSX pragma line, and validation script invocation are copy-paste ready, and the scaffold workflow specifies concrete steps ('Run bun install', placeholder replacements). Not a 5 because the build.mjs snippet references an undefined 'repoRoot' variable and omits output config, and Step 3 depends on template files not shipped in the bundle — minor but real gaps.

4 / 5

Workflow Clarity

The Template Selection Workflow is a clear 4-step sequence (list templates → gather customization → scaffold → report) reinforced by an explicit 'Validation Checklist' to verify before completing any operation and a runnable validation script. Not a 5 because the error-recovery path ('Fix issues → Consult TROUBLESHOOTING.md') points to a file that does not exist in the bundle, leaving the feedback loop incomplete.

4 / 5

Progressive Disclosure

The Quick Reference section clearly signals one-level-deep references ('See WORKFLOW.md', 'See TROUBLESHOOTING.md', 'See templates/_index.md'), but none of these files exist in the bundle — only scripts/validate-jsx.sh is present. The scaffold workflow dead-ends at Step 1 ('Read templates/_index.md'), so the claimed cross-file structure is unfulfilled and all real content is inlined in this single file. Not a 3 because broken reference destinations are a structural failure beyond 'could be better organized'; not a 1 because SKILL.md itself is well-sectioned and references are clearly signaled rather than buried or nested.

2 / 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 description with an explicit 'Use proactively when...' trigger clause, multiple concrete capabilities, and a clearly differentiated OpenTUI + SolidJS niche. Third-person voice is used consistently. The only weakness is slightly limited synonym coverage (e.g., 'terminal app', 'CLI') in the trigger terms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'create, scaffold, or modify Terminal User Interface (TUI) applications', 'generating TUI components, routes, contexts', 'ensuring correct build configuration with SolidJS preload and JSX pragma patterns' — comprehensively covering the skill's scope. Not a 4 because coverage extends beyond components/routes/contexts into build configuration details, matching the comprehensive anchor.

5 / 5

Completeness

Explicitly answers both: what ('Specialist for generating TUI components, routes, contexts, and ensuring correct build configuration') and when ('Use proactively when the user wants to create, scaffold, or modify Terminal User Interface (TUI) applications using OpenTUI with SolidJS reactivity') with concrete trigger phrases. Matches the anchor-5 good example structure.

5 / 5

Trigger Term Quality

Good natural keyword coverage: 'TUI', 'Terminal User Interface', 'create, scaffold, or modify', 'OpenTUI', 'SolidJS' — terms a user would naturally say. Not a 5 because common variations like 'terminal app', 'CLI dashboard', or 'terminal UI' are missing; not a 3 because both the full term and its acronym are present alongside multiple natural verbs.

4 / 5

Distinctiveness Conflict Risk

Clear niche — 'OpenTUI with SolidJS reactivity' with 'SolidJS preload and JSX pragma patterns' — that virtually no other skill would claim. Distinct library-specific triggers give minimal conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

14

/

16

Passed

Repository

KennethJefferson/cc_opentui-maker

Path

.claude/skills/opentui-maker/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.