init
Creates, updates, or optimizes an AGENTS.md file for a repository with minimal, high-signal instructions covering non-discoverable coding conventions, tooling quirks, workflow preferences, and project-specific rules that agents cannot infer from reading the codebase. Use when setting up agent instructions or Claude configuration for a new repository, when an existing AGENTS.md is too long, generic, or stale, when agents repeatedly make avoidable mistakes, or when repository workflows have changed and the agent configuration needs pruning. Applies a discoverability filter—omitting anything Claude can learn from README, code, config, or directory structure—and a quality gate to verify each line remains accurate and operationally significant.
What this skill does
## When to use Use this skill when creating or updating `AGENTS.md` for a repository. Use it especially when: - the current `AGENTS.md` is long, generic, or stale - agents repeatedly make the same avoidable mistakes - repository workflows changed and agent guidance needs pruning ## Instructions Treat `AGENTS.md` as a **living list of non-discoverable landmines and workflow gotchas**, not a codebase overview. ### Core rule: discoverability filter Before adding any line, ask: > Can an agent discover this by reading the repo (`README`, code, config, scripts, directory tree)? - If **yes**: do **not** include it in `AGENTS.md`. - If **no**, and it materially affects task success/cost/safety: include it. ### What earns a line Include only guidance that is: 1. **Non-discoverable** from repository files alone 2. **Operationally significant** (changes commands, outcomes, or safety) 3. **Actionable** (specific enough to execute) Typical examples: - Non-standard tooling choices (e.g. use `uv` instead of `pip`) - Command caveats (e.g. tests must run with `--no-cache` due to fixture behavior) - Hidden constraints/landmines (deprecated directories still imported in production) - Critical local conventions that are not encoded in lint/tests/config ### What to remove or avoid Do **not** include: - Tech stack summaries - Directory structure overviews - Architecture descriptions agents can infer from code - Generic best-practice advice - Rules already enforced by tooling (linters, typecheck, tests, CI) - Mandatory boilerplate headers unless the repo explicitly requires one ### Recommended structure Prefer short, high-signal sections such as: - `Scope & routing` (which areas need separate/module-local AGENTS files) - `Non-discoverable commands` - `Landmines / do-not-touch areas` - `Task-specific constraints` For large repos, recommend **hierarchical AGENTS.md** files near relevant modules instead of one monolithic root file. ### Source files to check first - Existing `AGENTS.md` - `README.md` - `PROJECT.md` (if present) - Cursor rules (`.cursor/rules/` or `.cursorrules`) - Copilot instructions (`.github/copilot-instructions.md`) - `GEMINI.md` - CI/workflow files and package manager config (for command/tooling mismatches) If `AGENTS.md` exists, improve it incrementally instead of replacing it blindly. ### Maintenance mindset `AGENTS.md` is temporary guidance, not permanent configuration. When recurring issues appear: 1. Prefer fixing the root cause in code/tooling (lint rule, test, script, structure) 2. Keep only the minimum instruction needed until the root cause is solved 3. Prune stale instructions aggressively ### Quality gate before finalizing For each line in `AGENTS.md`, verify: - Is it non-discoverable? - Is it still accurate today? - Does it materially reduce mistakes/cost/time? Delete any line that fails one of these checks.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.