mastra
Skill41 starsChanged 9 months agoApache-2.0View on GitHub
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.
5 other projects use a version of this, 3 of them edited.
Adopted by
Most recently taken up by
- svngoku/coding-agents-skillstheir own version, first seen Nov 8, 2026
- mastra-ai/skillsedited, first seen Nov 4, 2026
- vobase/vobaseedited, first seen Apr 25, 2026
- ssdeanx/AgentStackword for word, first seen Apr 20, 2026
- FelipeAngeli/skillsedited, first seen Apr 10, 2026
Other versions5 projects use a version of this.
Word for word · 1
- ssdeanx/AgentStack★ 44100% same
Edited · 3
- mastra-ai/skills★ 10221% same
- vobase/vobase★ 6064% same
- FelipeAngeli/skills★ 282% same
Wrote their own version · 1
- svngoku/coding-agents-skills★ 12same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
7 rules. 3 are common, 2 are distinctive, and 2 are very specific to this project.
3
Common
Most of the 4 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 29
If packages exist: Use embedded docs first (most reliable)
- Distinctive: line 78
Use for: Open-ended tasks (support, research, analysis)
- Distinctive: line 81
Use for: Defined processes (pipelines, approvals, ETL)
- Common: line 128
Verify current API in embedded docs
- Common: line 129
Don't assume the error is a user mistake - it might be your outdated knowledge
- Very specific: line 142
If installed → Use embedded docs references/embedded-docs.md
- Very specific: line 143
If not → Use remote docs references/remote-docs.md
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

