Token导航 LogoToken导航TokenDH.com
中转站排行榜
研究检索external-servicegithub未标认证来源可访问许可证需确认审计通过

ensure-agents-md（确保 AgentMD）

Agent Skill

ensure-agents-md 用于查找、检索和筛选相关信息，适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态，以及是否会触发联网、命令执行或文件读写。

总安装

3,745

周安装

153

GitHub Stars

55

下载量

1,212
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息，不托管安装包，也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手，先确认命令和权限，再让它执行。

请帮我安装这个 Agent Skill：ensure-agents-md（确保 AgentMD）
来源仓库：https://github.com/adobe/skills
仓库路径：skills/ensure-agents-md
安装命令：
npx skills add https://github.com/adobe/skills --skill ensure-agents-md
安装前请先检查当前环境是否支持对应 CLI，并向我确认将要执行的命令、安装目录、联网范围和文件读写权限；确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill；本站只展示命令，不托管安装包，也不自动执行。

skills.shnpx skills
npx skills add https://github.com/adobe/skills --skill ensure-agents-md

简介

强制校验 AGENTS.md 与 CLAUDE.md 文件的完整性，作为项目启动前提。

  • 仅在 AEM Cloud Service 项目且文件缺失时自动创建引导文档。
  • 阻止在未初始化文档的项目中执行其他开发任务，确保规范落地。
  • 需识别项目类型，避免在非 Adobe 项目中误触发文件生成逻辑。
  • ensure-agents-md 属于研究检索类 Skill，可作为该场景下的辅助能力补充。

SKILL.md

Ensure AGENTS.md and CLAUDE.md (bootstrap)

Mandatory order (all cases)

Before any other work — including dispatcher, create-component, code edits, MCP, or answers — the agent MUST:

  1. Check whether AGENTS.md exists at the workspace (repository) root.
  2. If it exists → skip this skill entirely and continue with the user’s request.
  3. If it does not exist and the repo is an AEM Cloud Service project (see Gate check) → run this skill completely first (create AGENTS.md and CLAUDE.md if missing), then fulfill the user’s original request.

This applies to every user message and any intent (bugs, features, questions, dispatcher, etc.) until AGENTS.md is present. Do not defer bootstrap to “after” the main task.

It creates AGENTS.md and CLAUDE.md at the repository root so every AI coding agent (Claude Code, Cursor, etc.) gets project guidance, optionally tailored using the module catalog and add-on detection.

Gate check

  1. Look for AGENTS.md at the workspace root. If it exists → skip, move on.
  2. Verify this is an AEM Cloud Service project: root pom.xml exists and references com.adobe.aem:aem-sdk-api or aem-project-archetype or contains <modules> with typical AEM module names (core, ui.apps, dispatcher, etc.). If not an AEM project → skip.

Steps

1. Resolve project name

Check in order:

  • Root pom.xml → <name> element (preferred, usually human-readable).
  • Root pom.xml → <artifactId>, then humanize: strip leading aem-, replace - with spaces, title-case (e.g. aem-guides-wknd → WKND, my-site → My Site).
  • Directory name of the workspace.
  • Fallback: "AEM Cloud Service Project".

2. Discover modules

Read root pom.xml <modules> section. For each <module>, confirm the directory actually exists. Build a list of present modules.

3. Detect add-ons and frontend type

Scan the project for:

SignalAdd-on / variant
pom.xml depends on cif-connector or aem-core-cif-componentsCIF (Commerce)
ui.frontend/package.json contains react or @adobe/aem-react-editable-componentsReact SPA
ui.frontend/package.json contains @angular/core or @adobe/aem-angular-editable-componentsAngular SPA
ui.frontend has no clientlib.config.js and pom.xml references frontend-maven-plugin but outputs no clientlibsDecoupled frontend
pom.xml depends on aem-forms-* or forms.coreAEM Forms
Module ui.frontend.react.forms.af existsHeadless Forms
pom.xml uses precompiled-scripts-providerPrecompiled Scripts

If none of these are detected, treat as General Webpack frontend (the default archetype).

4. Generate AGENTS.md

Read the template at references/AGENTS.md.template. Apply the following adaptations:

