ink-tui-wizard

Build terminal user interfaces (TUIs) using Ink (React for CLIs) and @inkjs/ui with a reactive, session-driven wizard pattern. Use when creating interactive CLI installation wizards, setup flows, or multi-step terminal applications in Node.js/TypeScript. Covers reactive screen resolution, declarative flow pipelines, overlay interrupts, session state management, Ink components, Flexbox terminal layout, and graceful degradation across terminal environments.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.cursor/skills/ink-tui/SKILL.md

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.

A well-organized architecture overview with strong progressive disclosure and clear workflows, weakened mainly by a lack of executable code examples and heavy deferral to source files for key details. Fixing the missing scaffold.sh reference and adding a concrete Ink component snippet would raise it further.

Suggestions

Add at least one copy-paste Ink component example (e.g. a minimal screen using <Box>/<Text> and useInput) so the guidance is executable rather than purely structural.

Inline the current values for key enums (Screen, Overlay, Flow, RunPhase, TaskStatus) instead of deferring to 'see the source files for current values', which leaves actionability incomplete.

Remove or create the missing scripts/scaffold.sh reference (the scripts/ bundle does not exist), since the broken link undermines the otherwise clean reference structure.

Dimension	Reasoning	Score
Conciseness	Mostly lean and assumes Claude's competence (the Browser→Ink table and structural guidance are tight), but the opening name-dropping ('used by Claude Code, Gemini CLI, GitHub Copilot CLI, Cloudflare Wrangler...') and 'dominant framework' framing are mild padding that could be trimmed.	4 / 5
Actionability	Provides concrete file paths, enum names, and a numbered screen-addition sequence, but repeatedly defers key details to source files ('read each primitive's source file for its current props interface', 'See the source files for current values') and includes no copy-paste executable code examples, leaving guidance incomplete.	3 / 5
Workflow Clarity	The 'Adding a screen' steps are a clear four-step sequence with an explicit 'No other files change' confirmation, and 'Adding store state' distinguishes two patterns; validation checkpoints are absent but the operations are additive rather than destructive, so this is a minor gap.	4 / 5
Progressive Disclosure	Well-structured overview with one-level-deep, clearly signaled references (ARCHITECTURE.md, PRIMITIVES.md, INK-API.md, etc., all verified present) and a dedicated 'Reference files' section; docked one point because scripts/scaffold.sh is referenced but no scripts/ bundle exists, a broken navigation path.	4 / 5
	Total	15 / 20 Passed

Description

87%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 explicitly covers both what the skill does and when to use it, with concrete trigger phrases and a well-defined niche. Minor room to tighten the coverage list into more discrete actions.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Build terminal user interfaces (TUIs)', 'creating interactive CLI installation wizards, setup flows, or multi-step terminal applications') plus a coverage list, but the coverage items are domain concepts rather than discrete executable actions, leaving minor gaps versus a fully comprehensive action list.	4 / 5
Completeness	Clearly states what ('Build terminal user interfaces using Ink and @inkjs/ui with a reactive, session-driven wizard pattern') and explicitly when ('Use when creating interactive CLI installation wizards, setup flows, or multi-step terminal applications in Node.js/TypeScript') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural terms a user would say ('TUIs', 'interactive CLI installation wizards', 'setup flows', 'multi-step terminal applications', 'Node.js/TypeScript') with good synonym coverage, though a few common variations (e.g. 'terminal app', 'command-line wizard') are absent.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Ink/@inkjs/ui TUI wizards) with distinctive triggers ('Ink', 'TUI', 'CLI wizard', 'session-driven') that make overlap with unrelated skills unlikely.	5 / 5
	Total	18 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 missing	Warning
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	14 / 16 Passed

Repository: novuhq/novu
Path: .cursor/skills/ink-tui/SKILL.md
Commit: fc9a0fd

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.