Skip to main content

atlas-agent-engine-docs

Answer Atlas Agent Engine platform questions from current documentation. Use for questions about the agentengine CLI, project creation, local development, deployment, Atlas setup, memory, remote MCP, agent-to-agent communication, governance, monitoring, or network egress. Consult the documentation source before answering rather than relying on prior knowledge.

来源信息

仓库
mongodb/agent-engine-examples
最近来源活动
2026年10月15日 14:22
检测到的 SKILL.md 语言
英语
星标
4
Forks
1

安装方式

默认使用会先检查来源的 Prompt;你也可以切换为直接命令,或下载本地副本。

检查来源文件

决定是否安装前,请先阅读 SKILL.md,以及 SkillsMP 当前展示的配套文件。

正在显示 SKILL.md

SKILL.md
来源说明 · 只读预览
name
atlas-agent-engine-docs
description
Answer Atlas Agent Engine platform questions from current documentation. Use for questions about the agentengine CLI, project creation, local development, deployment, Atlas setup, memory, remote MCP, agent-to-agent communication, governance, monitoring, or network egress. Consult the documentation source before answering rather than relying on prior knowledge.
# Atlas Agent Engine Documentation Use this skill to answer platform questions from the current documentation on demand. Do not preload the documentation set or answer platform-specific questions from memory when a documentation source is available. ## Documentation Source The only documentation source is the public site: ``` https://www.mongodb.com/docs/agentengine ``` The site's map of pages is published as a machine-readable index at: ``` https://www.mongodb.com/docs/agentengine/llms.txt ``` Use `llms.txt` as the site map to discover page URLs. Do not construct page URLs by guessing path segments. Entries in `llms.txt` link to `.md` files, which are suitable for reading. To give a human a link to the rendered page, drop the `.md` suffix to get the HTML URL. **Available** means a request to that site returns HTTP 200 with a documentation page body. Treat it as **unavailable** on any of: HTTP 404, any other 4xx or 5xx, a network error or timeout, or a 200 whose body is not documentation (for example a redirect to a generic landing or sign-in page). The site is not published yet, so unavailable is currently the expected outcome. ## Retrieval Workflow 1. Identify the platform topic in the request. 2. Request the documentation site and apply the availability check above. 3. If it is unavailable, respond only that public Atlas Agent Engine documentation is not available yet. Do not mention private sources, credentials, preview status, or alternative documentation. 4. If it is available, read the `llms.txt` site map to find the pages relevant to the topic, then read only those. 5. Answer from the retrieved page content and cite the page, linking to its HTML URL (the `.md` URL with the suffix removed). 6. If the documentation does not cover the question, say so. Do not invent platform behavior or fill gaps with stale knowledge. ## Topics In Scope Use this list to decide whether a question belongs to this skill and what to look for. These are topic names, not URLs or file paths; resolve the actual page through the site itself. - Getting started - CLI installation and authentication - Project creation - Local development - Deep agents - Build and deployment - Memory - Remote MCP - Agent-to-agent communication - Atlas organizations, projects, and workspaces - Guardrails and policy engine - Monitoring - Monorepos - Network egress - Agent manifest reference ## Answer Format - State the answer first. - Cite the retrieved documentation page at the end. - Call out preview-only behavior, prerequisites, or access requirements when the source documents them.
在 GitHub 查看