testing-mastracode-tui

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

Quality

87%

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

Quality

Content

92%

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

The body is concise, highly actionable, and clearly sequenced with verification steps — strong across the core dimensions. The only gap is progressive disclosure: it is a long monolithic file with no external reference files, where a reference split would help.

Suggestions

Move the full OpenRouter settings.json config block into a references/ file (e.g. references/openrouter-config.json) and link to it from the body to reduce inline bulk.

Consider extracting the programmatic rendering-test checklist into references/rendering-tests.md and signaling it as an optional deep-dive.

Dimension	Reasoning	Score
Conciseness	The body is lean: mostly concrete commands, config, and short numbered steps, with no padded explanation of concepts Claude already knows.	3 / 3
Actionability	Provides fully executable, copy-paste-ready bash commands, a complete JSON config block, and a concrete test-script approach (e.g. `npx tsx test-script.ts`, the vitest filter command).	3 / 3
Workflow Clarity	Multi-step processes are explicitly sequenced (numbered prerequisites, numbered thread-state isolation steps 1-5) with verification checkpoints like 'Verify the status bar' and build-failure recovery branches.	3 / 3
Progressive Disclosure	The skill is a single ~140-line file with no bundle references; while well-sectioned, the strict guideline reserves a score of 3-without-references for skills under 50 lines, and some inline detail (e.g. the full OpenRouter config) could live in a reference file.	2 / 3
	Total	11 / 12 Passed

Description

82%

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 is specific and well-scoped to a distinct niche with natural trigger terms, but it omits an explicit 'Use when...' clause, leaving the 'when to use' guidance only implied. Adding a trigger sentence would raise completeness.

Suggestions

Append an explicit trigger clause, e.g. 'Use when testing mastracode's TUI interactions, thread behavior, or model configuration in Konsole.'

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete testing domains — "model configuration, thread lifecycle, task state isolation, and common blockers" — rather than vague actions.	3 / 3
Completeness	It clearly states what the skill covers, but lacks any explicit "Use when..." trigger clause, which caps completeness at 2 per the guidelines.	2 / 3
Trigger Term Quality	Natural trigger terms a user would say are present — "Testing mastracode TUI features interactively in Konsole" — with good coverage of the niche's vocabulary.	3 / 3
Distinctiveness Conflict Risk	The niche (testing mastracode's TUI in Konsole) is highly specific and unlikely to trigger for the wrong skill.	3 / 3
	Total	11 / 12 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: 3b78ed9

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