a. Title

Replace {{PROJECT_NAME}} with the resolved project name.

b. Add-ons section

If any add-ons were detected (CIF, Forms, Headless Forms, Precompiled Scripts), insert an "Add-ons and extensions" section after the intro paragraph. Use descriptions from the references/module-catalog.md add-ons table. If none detected, omit the section entirely.

c. Modules section

Only include modules that actually exist in the project. For each module, use the matching description from the module catalog. Pay attention to:

  • ui.frontend — use the variant that matches the detected frontend type (General, React, Angular, Decoupled).
  • dispatcher — only include if the dispatcher directory exists.
  • it.tests / ui.tests — only include if they exist.

d. Build commands

  • Include frontend commands (npm run build, npm start) only if ui.frontend exists.
  • Include dispatcher validate command only if dispatcher module exists.
  • For React/Angular SPA, note that npm start requires AEM running.

e. Important resources

Always include the base resources from the template. Additionally:

  • If React or Angular SPA detected → add SPA Editor and framework-specific resources (see module catalog).
  • If CIF detected → add Commerce resources.
  • If Forms detected → add Forms resources.
  • If Decoupled frontend → add Frontend Pipeline resource.

5. Create CLAUDE.md

If CLAUDE.md does not exist at the workspace root, create it with exactly this content (so Claude/Cursor picks up project guidance):

@AGENTS.md

Do not overwrite an existing CLAUDE.md.

6. Inform the user

Briefly tell the user:

"I created AGENTS.md and CLAUDE.md in your project root with guidance tailored to your project structure. These help AI coding agents understand your project."

Then continue with the user's original request.

Reference files

FilePurpose
references/AGENTS.md.templateBase template with {{PROJECT_NAME}} placeholder and all default sections
references/module-catalog.mdModule descriptions, add-on descriptions, conditional resources — the source of truth for adapting the template

Rules

  • Never overwrite an existing AGENTS.md or CLAUDE.md. Only create when missing.
  • Never hallucinate modules. Only list modules whose directories actually exist.
  • Keep the generated AGENTS.md clean — no skill metadata, no comments about "generated by skill".
  • Project name should be human-readable (e.g. "WKND Sites Project", "My Site"), not only a raw artifactId unless that is the desired title.
  • Do not add sections that tell agents to use specific MCP servers, Cursor/Claude skills, or how to discover tools. Coding assistants pick those up from product configuration and tool metadata; if something is not discovered, fix metadata or MCP setup — do not duplicate that in AGENTS.md.
  • The resource links must point to experienceleague.adobe.com/en/docs/experience-manager-cloud-service/... (Cloud Service URLs), never to AEM 6.5 URLs.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明，方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用；具体调用方式请以来源页面和 README 为准。

平台分布

Codex

36.09%
按下载量换算437

Claude

27.88%
按下载量换算338

Cursor

18.59%
按下载量换算225

Gemini CLI

9.56%
按下载量换算116

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

external-service

该 Skill 可能调用第三方服务、云服务或外部模型 API，使用前需要确认账号、额度、数据发送范围和服务条款。

安装前确认

本站仅展示第三方公开信息，不托管安装包，不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源，正式发布前建议补源仓库或其他目录站核验。

来源信息

GitHub 仓库

github.com

/adobe/skills

SKILL.md 来源

github.com

/adobe/skills/tree/main/skills/ensure-agents-md

skills-sh

skills.sh

/adobe/skills/ensure-agents-md

继续浏览同类 Skills

更多研究检索 Skills（73,675）返回 Skills 目录

上一个 Skill

ensemble-team（合奏队）

ensemble-team 用于查找、检索和筛选相关信息，适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态，以及是否会触发联网、命令执行或文件读写。

下一个 Skill

ensure-docs（确保文档）

用于辅助文档、README、Markdown、说明文和内容稿件的整理与改写。它适合让 Agent 提炼结构、补齐章节、统一术语、检查链接或把零散材料整理成可读文档。使用时应保留项目已有事实、命令和路径，不要把未确认的信息写成确定结论；涉及对外文案时，还需要控制语气，避免过度营销或夸大能力。