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/OutlineDriven/odin-claude-plugin/tree/main/skills/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.
refactor-break-bw-compat
Refactor by removing backward compatibility and legacy layers. Use when modernizing APIs, cleaning up migration debt, removing compat shims, or eliminating stale feature flags.
pr-merge-temporal
Merge multiple PRs into a temporal integration branch before merging to base, with ordered conflict resolution. Use when you want to validate a set of PRs together on a staging branch before advancing the base branch.
tests-adversarial
Write adversarial tests that intentionally stress failure paths. Use when hardening error handling, stress-testing assumptions, validating boundary behavior, or hunting silent failures.
srgn-cli
Practical guide for building safe, syntax-aware srgn CLI commands for source-code search and transformation. Use when users ask for srgn commands, scoped refactors (comments/docstrings/imports/functions), multi-file rewrites with --glob, custom tree-sitter query usage, or CI-style checks with --fail-any/--fail-none.
askme
Verbalized Sampling (VS) protocol for deep intent exploration before planning. Use when starting ambiguous or complex tasks, when multiple interpretations exist, or when you need to explore diverse intent hypotheses and ask maximum clarifying questions before committing to an approach.
pr-merge-base
Merge one or more PRs into the base branch with queue-like sequencing and conflict resolution. Use when merging PRs that may conflict with each other or the base, requiring ordered application and intelligent conflict handling.
Didn't find tool you were looking for?