Skip to content
TrustedSkillsbeta
Back to all skills

Smoke Test

Official
mastra-ai·vlatest·agents

Helps with AI, testing as part of orchestrating AI agents and multi-step workflows workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add mastra-ai/mastra --skill smoke-test -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

mastra-ai

Matched to the vendor's own GitHub organisation.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned mastra-ai/mastra at 788ceed5b3.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
788ceed5b3
Manifest
.claude/skills/smoke-test/SKILL.md
Scanned
1 file, 344 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

The smoke-test skill provides a lightweight validation mechanism for Mastra AI agents, ensuring core functionalities operate correctly before deploying complex workflows. It acts as an initial health check to confirm that agent configurations, tools, and integrations are properly connected and responsive.

When to use it

  • Verify new agent deployments immediately after installation or configuration changes.
  • Validate that external tool integrations (e.g., APIs, databases) are reachable and functioning.
  • Perform quick regression checks before running full-scale integration tests.
  • Confirm basic prompt handling and response generation capabilities in a production environment.

Key capabilities

  • Executes rapid, non-intrusive checks on agent readiness.
  • Validates connectivity to configured tools and external services.
  • Provides immediate feedback on critical system health without deep testing overhead.

Example prompts

  • "Run a smoke test to verify my customer support agent is connected to the Zendesk API."
  • "Check if the data retrieval tool in my analytics agent is responding correctly."
  • "Perform a quick validation of my new agent's core configuration before the team review."

Tips & gotchas

Ensure all required environment variables and API keys are set before running the test, as missing credentials will cause immediate failure. This skill is designed for speed; it does not replace comprehensive unit or integration testing suites needed for complex logic verification.