CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

63

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/mastra-smoke-test/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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 highly actionable and well-structured with clear workflows, validation checkpoints, and excellent progressive disclosure through one-level-deep references. The main weakness is moderate verbosity in the inline browser-smoke section.

DimensionReasoningScore

Conciseness

Mostly efficient and free of basic-concept padding, but the long inline Local Studio Browser Smoke section and the duplicated Quick Start Flow could be tightened or moved to a reference.

3 / 5

Actionability

Fully executable guidance throughout: exact `gh pr view --json` fields, a curl readiness loop, full parameter tables, and route tables with specific per-page verifications.

5 / 5

Workflow Clarity

Clear sequenced release-branch points plus a mandatory test checklist with task_write tracking, a do-not-skip guardrail, and a per-test read/execute/mark-complete loop providing explicit validation checkpoints.

5 / 5

Progressive Disclosure

Well-signaled one-level-deep references with explicit branch points, a short index file, and a References table mapping each file to its purpose; all referenced paths verified present in the bundle.

5 / 5

Total

18

/

20

Passed

Description

66%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 does and lists specific capabilities, but omits any explicit 'Use when...' trigger guidance, which limits completeness. Trigger-term coverage is good but lacks a few natural synonyms.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when smoke testing a Mastra project, verifying a release, or deploying Mastra to staging/production.'

Replace 'and more' with the remaining concrete test areas so specificity reads as comprehensive rather than open-ended.

Include a couple of natural synonyms such as 'Mastra release smoke test' to strengthen trigger-term coverage.

DimensionReasoningScore

Specificity

Lists several specific test areas ('Studio UI, agents, tools, workflows, traces, memory') and concrete actions ('deploy to staging/production'), with minor coverage gaps hinted by 'and more'.

4 / 5

Completeness

Has a clear 'what' but lacks any explicit 'Use when...' trigger clause, which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Good keyword coverage including natural terms like 'smoke test', 'agents', 'workflows', 'staging', 'production', 'cloud deployments'; a few natural variations (e.g. 'Mastra release') are missing.

4 / 5

Distinctiveness Conflict Risk

The 'Mastra' niche and enumerated test areas make it mostly distinct, with minor overlap risk against the sibling platform-smoke-test skill referenced in the body.

4 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 14 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository
mastra-ai/mastra
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.