mastra-smoke-test

Smoke test Mastra projects locally or deploy to staging/production. Tests Studio UI, agents, tools, workflows, traces, memory, and more. Supports both local development and cloud deployments.

Quality

83%

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

85%

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

The body is highly actionable with strong workflow sequencing and excellent progressive disclosure into reference files. The only weak spot is mild redundancy/padding in the opening lines and the overlapping test tables, which keeps conciseness at 2.

Suggestions

Remove the redundant opening line 'Comprehensive smoke testing for Mastra projects.' since the frontmatter description already states this.

Consolidate the 'Mandatory Test Checklist' table and the 'Test Options (--test)' table, which largely duplicate each other; keep one as the source of truth and have the other reference it.

Trim the meta-instruction 'Use progressive disclosure: stay in this file until the workflow branches...' into a shorter signal, or move it into the release-smoke reference where the branching is described.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands and tables, but it carries some redundancy and lightweight padding — the intro 'Comprehensive smoke testing for Mastra projects.' and the duplicated test list/options tables echo the description — keeping it just below the fully lean score-3 anchor.	2 / 3
Actionability	Provides fully executable, copy-paste-ready guidance — exact 'gh pr view' and 'gh pr list' commands, curl readiness checks, concrete routes with expected values, and full parameter tables — matching the score-3 anchor.	3 / 3
Workflow Clarity	Multi-step flows are clearly sequenced with explicit branch points (open PR → alpha-versioning-pr.md, merged → alpha-publish.md) and validation checkpoints (dev-server readiness loop, restart-and-retry), with feedback loops appropriate for batch/deploy operations.	3 / 3
Progressive Disclosure	SKILL.md is a concise overview with one-level-deep, well-signaled references (inline pointers plus a References table), release-smoke.md is explicitly a 'short index', and every referenced file exists — matching the clear-overview anchor.	3 / 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-anchored to natural Mastra-domain triggers, but it omits any explicit 'Use when...' guidance, so a user may not know precisely when to invoke it. Adding a usage-trigger clause would lift completeness from 2 to 3.

Suggestions

Append a 'Use when...' clause, e.g. 'Use when the user asks to smoke-test a Mastra app, verify a Mastra release, or debug Mastra Studio/agent/tool/workflow behavior before or after deploy.'

Consider trimming the trailing 'Supports both local development and cloud deployments.' since 'locally or deploy to staging/production' already conveys the same — it is mildly redundant.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Smoke test Mastra projects locally or deploy to staging/production', 'Tests Studio UI, agents, tools, workflows, traces, memory' — matching the score-3 anchor of multiple specific actions rather than a vague or partial list.	3 / 3
Completeness	Clearly answers what the skill does but lacks an explicit 'when to use' trigger; per the rubric guideline a missing 'Use when...' clause caps completeness at 2 even though the 'what' is strong.	2 / 3
Trigger Term Quality	Uses natural terms a user would say — 'smoke test', 'Mastra', 'Studio UI', 'agents, tools, workflows, traces, memory', 'staging/production', 'cloud deployments' — giving good coverage of common phrasings.	3 / 3
Distinctiveness Conflict Risk	The Mastra-specific niche and distinctive triggers (Studio UI, Mastra traces/workflows, staging vs production) make it unlikely to fire for an unrelated skill.	3 / 3
	Total	11 / 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: 13 deeper-than-1-level	Warning

	Total	15 / 16 Passed

Repository: mastra-ai/mastra
Path: .claude/skills/mastra-smoke-test/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.