agents-md
This skill should be used when the user asks to "create AGENTS.md", "update AGENTS.md", "maintain agent docs", "set up CLAUDE.md", or needs to keep agent instructions concise. Enforces research-backed best practices for minimal, high-signal agent documentation.
What this skill does
# Maintaining AGENTS.md AGENTS.md is the canonical agent-facing documentation. Keep it minimal—agents are capable and don't need hand-holding. Target under 60 lines; never exceed 100. Instruction-following quality degrades as document length increases. ## File Setup 1. Create `AGENTS.md` at project root 2. Create symlink: `ln -s AGENTS.md CLAUDE.md` ## Before Writing Analyze the project to understand what belongs in the file: 1. **Package manager** — Check for lock files (`pnpm-lock.yaml`, `yarn.lock`, `package-lock.json`, `uv.lock`, `poetry.lock`) 2. **Linter/formatter configs** — Look for `.eslintrc`, `biome.json`, `ruff.toml`, `.prettierrc`, etc. (don't duplicate these in AGENTS.md) 3. **CI/build commands** — Check `Makefile`, `package.json` scripts, CI configs for canonical commands 4. **Monorepo indicators** — Check for `pnpm-workspace.yaml`, `nx.json`, Cargo workspace, or subdirectory `package.json` files 5. **Existing conventions** — Check for existing CONTRIBUTING.md, docs/, or README patterns ## Writing Rules - **Headers + bullets** — No paragraphs - **Code blocks** — For commands and templates - **Reference, don't embed** — Point to existing docs: "See `CONTRIBUTING.md` for setup" or "Follow patterns in `src/api/routes/`" - **No filler** — No intros, conclusions, or pleasantries - **Trust capabilities** — Omit obvious context - **Prefer file-scoped commands** — Per-file test/lint/typecheck commands over project-wide builds - **Don't duplicate linters** — Code style lives in linter configs, not AGENTS.md ## Required Sections ### Package Manager Which tool and key commands only: ```markdown ## Package Manager Use **pnpm**: `pnpm install`, `pnpm dev`, `pnpm test` ``` ### File-Scoped Commands Per-file commands are faster and cheaper than full project builds. Always include when available: ```markdown ## File-Scoped Commands | Task | Command | |------|---------| | Typecheck | `pnpm tsc --noEmit path/to/file.ts` | | Lint | `pnpm eslint path/to/file.ts` | | Test | `pnpm jest path/to/file.test.ts` | ``` ### Commit Attribution Always include this section. Agents should use their own identity: ```markdown ## Commit Attribution AI commits MUST include: ``` Co-Authored-By: (the agent's name and attribution byline) ``` Example: `Co-Authored-By: Claude Sonnet 4 <[email protected]>` ``` ### Key Conventions Project-specific patterns agents must follow. Keep brief. ## Optional Sections Add only if truly needed: - API route patterns (show template, not explanation) - CLI commands (table format) - File naming conventions - Project structure hints (point to critical files, flag legacy code to avoid) - Monorepo overrides (subdirectory `AGENTS.md` files override root) ## Anti-Patterns Omit these: - "Welcome to..." or "This document explains..." - "You should..." or "Remember to..." - Linter/formatter rules already in config files (`.eslintrc`, `biome.json`, `ruff.toml`) - Listing installed skills or plugins (agents discover these automatically) - Full project-wide build commands when file-scoped alternatives exist - Obvious instructions ("run tests", "write clean code") - Explanations of why (just say what) - Long prose paragraphs ## Example Structure ```markdown # Agent Instructions ## Package Manager Use **pnpm**: `pnpm install`, `pnpm dev` ## Commit Attribution AI commits MUST include: ``` Co-Authored-By: (the agent's name and attribution byline) ``` ## File-Scoped Commands | Task | Command | |------|---------| | Typecheck | `pnpm tsc --noEmit path/to/file.ts` | | Lint | `pnpm eslint path/to/file.ts` | | Test | `pnpm jest path/to/file.test.ts` | ## API Routes [Template code block] ## CLI | Command | Description | |---------|-------------| | `pnpm cli sync` | Sync data | ```
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.