CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tui-development

Guide for developing the OpenShell TUI — a ratatui-based terminal UI for the OpenShell platform. Covers architecture, navigation, data fetching, theming, UX conventions, and development workflow. Trigger keywords - term, TUI, terminal UI, ratatui, openshell-tui, tui development, tui feature, tui bug.

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/tui-development/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

An exceptionally actionable, project-specific reference with explicit lifecycles and copy-paste-ready code and commands. Its weaknesses are redundancy (duplicated sections and repeated fetch descriptions), and monolithic structure — all reference material is inlined in one large file with no progressive disclosure layer.

Suggestions

Deduplicate content: the 'gRPC timeouts' section is repeated verbatim in §4 and §8, and the per-entity fetch descriptions in §2 overlap §4 — keep one authoritative copy.

Split reference-heavy material (the theme field table, proto field gotchas, per-screen key hints) into references/ files linked from a leaner SKILL.md overview.

Embed validation checkpoints directly in the change workflows (e.g. 'run cargo clippy -p openshell-tui after adding a screen') instead of deferring verification to an external CONTRIBUTING.md.

DimensionReasoningScore

Conciseness

Nearly all content is project-specific (RPC names, proto field gotchas, key bindings) with no padding about concepts Claude already knows, but there is real trimmable fat: the 'gRPC timeouts' section appears verbatim in both §4 and §8, the fetch-per-entity descriptions in §2 are re-stated in §4, and the 16-row theme field table plus per-screen key-hint catalog run long. It could be meaningfully tightened without losing clarity.

3 / 5

Actionability

Fully executable guidance throughout: copy-paste-ready commands ('cargo build -p openshell-tui', 'mise run term:dev', 'helm upgrade --install openshell deploy/helm/openshell --namespace openshell'), literal proto request constructions with field names and '..Default::default()', the tokio::spawn/mpsc event pattern, and step-by-step recipes for adding a screen, gRPC call, or Event variant that cover the common change cases.

5 / 5

Workflow Clarity

Multiple explicit numbered lifecycles (log streaming, gateway switching, settings CRUD, startup, workspace switching) with failure paths ('On failure: status_text shows the error') and y/n confirmation gates on destructive operations, plus a Verification section with concrete commands. Validation is not embedded as checkpoints inside the workflows themselves, and verification defers to a CONTRIBUTING.md that is not part of the bundle, which keeps it below the top anchor.

4 / 5

Progressive Disclosure

Internal structure is strong (nine numbered sections, tables, a module dependency tree), but there are no bundle files at all — the 16-field theme table, proto field reference, per-screen key-hint catalog, and file-by-file architecture map are all inlined in a single ~640-line SKILL.md. Reference material of this volume is what the rubric expects split into clearly signaled, one-level-deep reference files.

3 / 5

Total

15

/

20

Passed

Description

73%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 well-targeted description with explicit trigger keywords and a clearly named niche domain. Its main weakness is that it describes topic coverage rather than concrete actions, and the trigger guidance is a keyword list rather than an explicit 'Use when' statement.

Suggestions

Convert the trigger keyword list into an explicit usage clause, e.g. 'Use when working on crates/openshell-tui, fixing a TUI bug, or adding a TUI feature'.

Replace the topic-area list with concrete actions, e.g. 'Build, debug, and extend the OpenShell TUI: add screens and key handlers, wire gRPC data fetching, and apply the theme system'.

Add natural trigger phrases users would type, such as 'openshell term' and 'log viewer', to broaden keyword coverage.

DimensionReasoningScore

Specificity

The description names the domain precisely ('a ratatui-based terminal UI for the OpenShell platform') and enumerates coverage areas ('architecture, navigation, data fetching, theming, UX conventions, and development workflow'), but these are topic labels rather than concrete actions. It does not state 3+ specific actions, so it falls short of the comprehensive-action anchors.

3 / 5

Completeness

Both what ('Guide for developing the OpenShell TUI... Covers architecture, navigation, data fetching, theming, UX conventions, and development workflow') and when (explicit trigger keyword list) are present, so the missing-trigger cap does not apply. The 'when' is a bare keyword list rather than an explicit 'Use when...' usage statement, which leaves room to be more explicit.

4 / 5

Trigger Term Quality

The explicit list 'Trigger keywords - term, TUI, terminal UI, ratatui, openshell-tui, tui development, tui feature, tui bug' contains natural terms users would say, including synonyms (TUI / terminal UI) and the launch command 'term'. A few plausible natural phrases (e.g. 'openshell term', 'dashboard', 'log viewer') are missing, keeping it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

Highly niche identifiers ('OpenShell TUI', 'openshell-tui', 'ratatui', 'term') give it a clear, distinct trigger surface with minimal overlap risk against generic skills.

5 / 5

Total

16

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (648 lines); consider splitting into references/ and linking

Warning

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

13

/

16

Passed

Repository

NVIDIA/OpenShell

Path

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