Skip to main content
ZICQ
中 Log in / Sign up

Skills ZICQ category：Agent Workflows agents-md

Agents Md

Use when the requested deliverable includes creating, reviewing, moving, splitting, or updating a repository AGENTS.md; produces scoped repo guidance. Do not trigger for standalone skills, prompts, non-AGENTS instruction files, READMEs, changelogs, or architecture docs.

1437 installs

Official URL：skills.sh

What this skill does

Intro in this page language first. The official description stays in its original wording; we do not rewrite SKILL.md.

What it does

Use when the requested deliverable includes creating, reviewing, moving, splitting, or updating a repository AGENTS.md; produces scoped repo guidance. Do not trigger for standalone skills, prompts, non-AGENTS instruction files, READMEs, changelogs, or architecture docs.

When to use it

- Create, update, review, split, move, or repair a repository `AGENTS.md`

How agents load it

Per Agent Skills progressive disclosure: name and description load at startup (~100 tokens); the full SKILL.md body loads when the skill activates; scripts/, references/, and assets/ load only as needed. This file's sections: Manage AGENTS.md; When to Use; When NOT to Use; Modes; Workflow; Rule Quality Rubric. It includes spec-recommended sections: step-by-step instructions.

File analysis

File analysis: besides SKILL.md, the body references references/topology-and-handoff-guidance.md, scripts/analyze_project.py, references/normal-authoring.md, references/template-selection.md, assets/agentsmd-minimal.md, scripts/validate_agentsmd.py. Those resources load on demand.

Manage AGENTS.mdWhen to UseWhen NOT to UseModesWorkflowRule Quality RubricEscalation MatrixFinal ResponseDeterministic ToolsReferences

Source category：skills.sh agent-skill

Sources & links

Market sources：skills.sh

Full package on GitHub

OSS Skill ranking

SKILL.md & Agent activation

Official spec ↗
name
agents-md
description
Use when the requested deliverable includes creating, reviewing, moving, splitting, or updating a repository AGENTS.md; produces scoped repo guidance. Do not trigger for standalone skills, prompts, non-AGENTS instruction files, READMEs, changelogs, or architecture docs.
  1. DiscoverThe client exposes names and descriptions to the agent.
  2. ActivateYour request or the task context selects the skill and loads its instructions.
  3. Load resourcesReferenced scripts, documentation and assets are used when needed.
Files referenced by the instructions · 8
  • references/topology-and-handoff-guidance.md
  • scripts/analyze_project.py
  • references/normal-authoring.md
  • references/template-selection.md
  • assets/agentsmd-minimal.md
  • scripts/validate_agentsmd.py
  • scripts/semantic_check_agentsmd.py
  • references/contract-bearing-agentsmd.md

These paths are extracted from the text. Check the upstream package to verify the files exist.

Invocation syntax and available tools depend on your Agent client. Client integration guide ↗

Install this skill

Skills CLI ↗

Choose the target agent and installation scope, keep referenced package files, then verify the skill appears in the client's catalog.

This skill references supporting files. Retrieve the complete directory from the source; copying SKILL.md alone may leave missing dependencies.

Ask your Agent to install

Copy these instructions to a compatible agent and confirm the target directory matches your client.

Install the agent skill "agents-md" into my project. The full SKILL.md and official description are at https://zicq.com/en/skills/skl-17f7283fea62c2e0-Agents-Md.html
Save it as .cursor/skills/agents-md/SKILL.md or .claude/skills/agents-md/SKILL.md and keep the frontmatter name and description exactly as-is.
This skill also ships scripts/, references/, or assets/ — fetch the whole folder from https://github.com/callicrate/skills instead of creating only a SKILL.md.

Full package on GitHub ↗

Install from the terminal · Skills CLI

Requires Node.js and npx. First inspect the repository's skill list to confirm the name.

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

npx skills add 'https://github.com/callicrate/skills' --skill 'agents-md'

The CLI lets you choose the agent interactively. The default scope is the project; use -g for user scope. Confirm package availability with the discovery command, then use npx skills list to inspect installed skills.

