Agent skill
inits
Analyze a codebase and create or improve an AGENTS.md file for future agent instances. Use when onboarding to a repository and capturing hard-to-rediscover conventions, constraints, and rationale.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/skills/other/init
SKILL.md
Init - AGENTS.md Generator
Analyze this codebase and create or improve an AGENTS.md file for future ODIN Code Agent instances.
Core principle
Only encode knowledge that is expensive to rediscover. An agent can fd, rg, ast-grep, and read files in seconds. If the information is one search away, omit it.
Objective guard
AGENTS.md is for priming and guiding future agents with conventions, constraints, and rationale. It is not a repository summary.
What to include
- Cross-cutting conventions and boundaries that span multiple files.
- Implicit contracts and operational constraints that are easy to miss in quick code exploration.
- Non-obvious command guidance only when hidden constraints matter (required ordering, flags, env vars, caveats).
- For each included item, state:
- the rule or constraint
- why it exists (rationale)
What to omit (the agent can discover these)
- File trees, per-directory descriptions, or component inventories.
- Dependency/version tables.
- Generic development best practices.
- Information that is easily discoverable via search/read.
- Fabricated filler sections such as "Common Development Tasks", "Tips", or "Support".
- Any summary-style prose that restates code organization without conventions or rationale.
Workflow
- If
AGENTS.mdalready exists, suggest targeted improvements instead of rewriting. - Do not repeat yourself. Each fact appears once.
- Every statement must be grounded in files you actually read. Never invent.
- If uncertain, omit the claim rather than speculate.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?