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

81%

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

Quality

Content

62%

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

The body is a well-structured overview with strong navigation and clear edit workflows, but it loses points for a marketing-flavored intro, the lack of any complete executable code example, and a dangling reference to a non-existent scripts/scaffold.sh. Tightening these would lift the score.

Suggestions

Remove or trim the 'dominant framework / used by Claude Code, Gemini CLI, ...' social-proof line; it adds no actionable guidance for Claude.

Add at least one complete, copy-paste-ready code example (e.g., a minimal screen component registering with the router, or a small store atom with its setter) so the actionability anchor for 'fully executable code' is met.

Either add the missing scripts/scaffold.sh to the bundle or drop the scripts/scaffold.sh entry from the 'Reference files' list so referenced paths resolve to real files.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and assumes Claude's competence, but the opening social-proof line ('Ink is the dominant Node.js TUI framework — used by Claude Code, Gemini CLI, GitHub Copilot CLI, Cloudflare Wrangler, Shopify CLI, Prisma, and many others') is marketing padding Claude does not need for the task.	2 / 3
Actionability	Concrete file paths, enums, and specific commands ('pnpm try --playground', '--ci') are present, but there is no complete executable code example (e.g., a full screen component or store snippet) that is copy-paste ready, leaving key details to external references.	2 / 3
Workflow Clarity	'Adding a screen' and 'Adding store state' are clearly numbered and sequenced with an explicit 'No other files change' checkpoint; the operations are non-destructive framework edits, so the absence of a validate-retry loop does not apply here.	3 / 3
Progressive Disclosure	The body is well organized with one-level-deep, clearly signaled references ('Read this first when...'), but scripts/scaffold.sh is referenced under 'Reference files' while no scripts/ directory or scaffold.sh exists — a dangling reference against the actual bundle structure.	2 / 3
	Total	9 / 12 Passed

Description

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.

The description is concise, third-person, and explicitly pairs concrete capabilities with a clear 'Use when' trigger. It is specific, well-triggered, and unlikely to conflict with other skills. No changes needed.

Dimension	Reasoning	Score
Specificity	Names many concrete capabilities — 'Build terminal user interfaces', 'reactive screen resolution, declarative flow pipelines, overlay interrupts, session state management, Ink components, Flexbox terminal layout, and graceful degradation' — matching the multiple-specific-actions anchor.	3 / 3
Completeness	Explicitly answers both what ('Build terminal user interfaces using Ink and @inkjs/ui') and when ('Use when creating interactive CLI installation wizards, setup flows, or multi-step terminal applications'), with an explicit 'Use when' trigger clause.	3 / 3
Trigger Term Quality	Natural phrasing a user would say — 'interactive CLI installation wizards, setup flows, or multi-step terminal applications in Node.js/TypeScript' — with good coverage of common variations; not just technical jargon.	3 / 3
Distinctiveness Conflict Risk	A clear niche (Ink-based TUI wizards) with distinct triggers; unlikely to be selected for unrelated skills, matching the clear-niche anchor.	3 / 3
	Total	12 / 12 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: d921755

Reviewed: about 13 hours 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.