mcpbeat

200 Agents Md

majiayu000/200-agents-md

Use when you need to generate an AGENTS.md file for a Java repository — covering project conventions, tech stack, file structure, commands, Git workflow, and contributor boundaries — through a modular, step-based interactive process that adapts to your specific project needs. This should trigger for requests such as Create AGENTS.md; Update AGENTS.md file; Add agent instructions. Part of cursor-rules-java project

974 tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
532
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/majiayu000/claude-skill-registry --skill 200-agents-md

What comes with it

779 bytes besides the instruction
metadata.json

The instruction itself

5 sections, as written by the author

AGENTS.md Generator for Java repositories

Generate a comprehensive AGENTS.md file for Java repositories through a modular, step-based interactive process that covers role definition, tech stack, file structure, commands, Git workflow, and contributor boundaries. This is an interactive SKILL.

What is covered in this Skill?

  • AGENTS.md generation for Java repositories of any complexity
  • Role and expertise definition for AI agents and contributors
  • Tech stack documentation: language, build tool, frameworks, pipelines
  • File structure mapping with read/write boundaries
  • Command catalogue for build/test/deploy/run workflows
  • Git workflow conventions: branching strategy, commit message format
  • Contributor boundaries using ✅ Always do / ⚠️ Ask first / 🚫 Never do formatting

Constraints

No Maven validation is required before generating AGENTS.md. Review the project structure and existing documentation before starting to provide accurate answers during Step 1.

  • BEFORE STARTING: Review the project structure and existing documentation to provide accurate answers during Step 1
  • BEFORE APPLYING: Read the reference for detailed good/bad examples, constraints, and safeguards for each AGENTS.md generation pattern
  • EDGE CASE: If the user goal is ambiguous, stop and ask a clarifying question before editing files or running project-wide commands
  • EDGE CASE: If required context, files, credentials, or tools are missing, report the blocker explicitly and ask whether to proceed with setup or fallback guidance
  • EDGE CASE: If requested changes conflict with project constraints or safety boundaries, explain the conflict and ask for user confirmation on the preferred trade-off

When to use this skill

  • Create AGENTS.md
  • Update AGENTS.md file
  • Add agent instructions

Workflow

  • Review repository context before drafting

Inspect project structure and existing documentation to prepare accurate responses for the AGENTS.md discovery phase.

  • Read AGENTS generation reference

Read references/200-agents-md.md and follow its generation patterns and safeguards.

  • Run interactive requirements capture

Gather role, tech stack, commands, workflow, and boundaries in a modular step-based conversation.

  • Generate AGENTS.md artifact

Create AGENTS.md with ✅ Always do / ⚠️ Ask first / 🚫 Never do boundaries and repository-specific conventions.

Reference

For detailed guidance, examples, and constraints, see references/200-agents-md.md.

How to use it

Copy the folder

Take majiayu000/200-agents-md from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.