mastra
Provides current documentation and API verification for Mastra development.
Install
mkdir -p .claude/skills/mastra && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/17544" && unzip -o skill.zip -d .claude/skills/mastra && rm skill.zipInstalls to .claude/skills/mastra
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Comprehensive Mastra framework guide. Teaches how to find current documentation, verify API signatures, and build agents and workflows. Covers documentation lookup strategies (embedded docs, remote docs), core concepts (agents vs workflows, tools, memory, RAG), TypeScript requirements, and common patterns. Use this skill for all Mastra development to ensure you're using current APIs from the installed version or latest documentation.Key capabilities
- →Find current Mastra framework documentation
- →Verify API signatures for Mastra components
- →Build Mastra agents and workflows
- →Understand core Mastra concepts like Tools and Memory
- →Troubleshoot common Mastra errors
How it works
It guides the user to prioritize embedded documentation if Mastra packages are installed, or remote documentation otherwise, to ensure code aligns with the latest APIs. It also explains core concepts and critical requirements like TypeScript configuration.
Inputs & outputs
When to use mastra
- →Setting up a Mastra agent
- →Verifying workflow API usage
- →Creating a new Mastra project
About this skill
Mastra Framework Guide
Build AI applications with Mastra. This skill teaches you how to find current documentation and build agents and workflows.
⚠️ Critical: Do not trust internal knowledge
Everything you know about Mastra is likely outdated or wrong. Never rely on memory. Always verify against current documentation.
Your training data contains obsolete APIs, deprecated patterns, and incorrect usage. Mastra evolves rapidly - APIs change between versions, constructor signatures shift, and patterns get refactored.
Prerequisites
Before writing any Mastra code, check if packages are installed:
ls node_modules/@mastra/
- If packages exist: Use embedded docs first (most reliable)
- If no packages: Install first or use remote docs
Documentation lookup guide
Quick Reference
| User Question | First Check | How To |
|---|---|---|
| "Create/install Mastra project" | references/create-mastra.md | Setup guide with CLI and manual steps |
| "How do I use Agent/Workflow/Tool?" | references/embedded-docs.md | Look up in node_modules/@mastra/*/dist/docs/ |
| "How do I use X?" (no packages) | references/remote-docs.md | Fetch from https://mastra.ai/llms.txt |
| "I'm getting an error..." | references/common-errors.md | Common errors and solutions |
| "Upgrade from v0.x to v1.x" | references/migration-guide.md | Version upgrade workflows |
Priority order for writing code
⚠️ Never write code without checking current docs first
-
Embedded docs first (if packages installed)
# Check what's available cat node_modules/@mastra/core/dist/docs/SOURCE_MAP.json | grep '"Agent"' # Read the actual type definition cat node_modules/@mastra/core/dist/[path-from-source-map]- Why: Matches your EXACT installed version
- Most reliable source of truth
- See:
references/embedded-docs.md
-
Remote docs second (if packages not installed)
# Fetch latest docs # https://mastra.ai/llms.txt- Why: Latest published docs (may be ahead of installed version)
- Use when: Packages not installed or exploring new features
- See:
references/remote-docs.md
Core concepts
Agents vs workflows
Agent: Autonomous, makes decisions, uses tools Use for: Open-ended tasks (support, research, analysis)
Workflow: Structured sequence of steps Use for: Defined processes (pipelines, approvals, ETL)
Key components
- Tools: Extend agent capabilities (APIs, databases, external services)
- Memory: Maintain context (message history, working memory, semantic recall)
- RAG: Query external knowledge (vector stores, graph relationships)
- Storage: Persist data (Postgres, LibSQL, MongoDB)
Critical requirements
TypeScript config
Mastra requires ES2022 modules. CommonJS will fail.
{
"compilerOptions": {
"target": "ES2022",
"module": "ES2022",
"moduleResolution": "bundler"
}
}
Model format
Always use "provider/model-name":
"openai/gpt-4o""anthropic/claude-3-5-sonnet-20241022""google/gemini-2.5-pro"
When you see errors
Type errors often mean your knowledge is outdated.
Common signs of outdated knowledge:
Property X does not exist on type YCannot find moduleType mismatcherrors- Constructor parameter errors
What to do:
- Check
references/common-errors.md - Verify current API in embedded docs
- Don't assume the error is a user mistake - it might be your outdated knowledge
Development workflow
Always verify before writing code:
-
Check packages installed
ls node_modules/@mastra/ -
Look up current API
- If installed → Use embedded docs
references/embedded-docs.md - If not → Use remote docs
references/remote-docs.md
- If installed → Use embedded docs
-
Write code based on current docs
-
Test in Studio
npm run dev # http://localhost:4111
Resources
- Setup:
references/create-mastra.md - Embedded docs lookup:
references/embedded-docs.md- Start here if packages are installed - Remote docs lookup:
references/remote-docs.md - Common errors:
references/common-errors.md - Migrations:
references/migration-guide.md - Official site: https://mastra.ai (verify against embedded docs first)
When not to use it
- →When relying on internal knowledge about Mastra APIs or patterns
- →When writing Mastra code without checking current documentation
- →When using CommonJS modules for TypeScript configuration
Limitations
- →Requires TypeScript config to use ES2022 modules
- →Relies on embedded or remote documentation for API accuracy
- →Does not support outdated Mastra APIs or patterns
How it compares
This skill enforces a documentation-first approach for Mastra development, explicitly warning against relying on outdated knowledge and providing a structured way to find current API information.
Compared to similar skills
mastra side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| mastra (this skill) | 0 | 5mo | Review | Intermediate |
| llm-application-dev | 3 | 3mo | Review | Intermediate |
| mcp-builder | 136 | 3mo | Review | Advanced |
| copilot-sdk | 7 | 3mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
llm-application-dev
skillcreatorai
Building applications with Large Language Models - prompt engineering, RAG patterns, and LLM integration. Use for AI-powered features, chatbots, or LLM-based automation.
mcp-builder
anthropics
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
copilot-sdk
github
Build agentic applications with GitHub Copilot SDK. Use when embedding AI agents in apps, creating custom tools, implementing streaming responses, managing sessions, connecting to MCP servers, or creating custom agents. Triggers on Copilot SDK, GitHub SDK, agentic app, embed Copilot, programmable agent, MCP server, custom agent.
langfuse
davila7
Expert in Langfuse - the open-source LLM observability platform. Covers tracing, prompt management, evaluation, datasets, and integration with LangChain, LlamaIndex, and OpenAI. Essential for debugging, monitoring, and improving LLM applications in production. Use when: langfuse, llm observability, llm tracing, prompt management, llm evaluation.
develop-ai-functions-example
vercel
Develop examples for AI SDK functions. Use when creating, running, or modifying examples under examples/ai-functions/src to validate provider support, demonstrate features, or create test fixtures.
chatgpt-app-builder
mcp-use
Build ChatGPT apps with interactive widgets using mcp-use and OpenAI Apps SDK. Use when creating ChatGPT apps, building MCP servers with widgets, defining React widgets, working with Apps SDK, or when user mentions ChatGPT widgets, mcp-use widgets, or Apps SDK development.