docs-agent-md

Security Community

Repo stars 0
Author repo skills-registry

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Create, refresh, or reconcile the repository root AGENTS.md using current branch truth. Use when Codex needs to update `AGENTS…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Required Inputs”, “Audit Check”, “Workflow”, “Content Rules”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name docs-agent-md directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Required Inputs / Audit Check / Workflow” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

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

Read the current AGENTS.md.
Check for a same-day audit in docs/audit/.
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
Use references/agents-md-template.md as the required output structure.
Update only AGENTS.md.
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. Purpose
## 2. Repository Overview
## 3. Agent Roles
## 4. Coding Standards
## 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 — distributed by TomeVault.

Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates

Fluxly category: Security
Author-declared agents: No explicit declaration found; this is not inferred or tested compatibility
Static check: 88 / 100 · heuristic scan, not runtime safety proof
Author / version / license: @tomevault-io · no license declared
Fluxly token estimate: Lean
Fluxly setup estimate: Plug-and-play
External API key: No requirement detected
Detected OS requirements: Unspecified
Runtime requirements: Unspecified
Detected file/system behavior: Read-only
Write / modify
Detected network behavior: Local-only
Install commands: None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview docs-agent-md.preview

The current SKILL.md does not define a fixed output example.

SKILL.md 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.

…

Evidence boundary and execution chain

Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.

sections -> Required Inputs → Audit Check → Workflow → Content Rules → Section Contract → Boundaries
terms    -> Use this skill to maintain the repository root AGENTS.md as a minimal, repo-grounded document. · If AGENTS.md is missing, create it at the repository root and still keep the scope limited to that file. · 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. · 1. Read the current AGENTS.md. · - Keep the document grounded in repository-observable facts. · 1. 1. · - Use $docs-audit for full documentation accuracy audits and dated audit reports in docs/audit/.
files/cmd -> AGENTS.md · YYYY-MM-DD · docs/audit/ · $docs-audit · docs/audit/2026-03-24.md · docs/audit/2026-03-2409:15:00.md · git status --short · git log --oneline -n 10
body sha256 -> 49c6817550e1