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.
83
78%
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
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.
This is a strong skill description that clearly communicates what the skill does (build TUI apps with Textual), when to use it (explicit trigger clause with natural keywords), and what resources it includes. It is specific, well-scoped, and distinctive enough to avoid conflicts with other skills. The description is concise without being vague.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions and artifacts: 'Build Text User Interface (TUI) applications', 'prototyping card games or interactive CLIs', 'comprehensive reference documentation, card game starter template, and styling guides'. It names the specific framework (Textual), version, and included resources. | 3 / 3 |
Completeness | Clearly answers both 'what' (build TUI applications using Textual framework, with reference docs, templates, and styling guides) and 'when' (explicit 'Use when...' clause covering terminal-based apps, card games, interactive CLIs, and specific trigger terms like Textual/TUI/terminal UI). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'TUI', 'terminal-based applications', 'Textual', 'terminal UI', 'interactive CLIs', 'card games'. These cover multiple natural phrasings a user might employ. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Textual Python framework for TUI apps. The specific framework name, version number, and domain (terminal UI) make it very unlikely to conflict with other skills like general Python development or web UI skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is well-structured with excellent progressive disclosure, clearly directing users to the right reference files based on their task. However, it suffers from moderate verbosity (explaining what Textual is, generic best practices) and the workflows lack concrete executable steps and validation checkpoints, reading more like tables of contents than actionable guides.
Suggestions
Remove the overview paragraph explaining what Textual is and the generic best practices that Claude already knows; replace best practices with Textual-specific gotchas or common mistakes with concrete code examples.
Add executable code snippets to the Common Workflows sections instead of abstract steps like 'Design layout' — show a minimal concrete example for each workflow.
Add validation/verification steps to workflows, e.g., 'Run `python app.py` to verify the layout renders correctly before adding interactivity' or 'Use `textual console` for debugging.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary verbosity, particularly in the 'When to Read Reference Documentation' section which repeats 'Read when:' and 'Covers:' patterns extensively. The overview paragraph explains what Textual is, which Claude likely already knows. The best practices section contains generic advice. However, it's not egregiously padded. | 2 / 3 |
Actionability | The Quick Start provides executable code which is good, and the template copy command is concrete. However, the Common Workflows sections are vague step lists without executable code (e.g., 'Design layout', 'Add widgets'). Best practices are generic advice rather than specific, actionable guidance with examples. | 2 / 3 |
Workflow Clarity | Workflows are listed as numbered steps but lack validation checkpoints or feedback loops. Steps like 'Creating a New TUI App' are essentially just 'read these docs in order' without concrete verification steps (e.g., 'run the app to verify layout renders correctly'). No error recovery guidance is provided. | 2 / 3 |
Progressive Disclosure | This is the skill's strongest dimension. It provides a clear overview with well-signaled one-level-deep references to specific documentation files. Each reference file has a clear 'Read when' trigger and 'Covers' summary, making navigation easy and purposeful. | 3 / 3 |
Total | 9 / 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
aed1afb
- 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.