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.
76
67%
Does it follow best practices?
Impact
87%
1.35xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./textual-builder/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description with strong trigger terms, explicit 'Use when' guidance, and a clear niche. Its main weakness is that the capability description leans slightly toward describing the skill's contents (documentation, templates) rather than listing specific concrete actions the skill enables. Overall, it would perform well in a multi-skill selection scenario.
Suggestions
Replace 'Includes comprehensive reference documentation, card game starter template, and styling guides' with specific actions like 'create widgets, handle input events, compose screen layouts, apply CSS styling' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (TUI applications with Textual framework) and some actions (creating terminal-based applications, prototyping card games, interactive CLIs), but doesn't list multiple concrete granular actions like 'create widgets, handle events, compose layouts'. The mention of 'comprehensive reference documentation, card game starter template, and styling guides' describes the skill's contents rather than specific actions it enables. | 2 / 3 |
Completeness | Clearly answers both 'what' (build TUI applications using Textual Python framework) and 'when' with an explicit 'Use when' clause listing specific triggers: creating terminal-based applications, prototyping card games, interactive CLIs, or mentioning Textual/TUI/terminal UI. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'TUI', 'terminal UI', 'Textual', 'terminal-based applications', 'card games', 'interactive CLIs', 'Text User Interface'. Good coverage of variations and natural terms a user might use when seeking this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche — Textual framework, TUI, terminal UI are highly specific triggers unlikely to conflict with other skills. The version number (v0.86.0+) and framework name make it clearly distinguishable from general Python or CLI skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
44%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill has excellent progressive disclosure structure with well-organized references, but suffers from vague workflows that lack concrete validation steps and executable examples beyond the basic Quick Start. The content includes some unnecessary explanations of concepts Claude already knows, and the workflows read more like tables of contents for the reference docs than actionable step-by-step guides.
Suggestions
Add concrete, executable code examples to each workflow step instead of abstract directions like 'Design layout' — show a minimal working example that builds incrementally.
Add validation/testing checkpoints to workflows, e.g., 'Run `python -m textual run app.py` to verify layout renders correctly before adding interactivity.'
Remove the overview paragraph explaining what Textual is and trim the Best Practices section to only non-obvious, Textual-specific guidance (e.g., keep message bubbling tip, remove type hints advice).
Include a concrete troubleshooting section for common Textual pitfalls (e.g., compose vs mount timing, CSS specificity issues) instead of generic best practices.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The overview section explains what Textual is ('a Python framework for creating terminal and browser-based applications with a modern web-inspired API') which Claude already knows. The 'When to Read Reference Documentation' section is useful but somewhat verbose with repeated 'Read when:' and 'Covers:' blocks that could be condensed into a table. Best practices are mostly things Claude already knows (type hints, progressive development). | 2 / 3 |
Actionability | The Quick Start provides executable code which is good, but the workflows sections are vague step lists without concrete code ('Design layout', 'Add widgets', 'Customize the Card widget'). The card game template copy command is concrete, but most guidance beyond the basic app example is abstract direction rather than executable instructions. | 2 / 3 |
Workflow Clarity | The workflows are high-level numbered lists without any validation checkpoints, concrete commands, or feedback loops. 'Creating a New TUI App' is essentially 'read these docs in order.' There's no guidance on testing, debugging, or verifying that the app works correctly at any step. No error recovery or validation steps are present. | 1 / 3 |
Progressive Disclosure | The skill excels at progressive disclosure with a clear overview, quick start, and well-signaled one-level-deep references to specific documentation files. Each reference file has a clear 'Read when' trigger and 'Covers' summary, making navigation intuitive. The structure appropriately separates concerns across reference files. | 3 / 3 |
Total | 8 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- YPares/agent-skills
- Commit
d2b7dff
- 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.