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

86%

Does it follow best practices?

Impact

87%

1.35x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

72%

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

A well-structured, actionable skill body with excellent progressive disclosure and executable Quick Start code. Its main weaknesses are mild redundancy plus time-sensitive version info (conciseness) and workflows that lack explicit validation checkpoints.

Suggestions

Move the version/date line (v0.86.0+, as of November 2025, latest v6.6.0) into an 'Old patterns / version notes' section or remove it from the main body to avoid time-sensitive decay and improve conciseness.

De-duplicate the reference list: keep the 'When to Read Reference Documentation' section and drop the near-identical re-listing under Resources/references/, or vice versa.

Add a verification step to each Common Workflow (e.g., 'run the app and confirm the layout renders' after styling) so the sequences include explicit validation checkpoints.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with well-structured reference navigation, but the reference files are re-listed in the Resources section, the Overview restates the description, and "Current version: v0.86.0+ (as of November 2025, latest is v6.6.0)" is time-sensitive information not placed in a deprecated/old-patterns section, which the rubric penalizes.	2 / 3
Actionability	Provides fully executable, copy-paste-ready code (the basic App example) and concrete shell commands (cp -r assets/card-game-template/*, pip install textual), with workflows pointing to specific real files.	3 / 3
Workflow Clarity	The three Common Workflows are sequenced as numbered steps, but none include validation or verification checkpoints; steps are present yet checkpoints are only implicit, matching the 'steps listed but validation gaps' anchor.	2 / 3
Progressive Disclosure	Clear overview with one-level-deep references; each of the five references/ files is signaled with a 'Read when' trigger and a 'Covers' list, the card-game template lives in assets/, and all referenced paths correspond to real bundle files.	3 / 3
	Total	10 / 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.

A strong, third-person description that states concrete capabilities, includes an explicit 'Use when' trigger, and uses natural user-facing terms with low conflict risk. The embedded version string (v0.86.0+) is mildly time-sensitive but does not weaken the description's core function.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — "Build Text User Interface (TUI) applications using the Textual Python framework", "prototyping card games or interactive CLIs", plus bundled "reference documentation, card game starter template, and styling guides" — matching the multi-action anchor.	3 / 3
Completeness	Explicitly answers both what (build TUI apps with Textual) and when via a clear "Use when creating terminal-based applications... or when the user mentions Textual, TUI, or terminal UI" trigger clause.	3 / 3
Trigger Term Quality	Covers natural terms users would say — "Textual", "TUI", "terminal UI", "terminal-based applications", "card games", "interactive CLIs" — giving good coverage of common phrasings.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (the Textual framework / TUI / card-game prototyping) with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 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
Commit: ac633fa

Reviewed: 5 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.