textual-builder

Build Text User Interface (TUI) applications using the Textual Python framework (v0.86.0+). Use when creating terminal-based applications, prototyping card games or interactive CLIs, or when the user mentions Textual, TUI, or terminal UI. Includes comprehensive reference documentation, card game starter template, and styling guides.

1.35x

Quality

76%

Does it follow best practices?

Impact

87%

1.35x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./textual-builder/SKILL.md

Quality

Content

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

Well-structured body with executable quick-start code and excellent progressive disclosure of real bundle files. Weaknesses are the contradictory time-sensitive version note, absent validation checkpoints in workflows, and some descriptive padding in the Overview.

Suggestions

Remove or relocate the 'Current version: v0.86.0+ (as of November 2025, latest is v6.6.0)' note—it is time-sensitive, internally contradictory, and sits outside a deprecated section; either drop the pinned version or move it under an 'Old patterns' heading.

Add a validation checkpoint to at least the card-game and new-app workflows (e.g., 'run the app and confirm it launches' or 'check `app.run()` exits cleanly') so workflows clear the validation bar.

Trim the Overview paragraph since it restates the frontmatter description; let the description carry the framing and keep the body focused on actionable Quick Start.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable quick-start code and tight reference pointers, but the Overview rephrases the description and the time-sensitive line 'Current version: v0.86.0+ (as of November 2025, latest is v6.6.0)' is placed in Installation rather than a deprecated/old-patterns section and is internally contradictory, which the guidelines penalize.	3 / 5
Actionability	Provides copy-paste-ready quick-start code, concrete template-copy commands, and specific numbered workflows; not a 5 because several sections (reference docs, best practices) are pointers/descriptions rather than executable examples covering common cases.	4 / 5
Workflow Clarity	Three numbered workflows (new TUI app, card game prototype, interactive features) give a clear sequence, but validation/checkpoints are entirely absent; anchor 3 fits because checkpoints are missing even though the operations are low-risk rather than destructive.	3 / 5
Progressive Disclosure	Clear overview with well-signaled one-level-deep references: each of references/basics.md, widgets.md, layout.md, styling.md, interactivity.md (all confirmed present) gets a 'Read when'/'Covers' block, and the card-game-template asset is linked from Quick Start, making navigation easy.	5 / 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 clearly states capabilities and explicit trigger conditions with good synonym coverage. Minor room to tighten the trailing descriptive clause and add format-level triggers.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions—'Build Text User Interface (TUI) applications', 'prototyping card games or interactive CLIs'—with only minor coverage gaps; not a 5 because the trailing 'comprehensive reference documentation, card game starter template, and styling guides' is descriptive filler rather than additional concrete actions.	4 / 5
Completeness	Explicitly answers both what ('Build Text User Interface (TUI) applications using the Textual Python framework') and when ('Use when creating terminal-based applications, prototyping card games or interactive CLIs, or when the user mentions Textual, TUI, or terminal UI') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural-term coverage including synonyms ('Textual, TUI, or terminal UI', 'terminal-based applications', 'interactive CLIs', 'card games'); not a 5 because it lacks file-extension or format triggers and a few common phrasings are absent.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche—the Textual Python framework—with distinct triggers (Textual, TUI, terminal UI) and minimal overlap risk with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 1 deeper-than-1-level	Warning

	Total	15 / 16 Passed

Repository: YPares/agent-skills
Path: textual-builder/SKILL.md
Commit: e9d2149

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.