Agent skill · Security

agent-init

Initialize or improve AGENTS.md files that define how coding agents operate in a repo. Use when asked to set up or replace an agent init command (Codex, Claude), standardize multi-agent behavior, or audit an existing AGENTS.md for clarity, commands, boundaries, and repo-specific context. For Claude Code, also create CLAUDE.md as a symlink to AGENTS.md.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill agent-init --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 6 KB
Bundled scripts: none
Path: skills/agent/agent-init/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# AGENTS.md Guide ## Overview Provide a repeatable workflow and quality bar for writing or updating AGENTS.md files so agents receive concrete, repo-specific instructions. ## Trigger examples - "Create an AGENTS.md for this repo and include exact test commands." - "Replace our agent init command with a proper AGENTS.md file." - "Audit our existing AGENTS.md for missing boundaries and commands." - "Update AGENTS.md to reflect the current build and lint commands." - "Create CLAUDE.md as a symlink to AGENTS.md for Claude Code." ## Core Principles (condensed) - Be concrete: prefer executable commands and code examples over prose. - Put commands early and include flags/options. - Use real code examples over explanations. - Remove ambiguity: state boundaries and non-goals explicitly. - Be specific about the tech stack; include versions and key dependencies. - Define the agent's role/persona and how it fits the team. - Cover the six core areas: purpose, code organization, run/test/validate, change management, dependencies/environment, and avoid list. - Use three-tier boundaries: Always / Ask first / Never. - Start small and iterate as the repo evolves. ## Brainstorming Mode (divergent Q&A

What's inside
Steps it walks through
  1. Overview
  2. Trigger examples
  3. Core Principles (condensed)
  4. Brainstorming Mode (divergent Q&A)
  5. Workflow
  6. 1) Clarify scope and placement
  7. 2) Gather repo-specific facts
  8. 2a) Shape the doc by repo structure
  9. 3) Draft with the six core areas
  10. 4) Add concrete commands and examples
  11. 5) Add boundaries and safety
  12. 6) Review for clarity
  13. Output Requirements
  14. Cross-agent compatibility
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the agent-init skill do?

Initialize or improve AGENTS.md files that define how coding agents operate in a repo. Use when asked to set up or replace an agent init command (Codex, Claude), standardize multi-agent behavior, or audit an existing AGENTS.md for clarity, commands, boundaries, and repo-specific context. For Claude Code, also create CLAUDE.md as a symlink to AGENTS.md.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill agent-init --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going