10x-agents-md

Generate and update AGENTS.md onboarding documents for AI coding agents in a repository.

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/michaail/hybrid-logs-analyzer --skill 10x-agents-md-michaail
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 10x-agents-md
Source: https://github.com/michaail/hybrid-logs-analyzer/tree/main/.cursor/skills/10x-agents-md
Command: npx skills add https://github.com/michaail/hybrid-logs-analyzer --skill 10x-agents-md-michaail

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Repositories often lack a concise, agent-oriented onboarding document, so AI coding agents waste context rediscovering build commands, conventions, and hard rules on every session. This Skill inspects the repo and writes a tight, reference-heavy AGENTS.md that a fresh agent can read once and stay unblocked. ## Core Features & Use Cases - Create and update flows: Drafts a new AGENTS.md from repo discovery, or surgically updates an existing one by diffing repo state against the file's last-touched commit. - Repo-level and directory-level scope: Produces a root onboarding guide or a focused per-directory guide (e.g. src/api/AGENTS.md) based on where it is invoked. - Quality-gated output: Enforces a 200-400 word budget, checkable rules only, @-references instead of code snippets, and critical-rules-first ordering. - Use Case: After restructuring a monorepo's scripts and CI, run the update flow to refresh AGENTS.md so it reflects renamed scripts, new lint configs, and current commit conventions without rewriting hand-edited sections. ## Quick Start Ask the agent to create an AGENTS.md onboarding document for this repository, optionally passing a target directory or file path.

Frequently Asked Questions about 10x-agents-md

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an AGENTS.md file for my repository?

Invoke the skill with no arguments to write AGENTS.md at the repo root. It reads your README, package manifest, lint and test configs, CI workflows, and git history, then drafts a 200-400 word guide titled Repository Guidelines.

How do I update an existing AGENTS.md without losing manual edits?

The update path classifies each existing line as keep, update, remove, or missing by diffing repo state since the file's last-touched commit. It then applies targeted edits after you confirm, preserving hand-written content that is still accurate.

Can I generate AGENTS.md for a subdirectory instead of the repo root?

Yes, pass a directory path as the argument and the skill switches to directory-level scope. It inspects sibling files and local configs to document that directory's naming, layout, and testing conventions in a shorter 120-250 word guide.

What makes a good AGENTS.md for AI coding agents?

A good AGENTS.md is 200-400 words, leads with hard rules and the most-used commands, and cites canonical files via @-references instead of embedding code. Every rule must be checkable against a diff, with no generic advice or restated framework defaults.

When should I not use subagents for repo discovery?

Skip subagent fan-out when the repo has under roughly 20 top-level files, when the host harness lacks a subagent tool, or when the relevant files are already loaded in context. In those cases sequential reads in the main loop are cheaper.