跳到主内容
智客 ZICQ

技能库 智客分类:文档办公 mastra

Mastra

用于构建代理,工作流程,工具,内存,工作空间,以及当前API存储的综合马斯特拉框架指南. 用于文档查询,API验证,TypeScript设置,常见错误,迁移,以及"mastra api" CLI任务:检查或调用本地,Mastra平台, Trace Intelligence,或远程服务器的资源. 对于马斯特拉工厂的操作,发现并激活伴奏马斯特拉-构件技能.

105191 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

用于构建代理,工作流程,工具,内存,工作空间,以及当前API存储的综合马斯特拉框架指南. 用于文档查询,API验证,TypeScript设置,常见错误,迁移,以及"mastra api" CLI任务:检查或调用本地,Mastra平台, Trace Intelligence,或远程服务器的资源. 对于马斯特拉工厂的操作,发现并激活伴奏马斯特拉-构件技能.

何时用

每一个原始的qq

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Mastra Framework Guide、Critical: Do not trust internal knowledge、Prerequisites、Resources、References、Scripts。 其中含规范建议的小节:边界情况。

文件分析

文件分析:除 SKILL.md 外,正文引用了 references/create-mastra.md、references/core-concepts.md、references/embedded-docs.md、references/remote-docs.md、references/model-selection.md、references/common-errors.md,属于带资源的技能包,这些文件按需再读。

官方 description(原文)

Comprehensive Mastra framework guide for building agents, workflows, tools, memory, workspaces, and storage with current APIs. Use for documentation lookup, API verification, TypeScript setup, common errors, migrations, and `mastra api` CLI tasks: inspect or call resources on local, Mastra platform, Trace Intelligence, or remote servers. For Mastra Factory operations, discover and activate the companion mastra-factory skill.

Mastra Framework GuideCritical: Do not trust internal knowledgePrerequisitesResourcesReferencesScriptsPriority order for writing codeCore conceptsMastra StudioMastra API CLIMastra FactoryTrace Intelligence

· 许可:Apache-2.0

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
mastra
description
Comprehensive Mastra framework guide for building agents, workflows, tools, memory, workspaces, and storage with current APIs. Use for documentation lookup, API verification, TypeScript setup, common errors, migrations, and `mastra api` CLI tasks: inspect or call resources on local, Mastra platform, Trace Intelligence, or remote servers. For Mastra Factory operations, discover and activate the companion mastra-factory skill.
许可
Apache-2.0
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。
指令中引用的文件 · 6
  • references/create-mastra.md
  • references/core-concepts.md
  • references/embedded-docs.md
  • references/remote-docs.md
  • references/model-selection.md
  • references/common-errors.md

以下路径提取自原文;文件是否齐全请以来源仓库中的完整目录为准。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

该技能引用了附属文件,请从来源获取完整目录;仅复制 SKILL.md 可能缺少依赖。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「mastra」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-690a47cfb7777e37-%E9%A9%AC%E6%96%AF%E7%89%B9%E6%8B%89.html
请存为 .cursor/skills/mastra/SKILL.md 或 .claude/skills/mastra/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。
该技能还带 scripts/、references/、assets/ 等文件,请从 https://github.com/mastra-ai/skills 取完整目录,不要只建一个 SKILL.md。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/mastra-ai/skills' --list

