文档代理

安全 社区

技能解读

当前原文的自动摘译,尚未人工审校。

所需输入

包含 AGENTS.md 用作事实来源的当前分支文件的存储库根如果缺少 AGENTS.md,请在存储库根中创建它,并仍然将范围限制为该文件。

审计检查

在更新AGENTS.md之前,请确定YYYY-MM-DD格式的当前本地日期并检查docs/audit/。如果任何审核文件名以今天的日期开头,请将其视为当前审核输入。如果没有审核文件名以今天的日期开头,则询问用户是否运行

工作流程

阅读当前的AGENTS.md。在docs/audit/中检查当日审核。在编辑之前检查当前存储库的真实情况:git status --short最近的提交,例如git log --oneline -n 10

内容规则

让文档以存储库可观察的事实为基础。当代码、配置和 CI 发生冲突时,优先选择代码、配置和 CI,而不是散文文档。保留当前的 ​​5 部分布局,除非用户明确要求不同的结构。保持文档最少;避免将其扩展为政策手册。

分段合同

遵循references/agents-md-template.md中的确切部分顺序:## 1. Purpose``## 2. Repository Overview``## 3. Agent Roles``## 4. Coding Standards

流狐档案 运行与权限由流狐静态检查推断,不代表作者声明或实际测试结果。
领域
安全
作者声明的智能体
未找到明确声明;不据此推断已兼容或已测试
静态检查
88 / 100 · 启发式扫描,不代表运行安全
运行环境证据
未执行;当前没有隔离运行测试证据
作者 / 版本 / 许可证
@tomevault-io · 未声明许可证
上下文用量评级
低消耗
接入复杂程度
即装即用
是否需要外部接口密钥
不需要
兼容的系统
未声明(默认跨平台)
运行环境要求
未检出明确要求
检测到的文件与系统行为
  • 只读
  • 允许写入 / 修改
网络行为
仅限本地
安装命令数
无(仅作为资料)

需要注意: 未声明工具权限范围;实际权限由运行环境决定。

作者说明文件(原文) SKILL.md

# Docs Agent MD

Use this skill to maintain the repository root `AGENTS.md` as a minimal,
repo-grounded document.

## Required Inputs

- Repository root containing `AGENTS.md`
- Current branch files used as source of truth

If `AGENTS.md` is missing, create it at the repository root and still keep the
scope limited to that file.

## Audit Check

Before updating `AGENTS.md`, determine the current local date in `YYYY-MM-DD`
format and inspect `docs/audit/`.

- If any audit filename starts with today's date, treat that as the current
  audit input.
- If no audit filename starts with today's date, ask the user whether to run
  `$docs-audit` before continuing.
- If the user wants the audit, use `$docs-audit` first and then continue with
  the refreshed report.

Accept both date-only and timestamped report names, for example:

- `docs/audit/2026-03-24.md`
- `docs/audit/2026-03-24_09:15:00.md`

## Workflow

1. Read the current `AGENTS.md`.
2. Check for a same-day audit in `docs/audit/`.
3. Inspect current repository truth before editing:
   - `git status --short`
   - recent commits such as `git log --oneline -n 10`
   - runtime and config files referenced by `AGENTS.md`
   - CI and policy files referenced by `AGENTS.md`
4. Use `references/agents-md-template.md` as the required output structure.
5. Update only `AGENTS.md`.
6. Re-read the final file for structure, wording, and claim accuracy.

## Content Rules

- Keep the document grounded in repository-observable facts.
- Prefer code, config, and CI over prose docs when they conflict.
- Preserve the current 5-section layout unless the user explicitly asks for a
  different structure.
- Keep the document minimal; avoid expanding it into a policy manual.
- State when a rule is observed guidance rather than hard enforcement.
- Do not invent ownership, deployment guarantees, or runtime behavior.

## Section Contract

Follow the exact section order in `references/agents-md-template.md`:

1. `## 1. Purpose`
2. `## 2. Repository Overview`
3. `## 3. Agent Roles`
4. `## 4. Coding Standards`
5. `## 5. Safety & Constraints`

## Boundaries

Allowed work:

- Read docs, audits, code, config, CI, and git metadata needed to verify
  `AGENTS.md`
- Update `AGENTS.md`

Default write scope:

- `AGENTS.md` only

Do not do this by default:

- Rewrite broader repository docs
- Edit `.github/workflows/*`, policy files, or API contract artifacts as part of
  an `AGENTS.md` refresh
- Expand the task into a full docs audit when the user only asked for
  `AGENTS.md`

## Redirects

- Use `$docs-audit` for full documentation accuracy audits and dated audit
  reports in `docs/audit/`.
- Use `$docs-feature` for `docs/features/*` authoring and index reconciliation.
- Use other repository docs skills when the target is not the root `AGENTS.md`.

## Bundled Resources

- `references/agents-md-template.md`: Required output template and section
  intent for the root `AGENTS.md`.

---
> Source: [CMSgov/emmy-api](https://github.com/CMSgov/emmy-api) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-05-23 -->

讨论

基于 GitHub Discussions。登录 GitHub 即可参与讨论、点赞、订阅更新。