CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ink-tui

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

89%

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

The canonical home for this skill is ink-tui-wizard in novuhq/novu

SKILL.md
Quality
Evals
Security

Quality

Content

78%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-structured, highly navigable skill body with a clear architecture overview, concrete recipes, and excellent progressive disclosure to verified reference files. The main improvement opportunities are trimming persuasive filler, inlining a few small code shapes so common tasks are copy-paste ready, and making validation steps explicit in the workflows.

Suggestions

Remove or shrink the adoption name-drop ('used by Claude Code (Anthropic), Gemini CLI (Google)...') and consider moving the browser-to-Ink mapping table into references/INK-API.md, keeping only a one-line pointer — this would tighten conciseness toward a lean, every-token-earns-its-place body.

Inline one short copy-paste example each for the two most common tasks — a minimal FlowEntry with an isComplete predicate in router.ts and a store setter calling emitChange() — so the 'Adding a screen' and 'Adding store state' workflows are fully executable without opening source files first.

Add an explicit verification checkpoint at the end of the 'Adding a screen' workflow (e.g., re-run the wizard or `pnpm try --playground` to confirm the new screen renders and the flow resolves) to close the minor validation gap in workflow clarity.

DimensionReasoningScore

Conciseness

The body is mostly dense and earning its tokens (file paths, numbered steps, commands, a deprecation warning), but a few sections could be trimmed: the 'Ink is the dominant Node.js TUI framework — used by Claude Code (Anthropic), Gemini CLI (Google), GitHub Copilot CLI, Cloudflare Wrangler, Shopify CLI, Prisma...' credibility name-drop and the browser-to-Ink analogy table, which duplicates content in references/INK-API.md. These are minor instances of over-explanation, matching anchor 4 rather than the every-token-earns-its-place anchor 5.

4 / 5

Actionability

Guidance is largely executable: the four numbered steps for adding a screen, two explicit recipes for adding store state, the barrel-export path, the 'pnpm try --playground' command, and specific enum-to-file mappings. It falls short of anchor 5 because no inline code is shown — the concrete shapes of a FlowEntry, a store setter, or a primitive usage are delegated to source files ('Read `store.ts` for examples of both patterns'), leaving minor gaps a reader must fill by opening other files.

4 / 5

Workflow Clarity

Multi-step processes are clearly sequenced: 'Adding a screen' is a 1-4 numbered list with the strong completeness claim 'No other files change', and 'Adding store state' distinguishes two well-defined patterns. Validation is present but implicit (the playground command, the --ci fallback) rather than explicit checkpoints in the workflow, which matches anchor 4's 'clear sequence with most checkpoints present; minor validation gaps' rather than the explicit validate-and-recover loops of anchor 5.

4 / 5

Progressive Disclosure

The SKILL.md is a clear overview that appropriately keeps key facts inline (mapping table, terminal compatibility rules) while moving bulk detail to six real, verified reference files, each linked with a one-line description and usage prioritization ('Read this first when working on screen flow or state'). References are one level deep and easy to navigate, matching anchor 5.

5 / 5

Total

17

/

20

Passed

Description

95%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 that clearly states what the skill does and when to use it, with concrete trigger phrasing and a distinctive, well-scoped niche. The only weakness is that the capability list reads as feature areas rather than crisp parallel actions, leaving slight room for tightening.

DimensionReasoningScore

Specificity

The description names the domain and tools concretely ('Build terminal user interfaces (TUIs) using Ink (React for CLIs) and @inkjs/ui') and enumerates seven specific coverage areas ('reactive screen resolution, declarative flow pipelines, overlay interrupts, session state management, Ink components, Flexbox terminal layout, and graceful degradation'). The 'Covers...' items are feature areas rather than parallel concrete actions and there are minor gaps (e.g., no testing or debugging of TUIs), matching anchor 4 rather than the fully action-oriented, comprehensive anchor 5.

4 / 5

Completeness

It explicitly answers 'what' ('Build terminal user interfaces... using Ink... and @inkjs/ui with a reactive, session-driven wizard pattern') and 'when' with a concrete 'Use when creating interactive CLI installation wizards, setup flows, or multi-step terminal applications in Node.js/TypeScript' clause. Both are present and explicit with concrete trigger phrases, exactly matching the anchor-5 pattern.

5 / 5

Trigger Term Quality

It covers both the full term and its acronym ('terminal user interfaces (TUIs)') plus natural synonyms users would say: 'CLI installation wizards', 'setup flows', 'multi-step terminal applications', 'Ink', 'React for CLIs', and 'Node.js/TypeScript'. This is comprehensive natural-term coverage with synonyms, matching anchor 5; no meaningful user phrasing is missing.

5 / 5

Distinctiveness Conflict Risk

The niche is clear and distinctive — Ink/@inkjs/ui-based terminal wizards in Node.js/TypeScript — with triggers ('TUI', 'Ink', 'installation wizards', 'setup flows') unlikely to fire for unrelated skills. This matches anchor 5's 'clear niche with distinct triggers; minimal conflict risk'; the specificity of the framework names keeps overlap risk minimal.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

novuhq/novu

Path

.agents/skills/ink-tui/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.