npx skills add 'https://github.com/mastra-ai/skills' --skill 'mastra'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版
--- name: mastra description: "Comprehensive Mastra framework guide for building agents, workflows, tools, memory, workspaces, and storage with current APIs. Use for documentation lookup, API verification, TypeScript setup, common errors, migrations, and `mastra api` CLI tasks: inspect or call resources on local, Mastra platform, Trace Intelligence, or remote servers. For Mastra Factory operations, discover and activate the companion mastra-factory skill." license: Apache-2.0 metadata: author: Mastra version: "2.2.0" repository: https://github.com/mastra-ai/skills --- # 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: ```bash ls node_modules/@mastra/ ``` - If packages exist: Use embedded docs first (most reliable) - If no packages: Install first or use remote docs ## Resources ### References | User Question | First Check | How To | | ----------------------------------- | ---------------------------------------------------------------- | ---------------------------------------------- | | Create/install Mastra project | [`references/create-mastra.md`](references/create-mastra.md) | Setup guide with CLI and manual steps | | Choose Agent/Workflow/Tool/Memory/Storage | [`references/core-concepts.md`](references/core-concepts.md) | Core concepts and when to use each primitive | | How do I use Agent/Workflow/Tool? | [`references/embedded-docs.md`](references/embedded-docs.md) | Look up in `node_modules/@mastra/*/dist/docs/` | | How do I use X? (no packages) | [`references/remote-docs.md`](references/remote-docs.md) | Fetch from `https://mastra.ai/llms.txt` | | Choose or validate a model | [`references/model-selection.md`](references/model-selection.md) | Model format and provider registry lookup | | I'm getting an error... | [`references/common-errors.md`](references/common-errors.md) | Common errors and solutions | | Upgrade from v0.x to v1.x | [`references/migration-guide.md`](references/migration-guide.md) | Version upgrade workflows | | Inspect/call server resources via CLI | [`references/mastra-api.md`](references/mastra-api.md) | `mastra api` CLI for local, Mastra platform, or remote servers | | Find exact traces with complex predicates | [`references/trace-query.md`](references/trace-query.md) | Query completed traces by trace fields or related spans, scores, and feedback | | Investigate agent health, recurring failures, or improvement opportunities | [`references/trace-intelligence.md`](references/trace-intelligence.md) | Start with aggregate Trace Intelligence themes, then inspect trace/log evidence | ### Scripts - `scripts/provider-registry.mjs`: Look up current providers and models available in the model router. Always run this before using a model to verify provider keys and model names. ## Priority order for writing code Never write code without checking current docs first. 1. Embedded docs first (if packages installed) Look up current docs in `node_modules` for a package. This matches the exact installed version and is the most reliable source of truth. See [`references/embedded-docs.md`](references/embedded-docs.md). 2. Source code second (if packages installed) If embedded docs don't cover the question, inspect the installed source and type definitions. This is the source of truth when docs are missing or unclear. See [`references/embedded-docs.md`](references/embedded-docs.md). 3. Remote docs third (if packages not installed) Use the latest published docs when packages are not installed or when exploring new features. Remote docs may be ahead of the user's installed version. See [`references/remote-docs.md`](references/remote-docs.md). ## Core concepts Use [`references/core-concepts.md`](references/core-concepts.md) when choosing between agents, workflows, tools, memory, and storage. - Agent: Use for open-ended tasks that make decisions and use tools. - Workflow: Use for defined multi-step processes. ## Mastra Studio Studio is the interactive UI for building, testing, and managing agents, workflows, and tools. Use Studio when advising a human to inspect or debug visually. Inside a Mastra project, run: ```bash npm run dev ``` Then open `http://localhost:4111` in a browser to show Mastra Studio to your human user. ## Mastra API CLI Use `mastra api` to inspect or call resources on local dev servers, Mastra platform deployments, or remote Mastra endpoints. It is useful for agent-readable state, execution, traces, logs, scores, threads, and workflow operations. See [`references/mastra-api.md`](references/mastra-api.md) for usage patterns. For exact trace selection that needs recursive predicates or conditions over related spans, scores, or feedback, read [`references/trace-query.md`](references/trace-query.md). Before using `mastra api trace query`, confirm that the installed CLI exposes the command. Use `--schema` for the target's request/response shape and structural constraints, and use the canonical documentation found through [`references/remote-docs.md`](references/remote-docs.md) for supported fields, operators, and semantics. Preserve opaque pagination cursors and fetch trace or span details only after selecting candidates. ## Mastra Factory For Factory projects, work items, queue health, decisions, session history, memory inspection, or authorized operations, activate the **`mastra-factory`** skill. Factory is an operational control plane, not a reason to scaffold or deploy a new Mastra app. If the skill is missing, offer to install it from this repository: ```bash npx skills add mastra-ai/skills --skill mastra-factory ``` Choose the user's intended agent and scope interactively. For global installation, target a supported agent explicitly with `--agent -g`; PromptScript does not support global installs. Verify installation and referenced files for the intended agent even if another agent target fails. The Factory skill covers CLI checks, `mastra auth whoami` / authorized `mastra auth login`, and connecting via the user's actual instance URL from any directory. A deployed repository or `.mastra-project.json` is not required with `--url`. Never guess a shared Factory host or project IDs. Its connection and session-inspection references cover deployment-specific authentication, project discovery, threads, and observational memory limitations. ## Trace Intelligence Trace Intelligence (private beta on the Mastra platform) clusters completed agent traces into recurring themes across four trace signals: goal, outcome, behavior, and sentiment. Use it first for aggregate agent-health questions: what users ask for, where outcomes fail or get blocked, which behaviors recur, how sentiment shifts, and where the agent can improve. Then use `mastra api trace`, `log`, `metric`, and `score` commands for concrete execution evidence from specific traces. Query Trace Intelligence with `mastra api learning` CLI commands, or over HTTP via the local dev server proxy or the platform endpoint. See [`references/trace-intelligence.md`](references/trace-intelligence.md) for the investigation workflow, CLI commands, and route reference. ## Critical requirements ### TypeScript config Mastra requires ES2022 modules. CommonJS will fail. See [`references/create-mastra.md`](references/create-mastra.md) for setup and [`references/common-errors.md`](references/common-errors.md) for troubleshooting. ### Model format Always use `"provider/model-name"` when defining models using Mastra's model router. When the user asks to use a model or provider, always run `scripts/provider-registry.mjs` first to verify the provider key and model name are valid. Do not guess model names from memory as they change frequently. See [`references/model-selection.md`](references/model-selection.md). ## When you see errors Type errors often mean your knowledge is outdated. Common signs of outdated knowledge: - `Property X does not exist on type Y` - `Cannot find module` - `Type mismatch` errors - Constructor parameter errors What to do: 1. Check [`references/common-errors.md`](references/common-errors.md) 2. Verify current API in embedded docs 3. Don't assume the error is a user mistake - it might be your outdated knowledge ## Development workflow Always verify before writing code: 1. Check whether Mastra packages are installed 2. Look up current API - If installed: Use embedded docs [`references/embedded-docs.md`](references/embedded-docs.md) - If not: Use remote docs [`references/remote-docs.md`](references/remote-docs.md) 3. Write code based on current docs 4. Test with the project scripts or Studio when available

相关技能

文档办公

Ontology

为结构化的代理内存和可堆肥技能所打入的知识图. 在创建/征服实体(Person, project, Task, Evention, Document)时使用,链接相关对象,强制约束,规划多步动作作为图变,或技能需要共享状态时使用. 触发到"记住","我知道什么","链接X到Y",…

文档办公

Nano Pdf

使用纳米-pdf CLI编辑带有自然语言指令的PDF.

文档办公

Word / DOCX

创建,检查,并编辑有可靠样式的Microsoft Word文档和DOCX文件,编号,跟踪更改,表格,章节,并进行相容性检查. 当 (1) 任务涉及 Word 或 ".docx " 时使用; (2) 文件包括跟踪的更改,评论,字段,表格,模板,或页面布局限制; (3) 文档必须在不…

文档办公

Api Gateway

通过 Maton 网关调用第三方 API, 它为用户已经连接的应用程序注入证书 。 当用户命名一个连接的应用程序和其中的具体行动时使用此技能——读取一个邮箱,查询一个CMM,归档一个问题,更新一个电子表格,通过一个连接的搜索或刮取提供者运行一个查询. 每一次通话都到用户连接的应用…