Agent skill · Security

mastra-system-check

Comprehensive system check for Mastra AI agent projects. Validates configuration, agents, workflows, memory, tools, prompts, and security across 66 rules organized by priority. Use when setting up new projects, debugging issues, reviewing code, or preparing for production deployment.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill mastra-system-check --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 10 KB
Bundled scripts: none
Version: 1.1.0
Declared author: stan
Path: skills/ai-llm/mastra-system-check/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Mastra System Check Validates Mastra AI agent projects with **66 checks** across **10 categories**. Finds configuration errors, missing best practices, and potential issues before they cause problems. --- ## Trigger Keywords Activate this skill when the user mentions: | Category | Example Phrases | |----------|-----------------| | **General Check** | "check my mastra project", "mastra system check", "validate mastra", "review my mastra code" | | **Setup Issues** | "mastra not working", "agent won't start", "can't find mastra instance" | | **Memory Issues** | "memory not persisting", "conversation lost", "agent forgets context" | | **Workflow Issues** | "workflow stuck", "workflow not executing", "steps not running" | | **Context Issues** | "context not propagating", "requestcontext empty", "can't access user data" | | **Deployment** | "prepare for production", "production checklist", "deploy mastra" | | **Debugging** | "debug mastra", "troubleshoot agent", "why is my agent..." | --- ## Quick Checks (Run First) Before deep analysis, verify these **4 common issues** that cause most failures: ### 1. Storage Configured? ```bash grep "storage:" src/mastra/index.ts ``` If missing → Add

What's inside
Steps it walks through
  1. Trigger Keywords
  2. Quick Checks (Run First)
  3. 1. Storage Configured?
  4. 2. API Keys Set?
  5. 3. Model Format Correct?
  6. 4. Workflows Committed?
  7. Execution Steps
  8. Step 1: Locate Entry Point
  9. Step 2: Check Dependencies
  10. Step 3: Scan for Agents
  11. Step 4: Scan for Workflows
  12. Step 5: Check Configuration Files
  13. Step 6: Run Category Checks
  14. Step 7: Report Findings
Ships with 1 file
  • metadata.json
Commands it runs
grep "storage:" src/mastra/index.ts
cat .env | grep -E "(OPENAI|ANTHROPIC|GOOGLE)_API_KEY"
grep -r "model:" src/mastra/ | grep -v "provider/"
grep -r "new Workflow" src/mastra/ -A 20 | grep "\.commit()"
Find the main Mastra instance
cat src/mastra/index.ts
Verify required packages
cat package.json | grep -E "@mastra|zod|@ai-sdk"
grep -rn "new Agent" src/
grep -rn "new Workflow" src/
More from claude-skill-registry
All skills →
About this skill
What does the mastra-system-check skill do?

Comprehensive system check for Mastra AI agent projects. Validates configuration, agents, workflows, memory, tools, prompts, and security across 66 rules organized by priority. Use when setting up new projects, debugging issues, reviewing code, or preparing for production deployment.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill mastra-system-check --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going