Readable layout
--- name: agents-md description: "Use when the requested deliverable includes creating, reviewing, moving, splitting, or updating a repository AGENTS.md; produces scoped repo guidance. Do not trigger for standalone skills, prompts, non-AGENTS instruction files, READMEs, changelogs, or architecture docs." metadata: short-description: Create or update AGENTS.md. --- # Manage AGENTS.md `AGENTS.md` gives coding agents scoped, current, repo-specific instructions. It is not a README, runbook, architecture doc, changelog, tutorial, or evidence log. Good guidance is evidence-backed, concise, scoped to the file's directory tree, and behavioral: it tells agents what to do differently in this repository. ## When to Use - Create, update, review, split, move, or repair a repository `AGENTS.md`. - Capture verified local commands, repo contracts, path ownership, or recurring agent mistakes. - Convert repo evidence into rules that future agents can follow. ## When NOT to Use - Standalone skills, prompts, global instructions, READMEs, architecture docs, changelogs, or runbooks. - Broad documentation rewrites where `AGENTS.md` is not an explicit deliverable. - Aspirational process guidance that is not supported by current repo evidence. ## Modes - **patch**: small text fix, typo, stale path, or narrow rule change. Inspect the affected section and evidence only. - **create**: no suitable `AGENTS.md` exists. Run the analyzer, sample source/config/docs, then draft the smallest useful file. - **update**: existing file needs new or corrected guidance. Preserve valid rules, remove stale or duplicated material, and add only evidenced changes. - **split/move**: scope boundaries are changing. Inspect existing root and nested files, then use [references/topology-and-handoff-guidance.md](references/topology-and-handoff-guidance.md). - **review**: do not edit unless asked. Return findings by severity with evidence and residual risk. - **exhaustive**: monorepos, contract-heavy repos, safety-sensitive guidance, operational handoffs, major topology changes, or unclear evidence. ## Workflow 1. Pick the mode and target scope. Read the nearest existing `AGENTS.md`, nested `AGENTS.md` files that may overlap, and `git status --short` when available. 2. For create, update, split/move, or exhaustive modes, run `python /scripts/analyze_project.py --repo-root --format json`. Treat it as a sampling guide, not authority. 3. For normal authoring details, use [references/normal-authoring.md](references/normal-authoring.md). Inspect only the sources needed for the claims you will make. 4. Draft from the smallest applicable template in [references/template-selection.md](references/template-selection.md). Prefer [assets/agentsmd-minimal.md](assets/agentsmd-minimal.md) unless the repo clearly needs a specialized template. 5. Keep evidence in working notes or the final summary. Add an evidence file only when the repo already owns one or the user asks. 6. Validate with `python /scripts/validate_agentsmd.py --repo-root --agents-file --mode ` and `python /scripts/semantic_check_agentsmd.py --repo-root --agents-file `. ## Rule Quality Rubric Keep a rule only when it is: - **specific**: names actual paths, commands, contracts, or local conventions. - **current**: supported by live files or user-provided current facts. - **scoped**: applies to this `AGENTS.md` directory tree. - **behavioral**: changes what an agent should do. - **evidence-backed**: traceable to inspected repo evidence. - **safe**: avoids secrets, unauthorized access, destructive commands, and production execution. - **non-duplicative**: does not restate global instructions, language basics, or README content. - **concise**: short enough to scan during normal coding work. ## Escalation Matrix Load extra references only when the task needs them: | Trigger | Read | |---------|------| | Tool, CLI, MCP, API, generated file, migration, schema, or public contract guidance | [references/contract-bearing-agentsmd.md](references/contract-bearing-agentsmd.md) | | Split, move, nested scopes, stale topology, or ownership handoff | [references/topology-and-handoff-guidance.md](references/topology-and-handoff-guidance.md) | | Live operations, degraded tools, manual dispatch, stop states, or environment resets | [references/degraded-tool-surface.md](references/degraded-tool-surface.md), [references/evidence-invalidation.md](references/evidence-invalidation.md) | | Subagents or delegated review workflows | [references/subagent-coordination-patterns.md](references/subagent-coordination-patterns.md) | | Python, TypeScript, other stack, Databricks/Spark, or ML-specific evidence prompts | [references/language-specific/python-guidance.md](references/language-specific/python-guidance.md), [references/language-specific/typescript-guidance.md](references/language-specific/typescript-guidance.md), [references/language-specific/other-stack-guidance.md](references/language-specific/other-stack-guidance.md), [references/domain-specific/databricks-spark.md](references/domain-specific/databricks-spark.md), [references/domain-specific/ml-projects.md](references/domain-specific/ml-projects.md) | | Review-only or judgment-heavy audit | [references/manual-audit.md](references/manual-audit.md) | ## Final Response For edit modes, include changed files, rules added/changed/removed, evidence sources sampled, validation commands and results, and residual risks. For review mode, lead with findings ordered by severity. Each finding needs the affected `AGENTS.md` section or line, supporting repo evidence, why it matters, and the recommended fix. Then list open questions, test/validation gaps, and a brief summary only after findings. ## Deterministic Tools | Tool | Use | |------|-----| | [scripts/analyze_project.py](scripts/analyze_project.py) | Stack, config, test, path, and suggestion inventory | | [scripts/validate_agentsmd.py](scripts/validate_agentsmd.py) | Structural validation | | [scripts/semantic_check_agentsmd.py](scripts/semantic_check_agentsmd.py) | Path, command, link, and example validation | | [scripts/check_agentsmd_templates.py](scripts/check_agentsmd_templates.py) | Skill template and guidance hygiene | | [scripts/run_agentsmd_fixture_checks.py](scripts/run_agentsmd_fixture_checks.py) | Known fixture behavior for validator changes | ## References - [references/tool-contracts.md](references/tool-contracts.md) and [references/template-selection.md](references/template-selection.md) - helper CLI contracts, modes, and templates - [assets/agentsmd-minimal.md](assets/agentsmd-minimal.md), [assets/agentsmd-contract-bearing.md](assets/agentsmd-contract-bearing.md), [assets/agentsmd-operational.md](assets/agentsmd-operational.md), [assets/agentsmd-full.md](assets/agentsmd-full.md) - starter templates - [assets/example-validated-agentsmd.md](assets/example-validated-agentsmd.md), [assets/example-contract-bearing-agentsmd.md](assets/example-contract-bearing-agentsmd.md), [assets/example-operational-agentsmd.md](assets/example-operational-agentsmd.md), [assets/writing-tips.md](assets/writing-tips.md) - compact examples

Related skills

Agent Workflows

Skill Creator

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that exte…

Agent Workflows

Clawdhub

Use the ClawdHub CLI to search, install, update, and publish agent skills from clawdhub.com. Use when you need to fetch new skills on the fl…

Agent Workflows

Agent Team Orchestration

Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows. Use when: (1) Setting up a team …

Agent Workflows

Superpowers

Spec-first, TDD, subagent-driven software development workflow. Use when: (1) building any new feature or app — triggers brainstorm → plan →…