testing-mastracode-tui

Testing mastracode TUI features interactively in Konsole. Covers model configuration, thread lifecycle, task state isolation, and common blockers.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/testing-mastracode-tui/SKILL.md

Quality

Content

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

The body is a tight, highly actionable testing guide with concrete commands, configs, and sequenced verification steps. It is well-structured for a single-file skill, with only minor conciseness and organization trim opportunities.

Dimension	Reasoning	Score
Conciseness	The body is efficient and dominated by concrete commands, JSON config, and a commands table with minimal padding; only minor instances (e.g. 'This may take a few minutes') could be trimmed.	4 / 5
Actionability	Guidance is fully executable: copy-paste build/launch commands, a complete settings.json config, a tsx rendering recipe, and a TUI commands table cover the common cases.	5 / 5
Workflow Clarity	Testing workflows are clearly sequenced with explicit verification steps (e.g. 'Verify tasks visible', 'Test /new') and error-recovery guidance in Common Issues, with only minor checkpoint gaps elsewhere.	4 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections with no need for external references, though at ~140 lines some detail (full JSON config, rendering recipe) could optionally be split out.	4 / 5
	Total	17 / 20 Passed

Description

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

The description clearly states what the skill covers and targets a distinct niche, but it lacks an explicit 'Use when...' trigger clause and leans on technical jargon over natural user phrasing. Specificity is adequate but rests on a single action verb.

Suggestions

Add an explicit trigger clause, e.g. 'Use when testing mastracode's terminal UI, verifying thread/task behavior, or debugging TUI rendering in Konsole.'

Reframe the listed topics as concrete actions (e.g. 'Configure custom providers, launch the TUI, verify thread state isolation') to lift specificity beyond a single verb.

Include natural synonyms users might say ('terminal UI', 'TUI rendering', 'thread isolation') to broaden trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('mastracode TUI features interactively in Konsole') and enumerates concrete coverage areas ('model configuration, thread lifecycle, task state isolation, and common blockers'), but the action is a single verb ('Testing'/'Covers') rather than multiple distinct actions.	3 / 5
Completeness	The 'what' is clear (testing mastracode TUI features), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Relevant keywords like 'mastracode TUI', 'Konsole', and 'thread lifecycle' are present, but the language is fairly technical jargon and lacks the common natural variations or synonyms a user might actually say.	3 / 5
Distinctiveness Conflict Risk	The niche is specific (mastracode TUI testing in Konsole) and unlikely to trigger for unrelated skills, with only minor overlap risk against general testing or other mastracode skills.	4 / 5
	Total	13 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: mastra-ai/mastra
Path: .claude/skills/testing-mastracode-tui/SKILL.md
Commit: d6ce34a

Reviewed: about 17 hours 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.